cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Homepage, Hyperlink, And Not Wanting to Show Portal Header

former_member552974
Participant
0 Kudos

Hello Everyone,

We are in the process of developing Employee Self Service and we are wanting to create a custom home page and not use the overview pages that come standard with ESS. We are still using standard ESS components, it's just that the home page of ESS will be a custom HTML page.

This custom HTML page will has been loaded into Knowledge Management.

With this being said, we want to provide links to the various ESS components/iviews from the custom home page. The problem we are encountering is that when a link from the home page is clicked, the Portal Header and Top Level Navigation is appearing in the Portal Content area along with the ESS service.

Does anyone know how to prevent the Portal Header and Top Level navigation from showing in the content area when an ESS service link is selected from a custom home page? We only want the ESS service itself to appear in the content area.

Thanks,

Scott

Accepted Solutions (0)

Answers (3)

Answers (3)

ChrisSolomon
Active Contributor
0 Kudos

I think you are making this much harder than it needs to be. As folks above said, it definately requires you using role navigation (this is what "jumps" you to a spot within a role).

If you want to launch from your homepage to a specific service/iView....define the URL with the PCD path THROUGH the role to that iView. That will "jump" the user to that specific service in the role (ie. maintaining all other role navigation correctly)

If you want to launch from your homepage to a secondary section (like jumping from Area Group to an Area page)....this is very similar. Your workset should have some kind of "start" page in it. As before, used the PCD path through the role to that Page. That will then jump the user to that location in their role and bring up the content as if they had clicked on that navigation directly.

Hope this helps.

former_member552974
Participant
0 Kudos

Hi Chris,

Thank you for the response. I really hope that I am over complicating this.

If you do not mind, will you elaborate on what you mean by the statement "Your workset should have some kind of "start" page in it?"

I will say that I am referencing the Role in the NavigationTarget value of the URL. This is achieved by going to the role itself and retrieving the PCD location of the page in which I need the link for. For example, pasted below is an example what I have retrieved. I think we are talking about doing the same thing (I may be wrong). It's just that my problem is that the Portal Header and Top Level Navigation appear when clicking the link below from my custom page.

http://<PORTAL SERVER>/irj/portal?NavigationTarget=ROLES://portal_content/<PATH TO PAGE IN ROLE>

Scott

ChrisSolomon
Active Contributor
0 Kudos

That's exactly how I do it Scott. I just tested it and was able to navigate whereever I wanted from the URL/Address bar. Now....possibly one thing to consider is to "force" you links to target "top". See if that clears up the duplicate headers.

Former Member
0 Kudos

This is good info, thanks for making this thread. I have a question too though. What do you do if you put the server name and then transport to different systems? Can you dynamically set the server address?

Former Member
0 Kudos

hi

how are you calling the service url in the custom html page.

I understand that you are not using any services from homepage framework.

You have developed your custom htm page.

Please confirm how are the urls being called to execute services.

regards

barin

former_member552974
Participant
0 Kudos

Hello Everyone,

Just to clarify. I am calling a variety of standard ESS iviews. One example is the Paycheck Inquiry Service.

I have tried a using the role name in the hyperlink which is on the custom page. This is where you specify "...NavigationTarget=Roles://...." in the hyperlink. I have also tried referencing the URL that is refrenced in the Framework Page (Yes, I did already set this up even though we are not using it) this too also references "NavigationTarget=Roles", but the link has additional info.

Both of these scenarios yielded the service with the header/navigation in the content area when the link is clicked from the custom homepage. I of course do not wish to see the header/navigation area of the service in the content area.

Any suggestions?

Thanks again for your help.

Scott

Former Member
0 Kudos

while using navigate_target make sure you provide pcd of iview and note of role.

this may help.

former_member552974
Participant
0 Kudos

Hi Barin,

Thanks for the response. I actually want the user to be directed to the proper place in the role. For example, if someone clicks on the Paycheck service from the custom home page, then I would like the user to be directed to the payroll workset/framework in the role which has all of the relevant payroll topics (in the detail navigation) but showing the Paycheck service in the content area. I would like for this to work just as the standard ESS framework home page. Thus I belief that this requires me to enter the Role name in the URL.

I would also like to mention that I have tried adding NavMode=3 as a URL parameter and this does in fact remove the portal header. But now my problem is that the contents of the detail navigation are gone and the history information on the page is appearing along with the history information from the iview (this is found in the upper right of the page)....seems strange I know, but there are actually two history items now.

Thus another question I have is...The URL Parameter NavMode=3 could possibly work. Does anyone know how to get the detail navigation to appear and to suppress the history information? Are there other URL Parameters that could be utilized to do this?

Thanks,

Scott

Former Member
0 Kudos

Hello Scot

What link of ESS components/iviews you have provided on your custom homepage?

Rajendra