Oracle Fusion Cloud Human Resources 22D What's New

Expand All

JANUARY MAINTENANCE PACK FOR 22D

Revision History
Overview
Feature Summary
Human Resources

DECEMBER MAINTENANCE PACK FOR 22D

Revision History
Overview
Feature Summary
Human Resources
1. Global Human Resources
  1. 1. Prepare for Changes to Load Additional Assignment Info in Update 23B

NOVEMBER MAINTENANCE PACK FOR 22D

Revision History
Overview
Feature Summary
Human Resources
1. Global Payroll Interface
  1. 1. Perform a Baseline Extraction of Payroll Interface for ADP Global Payroll V2

Update 22D

Revision History
Overview
Feature Summary
Human Resources
IMPORTANT Actions and Considerations for Human Resources
Controlled Availability for Human Resources

January Maintenance Pack for 22D

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Module	Feature	Notes
20 DEC 2022			Created initial document.

Overview

HCM Cloud applications have two types of patches you can receive that are documented in this What’s New:

Release Updates (22A, 22B, 22C, and 22D)
Optional Monthly Maintenance Packs to each update

It is important for you to know what Release Update your environment is on. You can find this in your Cloud Portal.

____________________

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our products better, please let us know. To enter an idea go to the Ideas Lab on Oracle Customer Connect. In this document wherever you see the light bulb icon after the feature name it means we delivered one of your ideas.

____________________

Parameters	Description
Checklist Name	Name of the checklist that needs to be force completed.
Allocation Date Range	The duration to consider when force completing assigned journeys.
Force Completion Date	Date on which to force complete the journey.

Parameters	Description
Checklist Name	Name of the checklist that needs to be deleted.
Allocation Date Range	The duration to consider when deleting assigned journeys.

Date	Module	Feature	Notes
22 NOV 2022			Created initial document.

Date	Module	Feature	Notes
28 OCT 2022			Created initial document.

Date	Module	Feature	Notes
22 NOV 2022	Global Human Resources / Document Records	Archive and Purge Document Records	Updated document. Revised feature information.
22 NOV 2022	HCM Communicate	Communication Teams	Updated document. Revised feature information.
28 OCT 2022	Global Human Resources/ Workforce Structures	Configure Default Effective Start Date for Work Structure Objects	Updated document. Revised feature information.
30 SEP 2022	UK Human Resources	Process Statutory Absences for Multiple Assignments	Updated document. Revised feature information.
30 SEP 2022	UK Human Resources	Process Statutory Parental Bereavement Pay and Leave	Updated document. Revised feature information.
30 SEP 2022	Human Resources / 23 Preparation	Prepare for Changes to Retained Grade Context in Assignment Extensible Flexfield in Update 23A	Updated document. Feature delivered in update 22D.
30 SEP 2022	Human Resources / 23 Preparation	Prepare For Change In Default Value of Profile Option For Deferring I9 Creation in Journeys	Updated document. Feature delivered in update 22D.
30 SEP 2022	Human Resources / Person	Last Updated By and Last Updated Date Fields Added to Personal Info Responsive Pages	Updated document. Feature delivered in update 22D.
30 SEP 2022	Human Resources / Workforce Structures	Prevent Inflight Department Transaction Updates When Using HCM Data Loader	Updated document. Revised feature information.
30 SEP 2022	Human Resources / Workforce Structures	Prevent Inflight Job Transaction Updates When Using HCM Data Loader	Updated document. Revised feature information.
30 SEP 2022	Human Resources / Workforce Structures	Prevent Inflight Location Transaction Updates When Using HCM Data Loader	Updated document. Revised feature information.
02 SEP 2022			Created initial document.

SUGGESTED READING FOR ALL HCM PRODUCTS

HCM Common What's New - In this What's New you will find feature that are used across applications.
Human Resources What’s New – In the Global Human Resources section you will find features on the base application in which other application are built upon.

NOTE: Not all Global Human Resource features are available for Talent and Compensation products.

Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1). These documents identify bug fixes and possible known issues. You will also need to review these documents based in the release update version you are currently on or will be moving to.
Oracle Help Center – Here you will find guides, videos and searchable help.
Release Readiness – New Feature Summary, What’s New, Feature Listing Spreadsheet, Spotlights and Release Training

GIVE US FEEDBACK

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

	Ready for Use by End Users (Feature Delivered Enabled) Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.
Feature	Report	UI or Process-Based: Small Scale	UI or Process-Based: Larger Scale*
Human Resources
Global Human Resources
23 Preparations
Prepare for Changes to Retained Grade Context in Assignment Extensible Flexfield in Update 23A
Prepare For Change In Default Value of Profile Option For Deferring I9 Creation in Journeys
Autocomplete
Autocomplete Support for Defaulting Effective Date in When and Why Section
Document Records
Archive and Purge Document Records
Move Deleted Document Records to Archive Table
Improved Document Type Description Field
Enhanced Process for Mass Download of Document Records
Employment
Workforce Structure Codes Added to Employment Info Page
Contextual Job Information Added to Employment Info Page
Synchronize Worker Data from Position When Using Worker REST API
Check Time Cards While Deleting an Assignment
Configurable Business Title Switcher in My Team
Journeys
Secure Journey Category Selection When Creating Journeys
Template Based Security For Journeys
Advanced Journey Task Type Using Combination of Different Task Types
Parameterized Deep Links for Journeys
Surveys in Journeys
Guided Journeys for Compensation Flows
Contextual Journeys for Compensation Flows
Person
Last Updated By and Last Updated Date Fields Added to Personal Info Responsive Pages
Person Name Formats Validation Updated
Prepare for Increase to the PER_ADDRESSES_F attribute TOWN_OR_CITY to 60 Characters in Update 23A
Work Structures
Configure Default Effective Start Date for Work Structure Objects
Prevent Inflight Job Transaction Updates When Using HCM Data Loader
Prevent Inflight Location Transaction Updates When Using HCM Data Loader
Prevent Inflight Department Transaction Updates When Using HCM Data Loader
Position Management: Profile Option to Restrict the Number of Valid Grades
Human Resources / Employment Replaced or Removed Features
Prepare for Removal of Person Gallery and Portrait Access in Update 23A
Prepare for Discontinuation of Support for Employees REST Resource in Update 23D
Human Capital Management for Germany
Updated Meaning of Various Attributes Used for Disability Reporting
Human Capital Management for Italy
Additional Sublevel segment at Collective Agreement
Human Capital Management for Oman
Additional Information at an Organization Level
Additional Information at a Person Level
Payroll Definitions
Payment Methods
Human Capital Management for Spain
Enhanced Validation of the Foreigner's Identification Number
Human Capital Management for United Kingdom
Process Statutory Parental Bereavement Pay and Leave
Process Statutory Absences for Multiple Assignments
Global Payroll Interface
Perform a Baseline Extraction of Payroll Interface for ADP Global Payroll V2
Perform a Baseline Extraction of Payroll Interfaces generated from Global Payroll Interface Template
Global Payroll Interface Process To Generate Interfaces For Payroll Connect Vendors
Global Payroll Interface Template Supports Salary Using Simple Components
HCM Communicate
Communication Teams
Email Follow-up Targeting for No Response
Seeded Campaign Templates
Transactional Business Intelligence for Human Resources
Assignment Termination Details In Assignment Subject Areas
New Attributes Related To Position And Documents Of Record
Reporting On Document Attachments Data
IMPORTANT Actions and Considerations for Human Resources
Controlled Availability for Human Resources

Human Resources

Global Human Resources

23 Preparations

Prepare for Changes to Retained Grade Context in Assignment Extensible Flexfield in Update 23A

In Update 23A, we will be making changes to the segment names and value sets in the Retained Grade Context in the Assignment Extensible Flexfield (EFF). This table lists the changes:

Existing Segment Name	New Segment Name	Existing Value Set	New Value Set
Grade Ladder	Pay Table ID	ORA_PER_RETGRD_GRADE_LADDER_VS	No Changes
Frequency	Pay Basis	HRC_CHAR_10 (Currently, it’s a free text field)	ORA_PER_RETGRD_PAY_BASIS_VS
Pay Plan	No Changes	HRC_CHAR_10 (Currently, it’s a free text field)	ORA_PER_RETGRD_PAY_PLAN_VS

New Segment Names and Value Sets for Retained Grade Context

The ORA_PER_RETGRD_PAY_BASIS_VS and ORA_PER_RETGRD_PAY_PLAN_VS value sets are SQL Query-based. The value sets display the existing retained grade data entered by the user in the Frequency and Pay Plan fields from the PER_ASSIGNMENT_EXTRA_INFO_M table.

Since the new values sets are SQL Query-based, you now have the flexibility to replace the existing SQL query with the one that suits your business needs. For example, you can replace the existing SQL query with the following query by defining custom lookup types and associating them with the new value sets:

Select MEANING from FND_LOOKUP_VALUES_VL where lookup_type = ‘<Custom Lookup Type Name>’

NOTE: When you define a custom lookup type, ensure that the lookup codes include all the stored values in the Frequency or Pay Plan field at the retained grade level. Else, you will receive an error when you view or update the retained grade values.

Control the way your users enter retained grade data. Users can now enter the data in a structured manner by using the LoV instead of using free text fields.

Steps to Enable

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

Tips And Considerations

If your requirement is to only select the existing data from the Frequency and Pay Plan fields, you don't need to change your current setup. The existing data will be displayed as values in the LoV.
If you want to enter new data, you must create a new lookup type which contains existing and new data according to your requirement. Then, update the value set query to get the data from your custom lookup type.

Key Resources

For more information see the following in the Implementing Global Human Resources guide on the Oracle Help Center:

Create Grade Retention Page and Associate With Retained Grade Context in the Employment chapter

Prepare For Change In Default Value of Profile Option For Deferring I9 Creation in Journeys

Make note of the default value of the Defer I9 Creation on Checklist Allocation Enabled profile option that will default to Y starting in Update 23A.

This feature enables you to use and transfer the latest data of the worker when creating the I-9 document on HireRight.

Steps to Enable

Currently, the default value for the profile option is set to N as indicated here. The default value for the profile option will be set to Y in 23A.

Profile Option Code	Description	Default
ORA_PER_CHECKLIST_DEFER_I9_CREATION Defer I9 Creation on Checklist Allocation Enabled	Enable the creation of I9 to be deferred during checklist allocation.	N

Profile Option Code

Description

Default

ORA_PER_CHECKLIST_DEFER_I9_CREATION

Defer I9 Creation on Checklist Allocation Enabled

Enable the creation of I9 to be deferred during checklist allocation.

To change the default profile option value:

Navigate to the Setup and Maintenance work area.
Search for and click the Manage Administrator Profile Values task.
Search for the ORA_PER_CHECKLIST_DEFER_I9_CREATION profile option code and select the profile option in the search results.
In the Profile Values area, enter the appropriate value in the Profile Value field.
Click Save and Close.

Tips And Considerations

You must check your existing profile option configuration and make changes as required.

Key Resources

For more information about Journeys and Checklists, refer to these resources on the Oracle Help Center:

Checklists and Journeys in the Implementing Global Human Resources guide
Checklists and Journeys in the Using Global Human Resources guide

Role And Privileges

You must be granted the Manage Journey (PER_MANAGE_CHECKLIST_TEMPLATE_PRIV) function privilege to work on checklist templates.

Autocomplete

Autocomplete Support for Defaulting Effective Date in When and Why Section

You can now default the effective date in the When and Why section of employment flows by using autocomplete rules. The defaulting by the autocomplete rule takes precedence over the default value that's set based on the ORA_PER_EMPL_DEFAULT_EFFECTIVE_DATE profile option.

Effective Date Defaulted According to Autocomplete Rule in Promote Flow

Example of Autocomplete Rule to Default the Effective Date to 30 Days After Today's Date in Promote Flow

NOTE: You can’t default the effective date for the Create Work Relationship and Convert Pending Worker flows by using the autocomplete rule.

This feature gives autonomy and control to customers to extend their existing applications by creating their own rules without relying on Oracle Development to implement it.

Steps to Enable

To enable Autocomplete Rules in the HCM Experience Design Studio, you need to log a Service Request (SR).

Review and follow the instructions provided in the My Oracle Support document, Fusion HCM Cloud: Enabling Autocomplete Rules Feature Starting with Release 21B (Doc ID 2767655.1) to get access.

Tips And Considerations

The effective date will be defaulted only the first time when the user visits the When and Why section of these employment update flows: Promote, Local and Global Transfer, Transfer, Change Assignment, Change Location, and Change Manager.

If the ORA_PER_EMPL_DEFAULT_EFFECTIVE_DATE profile option value is set to Y and no autocomplete rule is defined, the effective date will be defaulted to the current system date.
The ORA_PER_EMP_RETAIN_CHANGES profile option value is set to N and the autocomplete rule is defined to default the effective date. In this case, if the user manually changes the effective date in the employment flow, the new date value will be retained.
You can’t default the effective date using an autocomplete rule that’s based on a modified field in the employment transaction page. This is because each time the transaction date is modified in the page or the ORA_PER_EMP_RETAIN_CHANGES profile option value is enabled (set to Y), the transaction is rolled back and the changes are re-populated.
The effective date won’t be defaulted when you resume an employment transaction after saving it, or when the employment transaction is edited by an approver.
This feature isn’t supported in HCM Data Loader and REST API.

