February Maintenance Pack for 23A

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
27 JAN 2023			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 (23A, 23B, 23C, and 23D)
• 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.

____________________

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

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.

Feature Summary

Human Resources

Human Capital Management for Taiwan

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

National Identification Number Validation for Taiwan Foreign Nationals

Users can now enter a National ID number for Taiwan foreign nationals. The new National ID format comprises one English letter followed by nine numbers, similar to that of Taiwan citizens.

When users enter the new National ID for foreign nationals, the application will validate the format. For males, the first number will be 8. For females, the first number will be 9. 

The Worker Validation Report has also been enhanced to include the National Identifier cross validation gender check for foreign nationals. 

Steps to Enable

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

Update 23A

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
30 JUN 2023	OTBI / Global HR	New Subject Area to Report on Archived Documents of Record	Updated document. Revised feature information.
26 MAY 2023	Human Capital Management for United Emirates	Emirates ID Validation	Updated document. Revised feature information.
28 APR 2023	Human Resources/ Connections	Thank the Feedback Provider	Updated document. Feature delivered in update 23A.
31 MAR 2023	Human Resources/ Document records	Generate Letters Based on Document Records When Using HDL, REST, and Plugin Sections	Updated document. Revised feature information.
31 MAR 2023	Human Resources/Workforce Structures	Employee Location Attribute for Client-Side Location LOV on Position	Updated document. Revised feature information.
31 MAR 2023	Human Resources/Journeys	Schedule Recurring Journeys	Updated document. Revised feature information.
31 MAR 2023	Human Resources/Employment	Simplified Document Records Section in Responsive Employment Correction Flow	Updated document. Revised feature information.
31 MAR 2023	Human Resources / Global HR Replaced or Removed Features	V2 Seniority Dates Removed in Update 23B	Updated document. Feature delivered in update 23A.
31 MAR 2023	Human Resources for the US	New Hire State Electronic Report Enhancement	Updated document. Revised feature information.
24 Feb 2023	Human Resources for the US	New Hire State Electronic Report Enhancement	Updated document. Feature delivered in update 23A.
27 JAN 2023	Human Resources/Employment	Synchronize Action Reason from Position to Worker Assignments	Updated document. Revised feature information.
20 DEC 2022	Human Resources/ Journeys	Visibility of Gatekeeper Law Journey Template	Updated document. Feature delivered in update 23A.
02 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 (23A, 23B, 23C, and 23D)
• 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.

____________________

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

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.

Feature Summary

Human Resources

Global Human Resources

Oracle Global Human Resources enables your organization to plan, manage and optimize all workforce segments using flexible and extensible best practices to realize extraordinary gains while insuring compliance and increasing total workforce engagement.

Autocomplete

Autocomplete Support for Terminating an Assignment

You can now author autocomplete rules for terminating an assignment in the Terminate Employment flow. Using the Autocomplete Rules tab in HCM Experience Design Studio, you can create your custom rules to validate, default, and modify values. For example, you can author an autocomplete rule to default the last work day in the Terminate Employment flow.

These are the newly added attributes:

• Last Day Worked

• Review User Access

• Recommended for Rehire

• Recommendation Reason

• Rehire Authorizer Person ID

• Notification Date

• Termination Date

This table shows the objects for which you can create validation rules:

Object	Rule Type	Termination Level
When and Why	Object Validation	Work Relationship – Single Assignment Work Relationship – Multi Assignment Assignment
Termination Info	Object Validation	Work Relationship – Single Assignment Work Relationship – Multi Assignment Assignment
Work Relationship Info	Object Validation	Work Relationship – Single Assignment Work Relationship – Multi Assignment
Assignment Info	Object Validation	Work Relationship – Single Assignment Assignment
Additional Assignment Info	Object Validation	Work Relationship – Single Assignment Assignment

This table shows the objects for which you can create defaulting rules:

Object	Rule Type	Termination Level
When and Why	Object Defaulting	N/A
Termination Info	Object Defaulting	Assignment
Work Relationship Info	Object Defaulting	N/A
Assignment Info	Object Defaulting	Work Relationship - Single Assignment Assignment
Additional Assignment Info	Object Defaulting	N/A

This table shows the objects for which you can create field modification rules:

Object	Rule Type	Termination Level
When and Why	Field Modification	N/A
Termination Info	Field Modification	Work Relationship - Single Assignment Work Relationship - Multi Assignment Assignment
Work Relationship Info	Field Modification	Work Relationship - Single Assignment Work Relationship - Multi Assignment
Assignment Info	Field Modification	Work Relationship - Single Assignment Assignment
Additional Assignment Info	Field Modification	N/A

This table shows the objects for which you can create field validation rules:

Object	Rule Type	Termination Level
When and Why	Field Validation	N/A
Termination Info	Field Validation	Work Relationship - Single Assignment Work Relationship - Multi Assignment Assignment
Work Relationship Info	Field Validation	Work Relationship - Single Assignment Work Relationship - Multi Assignment
Assignment Info	Field Validation	Work Relationship - Single Assignment Assignment
Additional Assignment Info	Field Validation	N/A

You can use the following new HCM parameters (HcmParams):

HcmParam	Description
TERM_TerminationLevel	Indicates the termination level. For work relationship level, the HcmParam value is WR. For assignment level, the HcmParam value is ASG.
EMP_SensorProcessName	Indicates the current flow that’s started. For Terminate Employment flow, when  you perform a work relationship level termination, the HcmParam value is Terminations. When you perform an assignment level termination in the same flow, the HcmParam value is AssignmentTerminations. For Resign from Employment flow, when you perform a work relationship level resignation, the HcmParam value is Resignation. When you perform an assignment level resignation in the same flow, the HcmParam Value is AssignmentResignation.
EMP_Groovy_V3NotificationDate	Indicates the notification date selected for the flow.
EMP_Groovy_V3TerminationDate	Indicates the termination date selected for the flow.
EMP_AssignmentId	Indicates the assignment ID with which the flow was started.

These are the existing HcmParams:

HcmParam	Description
EMP_Groovy_TerminationRegion	Indicates the current section in which you are operating for a flow. For the different sections, the HcmParam values are as follows: When and Why - SkipValidations Termination Info - TerminationInfo Work Relationship Info - TerminationDetails Assignment Info - AsgTerminationDetails Additional Assignment Info - AdditionalAsgTerminationDetails
EMP_Groovy_ActionTypeCode	Indicates the action type code for the flow.
EMP_Groovy_ActionCode	Indicates the action selected for the flow.
EMP_Groovy_ActionReasonCode	Indicates the action reason selected for the flow.

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 Update 21B (Doc ID 2767655.1) to get access.

Key Resources

For more information refer to Terminations > Chapter Hire and Manage Workers in the Using Global Human Resources guide.

Access Requirements

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

Connections

Thank the Feedback Provider

Enhance your feedback experience using Connections. You can send a thank you note to the feedback provider for sending the feedback to you. Depending on the feedback visibility settings, the manager, HR specialist can also send a thank you note to the feedback provider. This feature must be enabled in Alerts Composer before you can use it.

To send a thank you note:

1. Go to Me > Connections and open the profile whose feedback provider you want to thank.
2. In the What Others Think section, on the feedback, click the Edit Feedback (...) icon and select Send Thank You.
3. On the Send Thank You card, enter your message and click Send.

When you send the thank you note, the feedback provider receives an email notification about it.

The administrator can enable or disable the alert notification template, Anytime Feedback Provided, in Alerts Composer:

1. Go to Tools > Alerts Composer.

2. Search for the HRT_ANYTIME_FEEDBACK_PROVIDED alert code.

3. From the search results section, click the alert name.

4. On the Templates tab, enable or disable these templates:

   • Worker Thanks Anytime Feedback Provider

   • Manager/HR Thanks Anytime Feedback Provider

5. Click Save and Close.

Steps to Enable

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

Tips And Considerations

• You can thank the feedback provider multiple times for the same feedback. Any others who can view the feedback can also thank the feedback provider multiple times for the same feedback.

• The thank you note is not saved in the application. Therefore, it’s visible only in feedback provider’s email notification.

• Even if the feedback notification in Talent Notifications is disabled, you can still use this feature as long as the Anytime Feedback Provided alert is enabled.

Key Resources

• Connections Profile

Document Records

Audit Access to Document Records and Mass Download of Document Records Pages

You can now monitor users who have accessed a document record page or data on the Document Records and Mass Download of Document Records pages by using the Workforce Management - Sensitive Data Access Audit Real Time subject area.

This table shows what data is logged by the application in the PER_SENSITIVE_DATA_AUDIT table.

Action	Page Title	Type of Data Accessed
Start Document Records page	Document Records list page	List of all document records
View a document record	Document Records details page	Document record ID
Delete a document record	Document Records details page	Document code of system document type and document record ID
Start Mass Download of Document Records page	Mass Download of Document Records page	Downloaded document records
Submit request to mass download document records	Submitted Mass Download Processes page	Submitted request ID
Start document records in plugin section	Document Records plugin section	List of all document records
View a document record in plugin section	Document Records details plugin section	Document record ID

Here's how you navigate to the Sensitive Data Access Audit page on the home page: My Client Groups > Transaction Configuration and Audit > Sensitive Data Access Audit

View the Read Audit Data on the Sensitive Data Access Audit Page

You can use this information for compliance and monitoring of access to document records data.

Steps to Enable

This feature is disabled at upgrade. To enable this feature, you need to set the Mobile-Responsive Sensitive Data View Audit Enabled (ORA_HCM_SENSITIVE_DATA_VIEW_AUDIT_ENABLED) profile option to Y.

1. Navigate to the Setup and Maintenance work area.

2. Search for and click the Manage Administrator Profile Values task.

3. Search for the ORA_HCM_SENSITIVE_DATA_VIEW_AUDIT_ENABLED profile option code and select it from the search results.

4. In the Profile Values area, set the Profile Level to Site and the Profile Value to Y.

5. Click Save and Close.

Tips And Considerations

• You can access the audit data by building a custom report using the OTBI - Subject Area - Workforce Management - Sensitive Data Access Audit Real Time.

• This feature is used to track the user who accessed the Document Records page or document record. The feature doesn’t track the user who created or edited the document record.

• This feature won’t track if the document record attachment was previewed or downloaded. The feature only tracks if the user visited a page from where the attachment can be previewed or downloaded.

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.

• Sensitive Data Access Audit > Chapter Auditing Oracle HCM Cloud Business Objects in the Securing HCM guide.

Access Requirements

The Sensitive Data Access Audit page is secured using a function security privilege with a privilege code of PER_VIEW_SENSITIVE_DATA_ACCESS_AUDIT_PRIV. At upgrade, it's granted to the predefined IT Auditor role. If you want to allow any custom job or abstract roles to access this page, you should grant this function security privilege to the custom roles.

Function Security Privilege	Predefined Role
PER_VIEW_SENSITIVE_DATA_ACCESS_AUDIT_PRIV	IT Auditor

Display Titles for Document Type Attachments in Reference Info Section

We have enhanced the ability to display titles for the document type attachments that you upload in the Reference Info section. The URL or file name that you enter is defaulted in the Title field in the Document Type Setup page. You can replace or change this defaulted value with a meaningful title to display in the Reference Info section.

Configure the Attachment Title in the Document Type Setup Page

Attachment Title Displayed in the Add Document Page

Attachment Title Displayed in the View Document Page

Users can easily relate to the attachments in the Reference Info section when adding, viewing, or editing document records for a document type.

Steps to Enable

1. Navigate to the Setup and Maintenance work area.

2. In the Tasks panel drawer, click Search.

3. Search and click the Document Types task name.

4. Click the Create icon in the Search Results area.

5. Enter the information that you want for the document type.

