Customization Strategy for (Fluid) Requisitions
PeopleSoft provides many great tools for "supported" customizations: Page and Field Configurator, Event Mapping, and Drop Zones
These work perfectly in nearly all Fluid and Classic pages, and don't make the resulting component "unstable"
We get MANY customization requests for Create/Edit Requisition.
HOWEVER the fluid Create/Edit Requisition component seems to be structured in a way that thwarts the above customization approaches
- Data is stored in the component buffer (sort of, depending on the section being worked on, mostly work records); a cart object; a synchronized CI to the classic requisition component. If you want to change data you somehow have to interact with all 3 correctly, and potentially change all 4 (e.g., updating the CI and classic component). As a result it's very easy to create a customization that makes it unstable.