The correct sequence of PeopleCode events in Save processing is -
-
SaveEdit, SavePreChange, SavePostChange, WorkFlow
-
Save PreChange, SaveEdit, SavePostChange, WorkFlow
-
SaveEdit, SavePreChange, WorkFlow, SavePostChange
-
WorkFlow, Save PreChange, SaveEdit, SavePostChange
The correct sequence of PeopleCode events during Save processing is: SaveEdit (validation first), SavePreChange (pre-processing), Workflow (workflow processing), and finally SavePostChange (post-processing after commit). This order ensures validation happens before changes, workflow runs before database commit, and post-change code runs after successful save.
In PeopleSoft PeopleCode, the Save processing sequence runs in this fixed order: SaveEdit fires first to validate field-level edits before anything is written; then SavePreChange fires right before the row is written to the database, giving a last chance to modify data; then the system evaluates WorkFlow (routing/notification rules) based on the pre-change state; finally SavePostChange fires after the row is committed, used for post-save actions like updating related records. The other orderings wrong because they place WorkFlow after SavePostChange or put SavePreChange before SaveEdit, which contradicts PeopleSoft's documented event model where edits must pass before pre-change logic runs, and workflow evaluation happens before the final post-change step, not after.