on 01-24-2007 6:51 PM
Hi,
If anyone knows this problem please help (description following). I'm using EP 6 SP17.
I have the full navigation already set up for our employees and it goes like this:
( -- Description of what I have follows -- )
First level: ESS
Second level: Group1 | Group2 | Group3
Navigation is setup in such a way that there is no Detailed navigation, meaning that from Role there's only 2 levels, like below:
ESS (role)
ESS (workset / entry point)
Group1 (page w/ iview referring area Z_AREA1 -> resource Z_AREA1_PAG)
Page1 (page w/ iview, invisible on navigation, for service Z_SRV1 -> resource Z_SRV1_RES)
The resources' definition are:
Z_AREA1_PAG:
Description: Page of group1
URL of PCD Page: url of Group1 from role (example: "ROLES://portal_content/client/roles/roleESS/wsESS/pgGroup1")
Z_SRV1_RES:
Description: Component of Page1
Directory Path: sap.com/essptaddr
Object Name: Per_Address_PT
URL of PCD Page: url of Page1 from role (example: "ROLES://portal_content/client/roles/roleESS/wsESS/pgPage1")
NOTE: The above configuration is done under the transaction SPRO in R/3.
( -- Existing problem -- )
I can navigate to the Area and from the Area to the Service, but when I click on "exit" (in the service) it does not go back to the Area, instead it has the same behavior as if the destination page doesn't have enough permissions to be displayed (I've checked that already).
When I go to the NWA page to read logs, I get the following Warning, everytime I click on "exit":
[PortalNode.fireEventOnNode.toEventListener] event=onNodeReadyEvent, target=com.sap.portal.detailedNavigationTree, operation failed
[EXCEPTION]
java.lang.NullPointerException
at com.sapportals.portal.navigation.DetailedNavigationTree.isCollaborationNode(DetailedNavigationTree.java:453)
( -- end of problem -- )
If anyone can help, points WILL be awarded upon solution.
Thanks in advance and my best regards,
Paulo R. Rosa
From what I am looking at, you seem to have Area page defined but no Area Group page (like an "Overview"). For most XSS services, at the end of the guided procedure, you will have a few "exit" choices...one taking you back to the Area Group page and one taking you back to the Area page. It looks like you are hitting an "exit" that attempts to go back to the Area Group but has no where to go. Your structure should look something like (and no, I don't like nesting Worksets, but in this case, here goes)...
Role +
-Workset (let's say ESS and entry point)
-Workset(Overview)
+page/iView for Area Group webdynpro (ex. ESS Overview)
-Workset(Group1)
+page/iView for Area webdynpro(ex. Group1)
+page/iView (service 1 in Group1)
+ ....
+page/iView (service X in Group1)
-Workset(Group2)
+page/iView for Area webdynpro(ex. Group2)
+page/iView (service 1 in Group2)
+ ....
+page/iView (service X in Group2)
-etc
so in the TLN of the portal you will see....
ESS=================================
+Overview + Group 1 + Group 2 =============
====================================
Where "Overview" is the landing page for the Area Group and
Group 1 and Group 2 are Area landing pages.
Make sense?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Paulo....trust me, I completely understand when it comes to clients and their wishes. 😃 I will check back to read up on what you did/do to resolve this!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, we are avoiding the overview because the client asked it so :). I'm going to check up on your sugestions. I'll be back asap :).
Thanks.
Paulo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Paulo.....thanks....and just as I thought. Keep in mind, the Homepage Framework is just that...a FRAMEWORK...and that frame is based heavily on the
ONE area group contains MANY areas concept.
If you do not want the overview (ie. Area Group) page, I would suggest a much different approach. Your first possible choice will be to "spoof" your WebDynpro services into thinking/linking your "exit" back to the Area page instead of the Area Group (you will need to look at how the links are made...I think it is via the App Integrator). Other than that, you would have to look at just customizing each service to hide/disable that link.
Not sure why you don't want the overview page...it actually is a nice summary of services that really helps for the non-technical users (which a lot of employees generally are).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Christopher ,
I thank you for your quick reply and it makes sense, but we don't want the overview to appear, and I do have it defined and correctly linked under SPRO.
I'm awarding you 2 points because you understood the problem, yet it is not the solution I need.
Again, thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.