6. Under the Attachments tab, click the Add (+) icon.

7. Select the attachment type (File, Text, or URL) and the attachment category.

8. Do the following based on the attachment type that you selected:

   1. File: Click Choose File to select the file from your local drive.

   2. Text: Enter the text in the File Name or URL field.

   3. URL: Enter the URL in the File Name or URL field.

9. Enter a meaningful title based on the attachment type you entered.

10. Enter the description for the attachment type.

11. Click Submit.

Tips And Considerations

• The title of the document type attachment won't be displayed in the Reference Info section of the document record when viewed on a mobile device.

• Titles are not supported for attachments that are added as part of a document record. For such attachments, only the file name or URL will be displayed.

• The character limit for the document title field is 80 characters. If file name is more than 30 characters, the document title field is defaulted with the first 30 characters of the file name. You can manually update the document title up to 80 characters.

Access Requirements

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

Generate Letters Based on Document Records When Using HDL, REST, and Plugin Sections

This enhancement is in continuation of the Update 20B feature, Generate Letters Based on Document Records.

We have further enhanced the process of generating letters and storing them as document record attachments. Earlier, you could generate a letter while creating a document record using only the Document Records quick action. Now, you can generate letters when using these additional document record sources:

• HCM Data Loader (HDL)

• HCM Spreadsheet Data Loader (HSDL)

• REST API

• Plugin sections in responsive Employment and Salary flows

Users can generate letters even when document records are created using methods other than the Document Records page.

Steps to Enable

You can enable letter generation for the document record sources by configuring appropriate values in the Letter Generation Configuration Based on Document Record Source EFF context.

1. Navigate to the Setup and Maintenance work area.

2. Search for and click the Manage Enterprise HCM Information task.

3. For the Letter Generation Configuration Based on Document Record Source EFF context, select the document record source.

Note: Values in the Document Record Source column will be populated from the ORA_PER_DOR_SOURCE lookup. Only supported values are displayed in the list.

4. In the Generate Letter column, select the value (Yes/No).

5. Click Done.

If the report path is configured for the document type, then by default the letter will be generated. Additionally, the letter will be stored as an attachment in the person's document record. In case of the Document Record plugin section, the letter generation and storage will happen when the parent transaction is approved and committed.

Tips And Considerations

• If you have configured your custom data model based on the sample data model delivered in release 22D or earlier, you need to make changes to your custom data model. This is because the seeded sample data model is modified as part of this enhancement. If you don't update your custom data model, then the letter that's generated after you commit from the UI won't have any data. For more information, refer to this product paper on Cloud Customer Connect: Document Records - Generate Letter from Document Record for Specific Doc Type

Access Requirements

When you build the data model and report, the roles in the following table must be added to the report, data model, and the folders containing the data model and report along with roles and users.

Role Title	Role Type	Role Name	Comments
Web Services Application Identity for HCM	ABSTRACT	FUSION_APPS_HCM_SOA_APPID	Used to invoke the BI report to generate the letter for the document record from the plug-in sections. Note that the parent transaction containing the Document Records plug-in section must be approved and committed before the letter can be generated and stored.
Batch Loader Enterprise Scheduler Job Application Identity for HCM	ABSTRACT	FUSION_APPS_HCM_ESS_LOADER_APPID	Used to invoke the BI report to generate the letter for the document record from HDL and HSDL.

Document Type Subcategory Displayed When Adding Document Records

You can now select the document type accurately when you create a document record by making use of the new Subcategory attribute displayed in the Document Type REST LoV.

Subcategory Attribute Displayed When Filtering Document Records

Subcategory Attribute Displayed When Adding a Document Record

Subcategory Attribute Displayed in the Document Records Plugin Section

Subcategory Attribute Displayed When Submitting a Request to Mass Download Document Records

Users can easily search and filter the document type they want from the Document Type LoV based on the subcategory attribute.

Steps to Enable

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

Tips And Considerations

It is recommended that you select a value for the Subcategory attribute when configuring a document type to further classify document records.

Access Requirements

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

Display Preferences of Document Records Descriptive Flexfields for Document Type

We have enhanced the Document Type setup page to configure display preferences for the document record flexfield (global and context) for each document type. You can additionally configure the default value for the document record flexfield context.

Display Preferences for DFF Segments in Document Type Setup Page

Users can configure the display preferences for the document record flexfield context attributes directly from the Document Type Setup page instead of using Page Composer.

Steps to Enable

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

Tips And Considerations

• The context attributes of the document record flexfield can be configured optionally on the Document Type Setup page.

• By default, the context attributes of the document record flexfield have a value of null.

• The context attribute fields of the document record flexfield are displayed as read-only or are hidden based on the configuration done for the document type in the Add Document Records and View Document Records pages.

• It is recommended that the context attribute of the document record flexfield is not mandatory if you set it as Hide or Read only. Else, the user will see an error message when adding or editing a document record.

• The context preferences of the document record flexfield are applicable only when adding or editing a document record from the page. These preferences are not applicable when a document record is added or edited by using HCM Data Loader or HCM Spreadsheet Data Loader.

• The existing Page Composer customizations will take precedence. You need to remove the existing customizations and configure the document record flexfield preferences accordingly.

• It’s strongly recommended to use this feature instead of page composer personalization.

• You can export and import the context attributes of the document record flexfield by using the Functional Setup Manager (FSM).

• The context attributes of the document record flexfield will be supported for OTBI in a future release.

Access Requirements

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

Configurable Labels for Standard Attributes for Document Type

You can now configure appropriate labels for the standard document record attributes based on the document type. For example, you can configure these new labels for the passport document type:

Existing Attribute Label	New Attribute Label
Name	Passport Name
Number	Passport Number
Issuing Comments	Passport Issuing Comments
Start Date	Passport Start Date
End Date	Passport End Date
Issued Date	Passport Issued Date
Issuing Authority	Passport Issuing Authority
Issuing Country	Passport Issuing Country
Issuing Location	Passport Issuing Location

These labels are displayed when you add, view, or edit a document record for the document type. Additionally, the labels are supported for translation.

Configure Labels for Standard Attributes in Document Type Setup Page

New Labels Displayed in Add Document Page

New Labels Displayed in Document List Page

Users can customize labels according to their organization’s business terminology.

Steps to Enable

1. Navigate to the Setup and Maintenance work area.

2. In the Tasks panel drawer, click Search.

3. Search and click the Document Types task name.

4. Search for a document type (for example Passport).

5. Click the document type link in the Search Results area.

6. In the Edit Document Type page, click the Translation Editor icon (globe icon).

7. In the Edit Translations dialog box, for the US source language, enter the new labels for name, number, issuing comments, from date, to date, issued date, issuing authority, issuing country, and issuing location. Click OK.

8. Click Submit.

9. Click Yes, and then click OK.

Tips And Considerations

• The labels for the document record attributes can only be configured in the translation editor and not on the Document Type Setup page.

• By default, the value for the document record attribute label is null.

• The character limit for each new label field is 200 characters.

• The document record attribute label configuration can be exported and imported using the Functional Setup Manager (FSM).

• The document record attribute labels can be created and updated using HCM Data Loader and HCM Spreadsheet Data Loader.

• The document record attribute labels will be supported in OTBI in a future release.

• If you have changed the labels for the document record attributes using page composer, it is recommended that you evaluate your changes and use this standard configuration option wherever applicable.

Access Requirements

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

Configurable Restrict Options for Document Type

You can now specify the roles that you want to exclude in the Roles Excluded from Restriction field in the Document Type Setup page. You can exclude specific roles for these document record restrict settings even if the settings are enabled for the document type:

• Restrict Create

• Restrict Update

• Restrict Delete

These examples show how the role exclusion works in the application pages:

• You have enabled the Restrict Create setting for a document type and have excluded certain roles from this restriction. In this case, users having these excluded roles can still create a document record when they select the document type in the Add Document Record page.

• You have enabled the Restrict Update setting for a document type and have excluded certain roles from this restriction. In this case, the Edit button will still be enabled for users having these excluded roles when they view the document record.

• You have enabled the Restrict Delete setting for a document type and have excluded certain roles from this restriction. In this case, the Delete button will still be enabled for users having these excluded roles when they view the document record.

John has two roles, employee and HR specialist. Sandra has only the employee role. You have enabled the Restrict Update setting to Yes for the Visa document type and have excluded the HR specialist role for the setting. With this configuration, Sandra can’t edit the Visa document record. However, John can since he has the HR specialist role which is excluded from the Restrict Update setting.

Exclude Roles Even When Restricting Creation, Update, or Deletion of Document Records

Users with specific roles can be excluded from the restriction for business reasons even though all other users in the organization are restricted.

Steps to Enable

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

Tips And Considerations

• The character limit for the Roles Excluded from Restriction field is 4000 characters (including commas).

• You need to enter the role codes, and not role titles, in the Roles Excluded from Restriction field. If there is more than one role, separate them using commas. Ensure that you don't include a space after the commas.

• By default, the value for the Roles Excluded from Restriction field is null.

• The Roles Excluded from Restriction field will be enabled only when the restrict setting is set to Yes.

• The document type exclusion configuration can be exported and imported using the Functional Setup Manager (FSM).

• The document type exclusion configuration is supported in HCM Data Loader and HCM Spreadsheet Data Loader.

• The document type exclusion configuration will be supported for OTBI in a future release.

• If you have made changes to the add, edit, and delete buttons using page composer, it is recommended that you evaluate the changes and use this standard configuration option wherever applicable.

Access Requirements

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

Additional Parameters to Filter Document Records on Mass Download of Document Records Page

This enhancement is in continuation of the Update 21D feature, Mass Download Document Records and Attachments.

You can now submit a request to mass download document records by using these additional parameters to filter document records:

• Category: Category of the document record.

• Created From: Source of the document record creation.

Filter Document Records for Mass Download Based on Category

Filter Document Records for Mass Download Based on Where They Were Created

Select document records for mass download by using additional filter parameters to meet your business requirements. For example, download all document records and attachments of category Employment and created from Allocated checklist tasks.

Steps to Enable

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

Control Access to Archived Document Records in OTBI

You can now control access to archived document records data in OTBI reports by using the new secured HR_DOR_ARCH_REPORTING_LIST_V view. This view is implemented in the Workforce Management - Documents of Record Archive Real Time subject area.

This feature allows consistent secured access to archived document records for workers.

Steps to Enable

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

Employment

Synchronize Action Reason from Position to Worker Assignments

You can now synchronize the action reason in assignments with the action reason specified when a position is updated.  This feature applies when a position is updated using these flows and processes.

• Update Position (from Position Details)
• Request a Position Change
• Synchronize Person Assignments from Position ESS process

The action reason is synchronized in the assignment if these conditions are satisfied.

• Position synchronization is enabled at the enterprise or the legal entity levels.
• Action reason attribute is selected for synchronization in the position synchronization setup.
• Action reason is specified in the selected position.
• Synchronization from Position action has associated reasons configured.
• Action reason specified in the position is one of the reasons associated with Synchronization from Position (ORA_POS_SYNC) action and to action of type Update Position (PER_POS_UPD)
• At least one of the synchronized attributes is updated in the position apart from action reason.

Example of  Action Reason Synchronization

Let's understand how this works with an example. Position synchronization is enabled at the Global Business Institute enterprise level and department, job, full time or part time, and action reason attributes are enabled for synchronization.

There are 3 positions - Architect, Sales Manager, and Director with these action reasons and jobs respectively.

Position Info

Position Name	Action Reason	Job
Architect	Promotion	Software Development
Sales Manager	Organization Change	Sales Manager - SAAS
Director	Assignment Change	Director - Operations

The Synchronization from Position action is associated with only promotion and Organization Change action reasons and the Update Position action is associated with Assignment Change and Organization Change action reasons.

