Redwood Change Assignment – Supported Approach for Cross-Object Validation in VBS
Summary
How can we implement a cross-object validation that prevents submission in Redwood Change Assignment?
Content
Hi Team,
We’re migrating Global HR transactions to Redwood and need to block a Change Assignment transaction, such as a Promotion, when the worker has an active record in another HCM business object requiring review.
The required data isn’t exposed in the Change Assignment Business Rules context. Could you clarify:
- Are cross-object checks and submission-blocking validations supported through VBS Business Rules?
- If not, what is the supported way to retrieve the data and validate the transaction?
- Are action chains or REST-based extensions supported, or should another HCM validation framework be used?
Tagged:
0