Default and Validate Field Values in HCM Redwood Applications

Human Capital Management (HCM) Redwood applications expands its support of the autocomplete features in Business Rules to more pages. You can enhance your users' experience by authoring defaulting and validation rules (warning and error) in Business Rules for a defined list of pages, regions, and fields in Redwood pages:

• Global Human Resources
  • Document Records
• Compensation
  • Change Salary
• Goal Management
  • Team Goals Center
  • Goals Center

NOTE: Only the listed above Redwood pages are newly supported in this release.

Glossary

Here are some terms to familiarize yourself with before you start using the new autocomplete feature in your Redwood pages

• Autocomplete: Generic term to designate the functionality to default and validate field values. It’s product agnostic.
• Autocomplete Rules: A feature of HCM Experience Design Studio used to default and validate field values in responsive pages. Autocomplete Rules is object-based.
• Business Rules: A feature of VB Studio Express Mode used to personalize Redwood pages including defaulting and validating field values (new in 24B). Business Rules is page-based.
• Initial Field Values and Field Values
  • Initial field value: The field value stored in the database. The initial field value doesn't change for a transaction.
    • When they are available for a region, they are listed under the hierarchy with the same name.
    • Note that the initial field values are page and region specific. For example, in Change and Correct Employment Details processes, the initial field values are available for the assignment attributes but not for salary attributes.
  • Field value is the value cached in a page, which may already have been modified by a rule or user.
  • Initial field values and field values can be used in conditions and rule logic.
  • Initial field values and field values correspond to old and new values in Autocomplete Rules.

Field Values (1) and Initial Field Values (2) in the Conditions

For example, an HR Specialist reduces an employee's working hours from 40h to 20h. In this case,

• Initial field value is 40
• Field value is 20

Example of Defaulting and Validation Values in Business Rules

You can typically use the defaulting and validation capabilities in these cases:

• Change Salary
  • Defaulting
    • Default the proposed salary basis based on the employee's legal employer when Line Managers are proposing salary change.
    • Default the effective date to current date and next salary review date to 1 year after the effective date, when line managers are proposing salary change.
  • Validation
    • Prevent users to enter retro-active salary changes.
    • Change of salary should occur the first of the month.
    • Salary amount should be above a minimum values.
• Document Records
  • Defaulting when creating or editing a new document
    • Default Document Number as "Person ID || Issued Date" based on the Document Type.
    • Default Publish Date to Issued Date based on the Document Type.
  • Validation in the landing page
    • For Passport document type, Issued Date should be greater than or equal to From Date.
    • For Drivers License document type, warn users if To Date is null.
• Goal Management
  • Goals Detail
    • Restrict goal category selection based on user roles.
    • Enforce minimum weight for goal.
  • Edit Weights
    • Enforce minimum weight for goal.

Validation and defaulting rules aren't mutually exclusive and can be used both for the same fields to ensure data quality and consistency while improving the user experience. Likewise, defaulting rules and rules to control the display of fields and regions can be combined such as defaulting a date and making the field read-only.

NOTE: Refer to the VB Studio and HCM documentation in the Key Resources section.

Accessing Defaulting and Validation Capabilities

The 2 new features are available in Business Rules under these sections:

• Configure Fields and Regions to default field values, and
• Validate field values

Default and Validate Field Values

Using Fields to Author Your Conditions or Rule Logic, or Both

Fields, including Initial Field Values when they have been enabled for the region, are available at different places in Business Rules:

• Conditions
• Simple or advanced expressions to write the rule logic or default a field value, or both

NOTE: Fields that can be used in the conditions, simple and advanced expressions are limited to the fields and direct attributes available in the page and that are listed in the Regions and Fields section.

Supported and Not Supported Fields and Attributes

Using Conditions, Simple Expression, Advanced Expression and JavaScript (JS)

We encourage you to start building simple rules using the condition builder to define when to trigger the defaulting or validation rules.

Use simple expressions to default a value with another field value, or to transform data before assigning the value to a field.

Use advanced expressions in conditions, if:

• The operators available in the conditions aren't sufficient to write the rule logic.
• You need to transform data. Note that the use of JS in advanced expression is strictly limited to data transformation like substring, day of, and so on.

Working with Extensible Flexfields

Not all context codes are displayed for the Additional Assignment Info and Additional Person Info in their respective Business Rules pages. To view all context codes, you need to Refresh and Deploy Offline for each EFF using the Manage Extensible Flexfields page.

Manage Extensible Flexfields Page

Supported Fields and Implementation Guidelines by Page

Document Records

This table lists the supported attributes, and exceptions if any, of Document Records, and the implementation recommendations.