Action Reason Info

Action	Associated Action Reason
Synchronization from Position	Promotion Organization Change
Update Position	Assignment Change Organization Change

Assignment Info

Person	Position	Job	Action Reason	Updated Job	Updated Action Reason
John Doe	Architect	Software Development	NA	NA	(no update in the assignment action reason)
Bonnie Vickers	Sales Manager	Sales Manager - SAAS	NA	Software Development	Organization Change
David Steward	Director	Director - Operations	NA	Software Development	(no update in the assignment action reason)

Action Reason Synchronization in Assignment

• John Doe - There is no update in the assignment action reason because none of the attributes were updated in the Architect position.

• Bonnie Vickers - The Sales Manager position was updated with a new job and the action reason specified in the position is Organization Change. The Organization Change action reason is associated with both - Synchronization from Position and Update position actions. Since all conditions are met, the assignment is updated with the Organization Change action reason.

• David Steward - Though the Director position was updated with a new job, but the action reason (Assignment Change) wasn't updated in the assignment because the action reason is associated only with Update Position action type and not the Synchronization from Position action.

Synchronize Person Assignments from Position Process

This process checks for the position action reason and the available action reasons under Synchronization from Position action to synchronize the assignment action reason.

This feature enables you to correlate the change in assignment attributes with the position attributes because of position synchronization.

Steps to Enable

You need to enable position synchronization at the enterprise or legal entity levels. These are the steps to enable position synchronization at the enterprise-level.

1. On the Home page, click My Client Groups > Workforce Structures.
2. Click the Manage Enterprise HCM Information task.
3. Click Edit > Update.
4. Click OK.
5. In the Position Synchronization Configuration section, select Enable Position Synchronization and Action Reason check boxes. Select any other attributes for synchronization.
6. Click Review to check your changes.
7. Click Submit.
8. Click OK.

Now that position synchronization is enabled, let's add action reasons to the Synchronization from Position and Update position actions.

1. On the Home page, click My Client Groups > Workforce Structures.
2. Click the Configure Actions task.
3. Search for Synchronization from Position (ORA_POS_SYNC) action.

4. Click Continue.
5. In the Action Reasons section, Click Associate to associate the action reasons with the action.

6. Click Ok.
7. Click Submit.
8. Click Configure Actions task
9. Search for and click Update (PER_POS_UPD) action.
10. Click Continue in the Action section.
11. Click Associate and add the same action reason you added to the Synchronization from Position action, for example, Promotion.
12. Click Ok.
13. Click Submit.

Tips And Considerations

The action reason is synchronized only when the first position synchronization record is created in the assignment. If there is a correction in the position, then all changed attributes from position will be synchronized in assignment apart from the action reason.

Key Resources

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

• Position Synchronization, Chapter; Jobs and Positions in the Implementing Global Human Resources guide
• How Assignment Values Are Inherited from Position, Chapter; Jobs and Positions in the Implementing Global Human Resources guide
• Synchronize Person Assignment from Position Process, Chapter; Jobs and Positions in the Implementing Global Human Resources guide
• How Line Managers Are Synchronized Using Position Hierarchy, Chapter Employment Information > Assignments in the Using Global Human Resources guide.
• Action Framework, Chapter Employment in the Implementing Global Human Resources guide

Record Additional Data When Deleting an Assignment Record Using Employment Info Page

You can now select the action and action reason while deleting an assignment record using the view employment details page accessed from the Employment Info page. Additionally, the Action Occurrence extensible flexfield (EFF) is added so that you can store extra information while deleting an assignment record.

Select the Assignment Record to Delete from Employment Info Page

Click Delete on the View Employment Details Page to Delete the Assignment Record

Select the Action, Action Reason, and Enter Additional Information on the Delete Employment Details Page

A new Delete Employment Details page is now available with the following sections:

• Details: You can use this section to track the action and action reason for the assignment deletion. The action date is the effective date of the record being deleted and can’t be edited. You can configure new actions and their action reasons under the action type Delete this change. The actions and action reasons will be available for selection in the Delete Employment Details page.

• Additional Info: You can use this section to enter extra information about deleting the assignment record. This section contains the EFF that you have enabled to store extra information.

If you have enabled the Additional Info section by using HCM Experience Design Studio and haven’t enabled any action occurrence EFF, then the Additional Info section will be blank.

This table shows details about the action occurrence EFF:

Name	Type	Module	Flexfield Code	Description
ActionOccurrence EIT Information EFF	Extensible Flexfield	Actions	PER_ACTION_OCC_EIT_EFF	Action Occurrence Extra Information EFF

• Comments and Attachments: You can use this section to add comments related to why the assignment record is being deleted. Additionally, you can add any file attachments to support the deletion. In this section, comments and attachments are associated with the approval workflow. The comments and attachments have a lifecycle of archive and purge after which the attachments are no longer accessible.

We have also introduced additional audit capabilities along with the existing application audit. The deleted data information will be stored in the newly created PER_EMPL_DELETE_TXN_DATA table. The deleted assignment data will be stored as XML in the EMPL_DELETE_TXN_DATA_XML column and can be retrieved using the BI Publisher.

Users can record additional data when deleting an entire assignment or deleting a date effective assignment record.

Steps to Enable

• By default, the ORA_PER_EMPL_ADD_ASG_DEL_INFO profile option is set to N and ORA_PER_EMPL_COMBINED_CORRECTION_DELETION is set to No. This means that you can’t add additional information while deleting an assignment update. If you want to additional information while deleting an assignment update, set the profile values to Y and Yes.

Profile Option Code	Profile Display Name	Default Profile Value
ORA_PER_EMPL_ADD_ASG_DEL_INFO	Add Additional Information While Deleting an Assignment Update	N
ORA_PER_EMPL_COMBINED_CORRECTION_DELETION	Combined Correction and Deletion Enabled for Employment Records	No

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

1. Navigate to the Setup and Maintenance work area.

2. Search for and click the Manage Administrator Profile Values task.

3. Search for the ORA_PER_EMPL_ADD_ASG_DEL_INFO profile option code and select the profile option in the search results.

4. In the Profile Values area, enter Y in the Profile Value field.

5. Search for the ORA_PER_EMPL_COMBINED_CORRECTION_DELETION profile option code and select the profile option in the search results.

6. In the Profile Values area, enter Yes in the Profile Value field.

7. Click Save and Close.

Tips And Considerations

You can configure the Delete page and sections for this feature by using HCM Experience Design Studio.

• The Delete button will be visible on the View Employment Details page only when the user has the Delete Worker Date Effective Assignment (ORA_PER_DELETE_WORKER_DE_ASSIGNMENT) privilege.

• The Delete Employment Details page is supported by the existing Delete Assignment approval process.

Key Resources

• Combined Correction and Deletion for Assignment, Salary, and Document Records on View Employment Details Page feature in the 22C Global Human Resources What's New.

Enhanced Retained Grade Context in Assignment Extensible Flexfield

We have improved the Retained Grade context in the Assignment Extensible Flexfield (EFF) to provide an enhanced user experience with new segment names and lookups.

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 refer to Create Grade Retention Page and Associate With Retained Grade Context chapter Employment in the Implementing Global Human Resources guide.

Person Costing Section in Local and Global Transfer Flow

We have enhanced the ability of users to enter person costing information, at assignment level, for permanent global transfers in the newly added Person Costing section of the Local and Global Transfer flow. The person costing data is populated in the section from the source assignment and you can make changes before it is copied to the destination assignment.

Person Costing Section for Global Transfer

This feature provides a better user experience while recording an employee's costing information as part of the Local and Global Transfer transaction.

Steps to Enable

Refer Steps to Enable documented in the feature Ability to Record Costing Information as Part of a Global Transfer feature in the 23A Global Payroll What's New.

Tips And Considerations

• By default, the Person Costing section isn’t displayed on the Local and Global Transfer flow. You need to enable the section and mark it as required by using HCM Experience Design Studio.

• Once enabled, the section only applies to a permanent global transfer and not local transfer. To display the Person Costing section in the Local and Global Transfer page, you need to change the legal employer and select the transfer type as permanent in the When and Why section.

• If the user doesn't visit the Person Costing section, then the data from the source assignment won’t be populated in the section and copied to the new assignment.

• The section won’t be displayed for global transfer transactions that are resumed after an upgrade.

• If both Copy Costing feature and Costing Region are enabled, the Costing Region takes priority, that is, the Copy person costing override to the new employment record flag on the Payroll region will be hidden

• When the Costing Region is enabled, no further copy will happen. If the costing data exists at other levels than assignment, they will NOT be copied to the new assignment, nor will any future dated costing records.

Key Resources

• For more information refer to Ability to Record Costing Information as Part of a Global Transfer feature in the 23A Global Payroll What's New.

Validate Salary During Hire Date Change for Worker

You can now validate the salary when you change the hire date for a worker. When the hire date is changed, the application now checks for salary related validations and displays them on the page as an error or warning message based on the user configuration.

When you change the hire date using actions, such as Change Hire Date or Work Relationship, the application will perform a salary validation. These are the salary validations:

• Check if a salary change proposal is pending for approval

• Check if there is more than one salary existing for the assignment

• Check if the salary basis is no longer active

• Check if the salary amount violates the salary range on the proposed hire date

Using a profile option, you can configure the validation result as an error or warning message. When a validation fails and the profile option is set to error, you won’t be allowed to submit the transaction. However, if the profile option is set to warning, a warning message is displayed and you can submit the transaction if you choose to ignore the warning.

Users can preserve data integrity by validating the salary when changing the hire date.

Steps to Enable

By default, this profile option is set to Error. If you don’t want the salary validations to prevent the transaction from being submitted, set the profile value to Warning.

Profile Option Code	Profile Display Name	Default Profile Value	Description
ORA_CMP_SALARY_CHECKS_BEHAVIOR_IN_CHANGE_START_DATE	Salary Validations Behavior When Changing Start Date	Error	Configure how to handle salary validation failures when people change the start date.

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

1. Navigate to the Setup and Maintenance work area.

2. Search for and click the Manage Administrator Profile Values task.

3. Search for the ORA_CMP_SALARY_CHECKS_BEHAVIOR_IN_CHANGE_START_DATE profile option code and select the profile option in the search results.

4. In the Profile Values area, enter Warning in the Profile Value field.

5. Click Save and Close.

Tips And Considerations

• Salary range validation will be performed only when the salary range violation behavior in salary basis is set to Error and the profile option is also set to Error. When the profile option is set to Warning, validation will not be performed even though the setting in salary basis is set to Error.

• The salary validations are performed when you submit the hire date change by using only the Change Hire Date and Work Relationship responsive pages. Similar validations will be done for HCM Data Loader and REST API in a future release.

• When the salary validation fails, the warning or error message is displayed based on how the profile option is configured. You can’t set separate error or warning messages for individual validations.

Simplified Document Records Section in Responsive Employment Correction Flow

We have streamlined the display of the Document Records plugin section on the correct employment details flow by not disabling the Edit and Delete buttons. Instead, the buttons are now hidden if the user has no access to edit or delete document records.

Edit and Delete Buttons Hidden in Document Records Plugin Section on Correct Employment Details Page

Users will experience a consistent behavior similar to the Document Records flow where the buttons are hidden.

Steps to Enable

Disabling of the Edit and Delete buttons doesn't require any configuration. However, to display the document records section on the page, you have to make the section visible in the Transaction Design Studio.

V3 Termination Support for End Temporary Assignment

We have enhanced V3 Termination by giving users the ability to end temporary assignments by using the Terminate Employment quick action. The original assignment is activated when you terminate the temporary assignment.

Note: Correct termination and reverse termination are not supported for temporary assignments.