Key Resources

For more information, refer to this resource on the Oracle Help Center: Employment, When and Why, Chapter Business Objects in Autocomplete in the Configuring and Extending HCM Using Autocomplete Rules guide.

Role And Privileges

You must be granted the Human Capital Management Application Administrator role to work in a sandbox.

Document Records

Archive and Purge Document Records Feature is from a customer submitted idea.

We have streamlined the retention and management of document records by giving users the ability to archive and purge document records that are no longer required for regular access.

You can archive and purge the document records for a document type by enabling the archive and purge settings for the document type and running the Archive Document Records ESS job. When you run the ESS job, all document records that match the archive criteria will be archived. The archiving process involves moving the document records from the HR_DOCUMENTS_OF_RECORD table to the HR_DOCUMENTS_OF_RECORD_ARCHIVE table. After the document records are archived, they will be removed from the HR_DOCUMENTS_OF_RECORD_ARCHIVE table based on the purge settings enabled for the document type.

These are the fields used for archive settings:

Archive Criteria Basis: By default this LoV is blank. You can select either the Creation Date, From Date, To Date, or Issued On.
Archive After Days: By default this field is blank. It’s a mandatory field where you enter a number that’s greater than 0 and less than or equal to 18000. For example, if you enter 2, the document records will be archived 2 days after the date selected for Archive Criteria Basis.
Purge After Days: By default this field is blank. It’s a mandatory field where you enter a number that’s greater than 0 and less than or equal to 18000. For example, if you enter 2, the document records will be purged 2 days after the archive date.

Here's how the archive process works:

For each document record, the process gets the Archive After Days and Archive Criteria Basis based on the document type.
For each document record, add the Archive After Days to the appropriate document record attribute selected for the Archive Criteria Basis (Creation Date, From Date, To Date, or Issue On). If the resultant value is greater than the system date, then the document record will be archived.
Copy all such document records data to the HR_DOCUMENTS_OF_RECORD_ARCHIVE table.
The archived document records in the HR_DOCUMENTS_OF_RECORD_ARCHIVE table will be marked with the archive date.
Delete all the copied document records data from the HR_DOCUMENTS_OF_RECORD table.

Here's how the purge process works:

For each archived document record, the process gets the Purge After Days based on the document type.
For each archived document record, add the Purge After Days to the archive date. If the resultant value is greater than the system date, then the document record will be purged.
Remove all such document records along with their attachments from the HR_DOCUMENTS_OF_RECORD_ARCHIVE table and the attachment repository.

Configure Archive Settings to Archive and Purge Deleted Document Records

Optionally Select the Document Type Parameter for the ESS Job

Archive document records to retain a copy for audit, data retention or analysis, and other purposes. Purge to remove the document records that are no longer needed.

Steps to Enable

Navigate to the Setup and Maintenance work area.
In the Tasks panel drawer, click Search.
Search and click the Document Types task name.
Click the Create icon in the Search Results area.
Enter the document type and select the category.
Under the Document Record Preferences tab, select the value for Archive Criteria Basis.

Note: Ensure that you have selected the relevant attributes in the Attributes area to match the selected value for the Archive Criteria Basis.

Enter the values for Archive After Days and Purge After Days.
Click Submit.

Tips And Considerations

To select the Archive Criteria Basis (Creation Date, From Date, To Date, and Issued On), you need to select the matching attributes from the Attributes area under the Document Record Preferences tab. If the matching attributes aren’t selected, you will receive a validation error.
You can only purge document records that are archived.
The document record ID in the HR_DOCUMENTS_OF_RECORD_ARCHIVE table will be the same as the document record ID in the HR_DOCUMENTS_OF_RECORD table. This ensures that the attachments continue to be available for the archived document records as well.
The archived document records in the HR_DOCUMENTS_OF_RECORD_ARCHIVE table will be marked with the archive date.
The archive setting fields are available in HCM Data Loader and HCM Spreadsheet Data Loader.
The archive setting fields and the HR_DOCUMENTS_OF_RECORD_ARCHIVE table will be made available in OTBI for reporting purposes in a future update.
When the Remove Person Information process is run, it removes document records from the HR_DOCUMENTS_OF_RECORD and HR_DOCUMENTS_OF_RECORD_ARCHIVE tables. The archive settings for document records don’t apply to the Remove Person Information process.

Key Resources

For more information, refer to the chapter Document Records in the Using Global Human Resources and Implementing Global Human Resources guides on the Oracle Help Center.

Role And Privileges

You must be granted the Manage HR Document Type function privilege to work on document types.

This table shows the functional privilege that supports this feature and the predefined roles that inherit them.

Functional Privilege Name and Code	Job Role Name
Run Global HR Processes PER_RUN_HR_PROCESSES	Enterprise Scheduler Job Application Identity for HCM Human Capital Management Application Administrator Web Services Application Identity for HCM

Functional Privilege Name and Code

Job Role Name

Run Global HR Processes

PER_RUN_HR_PROCESSES

Enterprise Scheduler Job Application Identity for HCM

Human Capital Management Application Administrator

Web Services Application Identity for HCM

If you are using the predefined roles, no action is necessary. However, if you are using custom versions of these roles, you must add this functional privilege to your custom roles to use this feature. See the Release 13 Oracle Human Capital Management Cloud Security Upgrade Guide on My Oracle Support (Document ID 2023523.1) for instructions about implementing new functions in existing roles.

Move Deleted Document Records to Archive Table

When you create or edit a document type, you can now configure the settings to archive deleted document records instead of permanently deleting them. When the archive setting is enabled, the deleted document records for the document type are moved to the HR_DOCUMENTS_OF_RECORD_ARCHIVE table.

These are the fields used for archive settings:

Archive Criteria Basis: By default this LoV is blank. You can select either the Creation Date, From Date, To Date, or Issued On.
Archive After Days: By default this field is blank. It’s a mandatory field where you enter a number that’s greater than 0 and less than or equal to 18000. For example, if you enter 2, the document records will be archived 2 days after the date selected for Archive Criteria Basis.

Configure Archive Settings to Archive Deleted Document Records

You can retain a deleted document record if you need to recreate the record again.

Steps to Enable

Navigate to the Setup and Maintenance work area.
In the Tasks panel drawer, click Search.
Search and click the Document Types task name.
Click the Create icon in the Search Results area.
Enter the document type and select the category.
Under the Document Record Preferences tab, select the value for Archive Criteria Basis.

Note: Ensure that you have selected the relevant attributes in the Attributes area to match the selected value for the Archive Criteria Basis.

Enter the value for Archive After Days.
Click Submit.

Tips And Considerations

By default, the Archive Criteria Basis isn’t selected in the Document Type setup page, and therefore the deleted document records aren’t moved to the HR_DOCUMENTS_OF_RECORD_ARCHIVE table.
To select the Archive Criteria Basis (Creation Date, From Date, Issued On, and To Date), you need to select the matching attributes from the Attributes area under the Document Record Preferences tab. If the matching attributes aren’t selected, you will receive a validation error.
If you enable the archive setting, the document records are deleted from the HR_DOCUMENTS_OF_RECORD table and moved to the HR_DOCUMENTS_OF_RECORD_ARCHIVE table. The attachments for the document records, if any, will continue to be stored in the FND_ATTACHMENTS table and not moved or deleted.
If you have configured the Purge After Days setting for the document type, then the deleted document records will be permanently removed from the HR_DOCUMENTS_OF_RECORD_ARCHIVE table as part of the archive and purge process.
The archive settings work for document records that are deleted using the Document Records page, HCM Data Loader, HCM Spreadsheet Data Loader, and REST API.
The archived document records in the HR_DOCUMENTS_OF_RECORD_ARCHIVE table will be marked with the archive date.

Key Resources

For more information, refer to the chapter Document Records in the Using Global Human Resources and Implementing Global Human Resources guides on the Oracle Help Center.

Role And Privileges

You must be granted the Manage HR Document Type function privilege to work on document types.

Improved Document Type Description Field Feature is from a customer submitted idea.

You can now compose and format meaningful instructions in the Description field on the Document Type setup page by using rich text format. This enhanced formatting is now available when you create or edit a document type. The character limit of the field is increased from 240 to 4000 characters. Additionally, the formatted content is displayed in the wider read-only Description field on the responsive Document Records page and plugin region for the document type. You can view the read-only Description field when you create or edit a document record.

Format the Content in the Description Field Using Rich Text Formatting When You Create a Document Type

View the Formatted Content in the Read-Only Description Field When You Add a Document Record

View the Formatted Content in the Read-Only Description Field of the Document Records Plugin Section

Enhance the look and feel of the document type description by using rich text formatting. You can use the increased character limit for the Description field to provide detailed meaningful instructions.

Steps to Enable

Navigate to the Setup and Maintenance work area.
In the Tasks panel drawer, click Search.
Search and click the Document Types task name.
Click the Create icon in the Search Results area.
Enter the Type and select the Category.
Enter the description in the Description field.
Click Submit.

Tips And Considerations

This feature is only applicable to the responsive document records flow.
If you add an image in the Description field, it will take up the 4000 character limit specified for the field. Instead, you can use the Reference Info (document type attachments) field to add the image.

Key Resources

For more information, refer to these resources:

Chapter Document Records in the Using Global Human Resources and Implementing Global Human Resources guides on the Oracle Help Center.
Ability to Include Instructional Attachments for Document Types feature in the 21A Global Human Resources What's New.
Display Document Type Description as Instructions feature in the 20B Global Human Resources What's New.

Role And Privileges

You must be granted the Manage HR Document Type function privilege to work on document types.

Enhanced Process for Mass Download of Document Records

We have enhanced the Mass Download of Document Records process by now including these additional features:

A consolidated ESS_O zip output file when you download attachments from the Submitted Mass Download Processes page. There will be a single output file even if the file size is greater than 2 GB.
The ESS_L zip log file is simplified and only contains details of document records that have errors. Document records that have succeeded aren’t displayed in the log file.

Consolidated Zip Output File

Users will have a streamlined experience when they mass download document records.

Steps to Enable

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

Key Resources

For more information, refer to these resources in the Oracle Help Center:

Chapter Document Records in the Using Global Human Resources guide
Chapter Document Records in the Implementing Global Human Resources guide
Mass Download Document Records > Chapter Document Records in the Using Global Human Resources guide

Employment

Workforce Structure Codes Added to Employment Info Page Feature is from a customer submitted idea.

We have enhanced the usability of the Employment Info page with the inclusion of additional fields in the Assignment and Managers sections of the page.

Assignment Section

Bargaining Unit Code
Collective Agreement Code
Department Title
Grade Code
Job Code
Location Code
Position Code
Proposed Start Date (Only for Pending Worker records)

Managers Section

Manager Assignment Number

Additional Code Fields in Assignment Section

Additional Fields in Managers Section

You can accurately identify the work structure and managers associated with the worker assignment. Also, you can view the proposed start date of workers without having to navigate to other pages.

Steps to Enable

By default, the new code fields are hidden out-of-the-box. To enable these fields in the responsive flow, you must use HCM Experience Design Studio. These are the steps to enable the fields in the Employment Info page:

Sign in as an administrator user who has the access to create and manage sandboxes.
Activate a sandbox where you can create a rule in the Transaction Design Studio.

Note: You need to enable the HCM Experience Design Studio and Page Composer options for the sandbox and also enable page-level configuration at the Site level.

On the application Home page, click My Client Groups > HCM Experience Design Studio.
Select the Transaction Design Studio tab.
Select Employment Info from the Actions drop-down list.
Click Add to add a new rule.
Enter a name and description for the rule in the Basic Details section.
In the Page Attributes section, select the region in which you want to enable the fields (for example, Assignment).
For the fields you want to enable, select Visible.

Click Save and Close, and then click Done.
The fields will be enabled in the Employment Info page.

Tips And Considerations

A custom seeded rule named Proposed start date visible for pending worker rule is delivered to display the Proposed Start Date field out-of-the-box only for the pending worker. You can change this behavior by using HCM Experience Design Studio.

Key Resources

For more information, refer to these resources:

Transaction Design Studio – What It Is and How It Works (Document ID 2504404.1) on My Oracle Support.
HCM Experience Design Studio > Chapter Responsive User Experience Setup in the Implementing Global Human Resources guide.

Contextual Job Information Added to Employment Info Page Feature is from a customer submitted idea.

We have improved data visibility by enabling the Job Info section on the Employment Info page. These job attributes are displayed when you enable the section:

Name
Code
Job Family
Job Function
Level
Management Level
Overtime Status
Job Attributes (Descriptive Flexfields (DFF))

Additional Fields in Job Info Section

You can view the assignment job details of workers in the Employment Info page itself without having to navigate to the job details page.

Steps to Enable

By default, the Job Info section is hidden out-of-the-box. To enable this section in the responsive flow, you must use HCM Experience Design Studio. These are the steps to enable the section in the Employment Info page:

Sign in as an administrator user who has the access to create and manage sandboxes.
Activate a sandbox where you can create a rule in the Transaction Design Studio.

Note: You need to enable the HCM Experience Design Studio and Page Composer options for the sandbox and also enable page-level configuration at the Site level.

On the application Home page, click My Client Groups > HCM Experience Design Studio.
Select the Transaction Design Studio tab.
Select Employment Info from the Actions drop-down list.
Click Add to add a new rule.
Enter a name and description for the rule in the Basic Details section.
In the Page Attributes section, select Reference Info Regions from the Region drop-down list.
For the Job Info region, select Visible.

