on 11-28-2005 6:52 PM
Hi All,
I have two roles that have differents contents and each content are into a folder that I did Merge (id). The point is I want to set the property Invisible Navigation in this folders.
Is there any way to do this?
Because I tried to set these properties in my two roles, but only one content can be visualized.
Is this a bug?
Role A (first tln)
- Folder K (second tln - Invisible Level)
- iview A (detailed navigation)
Role B
- Folder K
- iview B
Regards.
Hi Flavio,
I'm quite unsure what you have in mind. Please explain your UseCase!
If Roles A&B are getting merged, including Folder K with the same merge ID, and Folder K is set to be invisible, how do you want to navigate to the iViews?
Why do you want to set the folder to invisible?
Questions over questions...
Best regards
Detlev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Detlev,
My UseCase is:
I have a public role, and a restrict role, and I need to hide the second TLN level, and open directly the detailed Navigation.
E.G.:
Role A: The first level of role calls 'Applications', the second calls 'App1'(invisible) and the third level load a set of iviews.
Role B: The first level of role calls 'Applications', the second calls 'App1'(invisible) and the third level load another set of iviews.
I call the second tln(App1) role/iview from another iview through Navigation_Target. I want to do merge between the two invisible folders(second tln). But when I tried to set these properties in these two folders only one third level navigation is opened.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Flavio,
the case you describe is not the aim of this setting (as far as I understand your explanation). If you navigate to App1 and expect iV1, iV2, ... iVn within DetNav - what do you expect as selected second level navigation? Nothing selected at all?
The setting is thought for hiding <i>leaves</i> in the nav tree so that the elements are not visible in the nav but are accessible. But not to create "holes" in the nav structure.
See http://help.sap.com/saphelp_nw04/helpdata/en/ec/ae6ed43b204759a1dcdd788eb2a8dc/frameset.htm for a UseCase for which this setting is thought for.
Hope it helps nevertheless
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.