PeopleSoft Conditional Navigation

With the introduction of PeopleSoft Fluid User Interface in PeopleTools, PeopleTools offers the capability to render a page either in classic mode or fluid mode based on conditions and factors. Additionally, you can direct a user to a different content reference, instead of the default content reference, based on conditions and factors.

Here is an example and also an issue you will run into while implementing Fluid Approvals:

After setting up Fluid Approvals, you can notify the user using Emails or through worklist to approve items. 

So issue occurs when you already have a classic page and new fluid page is delivered for the same approval area. Let's say Voucher Approval had a classic page in past but with new application version, you have fluid voucher approval page. 

Assuming you started using fluid approval page for voucher approvals, the user is sent email to approve the voucher, when user clicks on email link user is directed to classic page instead of fluid page even though user is having proper security to access fluid approval page.

This is because conditional navigation is not setup on content references of both voucher classic and fluid pages.

To setup conditional navigation, navigate to cref in question for both classic and fluid approval voucher pages and add following attribute values

For classic page:

Name: CN_DISPLAYMODE_1

Attribute Value: FLUID=CREFNAME of Fluid Page where you want to route

For fluid page:

Name: CN_DISPLAYMODE_1

Attribute Value: CLASSIC=CREFNAME of Classic Page where you want to route

Uncheck translate checkbox and save the page, this should take care of Email URL's and CREF's from portal navigation.

Note: Setup needs to be done vice-versa (Classic and Fluid) and make sure URL link that is generated points to the same node as the CREF