E:AWE/FLUID: How to Implement Workflow Approvals if Users Want to Access Specific Transactions in Fluid While Other Worklists Open in Classic Mode (Doc ID 2584520.1)

Last updated on MARCH 14, 2024

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.57 and later
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Goal

The site is not ready to fully embrace Fluid Approvals just yet for all their modules that is being used. At this time, it was decided to implement Fluid Approvals only for Requisitions while retaining other transactions in Classic, for example, Vouchers, GL/Journal, Budget Checking, etc.

The requirement is that when users access their worklists, certain transactions should open in Classic while only Requisitions opens in Fluid Approvals page. How to accomplish this?

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

E:AWE/FLUID: How to Implement Workflow Approvals if Users Want to Access Specific Transactions in Fluid While Other Worklists Open in Classic Mode (Doc ID 2584520.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!