Redwood Experience: Defaulting and Validation Rules for Create Requisition Flow

Full support for defaulting and validation rules for the create requisition flow is available in Redwood.

Customers need to reconfigure the defaulting and validation rules in Visual Builder Studio which were supported using auto-complete rules in responsive UI.

The name of the flow in Visual Builder Studio is called Create Job Requisition. It’s located in the Hiring menu.

In Redwood, Visual Builder Studio defaulting rules will trigger to default the values in the targeted fields when the user visits the section during the create flow. If the user modifies the target field (on which BRF defaulting rule is written) and moves back and forth in the same create flow (without clicking the Save or Submit buttons), the user modified value will be retained. But if the user clicks Save and Close or Submit and revisits that section in a new create or edit flow, the defaulting rules will override the user modified value. Customer should pay attention to this Redwood behavior and make fields read-only if they have written defaulting rules for some fields and don’t want users to modify them.

Here are some examples of supported use cases:

• Default Minimum Salary and Maximum Salary fields on the requisition based on Job, Position, Grade attributes.
• Default the system logged in user in the Recruiter field.
• Default Job Family based on the logged in user primary assignment job.
• Default field on the descriptive flexfield (DFF) on the requisition details based on previous position incumbent information.
• Hiring Manager receives a warning message when creating a job requisition where the position already has an incumbent without a future termination date or future transfer effective date.
• Default the Hiring Manager field with the manager of the current incumbent of the position which is used to create the job requisition.

Use cases not supported in 25C:

• Use cases where defaulting is supposed to happen from UDT (user defined tables) on the job requisition.
• Use cases where defaulting is supposed to happen from Legal Entity EFF on the job requisition.
• Use cases related to defaulting fields in the job requisition Posting tab.
• Defaulting rules for editing requisitions.

With this feature, customers can configure defaulting and validation rules that they've configured using auto-complete rules.

Steps to Enable

For details, see How do I write defaulting and validation rules for the create requisition flow in Redwood user experience?

Key Resources

For details on enabling Redwood for HCM, see How do I adopt Redwood for HCM? and Extending Redwood Applications for HCM and SCM Using Visual Builder Studio.