End Temporary Assignment Using Terminate Employment Page

View Termination Page When You End a Temporary Assignment

V3 Termination users can now end temporary assignments.

Steps to Enable

You need to enable V3 Termination to use this feature. To do this, refer to the Steps to Enable section of the V3 Termination and Resignation feature in the 22A Global Human Resources What's New.

Tips And Considerations

• You can correct the end temporary assignment by selecting the record from the Employment Info page. However, you can't correct the termination date of the temporary assignment.
• You can reverse the end temporary assignment by selecting the record from the Employment Info page and deleting that record.
• Correction or deletion of the record from the Employment Info page will impact only the selected assignment. If you need to make changes for more than one assignment, you must perform the action for each assignment.

Key Resources

• For more information refer to Terminations > Chapter Hire and Manage Workers in the Using Global Human Resources guide.

HDL Support for Terminate Assignment Transactions

We have enhanced HCM Data Loader (HDL) support for V3 termination to now upload assignment level termination transactions, such as termination, correct termination, and reverse termination. Earlier, V2 and V3 termination users could only upload work relationship level termination transactions by using the TerminateWorkRelationshipFlag attribute and HistoryLoad. However, the assignment level termination transactions can be uploaded through HDL by only using the TerminateAssignmentFlag attribute.

Here are some example DAT files:

Terminate an Assignment

METADATA|Assignment|ActionCode|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|WorkTermsAssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId|TerminationDate|NotificationDate|LastWorkingDate|ReviewUserAccess|TerminateAssignmentFlagMERGE|Assignment|END_ASG|INACTIVE_PROCESS|E|Vision Corporation Enterprise|4712/12/31|Y|1|2022/07/03|TEST_WT_ut_hdl18_02|HRC_SQLLOADER|TEST_ASG_ut_hdl18_02|2022/07/02||2022/07/02|A|Y

Correct an Assignment Termination

METADATA|Assignment|ActionCode|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|WorkTermsAssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId|TerminationDate|NotificationDate|LastWorkingDate|ReviewUserAccess|CorrectAssignmentTerminationFlagMERGE|Assignment|END_ASG|INACTIVE_PROCESS|E|Vision Corporation Enterprise|4712/12/31|Y|1|2022/07/03|TEST_WT_ut_hdl18_02|HRC_SQLLOADER|TEST_ASG_ut_hdl18_02|2022/07/02||2022/07/02|A|Y

Reverse an Assignment Termination

METADATA|Assignment|WorkTermsAssignmentId(SourceSystemId)|SourceSystemId|SourceSystemOwner|ActionCode|ReasonCode|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|ReverseAssignmentTerminationFlagMERGE|Assignment|300100553121597|300100553121600|FUSION|ORA_EMPL_REV_TERMINATION||2022/05/02|4712/12/31|1|Y|Y

V3 Termination users will now have the ability to terminate an assignment, including correcting or reversing the termination by using HDL.

Steps to Enable

You need to enable V3 Termination to use this feature. To do this, refer to the Steps to Enable section of the V3 Termination and Resignation feature in the 22A Global Human Resources What's New.

Tips And Considerations

• To terminate an assignment using HDL, you must load the Assignment component with the TerminateAssignmentFlag attribute set to Y and specify the termination date for the TerminationDate attribute.

• If you don’t provide the WorkTerm attribute along with the Assignment component on the same date, the following error message will be displayed: WorkTerms records required. For date effective records having TerminateAssignmentFlag as Y, the error won’t be displayed. However, for date effective records without TerminateAssignmentFlag, the error will still apply.

• To reverse a termination, you must load the existing assignment component of type End Assignment and set the ReverseAssignmentTerminationFlag attribute to Y.

• The following points apply when you correct a termination:

  • To correct the termination attribute for an assignment, you must set the CorrectAssignmentTerminationFlag attribute to Y.

  • The LastWorkingDate attribute must be on or before the termination date. If the last working date exists and you don't provide a value, the existing last working date will be retained in case of postpone and auto calculated to the termination date in case of prepone. If you provide the last working date value, the new value will take precedence.

  • The notification date will be retained in case of postpone if you don’t provide a value. If you provide a value, the new value will take precedence. In case of prepone, you must provide a notification value. No error message will be displayed even if the notification date is after the termination date in case of postpone or prepone.

  • If you correct the termination date for a terminated assignment to a specific date, the end date must be blank or EOT.

  • If you correct the existing assignment termination record data without modifying the termination date, you must pass the EffectiveStartDate and EffectiveEndDate attributes of the existing assignment termination record. In this case, your changes will be applicable for the first inactive record (termination record).

  • Prepone will be allowed if there are future updates after the existing Termination or End Assignment inactive record. Future records will be deleted.

  • Postpone won’t be allowed if there are future updates after the existing Termination or End Assignment inactive record.

Key Resources

For more information refer to:

• Terminations > Chapter Hire and Manage Workers in the Using Global Human Resources guide.

• Examples of Loading Work Relationship Changes > Chapter Loading Workers in the HCM Data Loading Business Objects guide.

Include Work Schedule Information When Converting Pending Worker to Employee or Contingent Worker

You can now see a worker's work schedule assignment when you convert a pending worker to an employee or a contingent worker.

For example, an Elapsed 1 year work schedule is assigned to a pending worker, John Allens,

When the pending worker is converted to an employee, the work schedule is also copied.

This feature improves user experience by preventing assigning a work schedule again to an employee or contingent worker post conversion.

Steps to Enable

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

Tips And Considerations

• If you have overlapping or multiple work schedules, then the work schedules are copied if they are valid on conversion.
  • You can have overlapping work schedules only when the Primary attribute is set to yes for one work schedule and no for the other.
• This feature applies when the pending worker is converted either using Convert or the Quick Convert options or using the Run Convert Pending Workers Automatically ESS process.
• If the employment hire date is after the conversion date, the start date of the work schedule changes to the hire date.
• If you're quick converting a pending worker but want to change the date, then use the Edit Pending Worker task to change the date and then use the Quick Convert task.
• If you're using the Run Convert Pending Workers Automatically ESS process, only those pending workers are converted who have the Include in autoconversion attribute set to Yes.

Key Resources

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

• How You Convert Pending Workers, Chapter: Hire and Manage Workers > Hire People, in the Using Global Human Resources guide.
• How an Individual's Schedule Is Determined, Chapter: Absence Recording in the Using Absence Management guide.

Journeys

Visibility of Gatekeeper Law Journey Template

We have streamlined the visibility of the seeded Gatekeeper Law journey template by no longer displaying it on the Explore tab in Journeys.

Prevent users from exploring journeys that are not relevant to your organization.

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 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

Configure Task Groups in Journey Templates

You can now group common journey tasks in a task group and reuse this task group across multiple journey templates. For example, you can create a group of common tasks to use in various onboarding journeys.

You can configure a task group using the Task Groups tab on the Checklist Templates page. By default, any user who has access to Checklist Templates can create task groups.

If you want to restrict creation, then configure the role in Category Security. For example, if you add the HR specialist role, only users with that role can create task groups. 

Configure Access to Task Group Category

A HR specialist can use the Task Group button to view and create a task group.

Create Task Group

Configure Task Group Details

A task group acts like the parent task to which you add child tasks. You can specify the name and other details such as the eligibility profile and completion criteria at the task group level or at each specific task level.

Specify Task Group Details

When you add tasks to a task group, you can use any of the following options:

• Create Task – to create a new task
• Create Task from Task Library – to add an existing task from the task library

Add Tasks to Task Group

A task group can include one or multiple tasks. The tasks can be standalone, dependent, or a combination of both. You can also configure task groups that are dependent on each other.

Tasks Added to Task Group

To include the newly created task group in a journey template, you can use the Create Task from Task Group option when you add tasks to the template.

Add Task Group to Journey Template

You can select the predefined task group from the Task Group Name drop-down list.

Create Task by Selecting Previously Defined Task Group

Usage

You can use the Usage tab on the Task Groups page to see all the journey templates where the task groups are referenced. When you make a change to a task group, the changes reflect in all journey templates in which it is used.

Track Usage of Task Groups in Various Templates

Employee Experience

When a journey with a task group is assigned, the name of the task group doesn’t display anywhere. Workers only see a sequence of tasks that they need to complete. Based on any activation criteria or dependency configured on the setup side, the tasks display accordingly in Journeys.

Employee Views Only Tasks in Assigned Journey

This feature reduces redundancy, supports reusability, and makes it possible to manage tasks centrally.

Steps to Enable

To configure a task group, follow these steps:

1. Navigate to the Setup and Maintenance work area or My Client Groups > Employment.
2. Search for and click the Checklist Templates task or quick action.
3. Click the Task Group tab. Specify the name and other details.
4. Create new tasks or add tasks from the task library.
5. Include the configured task group in a journey template.
6. Click Save and Close.

Tips And Considerations

Task groups can’t be created in the Journeys app.

• Task groups can’t be added to an assigned journey or when creating a personal journey.
• Task group configuration is available only on the Checklist Templates setup page.
• Task groups can't be added to a journey template that has the Processing Mode as BI Publisher based notification. 
• Task groups that you reuse across journey templates work on the basis of reference. When you update a task group, the changes will reflect in all journey templates where the task group is used.
• The task group name you configure does not display to users when a journey template that includes that task group is assigned to them in Journeys.
• A journey template can have multiple task groups. But you can’t create a nesting of task groups, that is, you can’t create a task group within a task group.
• You can’t configure task dependency between tasks in one group and tasks in a different group. However, you can configure dependency between 2 task groups, say you have 2 task groups - task group A and task group B, you can configure task group B to get activated only when task group A is completed.  
• You can’t assign a stand alone task group to a user. A task group needs to be part of a journey template.
• A task group is also supported as a part of a journey template in the following operations:
  • Export and Import functionality to export or import a task group.
  • HDL support is scheduled for a future release.
• You can create a task group in the following checklist categories:
  • Enterprise Onboarding Step
  • Contextual Journey
  • All other general categories

Here are some points to consider when using tasks and task groups in a journey template:

Considerations	Task	Task Group
Where to configure?	Checklist Template page > Task Library or in template > Tasks tab	Checklist Templates page > Task Group  > Create
When to use?	Create tasks on a case by case basis.	When you have common tasks that can be used in different templates. You can use multiple task groups in a journey template.
How to manage?	Manage as part of template or manage as part of task library.	Go to Task Groups and manage the tasks. Use the Usage tab to track where the task groups are used.
Is eligibility criteria supported?	Yes, supports eligibility criteria.	Yes, supports eligibility criteria.
Is task dependency supported?	Yes. Task dependency works based on a one to one mapping.	Yes. Task dependency can be configured in the following ways: A task can be dependent on a task group. A task group can be dependent on a task. A task group can be dependent on a task group.
Can these features be used in all checklist categories?	Yes, you can create a task in all checklist categories.	No, task groups aren’t supported in the following checklist categories: Survey Guided Journeys
Can these be created in the task library?	Yes, you can create and add tasks to the task library.	No, a task group type can’t be created in or added to the task library.
How do users access the assigned tasks?	Access the task when the journey is assigned.	Access the tasks of a task group as individual tasks on the journeys pages. The task group name is not visible anywhere on the assigned journeys page.
After a task is assigned, and if the task configuration is updated, will the changes be reflected in assigned journeys?	Yes, using the Update Assigned Journey Attributes Based on Modified Journey Template ESS process.	No, currently this isn’t supported for task groups.

Key Resources

• 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.

Access Requirements

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

Schedule Recurring Journeys

You can now configure the recurrence for all categories of journeys except Survey and Enterprise Onboarding when assigning journeys using the Journeys app. For example, assign a recurring monthly check-in a manager schedules with their directs.