Click Save and Close, and then click Done.
The Job Info section will be enabled in the Employment Info page.

Key Resources

For more information, refer to these resources:

Transaction Design Studio – What It Is and How It Works (Document ID 2504404.1) on My Oracle Support.
HCM Experience Design Studio > Chapter Responsive User Experience Setup in the Implementing Global Human Resources guide.

Role And Privileges

You must be granted the Human Capital Management Application Administrator role to work in a sandbox.

Synchronize Worker Data from Position When Using Worker REST API

We have enhanced the Workers REST service by synchronizing worker data from the position. This synchronization happens when the user has enabled position synchronization.

The workforce structure attributes, such as Job, Location, Department, and other attributes are synchronized from the position when using the Workers REST API.

You can now synchronize worker assignment data from the position using the Workers REST API.

Steps to Enable

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

Tips And Considerations

You need to run the Synchronize Person Assignments from Position process to synchronize the following parameters:

Assignment Flexfields from Position Flexfields
Manager from Position Hierarchy
Manager from Position
Direct Reports from Position Hierarchy
Calculate FTE as per Position Working Hours

Key Resources

For more information, refer to this resource: Position Synchronization > Chapter Jobs and Positions in the Using Global Human Resources guide.

Check Time Cards While Deleting an Assignment

We have enhanced the application by providing a check when an additional assignment is deleted completely. The application checks if a time card exists for the assignment selected for deletion and if yes, stops the delete process and displays an error message. This check applies to the responsive employment details page from where you can completely delete the additional assignment. Additionally, the check is applicable when the user performs a global transfer by using the Local and Global Transfer flow. This is because the global transfer will delete future dated assignments from the source work relationship. This check is not applied when only a date-effective assignment record is deleted.

Error Message in Employment Info Flow When You Delete an Additional Assignment Having a Time Card

Prevent the time card from becoming orphaned by not allowing the associated additional assignment to be deleted.

Steps to Enable

By default, this profile option is set to N. If you don't want the application to prevent deletion of the additional assignment when a time card exists, set the profile value to Y.

Profile Option Code	Profile Display Name	Default Profile Value
ORA_PER_EMPL_DISABLE_TIME_CARD_CHK_CANCEL_WR	Time Card Check Disabled for Cancel Work Relationship and Delete Assignment	N

To change the default profile option value and enable the feature, follow these steps:

Navigate to the Setup and Maintenance work area.
Search for and click the Manage Administrator Profile Values task.
Search for the ORA_PER_EMPL_DISABLE_TIME_CARD_CHK_CANCEL_WR profile option code and select the profile option in the search results.
In the Profile Values area, enter Y in the Profile Value field.
Click Save and Close.

Key Resources

For more information, refer to these resources:

Integration with the Delete Assignment Process in Global Human Resources feature in the 22D Time and Labor What's New
Check Time Cards While Cancelling a Work Relationship feature in the 22C Global Human Resources What’s New

Configurable Business Title Switcher in My Team

You can easily identify the required assignment in My Team by configuring additional assignment attributes to display in the Business Title LoV switcher.

Workers, With Offer, Requisitions, and Vacancies also change according to the selected assignment.

Users working with multiple assignments can accurately identify the assignment that they want to work with.

Steps to Enable

By default, this profile option is set to N. To enable the profile option to use the REST LoV in the Business Title LoV, set the profile value to Y.

Profile Option Code	Profile Display Name	Default Profile Value
ORA_PER_EMPL_ENABLE_WRK_ASG_REST_LOV	Enable Worker Assignment REST LOV	N

To change the default profile option value and enable the action, follow these steps:

Navigate to the Setup and Maintenance work area.
Search for and click the Manage Administrator Profile Values task.
Search for the ORA_PER_EMPL_ENABLE_WRK_ASG_REST_LOV profile option code and select the profile option in the search results.
In the Profile Values area, enter Y in the Profile Value field.
Click Save and Close.

NOTE: If you enable this feature, then the new Business Title LoV will replace the existing Business Title switcher in the My Team page. If you have personalized the Business Title LoV using Page Composer, you need to redo the personalization.

Tips And Considerations

If you enable the Primary attribute, then it will display values of true or false. These values will display only in English language and not in the language set in the user preferences.

Key Resources

For more information, refer to this resource on Oracle Help Center: Business Title Configuration for Multiple Assignments > Chapter Workforce Records in the Using Global Human Resources guide.

Role And Privileges

This table shows the aggregate and function privileges that support this feature and the predefined roles that inherit them.

Privilege Name and Code	Job Role Name	Comments
Use REST Service - Worker Assignments List of Values PER_REST_SERVICE_ACCESS_WORKER_ASSIGNMENTS_LOV	Employee Human Resource Analyst Human Resource Specialist	This aggregate privilege is required to access the Business Title LoV.
Enable Worker Searches Using Effective Dates PER_ENABLE_WORKER_SEARCHES_USING_EFFECTIVE_DATES	Line Manager Human Resource Specialist	This function privilege is required to use the Business Title LoV when you perform search by using an effective date that's different from the system date. For example, if you search using a specific date in advanced search.

Privilege Name and Code

Job Role Name

Comments

Use REST Service - Worker Assignments List of Values

PER_REST_SERVICE_ACCESS_WORKER_ASSIGNMENTS_LOV

Employee

Human Resource Analyst

Human Resource Specialist

This aggregate privilege is required to access the Business Title LoV.

Enable Worker Searches Using Effective Dates

PER_ENABLE_WORKER_SEARCHES_USING_EFFECTIVE_DATES

Line Manager

Human Resource Specialist

This function privilege is required to use the Business Title LoV when you perform search by using an effective date that's different from the system date.

For example, if you search using a specific date in advanced search.

If you are using the predefined roles, no action is necessary. However, if you are using custom versions of these roles, you must add these privileges to your custom roles to use this feature.

Journeys

Secure Journey Category Selection When Creating Journeys

You can use Category Security to control what categories users see when creating templates in the Create Checklist Template page and when creating a personal journey in the Journeys app. For example, you can restrict a line manager to create journeys only of the Compensation category.

You can provide a role access to either of these options:

Specific categories
All categories

Security Configuration Option	Where You Configure This	What This Configuration Determines	Which Page is Impacted	Use Case
Journey Category	Checklist Templates page > Category Security tab > Checklist Categories	Roles that can select this category when creating a journey	Checklists Template setup page when creating global journeys. Create Journeys flow in the Journeys app when creating personal journeys.	Compensation category template to be available only for the Line manager role

NOTE: The ORA_PER_JOURNEY_SECURITY_ENABLED profile option should be set to Y. See Steps to Enable.

To configure security based on a journey template category, follow these steps:

Navigate to the Setup and Maintenance work area or My Client Groups > Employment.
Search for and click the Checklist Templates task or quick action.
Select the category you want to secure and add the necessary role.
Click Save and Close.

Control Access to Journey Template Creation Using Category Security

Determine Access for All Categories or a Specific Category

For example, if you give a line manager role access to the Compensation category, then only a user who has the line manager role will be able to create journeys of the Compensation category in the Journeys app.

Search and Select the Line Manager Role

Add the Line Manager Role

A line manager can only see the Compensation category configured for their role and create personal journeys for that category.

Line Manager Role Can Access the Compensation Category in Journeys

If you give a HR specialist role access to all categories, a user with the HR specialist role can see all the categories when they create a journey template on the Checklist Templates page.

HR Specialist has Access to All Categories

HR Specialist Role can Access All Categories When Creating a Journey

This feature provides the ability to allow your users to create journeys in categories relevant to their business areas.

Steps to Enable

To enable the security feature in journeys, set the profile option ORA_PER_JOURNEY_SECURITY_ENABLED to Y.

Profile Option Code	Description	Default Value
ORA_PER_JOURNEY_ SECURITY_ENABLED Data Security for Journeys Enabled	Enable to apply data security to journey templates and assigned journeys.	N

Profile Option Code

Description

Default Value

ORA_PER_JOURNEY_

SECURITY_ENABLED

Data Security for Journeys Enabled

Enable to apply data security to journey templates and assigned journeys.

To change the default profile option value:

Navigate to the Setup and Maintenance work area.
Search for and click the Manage Administrator Profile Values task.
Search for the ORA_PER_JOURNEY_SECURITY_ENABLED profile option code and select the profile option in the search results.
In the Profile Values area, enter Y in the Profile Value field.
Click Save and Close.

Tips And Considerations

The ability to view and manage journey templates of this category is controlled by the 22D feature: Template Level Security in Journeys,

Key Resources

For more information about Journeys and Checklists, refer to these resources on the Oracle Help Center:

Checklists and Journeys in the Implementing Global Human Resources guide
Checklists and Journeys in the Using Global Human Resources guide

Role And Privileges

This table shows the aggregate privilege that supports this feature and the predefined roles that inherit them.

Aggregate Privilege Name and Code	Duty or Job Role Name and Code
Use REST Service - Journey Categories List of Values PER_REST_SERVICE_ACCESS_JOURNEY CATEGORIES_LOV	Person Configuration (ORA_PER_PERSON_CONFIGURATION_DUTY) Human Capital Management Integration Specialist (ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB)

Aggregate Privilege Name and Code

Duty or Job Role Name and Code

Use REST Service - Journey Categories List of Values

PER_REST_SERVICE_ACCESS_JOURNEY

CATEGORIES_LOV

Person Configuration (ORA_PER_PERSON_CONFIGURATION_DUTY)

Human Capital Management Integration Specialist (ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB)

If you are using the predefined roles, no action is necessary. However, if you are using custom versions of these roles, you must add this aggregate privilege to your custom roles to use this feature.

Template Based Security For Journeys Feature is from a customer submitted idea.

NOTE: To enforce the security configuration you make here, the journey template should be active and the ORA_PER_JOURNEY_SECURITY_ENABLED profile option should be set to Y as indicated in Steps to Enable. In addition, you need to grant users configuring and enforcing security, the ORA_PER_MANAGE_JOURNEY_TEMPLATE aggregate privilege. With this privilege, a role can select the Enable data security check box to enforce security. See the Role section.

You can use Journey Template Operations to control journey template operations per journey template. Depending on the access you provide to a role, users with that role will be able to perform these actions:

Security Configuration Options	Where You Can Do This	Configuration Determines	Which Page is Impacted	Use Case
Journey Template	Specific template > Security tab > Journey Template Operations > Configure Journey checkbox	Controls which roles can manage this journey	Checklists Template setup page and Create Journey page on Journeys app	Onboarding Journey should only be managed by a HR specialist
	Specific template > Security tab > Journey Template Operations > Explore checkbox	Determines which roles can view this journey	Explore tab on Journeys app Allocate Checklists responsive page	Grow Your Career journey should be viewed by employee
	Specific template > Security tab > Journey Template Operations > Assign to Self checkbox	Controls which roles can assign this journey to themselves	Specific journey from the Explore tab	Employee should be able to self-assign Grow My Career journey
	Specific template > Security tab > Journey Template Operations > Assign to Others checkbox	Controls which roles can assign this journey to people in their person security profile	Specific journey from the Explore tab Allocate Checklists responsive page	Line manager should be able to assign Performance Review journey for their team

Securing Journey Templates

You can control different journey template operations for each journey template, based on the roles of a user.

To control journey template operations per template, follow these steps:

Navigate to the Setup and Maintenance work area or My Client Groups > Employment.
Search for and click the Checklist Templates task or quick action.
Create a checklist template.
Click on the Security tab.
Add the required roles and select the necessary check boxes under Journey Template Operations.

NOTE: You should select the Enable data security check box to enforce security.

Click Save and Close.

For example, for a specific Offboarding Journey template, you want a HR specialist to perform all operations, but a line manager to perform only some specific operations. Based on the configuration you make, the user will be able to perform only those configured operations based on their role.

Configure Journey Template Operations Access for HR Specialist and Line Manager

When you configure this, this is what happens:

A HR specialist role can configure the journey template, view this journey on the Explore tab and in LoVs, and assign this journey to themselves and others in their person security profile.
A line manager can view the journey on the Explore tab and in LoVs and assign this journey to others in their person security profile. A line manager cannot configure the journey template and assign this journey to themselves.

HR Specialist Views the Journey on the Explore Tab

HR Specialist has Access to All Operations

Line Manager Can View the Journey on the Explore Tab

Line Manager can Access Only Configured Operations

Securing Assigned Journey by Templates

In the Assigned Journey Operations section you can secure assigned journeys based on a specific journey template. By default, All roles is selected to maintain backward compatibility. However, you can disable the All roles option and add only those roles that should have access to view the journeys assigned based on this template. Roles that are enabled under this section will be able to view the journeys assigned based on this template. The access when configured takes into account the Person Security Profile and the View Assigned security configuration.

Security Configuration Options	Where You Configure This	What This Configuration Determines	Which Page is Impacted	Use Case
Assigned Journeys	Specific template > Security tab > Assigned Journey Operations	Control which roles can view assigned journeys, that are based on this journey, to persons in their person security profile	My Journeys tab in Journeys app Assigned Journeys tab in Journeys app Allocate Checklists responsive page REST Get method	Employee and HR specialist only should be able to view Vaccination Journey, not Line manager