It applies to all pages under Me, My Team, and My Client Groups.

	In the Conditions for both Defaulting and Validation	To Default Field Values	To Validate Field Values	Implementation Guidelines
Document Records Landing Page	User Roles When is the rule applied? (Values are Viewing other’s info and Viewing own info) Country Business Unit Legal Employer Document Type Category Subcategory Tags	Not Applicable	Not Applicable	There is no support to create rules to validate or default based on other reference objects like Person, or Assignment).
Document Records > Add Flow	Same as above	Code Comments Date From Date To Document Name Document Number Descriptive Flexfields Developer Flexfields Issued Date Issuing Authority Issuing Country Issuing Location Publish Date	Code Comments Date From Date To Document Name Document Number Descriptive Flexfields Developer Flexfields Issued Date Issuing Authority Issuing Country Issuing Location Publish Date	Same as above.

Change Salary

This table lists the supported attributes, and exceptions if any, of Change Salary, and the implementation recommendations.

It applies to both pages under My Team and My Client Groups.

In the Conditions	To Default Field Values	To Validate Field Values	Implementation Guidelines
User Roles Legal Employer Business Unit Country Start Date Action Reason	Start Date Action Reason Proposed Salary Basis Salary Amount Next Salary Review Date	User Roles Legal Employer Business Unit Country Fields from When and Why, Salary Details section: Start Date Action Reason Proposed Salary Basis Salary Amount Annual Salary Annual Full-time Salary Compa-ratio Salary Range Salary Range Minimum Salary Range Maximum Salary Range Midpoint Quartile Quintile Next Salary Review Date Grade Step Ladder Compensation Zone Compensation Zone Type	Defaulting Salary amount can be defaulted when using the user determined type of salary basis only. Fields in the salary section can be defaulted based on the fields "listed in the conditions" row of this table.

Goal Management

This table lists the supported attributes, and exceptions if any, of Goal Management pages, and the implementation recommendations.

It applies to both pages under Me and My Team.

	Defaulting		Validation
	Supported Fields In the Conditions	Supported Fields To Default Field Values	Supported Fields In the Conditions	To Validate Field Values	Implementation Guidelines
Performance Goal Details	All	Fields for which the value property is enabled.	performanceGoalsV2 GoalName PersonNumber AssignmentNumber Source GoalVersionType StatusCode StartDate TargetCompletionDate ActualCompletionDate PercentCompletion Category Level Weighting RequestContext Published Publication Date LoggedInPersonType GoalPlanWeightEnabled AssociatedGoalPlans Priority Weight perfGoalTasks TaskName TaskTypeCode StartDate Status TargetCompletionDate PriorityCode PercentCompletion ActualCompletionDate CompletionStatus TargetType TargetValue UomCode	developmentGoals Actual Completion Date Allow workers to update key attribute Category Goal name Source Goal version type Level completion percentage person number Priority RequestContext Start date Status Target completion date devGoalTasks Actual completion date completion status goal name Completion percentage priority start date status target completion date target type target value name type uom code learning item relations - learning item id source type
Development Goal Details	All	Fields for which the value property is enabled.	Same as above	Same as above
Edit Weights	Not Applicable	Weight	Not Applicable	Weight

Business Benefit

These features help in these ways:

• Ensures quality and consistency of your valuable HR data by validating your user entries.
• Streamlines your user experience and reduces time to execute tasks by defaulting data entries.
• Allows your organization to adjust quickly with HR compliance without relying on new release updates.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Edit Layout in Express Mode

Dynamic Form and Dynamic Table

• Don't use the Edit Layout feature in Dynamic Form or Dynamic Table in Express mode as it's not supported and may impact working of Business Rules.
• Edit Layout in Dynamic Form and Dynamic Table will be disabled from release 24D. Any changes made to the layout using this feature prior to release 24C must be removed.

Rule Editor in Express mode

Container Layout

• If a Container Layout is available in Express mode for the page you want to personalize, use the Customer Connect forum to post queries and seek guidance before using the Rule Editor.

Approval Process for Business Rules Express Mode

• Building rules in Business Rules editor doesn't require an approval from Oracle for this release as long as the implementation guidelines are followed. 
• The approval process may be reevaluated by Oracle as more capabilities are delivered in subsequent releases.

Rules from Autocomplete Rules Triggering in Redwood pages

• The existing object validation rules with error from Autocompletes Rules will continue to work in the Redwood pages, Change Salary and Document Records, listed above. This won't require modification in existing rules.
• All rules for all other pages built on the underlying business objects for this page must be disabled when you enable the Redwood page. Note that disabling rules on a business object will disable Autocomplete for both the Redwood and Responsive pages.
• Approval process for Autocomplete Rules in responsive UI is the same.

Key Resources

Here are the topics we recommend on how to start with Express Mode.

• 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