Prerequisite

You should have configured Enable recurrent scheduling to Yes on the Message tab of the journey template on the setup page to be able to specify the recurrence in the Journeys app.

With the recurrence configuration enabled, when you assign a journey in the Assign Journeys flow in Journeys app, you can choose these Repeat options:

• Never - Indicates the assignment is one-time and won't recur.
• Day - Indicates the assignment is on a daily basis.
• Week - Indicates the assignment is on a weekly basis. For example, every Monday.
• Month - Indicates the assignment is on a monthly basis. For example, say you have set the recurrence to start on 20th September and set the recurrence value to 3, then the journey is assigned on 20th September, 20th October, and 20th November.
• Year - Indicates the assignment is every year.

When you click Save, the recurrence is scheduled. Based on the start date and the frequency in the schedule, the assignment occurs in specific periods that fall between the start date and end date of the recurrence. In a specific period, you may want to assign the journey once or more than once. The Number of Runs Per Period drop-down list enables you to specify that. The journey assignment ends based on the configuration for End Recurrence.

If there are open periods from the previous assignment, you can enable the Expire previous open periods to set them to close automatically.  Confirmation details display after you save the schedule. You can edit the schedule before assigning the journey. Once assigned, the schedule can't be edited. 

Recurrence Configured

You can select the population to whom the journey must be assigned and assign the journey to them.

Select Assignees

Scheduled Allocations 

Once the journey is assigned, only HR specialists can deselect assignees or delete the whole schedule on the Scheduled Allocations tab in the Checklist Templates setup page.

Scheduled Allocations Tab

You can see the scheduled allocations for a specific journey by drilling down to the schedule and make changes to the assignees.

Assignees

The population to whom the journey is assigned are listed in the Assignees tab. You can select or deselect an assignee.

Period Summary

Based on the frequency selected in Journeys, a summary of the periods in the schedule is auto-generated and listed in Period Summary. The periods are Enabled by default and can’t be edited.

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

This feature enables you to schedule a journey on a recurring basis.

Steps to Enable

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

Tips And Considerations

• The recurring schedule and the selected population can't be edited from the Journeys pages.
• Only HR specialists can deselect assignees or delete the whole schedule for an already assigned journey using the Scheduled Allocations tab on Checklist Templates setup page.
• Once a period in the schedule completes, there’s no way to go back and update it.

Key Resources

• 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.

Access Requirements

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

Trigger Journeys Based on Nudges for Employment Events

You can now configure a nudge to automatically assign a journey when specific employment events occur.

You configure nudges for specific employment events in the Nudge Configuration work area. Nudges for employment events in this release update include the following:

Reason to Nudge	Purpose of Nudge
Employee's contract end date is approaching	Assign a journey to the recipient when the employee’s contract end date is approaching
Employee's probation period end date is approaching	Assign a journey to the recipient when the employee’s probation end date is approaching
Employee's retirement date is approaching	Assign a journey to the recipient when the employee’s retirement date is approaching

View Configured Nudges in the Nudge Configuration Page

This example shows you how to configure a nudge for the scenario, Employee’s contract end date is approaching:

1. Go to My Client Groups > Employment > Nudge Configuration. Click Add.
2. From the Module list, select the nudge type, Human Resources.
3. Select the reason, Employee's contract period end date is approaching.
4. Edit the default configuration name, as applicable.
5. Set the status to Active.
6. In the Days Before Contract Ends field, enter the number of days before the contract end date by when the nudge must be triggered and the journey must be assigned.
7. Click Add in the Channels section.
8. Select the Journeys channel type. The Active check box is selected by default.
9. Select the recipient type.
10. From the Action list, select a predefined journey in the Journey Name drop-down list.
11. Click OK.

Select the Channel Type and Associate a Predefined Journey

Run ESS Process

After the nudge is configured, when the Process HCM Nudges ESS job runs, it evaluates active nudges and identifies the population for whom the journey needs to be assigned.

The parameters you can specify for the job are:

• Module - The name of the product.
• Nudge Name - The name of the nudge.
• Mode - The mode to run the ESS process.
• Person Numbers - Comma separated list of person numbers.

This feature provides timely information to the employee, manager, or HR specialist and enables them to take appropriate actions.

Steps to Enable

1. Create the relevant journey template that needs to be assigned when a specific employment event occurs. Configure the journey template in My Client Groups > Employment > Checklist Templates.
2. Configure the nudge and associate the journey template. Configure the nudge in My Client Groups > Employment > Nudge Configuration.
3. Run the Process HCM Nudges ESS process.

Tips And Considerations

• Nudges that you configure for the Human Resources module currently support only employee as the recipient.
• Nudges for the predefined employment actions are evaluated only for the primary assignment of a worker. 
• When processing the nudge, the effective date in the system is taken into consideration. It is not based on the ESS job run date. The following dates are considered for the events:
  • Contract end date
  • Probation end date
  • Retirement date
•  After a journey is triggered for an event and there’s a change in the contract, probation, or retirement date, the journey assignment is reevaluated and reassigned again. The already assigned journey is not automatically removed.

Key Resources

• Refer to the 22D Talent What's New: Introducing Oracle Touchpoints.
• HCM Nudges section in the Using HCM Common Features guide.
• 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.

Access Requirements

• You must grant administrators the Nudge Configuration (ORA_PER_NUDGE_CONFIGURATION_DUTY) duty role to configure nudges.
• You must grant the Manage Journey (PER_MANAGE_CHECKLIST_TEMPLATE_PRIV) function privilege to work on checklist templates.

Learning Community and Learning Enrollment Task Types in Journeys

You can now use the Learn Community and Learn Enrollment task types in a journey. Using these task types, you can link a task to a learning community or a learning enrollment page as part of a journey. For example, a task which requires the user to join a collaborative community on design.

Prerequisite for using this feature

In order to use this feature you need to configure learning content. You should have subscribed to Oracle Learning Cloud. Contact Sales for this.

You can associate the learning community task type to the title of the learning item that you have already predefined.

Learn Community Task Setup

Link to Launch the Learn Community Task in Journeys

Joining Confirmation in Learn Community Page

You can configure the learning enrollment task type and associate it to the following content types:

• Course
• Learning journey
• Offering
• Specialization
• Video

Select Learn Enrollment Task, Specialization Content Type, and Learn Item

Link to Launch Specialization Course in Journeys Task

Information and Completion Criteria in Specialization Page

This feature enables you to directly join a predefined learning community or enroll in a learning course from a journey task.

Steps to Enable

1. Configure the learning content in Oracle Learning.
2. Associate the relevant learning content to the learning content type when configuring a journey task in Checklist Templates > Task setup.

Key Resources

• 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.

Access Requirements

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

This table shows the duty roles that support this feature and the predefined roles that inherits this duty roles.

Role	Job or Abstract Role
Use REST Service - eLearning Content Read Only ORA_WLF_REST_SERVICE_ACCESS_ELEARNING_CONTENT_RO	Human Capital Management Integration Specialist ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB
Use REST Service - eLearning Content ORA_WLF_REST_SERVICE_ACCESS_ELEARNING_CONTENT	Human Capital Management Integration Specialist ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB Learning Specialist REST Services ORA_WLF_LEARNING_SPECIALIST_REST_SERVICES_DUTY
Manage eLearning Content ORA_WLF_MANAGE_ELEARNING_CONTENT	Learning Specialist ORA_WLF_LEARNING_SPECIALIST_JOB

Person

Added Calculated Age Field to Biographical Info Region on Responsive Pages

The Age field is now added in the Biographical Info section of the Personal Details, and Family and Emergency Contacts responsive pages. This value is calculated based on the date of birth, date of death, and the effective date used when searching for a person.  When an employee views his or her own record,  the current date will be used for the calculation.  The calculation will also take into consideration the date of death. 

Age field in Biographical Info section

This feature improves data visibility and eliminates the need to manually calculate a person's age for extending benefits.

Steps to Enable

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

Tips And Considerations

• If approvals are enabled and effective date is specified in the Personal Details page and you edit the biographical info, after submitting the transaction, age is calculated based on the transaction date (sysdate). To get the updated value of age with respect to the specified effective date, minimize and expand the Biographical Info section.
• If you don't want the Age field to be displayed, you can create a Transaction Studio Design rule and set the field to 'Not visible'.
• The field is displayed only as a read-only field and is not editable since it's a calculated field.
• The Age field isn't stored and is not included in OTBI.
• Age is displayed in "y years m months d days" format.
• If effective date (specified in Advanced Search) is after the date of death, age will be calculated as the duration between date of birth and date of death.
• If effective date (specified in Advanced Search) is before the date of death, age will be calculated as the duration between date of birth and the effective date.
• Age is calculated in the user preferred time zone.
• This field isn't available in the REST resource.
• This field isn't available in the approval BIP report template.

Increase to the PER_ADDRESSES_F attribute TOWN_OR_CITY to 60 Characters

The field length of the TOWN_OR_CITY attribute in the PER_ADDRESSES_F table has been 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.  You need to 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).

Disability Attributes Added to the Change Personal Information Approval Rule

The Change Personal Information approval rule has been enhanced with the addition of the Current Person Disability and Proposed Person Disability attributes.  You can now configure your approval rule based on these attributes, as required.

Change Personal Information Approval Rule Disability Attributes

Configure the Change Personal Information approval rule with the newly added Current Person Disability or Proposed Person Disability attributes.

Steps to Enable

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

Tips And Considerations

There is no impact to existing rules on upgrade.

Key Resources

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

• Disability Disclosure, Chapter Person Information, Personal Information, Using Global Human Resources guide

SEARCH_PHONE_NUMBER Attribute in PER_PHONES Table to Store only Numeric Characters

The SEARCH_PHONE_NUMBER attribute in the PER_PHONES table is now improved so that it only stores numeric characters. This field stores a concatenation of the phone country code, area code, and phone number fields and is intended for searching people and isn't displayed on any page. For example, phone number 91-01-8768653789 is now stored just as 91018768653789.  Prior to this enhancement, special characters, such as hyphen, parenthesis, period, plus symbol, and alpha characters were being stored in the field.  

How You Update Existing Phone Details

You can update your existing data using a delivered person diagnostic job. All new phone records will begin to store the SEARCH_PHONE_NUMBER field with only numeric characters after this upgrade is complete.  Use these steps to run the diagnostic job:

1. Login with user having access to run diagnostic jobs.
2. Go to Settings and Actions > Troubleshooting > Run Diagnostic Tests.
3. Search for Person Diagnostic Auto Correct.
4. Select and click Add to run the job.
5.  Provide these input parameters
   1. Run Mode : Validate or Commit
   2. Corruption Type : 39
   3. Person Number : Person number (for example, 123) or comma separated list of person numbers (for example, 123,456,789) or blank.If left blank, it runs for the entire population.
6. Click Run.

This feature improves overall performance when searching for a person based on the phone number field, especially in Oracle Recruiting.

Steps to Enable

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

Tips And Considerations

• This feature doesn't impact phone number display in the Person pages.

• This feature might impact phone number-based saved searches and also phone numbers of all types, for example, work phone, home phone, and so on.
  • You need to upgrade your data so that searches become consistent.

• You can use the person diagnostic job to migrate existing phone numbers to the new format.
  • Data will be bulk ingested into the Oracle Search Index as part of the diagnostic job,.
  • Update Person Search Keywords ESS process will also be updated as part of the diagnostic job.
  • However, only primary work phone data will be ingested and updated in the ESS process.

• This feature applies to phone numbers uploaded using HCM Data Loader (HDL) and HCM Spreadsheet Data Loader (HSDL) as well.

• During upgrade, any inflight phone number transactions pending approval will be stored in the new format post approval.

Key Resources

