Presented at BLUEPRINT 4D 2024
Session ID: P-033710

Oracle has slowly transitioned most of their user-facing transactions to fluid objects/pages as fluid objects are designed to render more consistently across devices. Additionally: Northwestern has transitioned all other user-facing transactions to Fluid Pages. In 2022: a Fluid Requisition Discovery project was done to identify configurations/customizations that would be necessary to support the purchasing business process at Northwestern. Discovery included development to bring over configs and customizations currently in place in the Classic pages: functional analysis as well as User Acceptance Testing.In January of 2023: Northwestern went live with Fluid Requisitions but kept Classic Requisitions available to ease the transition for users as well as work out any additional bugs not found during the discovery and implementation phases. Configurations/customizations that had to be developed in Fluid Requisitions included but weren’t limited to: Making Supplier required: Disabling Unused Menu Items: Custom Field Labels and Look-ups: Integration with Third Party Marketplace: Removed Ability for Users to Editing Supplier/Item Info on Catalog Requisitions.During the transition phase while both Classic and Fluid Requisitions are still available: the most substantial issue discovered in Fluid Reqs was that users were not able to resubmit a Denied Requisition. With Classic Requisitions: we had a workaround to edit price or quantity which would retrigger workflow. This workaround did not work in Fluid Requisitions for multi-line requisitions. Oracle provided a workaround for Fluid which included adding/editing the Justification Comments which then re-triggered workflow. To help make this apparent to users: we implemented a customization which requires Justification Comments for all denied fluid requisitions.Now that we believe that we’ve worked out any roadblocks for users: we plan to discontinue Classic Requisitions as the end of this calendar year.