Parameters Supported for Guided Journeys on Redwood Compensation Pages
You can now add context-sensitive content, such as Oracle Transaction Business Intelligence (BI) reports or URLs using a section-level guided journey for these Redwood compensation pages:
- Line Manager Change Salary
- Admin Change Salary
- Salary History
- My Compensation
- Compensation Info
- View Compensation History
- Personal Contribution
- Individual Compensation
- Administer Compensation
- Salary section of Global HR and Oracle Recruiting flows, such as Hire an Employee and Create an Offer
- Individual compensation section of Global HR and Oracle Recruiting flows, such as Hire an Employee and Create an Offer
You can use these parameters to add context-sensitive content:
Pages: Personal Contributions, Individual Compensation, and Administer Compensation
| Section | Attribute | Parameter Name | Comments |
|---|---|---|---|
| When | ActionId LegalEntityId BusinessUnitId LegislationCode AssignmentNumber ActionDate |
Action ID |
|
| Additional Compensation |
Individual Compensation: ActionDate Assignment: LegalEntityId |
Individual Compensation: Assignment: Business Unit ID |
1. There can be multiple individual compensation allocations available. So attributes are suffixed with 0, 1, 2 and so on. 2. These attributes are also available in Global HR and Offer actions that include the additional compensation section. |
Pages: Change Salary and Admin Change Salary
| Section | Attribute | Parameter Name | Comments |
|---|---|---|---|
| When and Why | ActionDate ActionId ReasonId BusinessUnitId LegislationCode |
When Date |
|
| Salary |
Salary: WhenDate Assignment: GradeId |
Salary: When Date Assignment: Grade ID |
These attributes are also available in Global HR and Offer actions that include the salary section. |
Pages: Salary History
| Section | Attribute | Parameter Name | Comments |
|---|---|---|---|
| Landing Page |
Salary: WhenDate_0 Assignment: |
Salary: When Date Assignment: |
There can be multiple salaries available. So attributes are suffixed with 0, 1, 2 and so on. |
| Create and Edit Page |
Salary: WhenDate Assignment: |
Salary: When Date Assignment: |
Pages: My Compensation, Compensation Info, My Compensation - Salary Details, Compensation Info - Salary Details
| Section | Attribute | Parameter Name | Comments |
|---|---|---|---|
| Salary |
Current Salary: WhenDate ActionId ActionReasonId SalaryBasisId SalaryAmount GradeId SalaryRangeMinimum SalaryRangeMaximum RangePosition Quartile Quintile FTE CompaRatio LegislativeDataGroupId NextSalReviewDate GeographyTypeName GeographyName Assignment: GradeId GradeLadderName GradeStepName |
Current Salary: |
On the landing page, the current salary is passed as context. On the details page, the selected salary record is passed as context. |
|
Personal Contribution Additional Compensation |
PlanId_0 Assignment: |
Plan ID Assignment: |
There can be multiple individual compensation allocations available. So attributes are suffixed with 0, 1, 2 and so on. |
| Recurring and One-Time Payments |
ElementTypeId_0 Assignment: |
Element Type ID Assignment: |
There can be multiple payments available. So attributes are suffixed with 0, 1, 2 and so on. |
Pages: Employment Info, View Job Offer, Journeys
In addition to the attributes available on the page, respective sections also have these attributes available:
| Section | Attribute | Parameter Name | Comments |
|---|---|---|---|
| Salary | WhenDate ActionId ActionReasonId SalaryBasisId SalaryAmount GradeId FTE LegislativeDataGroupId |
When Date Action ID Action Reason ID Salary Basis ID Salary Amount Grade ID FTE Legislative Data Group ID |
|
| Additional Compensation | PlanId_0 OptionId_0 ProcessingType_0 PrimaryInputValue_0 StartDate_0 EndDate_0 ElementEntryId_0 ElementTypeId_0 |
Plan ID Option ID Processing Type Primary Input Value Start Date End Date Element Entry ID Element Type ID |
There can be multiple individual compensation allocations available. So attributes are suffixed with 0, 1, 2 and so on. |
| Recurring and One-Time Payments | ElementTypeId_0 ElementEntryId_0 StartDate_0 EndDate_0 ProcessingType_0 PrimaryInputValue_0 |
Element Type ID Element Entry ID Start Date End Date Processing Type Primary Input Value |
There can be multiple payments available. So attributes are suffixed with 0, 1, 2 and so on. |
Pages: View Compensation History
| Section | Attribute |
Parameter Name |
Comments |
|---|---|---|---|
| Landing Page |
SalaryBasisId Assignment: |
Salary Basis ID Assignment: |
Most recent salary is passed as context. |
|
Overall Salary Page |
LegislationCode | Legislation Code | |
| Recurring Payments Page |
ElementTypeId Assignment: |
Element Type ID Assignment: |
This feature lets you add context-sensitive content on the Redwood pages.
Steps to Enable
How do I configure guided journeys and enable them on Redwood compensation pages?
Key Resources
For more information about using guided journeys on Redwood pages, see these resources on the Oracle Help Center:
-
Overview of Guided Journeys in the Implementing and Using Journeys guide
-
Enable a Guided Journey for Redwood Pages in the Implementing and Using Journeys guide
-
How You Configure the URL for an External URL Task Type in Journeys in the Implementing and Using Journeys guide
-
How You Configure the Report Task Type in Journeys in the Implementing and Using Journeys guide
-
How You Configure Analytics Task Type in Journeys in the Implementing and Using Journeys guide
-
Extending Redwood Applications for HCM and SCM Using Visual Builder Studio guide