You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood: Oracle Cloud SCM and Purchasing

RSSP Application Naming Behavior and Sandbox Impact Verification

in Purchasing

Summary:

We initially enabled the opt-in feature "Procure Goods and Services Using the Responsive Self Service Procurement Application" to make both RSSP and Classic SSP available for user testing. As shown in the attached screenshot, the applications appeared as "Procurement Requisitions" and "Procurement Requisitions (New)"

Subsequently, we disabled the feature mentioned above and enabled "Enable the Responsive Version as the Default Self Service Procurement Application" While this made the Responsive version the default, the application name remained "Procurement Requisitions (New)" We then used a Sandbox in our environment to manually rename it to "Procurement Requisitions"

Questions:

When we enable the "Enable the Responsive Version as the Default Self Service Procurement Application" feature, should the app name update automatically to "Procurement Requisitions" or is the manual Sandbox change required?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!