• For more information, refer these resources on the Oracle Help Center: How You Update Person Search Keywords, Chapter: Person, Implementing Global Human Resources guide.

Workforce Structures

Include Employee Location in Approval Payload

You can now create approval rules based on the Employee Location attribute when creating a location.

This feature enables you to create approval rules if a location is an employee location.

Steps to Enable

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

Key Resources

For more information, refer to these resources:

• How You Manage HCM Approval Transactions, Chapter: Workflow Notifications and Approvals in the Using Common Features for HCM guide on the Oracle Help Center.

You can also refer to this document on My Oracle Support

• The Basics of Approval Rules, Oracle HCM Cloud Common Features Release 13 Transaction Console (Doc ID 2430452.1)

Employee Location Attribute for Client-Side Location LOV on Position

Location list of values (LoV) in position responsive pages is restricted to show only employee locations.

This restriction in selecting locations helps to keep the employment and position data synchronized.

Steps to Enable

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

Tips And Considerations

• If you want to exclude a specific location from the Locations LOV in the position pages, then you need to set the Employee Location attribute in the Location pages to No.
  • To enable the Employee Location attribute on the Location pages, go to the Transaction Design Studio (TDS) in the HCM Experience Design Studio and make the attribute visible for the Create Location and Location Details actions.

Key Resources

For more information, refer these resources:

• Locations, Chapter: Divisions, Departments, Worker Unions, Locations, and Trees, Implementing Global Human Resources guide on the Oracle Help Center.

Addition of Standard Annual Working Duration and Units of Measure for Organization

Full Time Equivalent (FTE) is the number of hours worked by a worker on a full-time basis and is typically used to determine the workload. The working hours and standard working hours are used to calculate the FTE for a worker.

Standard annual working duration and the units of measure (UOM) attributes are added to these pages - 

• Manage Enterprise HCM Information
• Manage Legal Entity HCM Information
• Manage Department

This is to calculate the adjusted FTE for workers belonging to organizations that don't work the standard 52 weeks annually. You can now default these values from the organization when you create a position.

You will be able to leverage these attributes on the responsive employment pages in a subsequent release.

Standard Annual Working Duration and Annual Working Duration Units attributes on the Manage Enterprise HCM Information page

Standard Annual Working Duration and Annual Working Duration Units attributes on the Manage Legal Entity HCM Information page

Standard Annual Working Duration and Annual Working Duration Units attributes on the Create Department page

The new attributes for organization can be used for defaulting the standard working annual duration in the position.

Steps to Enable

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

Tips And Considerations

• You can make date-effective updates and correct the existing values of standard annual working duration and UoM.

• For standard annual working duration attribute,
  • The minimum value is 0.0001.
  • You can specify a maximum of 8784 hours for standard annual working duration. The value of 8784 represents the maximum number of hours in a leap year.
  • If you provide a value between 8784 and 9999, then an error is displayed - "Standard Annual Working Duration 9,999 is too large - it must be a number less than the maximum value 8784.0000."
  • If you provide a value above 9999, then an error is displayed - "Value 10,000 for field Standard Annual Working Duration exceeds the number of decimal places allowed."

• The validations for the standard annual working duration and UOM  are shown only when you navigate from the page while similar validations for standard working hours and frequency are shown on tab out.

• You can see these fields on the update and correct pages for the enterprise and legal entity, whereas you can see these fields on the create, update, and correct pages for departments.

• The standard annual working duration and UOM attributes are also migrated when you migrate your location configuration using the Functional Setup Manager (FSM) export/import functionality.

• The standard annual working duration and Units of Measure (UOM) attributes are available in HCM Data Loader (HDL), HCM Spreadsheet Data Loader (HSDL), and the predefined HSDL department templates.

• The standard annual working duration and UOM attributes are added to the ManageOrganizations data model and to the UpdateOrganizationReport BIP template.

• You can't build rules using these attribute values as they aren't available in the approvals payload.

• These attributes will be available in the OTBI subject area in a future release.

• These fields aren't available to enable for audit.

Key Resources

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

• Work day Information chapter in the Implementing Global Human Resources guide.
• What happens if I specify the standard working hours in a position? chapter in the Implementing Global Human Resources guide.

Addition of Standard Working Hours, Standard Annual Working Duration, and Units of Measure for Location

Full Time Equivalent (FTE) is the number of hours worked by a worker on a full-time basis and is typically used to determine the workload. The working hours and standard working hours are used to calculate the FTE for a worker.

The following enhancements are included in this feature.

• Addition of standard working hours and frequency attributes on the location responsive pages. You can now default these values from the location when you create a position.
• Addition of standard annual working duration and the units of measure (UOM) attributes on the location responsive pages. This is to calculate the adjusted FTE for workers working from such locations because not all locations work the standard 52 weeks annually. You can now default these values from the location when you create a position.

Earlier, these values could only be defaulted from the enterprise or department.

You will be able to leverage these attributes on the responsive employment pages in a subsequent release.

The new location attributes can be used for defaulting the standard working hours and standard working annual duration in the position, in addition to defaulting from the department and the enterprise.

Steps to Enable

The Standard Working Hours and Standard Annual Working Duration are hidden, by default. You have to enable it for the Create Location and Location Details flows  in the Transaction Design Studio (TDS). These are the steps to enable the section on the Location Details page.

1. On the Home page, click  My Client Groups > HCM Experience Design Studio.
2. Select the Location Details action.
3. Click Add to add a rule.
4. Enter a name and description for the rule.
5. In the Page Attributes section, select the Location Details option.
6. For the Standard Annual Working Duration and Standard Working Hours attributes, select Visible.

7. Click Save and Close.

Repeat these steps to enable the fields for the Create Location action in the TDS.

Tips And Considerations

• You can make date-effective updates and correct the existing values of standard working hours, frequency, standard annual working duration, and UOM.

• The minimum value for standard working hours is 0 and 0.0001 for standard annual working duration.

• The values entered for standard working hours, standard annual working duration and UOM are copied when a location is duplicated. However, the date-effective update history isn't carried over for a duplicated location record.

• The standard working hours, frequency, standard annual working duration, and UOM attributes are also migrated when you migrate your location configuration using the Functional Setup Manager (FSM) export/import functionality.

• The standard working hours, frequency, standard annual working duration, and Units of Measure (UOM) attributes are available in HCM Data Loader (HDL), HCM Spreadsheet Data Loader (HSDL), and the predefined HSDL location templates.

• The standard working hours, frequency, standard annual working duration, and UOM attributes are added to the ManageLocations data model and also to the UpdateLocationReport BIP template.

• You can't build rules using these attribute values as they aren't available in the approvals payload as yet.

• These attributes will be available in the OTBI subject area in a future release.

• Standard Working Hours, Frequency, Standard Annual Working Duration and UOM will be included in the locations REST resources a future release.

• You can enable audit for these attributes, if required.

Key Resources

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

• Work day Information, chapter in the Implementing Global Human Resources guide.
• What happens if I specify the standard working hours in a position? chapter in the Implementing Global Human Resources guide.

Access Requirements

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

Addition of Standard Working Hours, Standard Annual Working Duration, and Units of Measure for Job

Full Time Equivalent (FTE) is the number of hours worked by a worker on a full-time basis and is typically used to determine the workload. The working hours and standard working hours are used to calculate the FTE for a worker.

The following enhancements are included in this feature.

• Addition of standard working hours and frequency attributes on the job responsive pages. You can now default these values from the job when you create a position.   
• Addition of standard annual working duration and the units of measure (UOM) attributes on the job responsive pages. This is to calculate the adjusted FTE for workers working on such jobs because not all jobs requires workers to work the standard 52 weeks annually. You can now default these values from the job when you create a position.

Earlier, these values could only be defaulted from the enterprise.

You will be able to leverage these attributes on the responsive employment pages in a subsequent release.

The new job attributes can be used for defaulting the standard working hours and standard working annual duration in the position, in addition to defaulting from the department and the enterprise.

Steps to Enable

The Standard Working Hours and Standard Annual Working Duration are hidden, by default. You have to enable it for the Job Details and Create Job flows in the Transaction Design Studio (TDS). These are the steps to enable the section on the Job Details page.

1. On the Home page, click  My Client Groups > HCM Experience Design Studio.
2. Select the Job Details action.
3. Click Add to add a rule.
4. Enter a name and description for the rule.
5. In the Page Attributes section, select the Job Details option.
6. For the Standard Annual Working Duration and Standard Working Hours attributes, select Visible.

7. Click Save and Close.

Tips And Considerations

• You can make date-effective updates and correct the existing values of standard working hours, frequency, standard annual working duration, and UOM.

• The minimum value for standard working hours is 0 and 0.0001 for standard annual working duration.   

• The values entered for standard working hours, standard annual working duration and UOM are copied when a job is duplicated. However, the date-effective update history isn't carried over for a duplicated job record.

• The standard working hours, frequency, standard annual working duration, and UOM attributes are also migrated when you migrate your job configuration using the Functional Setup Manager (FSM) export/import functionality.

• The standard working hours, frequency, standard annual working duration, and Units of Measure (UOM) attributes are available in HCM Data Loader (HDL), HCM Spreadsheet Data Loader (HSDL), and the predefined HSDL job templates.   

• The standard working hours, frequency, standard annual working duration, and UOM attributes are added to the ManageJobs data model and also to the UpdateJobReport BIP template.

• You can't build rules using these attribute values as they aren't available in the approvals payload as yet.  

• These attributes will be available in the OTBI subject area in a future release.

• You can enable audit for these attributes, if required.

Key Resources

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

• Work day Information chapter of the Implementing Global Human Resources guide.
• What happens if I specify the standard working hours in a position? chapter of the Implementing Global Human Resources guide.

Addition of Standard Annual Working Duration, Annual Working Duration and Units of Measure for Position

Full Time Equivalent (FTE) is the number of hours worked by a worker on a full-time basis and is typically used to determine the workload. The working hours and standard working hours are used to calculate the FTE for a worker.

Standard annual working duration, annual working duration, and units of measure (UOM) attributes are added to these position responsive pages -

• Request a New Position
• Request a Position Change
• Position Details (including Update, Correct, and Duplicate Position)

This is to calculate the adjusted FTE for workers in positions that don't work the standard 52 weeks annually. You can now default these values from the job, location, or organization when you create a position.

You will be able to leverage these attributes on the responsive employment pages in a subsequent release.

The new attributes can be used for capturing additional details of working duration on the position.

Steps to Enable

The Standard Annual Working Duration and Annual Working Duration fields are hidden, by default. You have to enable it for the Request a New Position, Request a Position Change, and Position Details flows in the Transaction Design Studio (TDS). These are the steps to enable the section on the Request a New Position page.

1. On the Home page, click  My Client Groups > HCM Experience Design Studio.   
2. Select the Request a New Position action.   
3. Click Add to add a rule.   
4. Enter a name and description for the rule.   
5. In the Page Attributes section, select the Position Details option.   
6. For the Annual Working Duration and Standard Annual Working Duration attributes, select Visible.

7. Click Save and Close.

Tips And Considerations

• You can make date-effective updates and correct the existing values of annual working duration, standard annual working duration, and unit of measurement (UOM). 

• The minimum value for standard annual working duration and annual working duration is 0.0001.

• Annual working duration is defaulted from the standard annual working duration if specified when a position is created. This behavior is similar to the defaulting of working hours from the standard working hours.
  • You can change the defaulted annual working duration value, but the UOM is the same as the standard working hours UOM.

• The values entered for the standard annual working duration, annual working duration, and UOM are copied when a position is duplicated. However, the date-effective update history isn't carried over for a duplicated position record.   

• The standard annual working duration, annual working duration, and UOM attributes are also migrated when you migrate your position configuration using the Functional Setup Manager (FSM) export/import functionality.