To secure assigned journeys based on a specific journey template, follow these steps:

Navigate to the Setup and Maintenance work area or My Client Groups > Employment.
Search for and click the Checklist Templates task or quick action.
Create or modify a checklist template.
Click on the Security tab.
Add the required roles and select the necessary check boxes in Assigned Journey Operations.

NOTE: You should select the Enable data security check box to enforce security.

Click Save and Close.

For example, you want to display an assigned journey based on a Vaccination Journey template only to an employee and HR specialist but don't want the line manager to view this journey. Based on the configuration illustrated below it will display an assigned journey based on the template only to the two roles configured in the Assigned Journey Operations section.

Configuration to Display Assigned Journey Only to HR Specialist and Employee

HR Specialist Can View Assigned Journey for Employee

Employee Can View Assigned Journey

This feature enables you to selectively decide which roles can view which journeys. For example, you can prevent managers from viewing the vaccination journey.

You can also control which journey users can assign to themselves. For example, an employee can only view and assign journeys related to growing their career.

Steps to Enable

To enable the security feature in journeys, set the profile option ORA_PER_JOURNEY_SECURITY_ENABLED to Y.

Profile Option Code	Description	Default Value
ORA_PER_JOURNEY_ SECURITY_ENABLED Data Security for Journeys Enabled	Enable to apply data security to journey templates and assigned journeys.	N

Profile Option Code

Description

Default Value

ORA_PER_JOURNEY_

SECURITY_ENABLED

Data Security for Journeys Enabled

Enable to apply data security to journey templates and assigned journeys.

To change the default profile option value:

Navigate to the Setup and Maintenance work area.
Search for and click the Manage Administrator Profile Values task.
Search for the ORA_PER_JOURNEY_SECURITY_ENABLED profile option code and select the profile option in the search results.
In the Profile Values area, enter Y in the Profile Value field.
Click Save and Close.

Tips And Considerations

Security configuration applies to the Journeys app and Allocate Checklists quick action, but not to the Onboarding and Checklist Tasks apps.
If you activate the Enable data security check box in the Security tab of your existing templates, but don't enable the profile option ORA_PER_JOURNEY_SECURITY_ENABLED for security, then no security is applied at the template level and at the assigned journey level.
If the ORA_PER_JOURNEY_SECURITY_ENABLED profile option is set to Y but you don’t select the Enable data security check box in the Security tab of the checklist template, then no security is applied at the template level and at the assigned journey level.
If you duplicate a journey that has security configured, the security configuration is copied as well.
If you duplicate a journey template and save it as a personal journey, the journey template and view assigned security details won’t be copied. You can still view the personal journey on the Explore tab and take actions such as Assign to Self, Assign to Others, Edit, Delete, and Force Complete of the personal journey.
Any security configuration you make in a journey template can’t be exported or imported in the Functional Setup and Manager (FSM). However, you can export or import the template and then reconfigure the security configuration.
Security configuration isn’t exported or imported when you Export and Import journey templates on the Checklist Template page. However, you can export or import the template and then reconfigure the security.
Template level and assigned journey level security configuration isn’t supported in HDL currently.
Syncing security configuration updates to assigned journeys using the Update Assigned Journey Attributes Based on Modified Journey Template ESS process isn’t supported currently.

Key Resources

For more information about Journeys and Checklists, refer to these resources on the Oracle Help Center:

Checklists and Journeys in the Implementing Global Human Resources guide
Checklists and Journeys in the Using Global Human Resources guide

Role And Privileges

This table shows the aggregate privilege that supports this feature and the predefined roles that inherit them.

Aggregate Privilege Name, Code and Description	Duty or Job Role Name, Code and Description
Manage Journey ORA_PER_MANAGE_JOURNEY_TEMPLATE Allows the user to manage the journeys to which they have been granted access.	Person Configuration ORA_PER_PERSON_CONFIGURATION_DUTY Manages person types, name formats, checklists, and document types.
View Journey ORA_PER_VIEW_JOURNEY_TEMPLATE Allows the user to explore the journeys to which they have been granted access.	View Worker Journey ORA_PER_VIEW_JOURNEY Allows users to access and view worker journeys. Manage Journey By Manager ORA_PER_MANAGE_JOURNEY_BY_MANAGER Allows managers to access and manage worker journeys. Manage Journey By HR ORA_PER_MANAGE_JOURNEY_BY_HR Allows HR specialists to access and manage worker journeys.

Aggregate Privilege Name, Code and Description

Duty or Job Role Name, Code and Description

Manage Journey

ORA_PER_MANAGE_JOURNEY_TEMPLATE

Allows the user to manage the journeys to which they have been granted access.

Person Configuration

ORA_PER_PERSON_CONFIGURATION_DUTY

Manages person types, name formats, checklists, and document types.

View Journey

ORA_PER_VIEW_JOURNEY_TEMPLATE

Allows the user to explore the journeys to which they have been granted access.

View Worker Journey

ORA_PER_VIEW_JOURNEY

Allows users to access and view worker journeys.

Manage Journey By Manager

ORA_PER_MANAGE_JOURNEY_BY_MANAGER

Allows managers to access and manage worker journeys.

Manage Journey By HR

ORA_PER_MANAGE_JOURNEY_BY_HR

Allows HR specialists to access and manage worker journeys.

This table shows existing privileges that are modified to support features in this update.

Privilege Type, Name, Code and Description	What has changed
Duty Role View Worker Journey ORA_PER_VIEW_JOURNEY Allows users to access and view worker journeys.	The role name has been changed from View Journey to View Worker Journey.
Function Privilege Manage Journey PER_MANAGE_CHECKLIST_TEMPLATE Allows management of journey templates.	The privilege name has been changed from Manage HR Checklist Template to Manage Journey. The privilege description has been changed from Allows management of checklist templates. to Allows management of journey templates.
Function Privilege Manage Personal Journey PER_MANAGE_JOURNEY Allows users to create and manage personal journeys.	The privilege name has been changed from Manage Journey to Manage Personal Journey. The privilege description has been changed from Allows users to create and manage journeys. to Allows users to create and manage personal journeys.

Privilege Type, Name, Code and Description

What has changed

Duty Role

View Worker Journey

ORA_PER_VIEW_JOURNEY

Allows users to access and view worker journeys.

The role name has been changed from View Journey to View Worker Journey.

Function Privilege

Manage Journey

PER_MANAGE_CHECKLIST_TEMPLATE

Allows management of journey templates.

The privilege name has been changed from Manage HR Checklist Template to Manage Journey.

The privilege description has been changed from Allows management of checklist templates. to Allows management of journey templates.

Function Privilege

Manage Personal Journey

PER_MANAGE_JOURNEY

Allows users to create and manage personal journeys.

The privilege name has been changed from Manage Journey to Manage Personal Journey.

The privilege description has been changed from Allows users to create and manage journeys. to Allows users to create and manage personal journeys.

Advanced Journey Task Type Using Combination of Different Task Types Feature is from a customer submitted idea.

You can now leverage the new Advanced task type that lets you combine a maximum of 3 task types as a single task. For example, you can combine a video, questionnaire, and an e-signature task if you want a new hire to watch a video, answer a questionnaire, and electronically sign an agreement as part of their onboarding.

Advanced Task Setup

You can select the check box next to each of the task types listed in the Create Tasks page when you set up the Advanced task. The order of the task types in the setup page and in an assigned task will be the same:

Document
External URL
Application Task
Video
Embedded Learning
Questionnaire
Configurable Form
Electronic Signature
Report

If you enable Comments and Attachments, it appears after the last task in the advanced task.

Combination of Video, Questionnaire, and Electronic Signature Tasks

Video, Questionnaire, and Electronic Signature in Assigned Journey Task

Video, Questionnaire, and Electronic Signature in Allocated Checklist Task

This feature reduces the need to create separate tasks and makes it easier to track and update details in a single task.

Steps to Enable

To create an advanced task:

Create a task and select Advanced Task as the task type.
Select a maximum of 3 task types listed in the section.
Specify the details based on the respective task types.
Click Save and Close.

Tips And Considerations

You can only select maximum of 3 tasks to combine.

If there’s a single advanced task in the journey, it is expanded by default.

These features are common for the task types being combined in an advanced task:
- Performer and Owner. Each individual task that is combined can't have a different performer and owner.
- Buttons such as Done, Not Applicable, and so on.
- Comments and Attachments section.
- Notes Header and Notes section. Anything you want to add for all the sub-tasks needs to be part of the single notes section that appears right on top of the advanced task.
- Contact info section.
- Rename Action labels section in Display Properties. All action labels for all the task types being combined are listed.

You can configure an advanced task type in the task library.

You can add an advanced task from the task library to an assigned journey.

An advanced task type is supported as a part of a journey template in the following operations:
- Export and Import of a single checklist template.
- Functional Setup Manager (FSM) Export and Import of checklist configuration.
- Duplicate Checklist Template.
- Add Task From Task Library.
- Add Task to Task Library.
- HCM Data Loader (HDL).

The following limitations apply for an advanced task type:
- Can't be created from the Journeys app.
- Can't be used in Guided Journeys.
- Doesn't allow DocuSign, I-9, and OPA task types.
- Doesn't allow the order to be specified. The task types that you select display in the order that they appear on the checklist task setup page.

Key Resources

For more information about Journeys and Checklists, refer to these resources on the Oracle Help Center:

Checklists and Journeys in the Implementing Global Human Resources guide
Checklists and Journeys in the Using Global Human Resources guide

Role And Privileges

You must be granted the Manage Journey (PER_MANAGE_CHECKLIST_TEMPLATE_PRIV) function privilege to work on checklist templates.

Parameterized Deep Links for Journeys Feature is from a customer submitted idea.

Make use of the parameters supported in Journeys deep links to directly go to specific application pages without additional clicks or navigation.

This table lists the deep links by use case.

Deep Link	Purpose	Parameters
https://<server_host>/hcmUI/hcm/vp/journey?tab=<tab_name>	Easily go to a specific tab in Journeys. For example, create a landing page deep link that shows all journey templates on the Explore tab	tab=<tab_name> tab=explore tab=myJourneys tab=myTasks tab=assignedJourneys tab=activity
https://<server_host>/hcmUI/hcm/vp/journey?tab=<tab_name>&searchTerm=<search_term>	Easily land on a specific tab with the search pre-populated with the searchTerm parameter value. For example, create a landing page deep link that shows all journey templates on the Explore tab where journey name starts with ‘Onboard’	searchTerm=<search_term> For Explore tab, searchTerm parameter value supports journey name For My Journeys tab, searchTerm parameter value supports journey name For My Tasks tab, searchTerm parameter value supports task name For Assigned Journeys tab, searchTerm parameter value supports journey name or person name For Activity tab, searchTerm parameter value supports journey name Note: This parameter works only in conjunction with the tab parameter.
https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=exploreJourneys&category=<Category_Code> https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=exploreJourneys&category=<Category_Code>&subCategory=<SubCategory_Code>	Easily land on a specific tab with journeys filtered by a specific category or a sub-category	pageName=exploreJourneys Note: This pageName parameter works only in conjunction with parameter of category=<Category_Code> or subCategory=<Subcategory_code>
https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=myJourneys&category=<Category_Code> https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=myJourneys&category=<Category_Code>&subCategory=<SubCategory_Code> https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=myJourneys&category=<Category_Code>&subCategory=<SubCategory_Code>&status=<Status_Code> https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=myJourneys&category=<Category_Code>&status=<Status_Code> https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=myJourneys&journeyCode=<Journey_Code> https://<server host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=myJourneys&journeyCode=<Journey_Code>&status=<Status_Code>	Directly list assigned journeys of a specific category, sub-category, journey code and statuses for the signed-in user on the My Journeys tab	pageName=myJourneys Note: This pageName parameter works only in conjunction with parameters of category=<Category_Code> or subCategory=<Subcategory_code> or status=<Status_Code> or journeyCode=<Journey_Code>
https://<server_host>/hcmUI/hcm/vp/journey/journey-redirect?pageName=journeyDetails&journeyCode=<Journey_Code>	Directly view details of a specific journey and use the allowed actions to assign the journey to themselves or to others	pageName=journeyDetails Note: This pageName parameter works only in conjunction with parameter of journeyCode=<Journey_Code>
https://<server_host>/hcmUI/hcm/vp/journey/journey-details?journeyId=<Journey_id>	Directly view details of a specific journey and use the allowed actions to assign the journey to themselves or to others	journeyId=<Journey_id>
https://<server_host>/hcmUI/faces/deeplink?objType=EMP_CHECKLIST&action=NONE&objKey=checklistCode=<Journey_Code> https://<server_host>/hcmUI/faces/deeplink?objType=EMP_CHECKLIST&action=NONE&objKey=checklistCode=<Journey_Code>;checklistStatus=<Status_Code>	View the latest assigned journey of a specific recurring journey or survey	checklistCode=<Journey_Code> checklistStatus=<Status_Code>

This table summarizes the different parameters used across multiple deep links:

