Wednesday, May 08, 2019

Launching into the middle of a Fluid Navigation Collection

One of the greatest challenges to a successful Fluid deployment is Classic navigation and one of the most common solutions to this challenge is the Tile Wizard-based Navigation Collection. Tile Wizard-based navigation collections allow us to build business process-based navigation for our back-office users (back-office pages are primarily Classic). Let's say you have built some amazing Navigation Collections for your back-office users and now you want to drill from one collection or page to a specific target page in another Navigation Collection. You know you can easily craft a URL to a Tile Wizard Navigation Collection, but can you load a specific target component from that Navigation Collection? This is a great question that my PeopleTools Fluid course students ask me often. The answer is Yes!

When using the Tile Wizard to publish a Navigation Collection, PeopleTools uses a special Activity Guide template to display the Navigation Collection. This means that every Tile Wizard-based Navigation Collection is viewed as an Activity Guide. Each link is considered a step in the Activity Guide. Fluid Activity Guide steps have an id attribute called ptgpid. Once we find the ptgpid of a step, we can use that ID in a URL. When the Activity Guide is a Navigation Collection, the step ID is the Navigation Collection CREF Link ID. Note: this is not the base CREF ID, but the CREF link that was created by the Navigation Collection utility. If we inspect the HTML for a Navigation Collection, we can find the ptgpid in the HTML. Alternatively, we can find it in the portal registry under Portal Objects > Navigation Collections. Here is an example from the HTML:

To launch the highlighted item, copy the ptgpid and add the following to the end of the URL:

&ptgpid=<the id goes here>

For example, in the Portal Navigation Collection that is part of the PeopleSoft Developer homepage, appending the following to the URL will navigate directly to the Find Object Navigation item:


At jsmpros we believe that navigation is a critical component of a successful Fluid implementation, which is why we devote the first day of our Fluid 1 course to Fluid navigation. To learn more or to schedule a course, visit us online at


Sasank Vemana said...

Thanks Jim! This is very handy especially when we are programmatically transferring users to specific pages within a Nav Collection. I am sure,there are many other use cases for this parameter!

In fact, I presented this tip during my 'Life Hacks' session at Collaborate this year!

Jim Marion said...

@Sasank, I wish I had seen your presentation. That would have saved me hours of digging through PeopleCode! Unfortunately, as you know, we were scheduled to present at the same time.

As I dug through the code, it looked as though this should work with other Activity Guides, but that hasn't been my experience. As far as I can tell, other Fluid Activity Guides seem to remember the last page visited and load it instead of the ptgpid. Have you seen anything different?

Manoj said...

This is useful, although i would prefer a much more robust parameter (like the Portal Object Name for instance, along with the Nav Collection) than this ptgpid.

If we modify Nav collections (I believe, removing a Content Reference and adding it back changes the ptgpid), there might be a problem with this hack.

Sasank Vemana said...

Jim - Sorry for the late response. I missed the notification to your comment.

Yes, it was very unfortunate that we were scheduled at the same time. :(

Thankfully for me, I did not dig into all the PeopleCode. I randomly found this thread when I was looking for something else:

I had the same experience with Fluid Activity Guides where it does not work. I will post back to this thread if I find out more on this topic.

Jim Marion said...

@Manoj, I haven't tested a change like that, but I agree, it would be nice to have the CREFID or something more consistent. I believe the behavior we are seeing is common to all Activity Guides. Navigation Collections just happen to be an implementation of a Fluid Activity Guide.

Manoj said...

@Jim - About Fluid Activity Guide remembering the page. It must be the classic implementation of remembering 'Current Item'.
PS: I enhanced Activity guide for 8.55 when i was with Oracle.
I also found an issue with the Fluid Activity guide, the devs team seems to have forgotten to implement the equivalent of "Pagelet Preprocessing". I understand, there is no Pagelets in fluid, but they should have done something equivalent.

Manoj said...

@Jim - "About Fluid Activity guides remembering the last page visited"
It must be the fluid implementation of "Current Active Item"

Manoj said...

@Jim: "Navigation Collections just happen to be an implementation of a Fluid Activity Guide"

Nav Coll, Fluid Activity guides are implementations of Master Detail page? :)

Jim Marion said...

That is correct. A navigation collection is an activity guide data type.

Margaret said...

I wanted to stop back in and say thank you for this post! I was working on an issue with our custom Fluid BioDemo Activity Guide. When the users reached one component of the Activity Guide to add an emergency contact, the footer page would not display in SFF after the user added an emergency contact, and the footer page was the only way for the user to confirm the change and move forward. I was able to link directly back into the emergency contact Nav Coll item using the ptgpid and some wrangling of the URL to insert the CONTEXTIDPARAMS . Thanks again!

Jim Marion said...

@Margaret, perfect! Thank you for letting us know how you applied this idea. Very cool!

David Thomson said...

Hi Jim

We found this blog very useful but it the ptgpid seems to have issues working in small form factor devices. Is there something we can do to correct this?



Jim Marion said...

@David, I haven't tried small form factor. That surprises me. I'll test it out and let you know.

Margaret said...

@David, I had to make some customizations recently because of how the pages work differently in with SFF. I'd be curious what pages/issues you are seeing.