• The standard annual working duration, and UOM attributes are available in HCM Data Loader (HDL), HCM Spreadsheet Data Loader (HSDL), and the predefined HSDL position templates.  

• The standard annual working duration, annual working duration, and UOM attributes are added to the ManagePositions data model and also to the UpdatePositionReport BIP template.

• You can't build rules using these attribute values as they aren't available in the approvals payload as yet.

• These attributes will be available in the OTBI subject area in a future release.

• You can enable audit for these attributes, if required.

Key Resources

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

• Work day Information chapter in the Implementing Global Human Resources guide.
• What happens if I specify the standard working hours in a position? chapter in the Implementing Global Human Resources guide.

Access Requirements

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

Default Standard Working Hours, Standard Annual Working Duration and Units of Measure for Position

You can now default the standard working hours, frequency and standard annual working duration and annual working duration units in a position. You can default these values from the job, location, department, or enterprise in that order.

Let's understand how this works with the help of the following diagram.

The defaulting logic for the standard working hours, frequency, standard annual working duration and units of measure is given below.

1. Job: The first check is on the job specified in the position. If values for any of these attributes are available in the job, then these values are defaulted on the position.
2. Location: If any of the attribute values aren't specified on the job, then the check is done on the location specified in the position. If these values are specified in the location, then these values are defaulted on the position.
3. Department: If any of the attribute values aren't specified on the location, then the check is done on the department specified in the position. If these values are specified in the department, then these values are defaulted on the position.
4. Enterprise: If any of the attribute values aren't specified on the department, then the check is done on the enterprise. If these values are specified in the enterprise, then these values are defaulted on the position.

Earlier, you could default the standard working hours from either the enterprise, legal employer, or department. With this feature you can also default the attribute values from the job and location too.

Steps to Enable

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

Tips And Considerations

• You can default the standard working hours, standard annual working duration, and UOM on Request a New Position and Duplicate Position flows.

• If you change the business unit, department, location, or job in the position, then the existing defaulted standard working hours, standard annual working duration, and units of measure (UOM) values are also removed if they are defaulted from any of these objects. However, this doesn't apply when you duplicate a position.

• If you add a value for the standard working hours, standard annual working duration, and UOM at anytime after the work day information is defaulted, the values will be defaulted based on the recent hierarchy update. For example, if the standard annual working duration was earlier defaulted from the enterprise and you specify a value for the standard annual working duration for a department now, then the latest standard annual working duration value will be defaulted from the department.

• You can change any of the defaulted values in the position.

• The standard working hours, standard annual working duration, and UOM values are defaulted only when using the position pages and not when positions are loaded using HCM Data Loader (HDL) or HCM Spreadsheet Data Loader (HSDL).

Position Management - Filter Action Reasons Based on User's Roles

You can now filter the actions reasons LOV based on the logged in user's role. This LOV is now changed to a client-side LOV.

This feature is available on these responsive position 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 improves the user experience when working in responsive position pages by displaying action reasons relevant for the role.

Steps to Enable

You need to associate the action reasons on the Configure Actions page. In these steps, we will create a new action reason and associate the role.

1. On the Home page, click My Client Groups > Workforce Structures > Action Reasons.
2. Click Add.
3. Enter a name, code, and description for the action.

4. Click Submit.
5. On the Home page, click My Client Groups > Workforce Structures > Configure Actions.
6. Search and click the action with which you want to associate the specific action reason, for example, Update.
7. On the Edit Action page, click Continue in the Action section.
8. Click Associate.
9. Select the action reason you created.
10. Enter a start date for the association.
11. Select the roles you want to associate.

12. Click Submit.
13. On the Home page, click My Client Groups > Workforce Structures > Position Details.
14. Search for the position you want to update and click Update.

You can see the newly associated action reason for the logged in user.

NOTE: You can also see the action reasons that are available for all users and not associated with any role in the Action Reasons LOV.

Tips And Considerations

• There is no impact on HCM Data Loader (HDL) or HCM Spreadsheet Data Loader (HSDL) because of this feature.
• You can associate an action reason with multiple roles but the user needs to have at least one of the roles to see the relevant action reasons.
• The keyword search doesn't search for action type on the Configure Actions page. You might need to use the specific filter action type to easily find the right action.
• Action reasons that aren't associated with any role will be available to all users.
• Action reasons aren't supported for the delete action.
• If you're correcting the first date-effective position record, then the action reasons for the create action will be listed in the Actions Reasons LOV.
• Duplicate position flow is similar to the create position, hence action reasons related to the create action will be listed in the Actions Reasons LOV.

Key Resources

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

• Action Framework in the Implementing Global Human Resources guide.

Global HR 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.

Removal of Person Gallery and Portrait Access

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.

V2 Seniority Dates Removed in Update 23B

V2 seniority dates have been removed in Update 23B and are no longer supported. However, support for V1 seniority dates is still available.

Customers must move to either V1 seniority dates or V3 seniority dates to ensure business continuity. Moving to V3 seniority dates gives users richer capabilities.

To move to V3 seniority dates, customers must follow these steps:

1. Follow instructions in the Help Center topic Implement Global Human Resources Guide - Process to Migrate Seniority Dates.
2. Identify areas that reference Seniority Dates V2 tables - custom reports, fast formulas, eligibility profiles, extracts, and other custom integration.
3. Execute the trial migration in your non-production environments using the "Migrate to Version 3 of Seniority Dates" ESS process.
4. Compare the seniority dates results pre- and post-migration.

This will eliminate usage of unsupported pages.

Steps to Enable

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

Key Resources

For more information on V2 seniority dates, refer the following doc on MyOracleSupport.

• V2 Seniority Dates Deprecation in Release 23B (Doc ID 2935517.1)

Global Payroll Interface

Oracle Global Payroll Interface sends personal payroll information to third-party payroll providers and imports payslips and processed payroll data into Oracle HCM Cloud. You can configure payroll interfaces using the ‘Global Payroll Interface’ template to extend and augment your data feed to third-party payroll systems. If you import processed payroll data or payslips from your third-party payroll provider, the data is available for further reporting and analysis.

Global Payroll Interface For Absence Template Supports Basic Absence Records

Generate payroll interfaces using the enhanced Global Payroll Interface For Absence template to integrate summary level person absence records with third-party payroll vendors.

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

1. On the Home page, click the Data Exchange quick action under the My Client Groups tab.

2. Search for and select Extract Definition on the Data Exchange page.

3. Create an extract. On the Create Extract Definition dialog box, complete these fields:

   1. 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.

   2. Start Date: Provide a start date to create the extract definition.

   3. Type: Select the type as Payroll Interface.

   4. Changes Only: Ensure that you have selected this check box.

   5. Legislative Data Group: Search for and select an appropriate legislative data group.

   6. Source Template: Select the source template as Global Payroll Interface For Absence.

4. Click OK. You will find a list of default objects and attributes that are available.

5. Select Absence Information. You can find the attributes available under Attributes.

6. Once you have selected the attributes, click Review in the left-most pane to review your selection.

7. Click Save to submit your configuration and wait for the status to reflect Ready.

This feature supports basic person level absences integration.

Steps to Enable

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

Perform a Baseline Extraction of Global Payroll Interface V2

Perform a baseline extraction of delivered Global Payroll Interface V2 interface and payroll interfaces created as copies of Global Payroll Interface V2 to ensure that a full file doesn't get extracted. Changes have been delivered to handle payroll transfer scenarios.

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

You can perform regular data changes and extractions after the baseline extraction.

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

Steps to Enable

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

Key Resources

• For more information see Chapter 3, Generate Baseline Extract in the Implementing Global Payroll Interface guide located in the Oracle Help Center.

Perform Baseline Extraction Of Payroll Interfaces Generated Using Global Payroll Interface Template

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

Changes have been delivered to handle payroll transfer scenarios.

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

You can 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.

Payroll Interface for ADP Global Payroll V2 Supports Salary Using Simple Components

Integrate salary based on simple components with ADP Global Payroll systems using the Payroll Interface For ADP Global Payroll V2 template to generate payroll interfaces.

Sample Output File with Salary Components

Integrate salary based on simple components with ADP Global Payroll

Steps to Enable

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

Perform a Baseline Extraction of Payroll Interface for ADP Global Payroll

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

Changes have been delivered to handle payroll transfer scenarios.

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

You can 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.

Steps to Enable

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

Key Resources

For more information see Chapter 3, Generate Baseline Extract in the Implementing Global Payroll Interface guide located in the Oracle Help Center.

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

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

Changes have been delivered to handle payroll transfer scenarios.

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

You can 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.

Key Resources

For more information see Chapter 3, Generate Baseline Extract in the Implementing Global Payroll Interface guide located in the Oracle Help Center.

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.

Amendment of Driving License Categories

You can now use the enhanced Driving Licenses Categories for the keys AM and A2.

This feature provides a better user experience as you can use the enhanced categories to be in sync with the current law.

Steps to Enable

You don't need to do 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.

Organization Calculation Cards

The Organization Employer Social Insurance Details calculation card is available to store details of Employer Type (Private or Government sector) and Contributory Salary Reference Formula in the Social Insurance component group.

You can choose the formula you need to calculate the Contributory Salary.

Enter the required information like Gratuity to be Paid, Gratuity Salary Formula, and Gratuity Reference Formula in the Gratuity component group of the Employer Gratuity Details calculation card to process the Oman gratuity calculation.

IMPORTANT:: Write your own formula linked to the Legal Entity.  This formula sets the mandatory monthly salary as an input for the delivered Gratuity Formula, to calculate the pay that gratuity will be calculated on.

Gratuity Reference Formula: This formula is delivered based on the Oman labour laws. If your organization doesn't follow the labour law, you can write your own formula to be linked to the Legal Entity and this replaces the predefined formula to calculate the gratuity amount.

.

Process the Oman gratuity and social insurance calculation with Organization Calculation cards.

Steps to Enable

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

Person Calculation Cards

Create the Employee Social Insurance Details calculation card as part of the new hire process, or when you rehire an employee, when your product usage is set to Payroll or Payroll Interface. The following information can be recorded on an employee calculation card at payroll relationship level:

• Citizenship
• Registration for Social Insurance
• Exemption for Social Insurance Contribution Difference
• Country of Citizenship Pension
• Exception Type (if person is Emirati)
• Contributory salary override
• Contributory salary adjustment

Use the Employee Gratuity Details calculation card to trigger the gratuity payment process. This card is created automatically as part of the termination process if your product usage is also set to Payroll or Payroll Interface. The Oman Employee Gratuity Details hold values for the Override Amount and Latest Gratuity Payment Date.

You can use the Override Amount to replace the calculated gratuity amount. The application displays an error message if you enter a negative amount.

Use the Employee Gratuity Details calculation card to trigger the gratuity payment process and the Employee Social Insurance Details calculation card to trigger the social insurance process.

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.

New Segments Delivered in the Person Legislative Information Area

Two new optional attributes are delivered to store the relevant information: Gender Identity (ORA_HRX_ES_GENDER_IDENTITY) and Sexual Orientation (ORA_HRX_ES_SEXUAL_ORIENTATION). These are Person Legislative Information developer descriptive flexfield segments with empty lists of values. They are hidden by default. You’ll need to use HCM Experience Design Studio to enable these fields as required. You'll also need to update the Lookup Types with your specific values.

These new attributes will allow you to store complex employee data on gender identity and sexual orientation for diversity recording purposes.

You can use the HCM Experience Design Studio to determine in which flows and for which roles the fields should be made visible.

Steps to Enable

Configure the list of valid values for the fields:

