Default and Validate Field Values in Redwood Succession Management
As administrators, you can improve the user experience by creating defaulting and validation rules (warnings and errors) in Business Rules for the succession plan page in the create and edit flows.
This table indicates the defaulting and validation fields for the Create and Edit Succession Plan flow.
Process/Pages | In the Conditions | To Default Field Value | To Validate Field Values |
---|---|---|---|
|
Fields as per flow | Private checkbox |
|
You can now use these delivered validation templates for succession plans to avoid creation of duplicate succession plans:
- Validate Accessible Incumbent Succession Plans Based on Incumbent ID: Checks succession plans that the logged in user can access to find if a succession plan has already been created for the same incumbent.
- Validate Incumbent Succession Plans Based on Incumbent ID: Checks all succession plans to find if a succession plan has already been created for the same incumbent.
- Validate Accessible Job Succession Plans Based on Job ID: Checks succession plans that the logged in user can access to find if a succession plan has already been created for the job selected in the current succession plan.
- Validate Job Succession Plans Based on Job ID: Checks all succession plans to find if a succession plan has already been created for the job selected in the current succession plan.
- Validate Accessible Position Succession Plans Based on Position ID: Checks succession plans that the logged in user can access to find if a succession plan has already been created for the position selected in the current succession plan.
- Validate Position Succession Plans Based on Position ID: Checks all succession plans to find if a succession plan has already been created for the position selected in the current succession plan.
You can also use the Default Succession Plans as Public rule to ensure that private succession plans can’t be created in your organization.
Streamline creation of succession plans in your organization by validating the succession plans created and enhance your succession planning.
Steps to Enable
To add validation rules for succession plans:
- Create a succession plan.
- Edit the New Succession Plan page in Visual Builder Studio.
- Select a project.
- Click Validate Field Values.
- Click the + icon near the search field.
- In the Create Validation dialog, do these actions:
- Select one of these delivered templates:
- Validate Accessible Incumbent Succession Plans Based on Incumbent ID
- Validate Incumbent Succession Plans Based on Incumbent ID
- Validate Accessible Job Succession Plans Based on Job ID
- Validate Job Succession Plans Based on Job ID
- Validate Accessible Position Succession Plans Based on Position ID
- Validate Position Succession Plans Based on Position ID
- Enter a suitable label for the template. The ID is automatically generated.
- Optionally, enter a description.
- Click Create.
- Ensure that the rule is active.
- Edit the message summary and detail according to your organization’s requirements.
To ensure that plan owners can’t create private plans:
- Create a succession plan.
- Edit the New Succession Plan page in Visual Builder Studio.
- Select a project.
- Click Configure Fields and Regions.
- Add a form rule.
- In the Create Business Rule dialog box, do these actions:
- Select the Default Succession Plans as Public rule.
- Enter a suitable label for the template. The ID is automatically generated.
- Optionally, enter a description.
- Click Create.
- Ensure that the rule is active.
Key Resources
- Refer to the following documentation in this order:
- Express Mode in VBS for detailed instructions on using specific Express Mode features.
- Extending Redwood Applications for HCM and SCM Using VB Studio for details on what’s supported by HCM.
- You can refer to the VB Studio documentation "Configure an Oracle Cloud Application" to check the steps to access VB Studio from a Redwood page.
- Check the same documentation if you don’t see the Edit Page in Visual Builder option in your Oracle Cloud Application.
- Extending Oracle Cloud Applications in Visual Builder Studio Express Mode
- Refer to the Customer Connect forum Visual Builder Studio for HCM