Parameter	Type	Description
tab	String	The tabs that appear on the Journeys app.
searchTerm	String	Search string. Search terms will vary based on the tab being referenced.
pageName	String	The only values supported are exploreJourneys, myJourneys and journeyDetails
category	String	Category of the checklist. For example, ONBOARD, ORA_PERSON, ORA_SURVEY and so on. If category parameter isn’t passed, journeys of all categories are displayed.
subCategory	String	Lookup code for the Survey Subcategory lookup. These are the only values supported for the subcategory parameter when the category parameter is ORA_SURVEY. ORA_CHK_TOUCHPOINT_SURVEY ORA_CHK_GENERAL_SURVEY
status	String	These are the only values supported for the Status parameter. ORA_OPEN - indicates all open assigned journeys. ORA_CLOSED - indicates all completed assigned journeys. If Status parameter isn’t passed, both open and completed assigned journeys display.
journeyCode	String	Unique alphanumeric identifier for the journey template. This is auto generated based on the journey name when the journey template is created and displayed in the checklist template page.
journeyId	Number	Unique numeric identifier for the journey template.
checklistCode	String	Unique alphanumeric identifier for the checklist template. This is auto generated based on the checklist name when the checklist template is created and displayed in the checklist template page.
checklistStatus	String	These are the only values supported for the Status parameter. ORA_OPEN - indicates all open assigned journeys. ORA_CLOSED - indicates all completed assigned journeys. If Status parameter isn’t passed, both open and completed assigned journeys display.

This feature provides easy navigation and thereby saves time and improves user experience.

Steps to Enable

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

Key Resources

For more information about Journeys and Checklists, refer to this resource on the Oracle Help Center: Chapter Checklists and Journeys in the Implementing Global Human Resources guide.

Surveys in Journeys

You can now use Survey Journeys to create a survey and assign it to people in your organization. For example, regular pulse surveys to seek feedback on workplace satisfaction or a general survey to provide feedback on the onboarding process.

Before you create the journey of the category Survey, you should have defined a questionnaire to associate to the following survey subtypes:

Survey subtype	Questionnaire Subscriber	Where to view survey results
General	Journey Surveys	Create your own BI report
Touchpoints	Touchpoints	Use Touchpoints dashboard

For more information on defining questionnaires for surveys, see the 22D Talent What's New: Enhanced Presentation Options for New Subscribers.

To configure the survey journey, you need to do the following:

Create the Survey Journey in Checklist Templates with the new category Survey. Specify the survey subtype as either General or Touchpoints.

Configure Survey Journey in Checklist Templates

The survey template allows only one task of the type Survey. Associate the predefined questionnaire to the task. For the Touchpoints survey subtype, only Touchpoints subscriber based questionnaires are listed in the Questionnaire list of values. Similarly, for the General survey subtype, only Journey Survey subscriber based questionnaires are listed in the Questionnaire list of values.

Associate Predefined Questionnaire to Survey Task

Configure the criteria at the survey journey level. When assigning the journey, only those persons who meet the criteria will be assigned the survey journey. For example, a survey journey specific to a legal employer and business unit.

Configure Criteria for Survey Task

You can configure the periods during which you want to allocate the survey journey. Configure this duration in the Schedule Allocation tab of the survey journey. The survey period is mandatory and needs to be configured irrespective of whether the survey is allocated one-time or over a recurring period of time. Survey allocations, both recurring or one-time, can only happen for the active periods defined in the survey definition.

Schedule Allocations for Survey Journey

Schedule Allocation

Specify the frequency to assign the survey journey by selecting one of these recurrence options:

Day
Week
Calendar month
Year
Specific date

When you click Generate, based on the date and frequency you specify, the periods are auto- generated. If you regenerate the period after some of the periods are completed, only future periods will be regenerated. Completed periods in the past can't be updated. Within a period, you may want to assign the survey journey once or more than once. The Number of Runs Per Period drop-down list enables you to specify that. On completion of a period, the survey journey automatically expires.

Note: You need to carefully review before making any changes to the frequency in an already assigned survey journey. Any change to the frequency, will impact any reporting you may have configured for the survey journey.

II. Period Summary

The period summary is auto-generated based on the frequency you select. The periods are Active by default. If you don’t want the survey journey to be assigned during a specific period, you can deselect Active.

111. Reporting Attributes

Configure the attributes for reporting. To compute survey responses, you can specify the analysis period in days, weeks, months, or years. You can set the threshold against which to measure the survey response scores.

When you assign a survey journey in the Assign Journeys flow in Journeys, you can choose these Repeat options:

As per schedule - Assigns the survey journey in the respective period under which the assignment date falls.
Never – Assigns the survey journey on an ad hoc basis but the date needs to fall within a specific period.

Allocate Scheduled Journeys ESS Process

The Allocate Scheduled Journey ESS process which runs daily automatically assigns the journey. If it’s a recurring survey journey, the process checks for new population within that period and assigns the survey journey only to them.

Schedule Allocations

Review Scheduled Allocations

Administrators can use the Scheduled Allocations tab in the Checklist Templates page to review the status of scheduled survey journeys. If a particular allocation needs an update, administrators can drill-down to that allocation and make changes by deselecting a person or period.

Scheduled Allocations Tab in Checklist Templates

List of Allocations by Status in Scheduled Allocations Tab

Survey Title and Completion Message

Use the Message tab of the survey journey template to configure the title, subtitle, and completion message that displays to the worker when the survey journey is assigned.

Configure Survey Title, Subtitle, and Completion Message

Title and Subtitle in Assigned Survey Journey

Message on Survey Journey Completion

Employee Experience

When an employee is assigned a survey journey, they receive a notification. They can also see the survey journey in their My Journeys tab. They can then respond and submit the survey journey.

Survey Journey Displays in My Journeys

Employee Responds to Survey Questionnaire

This feature provides an end-to-end survey mechanism that enables you to not just create and send surveys but also analyze and report on the survey results.

Steps to Enable

To create a survey journey:

Create a checklist template and select Surveys as the journey category.
Select the survey subtype.
Associate the predefined questionnaire to the survey task.
Specify other details.
Click Save and Close.

Tips And Considerations

This feature is available only in the Journeys app. It is not available on the responsive Checklist and Onboarding pages.
You can configure survey journeys from the Checklist Templates setup page.
The Create Journey button in the Explore tab on Journeys doesn't support creation of survey journeys. You can’t create personal journeys of the Survey category.
You can’t change the category of an existing journey to Survey Journey. Instead, define a new survey journey.
The attributes available for configuring a survey journey are different than the regular journey setup.
The My Tasks tab in Journeys app doesn’t display the survey task.
You can only assign survey journeys in the active periods defined in the schedule of a survey journey.
The Repeat drop-down in the Assign Journey flow in Journeys is available only for survey journeys.
The journey survey is rendered based on the way the questionnaire is configured. A questionnaire can display one question per page, one section per page, or all questions on a single page.
Touchpoints surveys are distributed only through Journeys at this point.
You should have enabled Journeys to use Touchpoints surveys.
The Reporting Attributes details are only applicable to Touchpoints surveys currently.

Key Resources

For more information on Touchpoints, see the 22D Talent What’s New: Introducing Oracle Touchpoints.
For more information on journeys, refer to this resource on the Oracle Help Center: Chapter Checklists and Journeys in the Implementing Global Human Resources guide.

Role And Privileges

You must be granted the Manage Journey (PER_MANAGE_CHECKLIST_TEMPLATE_PRIV) function privilege to work on checklist templates.

Guided Journeys for Compensation Flows

In continuation of the Guided Journeys to Assist Complex HCM Flows feature introduced in 22B, you can now configure guided journeys for more Compensation actions using Transaction Design Studio (TDS) rules.

The list of additional actions supported are:

TDS Action	Comments
My Compensation	Page level and section level guided journey supported.
Compensation Info	Page level and section level guided journey supported.
Salary History	Page level and section level guided journey supported.

This feature provides guidance to users in the context of the transactions they perform based on their role.

Steps to Enable

To view guided journeys, set the profile option ORA_PER_GUIDED_JOURNEYS_ENABLED to Y.

Profile Option Code	Description	Default Value
ORA_PER_GUIDED_ JOURNEYS_ENABLED Enable Guided Journeys	Enable the user interface for guided journeys.	N

Profile Option Code

Description

Default Value

ORA_PER_GUIDED_

JOURNEYS_ENABLED

Enable Guided Journeys

Enable the user interface for guided journeys.

To change the default profile option value follow these steps:

Navigate to the Setup and Maintenance work area.
Search for and click the Manage Administrator Profile Values task.
Search for the ORA_PER_GUIDED_JOURNEYS_ENABLED profile option code and select the profile option in the search results.
In the Profile Values area, enter Y in the Profile Value field.
Click Save and Close.

Tips And Considerations

Guided journeys can be configured only from the Checklist Templates setup page.
You can't change the category of an existing journey to Guided Journey. Instead, define a new guided journey.
The Create Journey button in Explore tab on Journeys doesn't support creation of guided journeys.
Guided journeys are supported only in ADF pages and not on VBCS pages.
Supported task types in a guided journey are Analytics, Document, Embedded Learning, External URL, Manual Task, Questionnaire, Report, and Video.
The attributes available for configuring a guided journey are different than the regular journey setup.
A new subscriber code is available for Guided Journeys in Questionnaires to store the responses provided.
You can configure the rule in TDS even if the guided journey profile option is set to N. Guided journeys won't be displayed in the Explore, My Journeys, My Tasks, and Assigned Journeys tabs.
It's recommended to use only one guided journey per TDS action.
A recommended best practice when creating multiple guided journeys and adding in TDS is to follow a naming convention to help identify the guided journey. Something like this: actionName_ruleConfigParams_pageLevel or actionName_ruleConfigParams_sectionName. For example, Transfer_Employee_Page or Transfer_USManager_AssignmentDetails.

Key Resources

For more information, refer to these resources on the Oracle Help Center:

Chapter Checklists and Journeys in the Using Global Human Resources guide
Chapter Checklists and Journeys in the Implementing Global Human Resources guide

For more information on contextual journeys, see Quick Guide: Contextual and Guided Journeys on Customer Cloud Connect.

Use Transaction Design Studio to Configure Field Displays, Chapter Responsive User Experience Setup in the Implementing Global Human Resources guide
Transaction Design Studio -What It Is and How It Works (Document ID 2504404.1)

Role And Privileges

You must be granted the Manage Journey (PER_MANAGE_CHECKLIST_TEMPLATE_PRIV) function privilege to work on checklist templates.
You must be granted the Access HCM Common Components function privilege to view guided journeys on the transaction pages.

Contextual Journeys for Compensation Flows

In continuation of the Contextual Journeys to Orchestrate Business Processes feature introduced in 22B, you can now use additional Compensation quick actions that are available when configuring contextual journeys that need to be performed by different performers before a HR transaction.

Based on the contextual journey setup, when you initiate a specific HR quick action from either Me, My Team, or My Client Groups, a single contextual journey or a list of eligible contextual journeys displays. You can then start the relevant contextual journey.

The list of additional Compensation quick actions now supported in the Contextual Journeys are:

Category	Quick Action Name
Me	My Compensation
My Team	Change Salary
My Team	Compensation Info
My Team	Individual Compensation
My Team	Team Compensation
My Client Groups	Administer Compensation
My Client Groups	Change Salary
My Client Groups	Compensation Info
My Client Groups	Individual Compensation
My Client Groups	Salary History

This feature enables you to orchestrate the different activities that need to be done as part of a business process.

Steps to Enable

You need to enable contextual journeys using the new ORA_PER_CONTEXTUAL_JOURNEYS_ENABLED profile option. Set the profile option value to Y.

Profile Option Code	Description	Default Value
ORA_PER_CONTEXTUAL_ JOURNEYS_ENABLED Enable Contextual Journeys	Enable contextual journeys user interface.	N

Profile Option Code

Description

Default Value

ORA_PER_CONTEXTUAL_

JOURNEYS_ENABLED

Enable Contextual Journeys

Enable contextual journeys user interface.

To change the default profile option value follow these steps:

Navigate to the Setup and Maintenance work area.
Search for and click the Manage Administrator Profile Values task.
Search for the ORA_PER_CONTEXTUAL_JOURNEYS_ENABLED profile option code and select the profile option in the search results.
In the Profile Values area, enter Y in the Profile Value field.
Click Save and Close.

Tips And Considerations

You need to configure the required Application Task (quick action) in your journey template so that the user can perform it as part of the contextual journey. For example, when you are defining a contextual journey for Change Salary, include an application task that invokes the Change Salary. This will ensure that the person performing the transaction can perform a Change Salary.

You can configure Contextual journeys only from the Checklist Templates setup page.

You can't change the category of an existing journey to Contextual Journey. Instead, define a new contextual journey.

The attributes available for configuring a contextual journey are different than the regular journey setup. For example, you can’t configure an eligibility profile at the checklist or task level for contextual journeys.

The attributes in the Configure Criteria section will vary for each contextual action.

The DocuSign, I-9, and OPA task types aren’t supported in contextual journeys.

The processing mode for contextual journeys is set to Alerts based notifications by default and BI Publisher notifications aren’t supported.

Continue Without Journey button on the Contextual Journey Gallery page is controlled using a security privilege. See the Role section.

Contextual journeys won't be displayed in the Explore, My Journeys, and Assigned Journeys tabs.

The My Tasks tab in Journeys displays tasks from contextual journeys.

The Create Journey button in the Explore tab doesn't support creation of contextual journeys.

Only a limited set of quick actions are currently supported for configuring contextual journeys.

The application task configured within the contextual journey is always launched in the context of the primary assignment. This is true even if a non-primary assignment is selected for the quick action which triggers the contextual journey.

