Implementation Guidelines

These are the supported fields and implementation guidelines for HCM Redwood pages.

Additional Person Info

This table lists the supported attributes, and exceptions if any, for the Additional Person Info page, and the implementation recommendations.

Supported fields

  • in the conditions,
  • to default field values
  • to validate field values
Implementation Guidelines
  • Any segment part of a single or multi-rows context
  • Initial Field Values
  • Defaulting and validation with error rules only, are supported within the same Person EFF context.

Change Assignment and Correct Employment Details

This table lists for each supported regions for the Change Assignment and Correct Employment Details processes, the supported attributes, and exceptions if any, and the implementation recommendations.

Region In the Conditions To Default Field Values To Validate Field Values Implementation Guidelines
When and Why
  • When and Why attributes
  • Action Reason
  • Action
  • Business Unit
  • Not supported
Assignment
  • When and Why attributes
  • Assignment attributes
  • Initial Field Values

Are not supported for defaulting:

  • FTE
  • KFF
  • Not supported

Additional Assignment Info

(PerAssignmentEITCategory)

  • When and Why attributes
  • Assignment attributes
  • Additional Assignment Info, single or multi-rows context
  • Additional Assignment Info, single or multi-rows context
  • Additional Assignment Info, single or multi-rows context
  • Refer to Working with Extensible Flexfields to view all context codes in Business Rules
Salary
  • Assignment attributes
  • Proposed Salary Basis
  • Adjustment Amount
  • Adjustment Percentage
  • Next Salary Review Date
  • Proposed Salary Basis,
  • Salary Amount
  • Proposed Salary Basis field should be initialized with the Salary Basis ID, not Name.
  • Initial Field Values on salary fields are not supported.

Departments

This table lists the supported attributes, and exceptions if any, for the Departments page, and the implementation recommendations.

In the Conditions To Default Field Values To Validate Field Values Implementation Guidelines
  • ActiveStatus
  • Departments Descriptive Flexfields
  • InternalAddressLine
  • LocationId
  • Name
  • SetCode
  • Title
  • Departments Descriptive Flexfields
  • InternalAddressLine
  • LocationId Name
  • Title
  • Departments Descriptive Flexfields
  • InternalAddressLine
  • LocationId
  • Name
  • Title

These are not supported in this release:

  • Defaulting in edit and duplicate flows
  • Attachments
  • Initial field values
  • Defaulting and validation for extensible flexfields