Leila Fielding
Why I picked it
Mass changes are high-stakes, and the Redwood version makes choosing and checking the group of workers much clearer.
Where it helps
HR moves a whole department to a new location by entering their assignment numbers, checks how many validated, and removes anyone who shouldn't be included.
Watch out: Changes made in Redwood can't be edited in the classic page afterwards.
From Oracle's note
The mass assignment change transaction is converted from the classic page to a modern VBCS experience, retaining the transaction’s existing functions and validations. On the dashboard, a Validated column shows the count of workers validated. You can build a worker population using criteria such as legal employer or business unit, or enter assignment numbers directly. Redwood-created or updated transactions are maintained in Redwood, rather than being reopened for edits in the classic page.
- Create, update, rerun or delete mass assignment transactions.
- Select workers by criteria or up to 500 comma-separated assignment numbers.
- Review validated-worker counts and remove workers from Validate Changes.
Enable ORA_HCM_VBCS_PWA_ENABLED (Y) and ORA_PER_EMPL_MASS_ASG_UPDATE_REDWOOD_ENABLED (Yes) at site level. Some classic fields are hidden until exposed in Business Rules; category tags aren't supported, and Redwood transactions can't be updated in the classic UI.
Last reviewed November 2026