Key Resources

For more information, refer to these resources on the Oracle Help Center:

Chapter Checklists and Journeys in the Using Global Human Resources guide
Chapter Checklists and Journeys in the Implementing Global Human Resources guide

For more information on contextual journeys, see Quick Guide: Contextual and Guided Journeys on Customer Cloud Connect.

Role And Privileges

You must be granted the Manage Journey (PER_MANAGE_CHECKLIST_TEMPLATE_PRIV) function privilege to work on checklist templates.

This table shows the function security privilege that supports this feature and the predefined role that inherits this privilege.

Function	Duty Role	Job or Abstract Role
Bypass Contextual Journeys PER_BYPASS_CONTEXTUAL _JOURNEYS_PRIV	Manage Contextual Journey by HR ORA_PER_MANAGE_ CONTEXTUAL_JOURNEY_ BY_HR	Human Resource Specialist

Function

Duty Role

Job or Abstract Role

Bypass Contextual Journeys

PER_BYPASS_CONTEXTUAL

_JOURNEYS_PRIV

Manage Contextual Journey by HR

ORA_PER_MANAGE_

CONTEXTUAL_JOURNEY_

BY_HR

Human Resource Specialist

Person

Last Updated By and Last Updated Date Fields Added to Personal Info Responsive Pages

We have improved the user experience by adding the Last Updated By and Last Updated Date fields in the Transaction Design Studio for the Personal Details, Contact Info, Identification Info, Family and Emergency Contacts, and Person Identifiers for External Applications responsive pages.

Last Updated By and Last Updated Date Fields Added to Transaction Design Studio

This feature improves data visibility in the Personal Details, Contact Info, Identification Info, Family and Emergency Contacts, and Person Identifiers for External Applications responsive pages with the addition of these 2 fields.

Steps to Enable

The Last Updated By and Last Updated Date fields are hidden out-of-the-box on the Personal Details, Contact Info, Identification Info, Family and Emergency Contacts, and Person Identifiers for External Applications responsive pages. Use these steps to enable the Last Updated By and Last Updated Date fields in the Transaction Design Studio. In this example, we will enable the fields on the Personal Details responsive page. As a prerequisite, you must be in a sandbox to work in the HCM Experience Design Studio.

Navigate to Home > My Client Groups > HCM Experience Design Studio.
Click Transaction Design Studio and select the Personal Details action.
Click Add.
Enter a name and description for the rule.
In the Page Attributes section, select any data source.
Make the Last Updated By and Last Updated Date fields visible.
Click Save and Close.

Key Resources

For more information refer to these resources on the Oracle Help Center.

Transaction Design Studio – What It Is and How It Works (Document ID 2504404.1) on My Oracle Support
HCM Experience Design Studio in the chapter Responsive User Experience Setup in the Using Common Features for HCM guide.

Person Name Formats Validation Updated

A new validation has been added to the Person Name Formats task in the Setup and Maintenance work area to prevent a user from creating a global person name format with a legislation code.

Users will have one version of the global name across all countries.

Steps to Enable

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

Key Resources

For more information, refer to the Oracle Help Center for this topic: Person Name Formats in the Chapter Person in the Implementing Global Human Resources guide.

Prepare for Increase to the PER_ADDRESSES_F attribute TOWN_OR_CITY to 60 Characters in Update 23A

In Update 23A, the field length of the TOWN_OR_CITY attribute in the PER_ADDRESSES_F table will be increased from 30 characters to 60 characters. This is so that the data entered into the TCA Geography data for a Town or City with greater than 30 characters can be saved without error in the PER_ADDRESSES_F table. This change will apply to all addresses saved within HCM, not limited to a person's address, but also the work location address, Health and Safety Incident address, a Candidate address. Please analyze your integrations that reference this attribute and make any necessary changes so that when the data model change is made in update 23A, it doesn't negatively impact the behavior.

These are some of the instances where this change may have an impact.

If your BIP report is designed for only 30 characters for Town or City attribute, then you may need to adjust your report layout and extend it to 60 characters.

If you have an application extract that references the Town or City and the application that receives the output file can't handle 60 characters for the Town or City, you may need to adjust your system extract layout to limit it to your downstream application field size.

If you're implementing an integration, and using the Town or City attribute in any of the Workers, Public Workers, Locations V2, HCM Contacts, Recruiting Candidates, or Recruiting CE Candidate Details, REST API, you may need to adjust your integration.

If you're displaying the Town or City attribute in any of your custom application pages, then you may need to adjust the attribute length to fit 60 characters.

This feature will improve the user experience with how addresses are stored in the application.

Steps to Enable

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

Key Resources

For additional information, refer to the following resource on My Oracle Support: Fusion Global HR: TOWN_OR_CITY From PER_ADDRESSES_F Table Attribute Size Change Starting with 23A (Doc ID 2870877.1).

Work Structures

Configure Default Effective Start Date for Work Structure Objects Feature is from a customer submitted idea.

You can now specify a default effective start date to be used on these responsive and classic workforce structure pages, if an effective start date isn't specified in the search pages.

Responsive Pages

Request a New Position
Position Details > Add
Job Details > Add
Location Details > Add

Classic Pages

Manage Positions
Manage Job
Manage Job Families
Manage Locations
Manage Departments
Manage Divisions
Manage Disability Organizations
Manage Reporting Establishments
Manage Worker Unions
Manage Grades
Manage Grade Ladders
Manage Grade Rates

How You Specify the Default Effective Start Date

You need to specify the default effective start date for workforce structures on the Manage Enterprise HCM Information page.

Navigate to Home > Workforce Structures > Manage Enterprise HCM Information page.
Click Update.
Click OK.
In the Workforce Structures Configuration section, select the Default Effective Start Date.

Click Submit.
Click Yes.
Click OK.

When you set a default effective start date, the above mentioned flows inherit the effective start date from the enterprise configuration.

This feature provides an ability to set a default effective date to be used for responsive and classic pages in a consistent manner while creating workforce structure objects.

Steps to Enable

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

Tips And Considerations

This table lists the behavior of the effective date on responsive and classic pages in certain scenarios.

Scenario	Behavior in Responsive Pages	Behavior in Classic Pages
Default Effective Start Date field on the Manage Enterprise HCM Information page is blank and an effective date isn't specified on the search pages.	Current date is defaulted when creating a new workforce structure.	1-Jan-1951 is defaulted when creating a new workforce structure.
Default Effective Start Date field on the Manage Enterprise HCM Information page is blank and an effective date is specified on the search pages.	Current date is defaulted when creating a new workforce structure.	When you search for a workforce structure using an effective date, then this date is defaulted when creating a new workforce structure from the search page.
Default Effective Start Date field on the Manage Enterprise HCM Information page isn't blank and an effective date is specified on the search pages.	Configured default date specified for the enterprise is defaulted when creating a new workforce structure.	When you search for a workforce structure using an effective date, then this date is defaulted when creating a new workforce structure from the search page.
Default Effective Start Date field on the Manage Enterprise HCM Information page isn't blank and an effective date isn't specified on the search pages.	Configured default date specified for the enterprise is defaulted when creating a new workforce structure.	Configured default date specified for the enterprise is defaulted when creating a new workforce structure.

This feature doesn't apply to HCM Data Loader (HDL), HCM Spreadsheet Data Loader (HSDL), and REST.
The Default Effective Start Date field is non-date effective. Any changes in this value will be reflected in all date-effective records.
Even if the effective start date is defaulted from the value specified in the enterprise configuration, you can override this value in the create flows.
You can specify a future date also as default effective start date.

Key Resources

For more information, refer to this topic on the Oracle Help Center:

Workforce Structures Enterprise-Level Configuration topic in the Workforce Structures - Configuration Options chapter of the Implementing Global Human Resources guide.

Role And Privileges

You must be granted the Human Capital Management Application Administrator role to work in setup and maintenance area.

Prevent Inflight Job Transaction Updates When Using HCM Data Loader

You can now prevent inflight job updates when using HCM Data Loader (HDL) or HCM Spreadsheet Data Loader (HSDL) when approvals are pending for the same.

This feature is applicable in these scenarios.

When a job is updated (update and correct flows)
When a date effective job record is deleted

Let's understand how this works. In this example, approvals are enabled for the Edit Job process and a job, Accounts Manager is updated with a new job family.

While approvals are pending for the job updates made on the job pages, changes are loaded for the same job using HDL.

Because approvals are pending, a conflict is detected in the data load, which fails showing a validation error.

Click the message to see the details.

This feature will reduce the errors due to overlap of updates made to the same job record using HDL or HSDL and job pages when approvals are enabled. In addition, approvers won't encounter errors because of the inflight updates. Scope of duplicate updates made using the application and HDL or HSDL are removed thereby ensuring less rework.

Steps to Enable

