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
  • Jobs
  • Positions
• Compensation
  • Change Salary
• Payroll
  • Payroll
• Talent Management
  • Talent Review and Succession Management

NOTE: Only the above listed 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:

• Jobs
  • Defaulting
    • Default Full time or Part time field with value as Part time
    • Default job level based on selected management level
  • Validation
    • Validate job name doesn't contain special characters
    • Validate job code contains six characters of which the first 3 are alphabets and the last 3 are numbers, without any special characters.
• Positions
  • Defaulting
    • Default assignment category
    • Default location based on position descriptive flexfield (DFF)
  • Validation
    • Validate that position name includes job name and department name
    • Validate standard working hours is not equal to 375 or 40
• 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 value
• Payroll
  • Defaulting
    • Default payroll based on legal employer and whether the employee is Salaried or Hourly Paid
    • Default Timecard Required for Assignment field for hourly paid employees
• Talent Review and Succession Management
  • Defaulting
    • Default succession plans to public plans
    • Default flexfields when adding a succession plan
  • Validation
    • Validate Succession Plan Candidate Ranking field
    • Validate Talent Review Meeting Status field

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

Jobs

This table lists the supported attributes, exceptions, and the implementation recommendations for Jobs.

It applies to the Jobs pages under My Client Groups tab.

	In the Conditions	To Default Field Values	To Validate Field Values	Implementation Guidelines
Jobs: Add, Duplicate, and Update flows	User Roles	Full time or Part time Manager level Level Regular or Temporary Jobs descriptive flexfield	Job Family Id Job Name Job Code Job Function Code Level Jobs descriptive flexfield

Positions

This table lists the supported attributes, exceptions, and the implementation recommendations for Positions.

It applies to the Positions pages under My Client Groups tab.

	In the Conditions	To Default Field Values	To Validate Field Values	Implementation Guidelines
Positions:  Add, Duplicate, and Update flows	User Roles	BargainingUnitCode Budget Currency Code BudgetedPositionFlag Business Unit ID Department ID FullPartTime HiringStatus Job ID Location ID OverlapAllowedFlag Position DFF PositionType ProbationPeriod ProbationPeriodUnitCode Regular or Temporary Requisition Template ID Union ID	ActionReasonId PositionName PositionCode JobName DepartmentName LocationName PositionsDFF RequisitionTemplateId AssignmentCategory FullPartTime RegularTemporary Status BusinessUnitId StandardWorkingHours Type WorkingHours EffectiveStartDate BargainingUnitId CollectiveAgreementId UnionId HiringStatus ParentPositionCustomField FTE Cost Center ID Headcount StartTime OverlapAllowedFlag	Any rule that refers to incumbent assignment data or collective agreement data is currently not supported.

Change Salary

This table lists the supported attributes, exceptions, and the implementation recommendations for Change Salary.

It applies to Line Manager Change Salary and Admin Change Salary pages accessed from My Team and My Client Groups tabs respectively.

In the Conditions	To Default Field Values	To Validate Field Values	Implementation Guidelines
Assignment attributes including Assignment Status Bargaining Unit Business Unit Working Hours Frequency Hourly or Salaried Legal Employer Next Payroll Start Date Payroll Start Date Primary Work Relationship Termination Date US Job Info Overtime Status Working Hours Job Job Code Job Function Job Family Position Position Code Position Budget Value Position Standard Working Hours Grade Ladder Grade Grade Code Department Department Code Location FTE Additional Assignment Info segments	Proposed Salary Basis Salary Amount Next Salary Review Date	Proposed Salary Basis   Salary Amount Adjustment Amount Adjustment Percentage Next Salary Review Date Rate Component Values through Advanced Expression Validation with Error from Autocomplete Rules	Initial Field Values on salary fields aren't supported Salary Amount can be defaulted for User Determined Type Only

Payroll

This table lists the supported attributes, exceptions, and the implementation recommendations for Payroll.

It applies to the Payroll section for below mentioned flows under My Client Groups tab.

	In the Conditions	To Default Field Values	To Validate Field Values	Implementation Guidelines
Payroll section in the following flows: Add Assignment Add Contingent Worker Add Nonworker Add Pending Worker     Convert Pending Worker Create Work Relationship Hire an Employee	Fields supported by Global Human Resources	Payroll Overtime Period for Payroll Timecard Required for Payroll Tax Reporting Unit Overtime Period for Assignment Timecard Required for Assignment	Payroll Overtime Period for Payroll Timecard Required for Payroll Tax Reporting Unit Overtime Period for Assignment Timecard Required for Assignment	Existing Autocomplete rule to default the Final Close during Termination will work in VB.

Talent Review and Succession Management

This table lists the supported attributes, exceptions, and the implementation recommendations for Talent Review and Succession Management.

It applies to pages under My Client Groups tab.

	In the Conditions	To Default Field Values	To Validate Field Values	Implementation Guidelines
Add Succession Plan	User Roles SuccessionPlanCandidates Ranking Candidate Readiness Code Is Interim Successor CandidateStatusCode SuccessionPlanOwners enableAlert OwnerTypeCode talentSuccessionPlans Private Business Unit ID DepartmentID Grade ID Incumbent Person ID Job ID PlanTypeCode Position ID Status Code			In Configure Fields and Regions, the Value property is only available for fields that can be defaulted.
Edit Succession Plan	User Roles SuccessionPlanCandidates Ranking Candidate Readiness Code Is Interim Successor CandidateStatusCode SuccessionPlanOwners enableAlert OwnerTypeCode talentSuccessionPlans Private Business Unit ID DepartmentID Grade ID Incumbent Person ID Job ID PlanTypeCode Position ID Status Code			In Configure Fields and Regions, the Value property is only available for fields that can be defaulted.
Talent Review Configuration	User Roles meetings Business Leader Id Dashboard Template Id Meeting Date Meeting Purpose Meeting Status Organization Rating Submission Deadline Talent Review Meeting Talent Review Meeting DFF Review Content Data Validity Code Include Matrix Manager Questionnaire Id Use Potential Assessment Prior Rating Start Date Prior Rating End Date Template Name  Dashboard Template Id CreatedBy CreationDate IncludeMatrixMgmt IncludeSuccessionPlans IncludeTalentPools LastUpdateDate LastUpdatedBy OwnerId PopulationSizeForESS QuestionnaireId TemplateStatusCodeInUse Business Leader Assignment AssignmentId PersonId BusinessTitle EffectiveLatestChange BusinessUnitId AssignmentType UserPersonTypeId ProposedUserPersonTypeId PrimaryFlag PrimaryAssignmentFlag PrimaryWorkRelationshipFlag PositionId JobId GradeId DepartmentId ReportingEstablishmentId LocationId FullPartTime ManagerFlag CreatedBy CreationDate LastUpdatedBy LastUpdateDate JobSetId GradeSetId LocationSetId DepartmentSetId assignmentsEFF managers			In Configure Fields and Regions, the Value property is only available for fields that can be defaulted.

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 Update 24D. Any changes made to the layout using this feature prior to Update 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 validation rules with the 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