1. Navigate to Setup and Maintenance.
2. Search for the task Manage Common Lookups.
3. Search for the Lookup Type ORA_HRX_ES_GENDER_IDENTITY and create the desired Lookup Codes.
4. Search for the Lookup Type ORA_HRX_ES_SEXUAL_ORIENTATION and create the desired Lookup Codes.

Enable the new fields for specific flows and roles:

1. Enter a sandbox. 
2. Click My Client Groups and access HCM Experience Design Studio > Transaction Design Studio.
3. Select the action (flow), in this example Personal Details, for which you want to enable the new field, or fields.
4. Create a new rule, specifying the criteria for which the rule is applicable, where Region is Demographic Info.
5. In the Person Legislative Information Developer Attributes row, click the Edit icon and choose which flexfield segments you want to make visible.

6. Validate that the rule is meeting the business requirements.
7. Publish the sandbox.

Tips And Considerations

The actions that contain the Gender Identity and Sexual Orientation fields are:

• Add a Nonworker
• Add Contingent Worker
• Add Pending Worker
• Create Work Relationship
• Edit Pending Worker
• Family and Emergency Contacts
• Hire an Employee
• Local and Global Transfer
• Personal Details

Key Resources

For more information, please refer to Transaction Design Studio – What It Is and How It Works (Document ID 2504404.1) on My Oracle Support.

Access Requirements

You must have the Human Capital Management Application Administrator role to perform the previously described steps.

Human Capital Management for United Arab Emirates

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

Emirates ID Validation

Comply with legislative requirements. The validation for the Emirates ID is now in the format NNN-NNNN-NNNNNNN-N where N represents a number. The 4-digit section corresponds to the year of birth, the application displays a warning message if the details are incorrect.

Comply with legislative requirements, the emirates ID validation is now 18-digits including the usage of hyphens.

Steps to Enable

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

Tips And Considerations

New hire employees will have the new format of 18 digits, but the old employees will continue to use the previous format of 15 digits. This may create some inconsistencies.

You can update the national identifiers using HCM Data Loader.

Human Capital Management for United States

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

New Hire State Electronic Report Enhancement

We have improved the New Hire State Electronic Report.  In support of Ohio's requirement, this report now includes a single header that records totals from all reported legal entities.

This enhancement removes manual work-arounds that were needed.

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.

SMS Integration in HCM Communicate

Quickly send an SMS to employees as an easy way to send communications. Campaign managers can now target employees who don’t have access to corporate emails.

Campaign administrators configure a messaging provider that then enables campaign managers to create an SMS communication.

Create SMS Campaign

Reach out to employees using SMS as well as email for a seamless customer communication experience.

Steps to Enable

Here’s how the campaign administrator configures the messaging provider:

NOTE: Before you configure the SMS messaging provider, you need an account with Twilio. Currently, Twilio is the only supported provider.

1. In the Setup and Maintenance work area, go to:
   • Offering: HCM Communicate
   • Functional Area:  Employee Communications
   • Task: Manage SMS Configuration
2. Select the option to Enable SMS Communications.
3. In the Manage SMS Configuration page, click Add.
4. Enter the basic provider account details.
5. Enter the message length, which is the maximum amount of characters employees can receive as an SMS. If the campaign manager exceeds this character limit, the application won't send the employees any characters exceeding the limit.
6. Select the Add footer text in all SMS sent by campaign managers option if you want to add text to the end of an SMS. For example, you can add a note about how to unsubscribe from the SMS message. The footer text isn't visible to the campaign manager.
7. Enter the account details of the provider, Twilio. Contact Twilio for more information.

8. When you set up Twilio as the provider, try testing the details using the Test Outbound Message button. Enter a mobile number and a message, then navigate to the Twilio site and view the message.

9. Click Save and Close.

10. Activate the account on the Manage SMS Configuration page.

NOTE: You can have only one active messaging provider.

Create SMS Messaging Provider

Journeys Integration with HCM Communicate

Promote Journeys with HCM Communicate for any Journey’s related employee communication campaigns. There are 2 types of journeys where HCM Communicate can help:

1. A journey that’s already assigned to an employee. A campaign manager can target, track, and follow up with employees to promote journey completion and increase completion rate using employee communications.
2. A journey that’s not assigned to an employee yet. A campaign manager can make employees aware of a journey using campaign communications and encourage them to complete that journey. They can also inspire employees to explore a specific journey and self-assign themselves to it.

As a campaign manager with the relevant access, you can do these tasks when creating an employee communication for Journeys:

• Create a campaign and associate one journey by selecting Promote Journey as the campaign purpose
• Select one active journey only
• Choose to promote a journey that’s not yet assigned to an employee or choose to drive a journey to completion if it’s already assigned to an employee
• Target a subsection of a previously targeted group
• Aim to target only those who don't have a journey assigned to them yet

Create a Campaign with Promote Journey as Campaign Purpose

Increase the rate of journey completion and journey assignment using employee communication campaigns.

Steps to Enable

The campaign administrator needs to create a communication team with Promote Journey as the purpose of the campaign. This setup enables the campaign manager to select Promote Journey when they create the campaign.

Add Communication Team Page with Promote Journey Campaign Purpose

1. In the Setup and Maintenance work area, go to:
   • Offering: HCM Communicate
   • Functional Area: Employee Communications
   • Task: Manage Communication Teams

2. On the Manage Communication Teams page, click Add.

3. In the Details section, enter a name and description for the communication team. Select Promote Journey as the campaign purpose.

4. 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.

5. 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.

6. 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.

7. Click Save and Close.

8. On the Manage Communications Team page, select the Activate option for the team.

Tips And Considerations

Key Resources

For more information see the following in the Administering HCM Communicate guide on the Oracle Help Center: Create a Communication Team

Access Requirements

Before the campaign manager and employee use this feature, review these setup details:

• Ensure the Explore Journeys privilege (PER_EXPLORE_JOURNEYS_PRIV) and the View Global Journeys privilege (PER_VIEW_GLOBAL_JOURNEYS_PRIV) are assigned to the role responsible for assigning journeys to employees. These privileges give the role access to the Explore tab in Journeys so they can assign journeys to employees.
• Ensure the Explore and the Assign to Others options are enabled in the Checklist template in the Security tab for the role responsible for viewing and assigning the specific checklist template or journey that their role allows them to view.

A campaign manager needs the following to use this feature:

• View Global Journeys (PER_VIEW_GLOBAL_JOURNEYS_PRIV) functional privilege to view journeys from the list of values.
• Explore option enabled in the Checklist template in the Security tab to view the specific checklist template or journey that their role allows them to view. The journey administrator enables this option.

An employee needs the following to use this feature:

• View Global Journeys (PER_VIEW_GLOBAL_JOURNEYS_PRIV) and the Explore Journeys (PER_EXPLORE_JOURNEYS_PRIV) functional privileges to access the Explore tab and view journeys in the Explore tab on the Journeys page.
• Explore and Assign to Self options enabled in the Checklist template in the Security tab to view specific checklist template or journey that their role allows them to view and the ability to assign it to themselves.

Sender Profiles in Test Emails

Give campaign managers the ability to configure campaigns that send communications on behalf of senior management using sender profiles. As a campaign manager with sender profiles, you can preview emails with a sender profile before activating a campaign. Before this, preview emails used the sender profile associated with the application, not those assigned to the campaign. To start using sender profiles in test emails, the campaign administrator needs to create a sender profile and associate it to a communications team. The campaign manager can then create a campaign with that communication team and send a test email using the sender profile before activating the campaign.

Sender Profile Test Email

Control the sender details when testing emails before they’re officially sent out.

Steps to Enable

Here’s how the campaign administrator configures a sender profile:

1. In the Setup and Maintenance work area, search for:
   • • Offering: HCM Communicate
     • Functional Area: Employee Communications
     • Task: Manage Email Profile Options
2. Select the option to enable email profiles.
3. Enter the details for the sender profile.
4. Click Save and Close.

Now the campaign administrator adds the sender profile to a communications team:

1. In the Setup and Maintenance work area, search for:
   • • Offering: HCM Communicate
     • Functional Area: Employee Communications
     • Task: Manage Communications Team

2. On the Manage Communication Teams page, click Add.

3. In the Details section, enter a name and description for the communication team. Select the campaign purpose.

4. 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.

5. 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.

6. 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.

7. Click Save and Close.

8. On the Manage Communications Team page, select the Activate option for the team.

Key Resources

For more information see the following in the Administering HCM Communicate guide on the Oracle Help Center:

• Create an Email Sender Profile
• Create a Communication Team

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.

Global HR

New Subject Area to Report on Archived Documents of Record

You can now view reports on the attributes related to the archived documents of record with the Workforce Management - Documents of Record Archive Real Time subject area.

You need to run the ESS job - Archive Documents of Records, before reporting using this subject area. The subject area has the same data security as the existing subject area named Workforce Management - Documents of Record Real Time.

Additionally,following attributes related to archive are included in the Document Type dimension under the subject area Workforce Management - Documents of Record Real Time subject area:

• Archive Criteria Basis (ARCHIVE_CRITERIA_BASIS)
• Archive After Days (ARCHIVE_CRITERIA_DAYS)
• Purge After Days (PURGE_ARCHIVE_CRITERIA_DAYS)

You can view advanced reports on the archived documents of record with the new subject area Workforce Management - Documents of Record Archive Real Time.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Access Requirements

BI Duty Role	BI Job Role
Documents of Record Transaction Analysis Duty Documents of Record Transaction Analysis	Human Resource Analyst Line Manager

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	Removal of Person Gallery and Portrait Access	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.
Global HR	V2 Seniority Dates Removed in Update 23B	23B	Seniority Dates Enhancements	17D	Customers must move to either V1 seniority dates or V3 seniority dates to ensure business continuity. Moving to V3 seniority dates gives users richer capabilities.

__________________________

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
All HCM Products	Get News Feed Suggestions On Your Next Likely Actions	Get suggestions on your next likely actions in your news feed layout. This feature is currently in Controlled Availability and is available in Oracle Fusion Cloud HCM, Financials, Project Management, and Procurement. Artificial intelligence and machine learning algorithms predict and suggest the actions each user is most likely to take during a session. The algorithms use historic navigation behavior and patterns of each user and users like them to determine which navigation target they’re most likely to visit.	All Newsfeed Customers	You will need to log a Service Request (SR) through My Oracle Support and request for a promotion code.	23A	Yes

Human Resources Controlled Availability

Get News Feed Suggestions On Your Next Likely Actions

Get suggestions on your next likely actions in your news feed layout. This feature is currently in Controlled Availability and is available in Oracle Fusion Cloud HCM. Artificial intelligence and machine learning algorithms predict and suggest the actions each user is most likely to take during a session. The algorithms use historic navigation behavior and patterns of each user and users like them to determine which navigation target they’re most likely to visit.

Oracle Fusion Cloud Applications have a wide range of functionality and it can sometimes be difficult to know how to navigate to a task. With news feed suggestions, you can get to the tasks that matter faster. For example, if reviewing and approving expense reports is a task commonly performed by managers in your organization, new managers will receive a suggestion in their news feed to perform that task. Or if a few team members are entering performance goals, other members of that team see this task as a suggestion in their news feed.

These are some of the business benefits of this feature:

• Receive recommendations in your news feed on your next likely actions during that session
• Discover actions that other users like you have taken within Fusion
• As an administrator, you can pin specific task flow pages as a suggestion to raise the visibility of the task

Suggestions Tab in the News Feed Layout Showing Six Recommendations

Steps to Enable

To enable this feature, you need to log a Service Request (SR) through My Oracle Support and request for a promotion code. This feature is currently in Controlled Availability and requires a promotion code. For details, see Fusion Global HR: How to Apply for News Feed Suggestions Under Controlled Availability (DOC ID 2914373.1).