You need to create (if it doesn't exist) and set the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option and set it to No. Setting this profile option to No will prevent inflight job transaction updates using HDL or HSDL when changes to a job are pending approval.

Use these steps to create and set the profile option.

On the Home page, navigate to Setup and Maintenance work area.
Search and select the Manage Profile Options task.
In the Search Results: Profile Options section, click the New icon.
On the Create Profile Option page, enter these details

Field	Value
Profile Option Code	HR_DISABLE_PENDING_APPROVALS_CHECK_IN HCM_DATA_LOADER
Profile Option Display Name	HR: Disable pending approvals check in HCM Data Loader
Application	Global Human Resources
Module	Employment
Description	Disable pending approvals check in HCM Data Loader.
Start Date	1/1/00

Click Save and Close.
Navigate to Setup and Maintenance > Search.
Search and select the Manage Administrator Profile Values task.
Search for the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option code
Click Search.
In the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER: Profile Values section, set the Site profile value to No.

Click Save and Close.

Tips And Considerations

Approvals aren't applicable for data created using HDL or HSDL.

Date-effective deletion of job records is also included when checking for conflicts.

When a job is updated or deleted from the job pages and the transaction is saved and closed; and when you update the same job using HDL or HSDL, the data load will be successful, but you can't submit the resumed transaction from the job pages.

There isn't any impact on inflight transactions. However post upgrade if data changes are loaded using HDL or HSDL for the same jobs that are pending approval; then the validation will be triggered.

When job data is loaded in bulk, conflicts are identified only for those jobs that are pending approvals.

This feature doesn't impact the create job flow.

Key Resources

For more information, refer to the topic Guidelines for Loading Jobs > Chapter: Guidelines for Loading Work Structures in the HCM Data Loading Business Objects guide on the Oracle Help Center.

Role And Privileges

You must be granted the Human Capital Management Application Administrator role to work in setup and maintenance area.

Prevent Inflight Location Transaction Updates When Using HCM Data Loader

You can now prevent inflight location updates when using HCM Data Loader (HDL) or HCM Spreadsheet Data Loader (HSDL) when approvals are pending for the same.

This feature is applicable in these scenarios.

When a location is updated or corrected
When a date effective location record is deleted

Let's understand how this works. In this example, approvals are enabled for the Edit Location process and a location, Location-IDC is updated with a new address.

While approvals are pending for the location updates made on the location pages, changes are loaded for the same location using HDL.

Because approvals are pending, a conflict is detected in the data load, which fails showing a validation error.

Click the message to see the details.

This feature will reduce the errors due to overlap of updates made to the same location record using HDL or HSDL and location pages when approvals are enabled. In addition, approvers won't encounter errors because of the inflight updates. Scope of duplicate updates made using the application and HDL or HSDL are removed thereby ensuring less rework.

Steps to Enable

You need to create (if it doesn't exist) and set the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option and set it to No. Setting this profile option to No will prevent inflight location transaction updates using HDL or HSDL when changes to a location are pending approval.

Use these steps to create and set the profile option.

On the Home page, navigate to Setup and Maintenance work area.
Search and select the Manage Profile Options task.
In the Search Results: Profile Options section, click the New icon.
On the Create Profile Option page, enter these details

Field	Value
Profile Option Code	HR_DISABLE_PENDING_APPROVALS_CHECK_IN HCM_DATA_LOADER
Profile Option Display Name	HR: Disable pending approvals check in HCM Data Loader
Application	Global Human Resources
Module	Employment
Description	Disable pending approvals check in HCM Data Loader.
Start Date	1/1/00

Click Save and Close.
Navigate to Setup and Maintenance > Search.
Search and select the Manage Administrator Profile Values task.
Search for the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option code
Click Search.
In the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER: Profile Values section, set the Site profile value to No.

Click Save and Close.

Tips And Considerations

Approvals aren't applicable for data created using HDL or HSDL.

Date-effective deletion of location records is also included when checking for conflicts.

When a location is updated or deleted from the location pages and the transaction is saved and closed; and when you update the same location using HDL or HSDL, the data load will be successful, but you can't submit the resumed transaction from the location pages.

There isn't any impact on inflight transactions. However post upgrade if data changes are loaded using HDL or HSDL for the same locations that are pending approval; then the validation will be triggered.

When location data is loaded in bulk, conflicts are identified only for those locations that are pending approvals.

This feature doesn't impact the create location flow.

Key Resources

For more information, refer to the topic Guidelines for Loading Locations > Chapter: Guidelines for Loading Work Structures in the HCM Data Loading Business Objects guide on the Oracle Help Center.

Role And Privileges

You must be granted the Human Capital Management Application Administrator role to work in setup and maintenance area.

Prevent Inflight Department Transaction Updates When Using HCM Data Loader

You can now prevent inflight department updates when using HCM Data Loader (HDL) or HCM Spreadsheet Data Loader (HSDL) when approvals are pending for the same.

This feature is applicable in these scenarios.

When a department is updated (update and correct flows)
When a date effective department record is deleted

Let's understand how this works. In this example, approvals are enabled for the Edit Organization process and a department, Sales Department is updated with a new location.

While approvals are pending for the department updates made on the department pages, changes are loaded for the same department using HDL.

Because approvals are pending, a conflict is detected in the data load, which fails showing a validation error.

Click the message to see the details.

This feature will reduce the errors due to overlap of updates made to the same department record using HDL or HSDL and department pages when approvals are enabled. In addition, approvers won't encounter errors because of the inflight updates. Scope of duplicate updates made using the application and HDL or HSDL are removed thereby ensuring less rework.

Steps to Enable

You need to create (if it doesn't exist) and set the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option and set it to No. Setting this profile option to No will prevent inflight department transaction updates using HDL or HSDL when changes to a department are pending approval.

Use these steps to create and set the profile option.

On the Home page, navigate to Setup and Maintenance work area.
Search and select the Manage Profile Options task.
In the Search Results: Profile Options section, click the New icon.
On the Create Profile Option page, enter these details

Field	Value
Profile Option Code	HR_DISABLE_PENDING_APPROVALS_CHECK_IN HCM_DATA_LOADER
Profile Option Display Name	HR: Disable pending approvals check in HCM Data Loader
Application	Global Human Resources
Module	Employment
Description	Disable pending approvals check in HCM Data Loader.
Start Date	1/1/00

Click Save and Close.
Navigate to Setup and Maintenance > Search.
Search and select the Manage Administrator Profile Values task.
Search for the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option code
Click Search.
In the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER: Profile Values section, set the Site profile value to No.

Click Save and Close.

Tips And Considerations

Approvals aren't applicable for data created using HDL or HSDL.

In the department pages (which are classic pages), the approval pending message is displayed only when you hover over the disabled Edit button.

Date-effective deletion of department records is also included when checking for conflicts.

When a department is updated or deleted from the department pages and the transaction is saved and closed; and when you update the same department using HDL or HSDL, the data load will be successful, but you can't submit the resumed transaction from the department pages.

There isn't any impact on inflight transactions. However post upgrade if data changes are loaded using HDL or HSDL for the same departments that are pending approval; then the validation will be triggered.

When department data is loaded in bulk, conflicts are identified only for those departments that are pending approvals.

This feature doesn't impact the department create flow.

Key Resources

For more information, refer to the topic Guidelines for Loading Organizations > Chapter: Guidelines for Loading Work Structures in the HCM Data Loading Business Objects guide on the Oracle Help Center.

Role And Privileges

You must be granted the Human Capital Management Application Administrator role to work in setup and maintenance area.

Position Management: Profile Option to Restrict the Number of Valid Grades

You can now restrict the number of valid grades that can be defined for a position using the Number of Valid Grades Allowed on a Position (ORA_PER_POS_NUM_VALID_GRADES_ALLWD) profile option.

You can restrict the number of valid grades on a position up to a maximum of 5. Select 0 to enter any number of valid grades. The number of valid grades added in the position can be less than the number defined in the profile option but if the number of valid grades exceed this number, then a validation message is displayed.

The validation applies to these responsive pages:

Request a New Position
Request a Position Change
Update Position (from Position Details)
Correct Position (from Position Details)
Duplicate Position (from Position Details)

This feature can be used to maintain a 1:1 relationship between position and valid grades for better data integrity.

Steps to Enable

You need to specify the number of valid grades you want to allow in the Number of Valid Grades Allowed on a Position (ORA_PER_POS_NUM_VALID_GRADES_ALLWD) profile option.

Navigate to Home > My Enterprise > Setup and Maintenance.
Click Search and search for the Manage Administrative Profile Values task.
Enter ORA_PER_POS_NUM_VALID_GRADES_ALLWD in the Profile Option Code field and click Search.
In the ORA_PER_POS_NUM_VALID_GRADES_ALLWD: Profile Values section, select the profile value. You can select a value between 0 and 5. If you specify the value as 0, then you can specify any number of valid grades for a position.

Click Save and Close.

Tips And Considerations

If you're using this feature along with the match position's valid grades with job's valid grades feature, then the number of grades defined for a job must be less than or equal to the number of grades allowed on the position.
This validation is also enabled for positions created, updated, or corrected using HCM Data Loader (HDL).

Key Resources

For more information refer to the Oracle Help Center for the following topic: Workforce Structures Profile Options in the Chapter Workforce Structures Configuration in the Implementing Global Human Resources guide.

Human Resources / Employment Replaced or Removed Features

From time to time, Oracle replaces existing features with new features, or removes existing features.

Replaced features may be put on a path of removal, the features below will let you know what update you will have to have moved to the newer feature. As a best practice, you should move to the newer feature as soon as possible for full support and to stay up with the latest updates that the product offers.

Any feature that is removed, will have an Update in which that feature is no longer available. Please make necessary plans to move off the feature by the Update indicated, as it will no longer be available.

Prepare for Removal of Person Gallery and Portrait Access in Update 23A

The Person Gallery and Portrait pages have been decommissioned and are no longer supported.

In Update 23A, if you attempt to open the Person Gallery or the Portrait page, a blank page will be displayed. Also, the View Portrait link will be hidden on the Person Contextual Actions dialog. If you have a specific use case for continuing to access the Person Gallery or the Portrait page, log an Oracle Service Request documenting your specific use case so that it can be reviewed and evaluated.

You need to update any links that you have to the Person Gallery and Portrait pages to the latest responsive pages as needed.

This will eliminate usage of unsupported pages.

Steps to Enable

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

Prepare for Discontinuation of Support for Employees REST Resource in Update 23D

Support for Employees REST resource (/emps) will be discontinued in Update 23D. Any usage of this resource must be replaced with the already existing Workers (/workers) and User Accounts (/userAccounts) REST resources, which extend its functionality.

This includes any usage including but not limited to usage by any custom code, by Oracle Integration Cloud (OIC), Employee ATOM feeds integrations, and Resource Alerts.

Moving to the Workers API gives users richer capabilities compared to the outgoing Employees REST resource.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

For more information, refer to these resources on the Oracle Help Center:

Workers API resources:

User Accounts API resource:

User Accounts API

Human Capital Management for Germany

Oracle HRMS (Germany) supports country specific features and functions for Germany. It enables users to follow Germany’s business practices and comply with its statutory requirements.

Updated Meaning of Various Attributes Used for Disability Reporting

You can now use the updated meaning of attributes used for the IW-Elan disability reporting. The changes are related to the usage of paragraphs regarding the social insurance law SGB IX and impact the following attributes:

Employee Disability Data: Certifying Authority
Legal Employer: Company Type
Employee Employment Data: Exemptions regarding Paragraph 73

This enhancement enables you to comply with the legislative changes.

Steps to Enable

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

Human Capital Management for Italy

Oracle HRMS (Italy) supports country specific features and functions for Italy. It enables users to follow Italy’s business practices and comply with its statutory requirements.

Additional Sublevel segment at Collective Agreement

You can now add Sublevel information to the existing Qualification and Level data at Collective Agreement for the Italian national labour agreements, as required.

This feature also allows the Sublevel information to be entered at the contract information level. The value of the Sublevel will be validated against the setup defined at collective agreement level. This is required to correctly manage the contract data according to the Italian law and ensure proper payroll calculation.

This feature provides a better user experience while managing Italian collective agreements.

Steps to Enable

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

Key Resources

You don't need anything to enable this feature.

Human Capital Management for Oman

Oracle HRMS (Oman) supports country specific features and functions for Oman. It enables users to follow Oman’s business practices and comply with its statutory requirements.

Additional Information at an Organization Level

You can select the employer category and the employer sector. Use the ORA_HRX_OM_EMPLOYER_CATEGORY and ORA_HRX_OM_EMPLOYER_SECTOR lookup codes to access Employer Category and Employer Sector values. The employer sector value is limited based on the value entered for employer category. For example, you can select the values Military, Army or Police if the employer category is Military sector.

With this enhancement record the relevant employer category, and sector, to be used in any ad hoc query.

Steps to Enable

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

Additional Information at a Person Level

With this enhancement, you can use the additional information provided to complete the hire or manage person functionality to meet legislative requirements.

Sponsor Details: Information about the Sponsor such as Sponsor Type, Sponsor Name, Sponsor Number, Sponsor Relationship and Sponsor Nationality has been added to the Visa Details.

Statutory Dependent Contacts: Added a check box to indicate whether a contact is Statutory Dependent used to calculate child allowance payments.

Reporting Description: Use this field to enter disability information to be reported to the Ministry of Social Affairs and the Social Insurance Office.

Continuous Period of Service (C): Use the Payroll Relationship Rule 'Continuous Period of Service (C)' to calculate an employee’s payroll. This payroll relationship rule checks for a Payroll Relationship of the same type as of the Work Term. If one exists, the Last Standard Earnings Date of the payroll relationship will be validated.

If the Last Standard Earnings Date is greater than the Term start date, the Work Term is attached to it.
If the Last Standard Earnings Date is less than the Term start date, a new Payroll Relationship is generated.
If the Last Standard Earnings Date does not exist, a new Payroll Relationship is generated.

When a Work Term is terminated, and if it is the last active Work Term associated with the Payroll Relationship, the Payroll Relationship is also be terminated.

Use HCM Experience Design Studio to manage person attributes for different regions. You can access HCM Experience Design Studio from My Client Groups, select one of the actions below to view the attributes.

Attribute	Region
Correspondence Language	Personal Details
Person Contact Relationship Legislative Attributes	Relationship Information, My Contacts, Relationship
Person Legislative Information Developer Attributes	Legislative Info, Demographic Info
Person Visa Legislative Attributes	Visas and Permits
Working Hours	Employment Details, Employment Info
Null (working hours frequency)	Employment Details, Employment Info
Probation Period	Employment Details, Employment Info
Probation End Date	Employment Details, Employment Info
Tax Reporting Unit	Payroll Details

You can select the following actions:

Hire an Employee
Add Assignment
Add Contingent Worker
Add Pending Worker
Add a Non Worker
Edit Pending Worker
Create Work Relationship
Employment Contracts
Local and Global Transfer
Identification Info
Family and Emergency Contacts
Personal Details
Mass Legal Employer Change

Use the additional information provided to complete the hire or manage person functionality to meet legislative requirements.

Steps to Enable

Access HCM Experience Design Studio from My Client Groups
Enter an Action such as Hire an Employee
Click on Add in the Rules section
Under Page Attributes select the attributes you want to make visible or hidden.

Payroll Definitions

With this enhancement use the Calendar Month as the payroll period that forms the basis to calculate Social Insurance in (Fusion) payroll. You can create a payroll definition for a bi-weekly payroll for use with third-party payroll providers, but you must set the country extension as Human Resources or Payroll Interface.

Use the Calendar Month as a payroll period to calculate the Social Insurance.

Steps to Enable

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

Payment Methods

With this enhancement, you can use the supported payment methods Direct Deposit, Payment by Cheque, Cash and International Transfer to pay employees by their chosen method of payment.

Process payments to employees by their chosen method of payment.

Steps to Enable

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

Human Capital Management for Spain

Oracle HRMS (Span) supports country specific features and functions for Spain. It enables users to follow Spain’s business practices and comply with its statutory requirements.

Enhanced Validation of the Foreigner's Identification Number

The validation of the Foreigner's identification number is now enhanced to accept two formats of this Spanish national identifier: the existing 9-character and the newly added 10-character. Both format and check digit validation are enabled for the two options.

You are now able to record identifiers issued before the adoption of the currently used format.

Steps to Enable

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

Key Resources

Please refer to Validating National Identifier Numbers in Oracle Fusion Human Capital Management (Document ID 2159758.1).

Human Capital Management for United Kingdom

Oracle HRMS (UK) supports country specific features and functions for the United Kingdom. It enables users to follow the UK’s business practices and comply with its statutory requirements.

Process Statutory Parental Bereavement Pay and Leave

This feature enables you to process Statutory Parental Bereavement Pay and leave for employees. To process this absence type, you need to create an element with primary classification Absences and secondary classification Parental Bereavement. On the Create Element: Additional Details page, you can select the absence type for the absence payment as Statutory parental bereavement.

A warning is generated if you enable assignment level entry for this absence type. Also, an error message is displayed when the user tries to record an absence on assignment level entry.

Once the absence is recorded, you can verify that the Average Weekly Earnings is calculated and displayed on the Absences calculation card.

When you run the payroll process (including retro), the application automatically calculates the amounts for aggregated and non-aggregated assignments.

For aggregated assignments, the payments are split by the number of assignments.
For non-aggregated assignments, each qualifying assignment receives the appropriate payment.

You can verify that the balance results for the Statutory Parental Bereavement Pay is populated with the appropriate run results.

You can comply with the statutory processing rules for Statutory Parental Bereavement Pay.

Steps to Enable

See the Administering Absences for the United Kingdom guide on Oracle Hep Center > Cloud Applications >Fusion Application Suite > Human Resources > All Books.

Key Resources

For more information, see Administering Absences for the United Kingdom on the Oracle Hep Center

Process Statutory Absences for Multiple Assignments

This feature enables you to process statutory absences for maternity, adoption, paternity, and sickness during maternity payments for employees for all their assignments.

Here's how the enhanced process to calculate entitlements for statutory absences for maternity, adoption, paternity, and sickness during maternity payment works:

Aggregate assignments, if they are all on the same Statutory Deductions card
Calculate the average weekly earnings using the appropriate pay information for the aggregated assignments

When you run the payroll process (including retro), the application automatically calculates the amounts for aggregated and non-aggregated assignments.

For aggregated assignments, the payments are split by the number of assignments.
For non-aggregated assignments, each qualifying assignment receives the appropriate payment.

You can comply with the statutory processing rule of processing statutory absences for multiple assignments.

Steps to Enable

See the Administering Absences for the United Kingdom guide on the Oracle Hep Center.

Tips And Considerations

Once you enable this feature, you won't be able to use the previous UK Statutory Maternity/Adoption/Paternity and Sickness During Maternity Pay Period solution.

Global Payroll Interface

Perform a Baseline Extraction of Payroll Interface for ADP Global Payroll V2

Perform a baseline extraction to ensure that a full file doesn't get extracted in the Payroll Interface for ADP Global Payroll V2.

Changes have been delivered on underlying routes to address issues in filter criteria and additional fixes have been delivered to improve performance.

NOTE: You should perform a baseline extraction after applying this patch to avoid a full file extraction.

Perform regular data changes and extractions after the baseline extraction.

This ensures that a full file doesn't get extracted in the Payroll Interface for ADP Global Payroll V2.

Steps to Enable

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

Perform a Baseline Extraction of Payroll Interfaces generated from Global Payroll Interface Template

Perform a baseline extraction of the payroll interfaces generated using the Global Payroll Interface template to ensure that a full file doesn't get extracted.

Changes have been delivered on underlying routes to address issues in filter criteria and additional fixes have been delivered to improve performance.

NOTE: You should perform a baseline extraction after applying this patch to avoid a full file extraction.

Perform regular data changes and extractions after the baseline extraction.

This ensures that a full file doesn't get extracted in the Payroll Interface generated using the Global Payroll Interface template.

Steps to Enable

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

Global Payroll Interface Process To Generate Interfaces For Payroll Connect Vendors

Use the Generate Payroll Connect Interfaces process to generate payroll interfaces for Oracle Payroll Connect vendors.

Use this process to convert an interface defined at one Legislative Data Group level to enterprise level and to inject country level data into the interface converted to enterprise level.

When configuring payroll interface for payroll connect partners, customers can create an initial interface at any LDG level selecting the global attributes they want to include in their interface across countries. This creates an interface with all global data required in the standard interface for the payroll partner. Steps to run the Generate Payroll Connect Interfaces process to convert LDG level interface to enterprise level interface:

Search for and select Submit a Flow task under the My Client Groups tab.
Search for and select Generate Payroll Connect Interfaces flow.
Complete these fields:
- Payroll Flow Name: Provide a meaningful name.
- Usage: Select Configure Payroll Connect.
- Consumer: Select the appropriate Payroll Connect partner.
- Extract Definition: Select the extract definition created through the configurator for the selected payroll partner.
Submit the flow.

After converting to enterprise level interface, if you want to include country specific data for countries, run the Generate Payroll Connect Interfaces process again with the usage parameter value as Incorporate Country and inject country level data for countries which have an extension provided by GPI.

You can start using the interface after running this process to generate the output files for the payroll partner.

Generate a standard payroll interface for the Payroll Connect vendors. You don't have to create multiple copies of same interface for various countries.

Steps to Enable

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

Global Payroll Interface Template Supports Salary Using Simple Components

Integrate salary based on simple components with third-party payroll systems using the enhanced Global Payroll Interface template to generate payroll interfaces.

Here's how you configure the payroll interface using the Global Payroll Interface template:

On the Home page, click the Data Exchange quick action under the My Client Groups tab.
Search for and select Extract Definition on the Data Exchange page.
Create an extract. On the Create Extract Definition dialog box, complete these fields:
- Name: Provide the name of the interface. The application generates the flow with this name. Let's say, the name is ABC Payroll Interface, then the flow gets generated as Run ABC Payroll Interface.
- Start Date: Provide a start date to create the extract definition.
- Type: Select the type as Payroll Interface.
- Changes Only: Ensure that you have selected this check box.
- Legislative Data Group: Search for and select an appropriate legislative data group.
- Source Template: Select the source template as Global Payroll Interface.
Click OK. You will find a list of default objects and attributes that are available.
Select Salary Simple Component Details under Salary. You can find the attributes available under Attributes.
Click Save to submit your configuration and wait for the status to reflect Ready.

Customers can integrate salary using simple components with their payroll partners.

Steps to Enable

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

HCM Communicate

HCM Communicate provides communication teams a powerful way to create, target and track company communications sent to employees. The product allows teams to granularly target communications to their employees, as well as retarget future communications based on employee engagement. HCM Communicate provides an intuitive templated WYSWYG content creator that allows communication teams to quickly create engaging content. The system allows communication teams to send out communication on behalf of others in the organization. HCM Communicate provides a robust toolkit that allows organizations to engage effectively with their employees. HCM Communicate requires a subscription to Fusion HCM Communicate Cloud Service. Customers must first subscribe to this service prior to using HCM Communicate.

Communication Teams

As an administrator, you can create communication teams with specific campaign managers, campaign purposes and types, predefined audiences and sender profiles. Communication teams can limit access of campaign managers to specific campaign parameters specified on their communication team. Campaign managers can then use these predefined configurations when creating communication campaigns.

In the Setup and Maintenance work area, go to:
- Offering: HCM Communicate
- Functional Area: Employee Communications
- Task: Manage Communication Teams
On the Manage Communication Teams page, click Add.
In the Details section, enter a name and description for the communication team. Select the campaign purpose.
- General: Select this option for general communications where a response isn't required. For example, a list of holidays.
- Get Responses: Select this option to solicit a response on a particular subject. For example, asking employees if they prefer to work from home or the office.
- Select All if you want the communication team to create both General and Get Responses communication campaigns.
In the Team Members section, add campaign managers within your organization who can use the sender profile and predefined audience configurations defined for this specific team.
In the Sender Profile section, select all possible sender profiles that could be used by this communication team when sending out communications to employees. The list contains the sender profiles that you created.
In the Audience section, select all possible audiences that could be used by this communication team when sending out communications to employees. The list contains the pre-defined audiences that you created.
Click Save and Close.
On the Manage Communication Teams page, click the Actions menu and select Activate. This will allow campaign managers to select a communication team they're part of when creating a campaign.

This feature helps promote a more tailored and secure experience for campaign managers.

Steps to Enable

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

Email Follow-up Targeting for No Response

As a campaign manager, when you create an employee communication of type Get Responses, you can target audience members who either didn’t open an email or opened an email but didn't click a response for follow up emails.

On the Communicate page, open a communication campaign.
Click the Emails tab.
In the Emails section, click Add.
In the Audience tab, select the option Not clicked on any response.

Option Not Clicked on Any Response

This feature helps campaign managers in tailoring communications for specific audience segments to improve engagement.

Steps to Enable

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

Seeded Campaign Templates

As a campaign administrator, you can use a list of predefined templates for common types of communications. You can use these templates as is, or further customize them to align with your organization’s brand and communication needs.

In the Setup and Maintenance work area, go to:
- Offering: HCM Communicate
- Functional Area: Employee Communications
- Task: Manage Email Templates
On the Manage Email Templates page, click Add to create a new template.

The Template field provides a list of seeded templates.

Seeded Templates

These seeded templates help administrators get quickly started on template creation for their organization.

Steps to Enable

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

Transactional Business Intelligence for Human Resources

Oracle Transactional Business Intelligence is a real time, self service reporting solution offered to all Oracle® Cloud application users to create ad hoc reports and analyze them for daily decision-making. Oracle Transactional Business Intelligence provides human resources managers and specialists, business executives, and line managers the critical workforce information to analyze workforce costs, staffing, compensation, performance management, talent management, succession planning, and employee benefits.

Don’t want to start from scratch building a report or analytics? Check out the library of sample reports for all products on Customer Connect on the Report Sharing Center.

Assignment Termination Details In Assignment Subject Areas

Worker assignments has included attributes related to assignment termination. The subject areas and the attributes added are listed below:

Subject Area	Folder	Sub Folder(new)	Attributes
Workforce Management - Worker Assignment Real Time	Worker Assignment Details	Assignment Termination	Termination Date Termination Notification Date Last Working Date Review User Access Rehire Recommendation Rehire Reason Rehire Authorizer Rehire Authorizer Person Number Rehire Authorizer Person Identifier
Workforce Management - Worker Assignment Event Real Time	Assignment Event Details	Assignment Termination	Termination Date Termination Notification Date Last Working Date Review User Access Rehire Recommendation Rehire Reason Rehire Authorizer Rehire Authorizer Person Number Rehire Authorizer Person Identifier
<All Subject Areas>	Worker		Assignment Termination Date Assignment Termination Notification Date

Improve your reporting on worker assignments with the inclusion of the attributes related to assignment termination.

Steps to Enable

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

New Attributes Related To Position And Documents Of Record

The new attributes are added to the position and documents of record details dimensions. These are detailed below:

Subject Area	Folder	Attribute
<All Subject Areas>	Position	Calculate FTE Calculate FTE Code
Workforce Management - Position Real Time	Position Details	Calculate FTE Calculate FTE Code
Workforce Management - Documents of Record Real Time	Documents of Record Details	Creation Source Creation Source Code

Enhance your reporting on position dimension and documents of record details dimension with the addition of new attributes.

Steps to Enable

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

Reporting On Document Attachments Data

A new dimension named Document Records Attachment is added to Workforce Management - Documents of Record Real Time subject area. This dimensions contains attributes to report on details of the attachments like name, title, description, type, url, etc.

Enhance your reporting on documents of record with the addition of the data related to the attachments to these records.

Steps to Enable

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

IMPORTANT Actions and Considerations for Human Resources

REPLACED OR REMOVED FEATURES

From time to time, Oracle replaces existing Cloud service features with new features or removes existing features. When a feature is replaced the older version may be removed immediately or at a future time. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.

Product	Removed Feature	Target Removal	Replacement Feature	Replaced In	Additional Information
Global HR	Prepare for Removal of Person Gallery and Portrait Access in Update 23A	23A			You need to move to the responsive pages.
Global HR	Prepare for Discontinuation of Support for Employees REST Resource in Update 23D	23D			Workers (/workers) and User Accounts (/userAccounts) REST resources.

__________________________

KNOWN ISSUES / MAINTENANCE PACK SPREADSHEETS

Oracle publishes a Known Issues document for every Update to make customers are aware of potential problems they could run into and the document provides workarounds if they are available.

Oracle also publishes Maintenance Pack and Statutory Maintenance Pack documentation of bugs that are fixed in the monthly or statutory patching.

To review these documents you must have access to My Oracle Support:

Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1)

Controlled Availability for Human Resources

The following is a list of Controlled Availability features that are being offered by our Controlled Availability Program.

NOTE: These features are not generally available for all customers at this time. These are only available through the Controlled Availability Program and will require approval to become a part of the features program. To be a part of these programs you will be required to participate in testing and providing feedback. Some programs may require other participation as well.

Not to worry if you don't have to time to be a part of these early stage programs. You can uptake this feature when it is generally available for all customers. When these features are available for all customers you will see the features under their product headings as usual.

We invite you all to browse through the list of features to see if there are any features you are interested in implementing in advance of the features scheduled release. The table below will provide information on signing up for features. Please sign up soon, as these programs have limited availability and some are designed for specific types of customers.

The table below gives you a brief description of the features available and how to sign up. Some features are bigger than others, so for more information there may be a What's New describing the feature in more detail below this table.

We look forward to hearing your thoughts and ideas as you participate the Controlled Availability programs!

Product	Feature Name	Feature Description	Type of Customer Needed to Test	How to Sign Up	Controlled Availability Release	Is the Program Still Open?
Global Human Resources	Autoprovision Areas of Responsibility (AORs)	Automatically assign or remove worker responsibilities based on user-defined AOR Template Criteria. Enhancements have been made to improve user experience and simply the autoprovisioning process in a production environment.	HCM AOR customers willing to move to Responsibility Templates	Open a Service Request in My Oracle Support and include a tag for "AOR-Autoprovision" Refer to My Oracle Support - Fusion Global HR: How to Apply for Autoprovision Areas of Responsibilities Feature Under Controlled Availability (Doc ID 2765388.1)	21B	Yes

Product

Feature Name

Feature Description

Type of Customer Needed to Test

How to Sign Up

Controlled Availability Release

Is the Program Still Open?

Global Human Resources

Autoprovision Areas of Responsibility (AORs)

Automatically assign or remove worker responsibilities based on user-defined AOR Template Criteria. Enhancements have been made to improve user experience and simply the autoprovisioning process in a production environment.

HCM AOR customers willing to move to Responsibility Templates

Open a Service Request in My Oracle Support and include a tag for "AOR-Autoprovision"

Refer to My Oracle Support - Fusion Global HR: How to Apply for Autoprovision Areas of Responsibilities Feature Under Controlled Availability (Doc ID 2765388.1)

21B

Yes