What's New

October Maintenance Pack for 23C

Revision History

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

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.

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.

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.

Phone Validity Field Updated to List of Values

The Phone Validity field, which is used to identify when the phone number should be used as a method of contacting a person, such as day, evening, or weekends, has been updated to be a List of Values rather than a text box.

In earlier releases, if the Phone Validity field was exposed using Page Composer, it was displayed as a text box. The data was validated against the lookup code Contact Times (PER_CONTACT_TIMES). Now, if the validity field is displayed using Page Composer, there will be two fields displayed, one with the List of Values and one as a text box. You need to use Page Composer to hide the text box field, so that you see only one Phone Validity field with the List of Values. 

The benefit of this change is that the Phone Validity field will be displayed correctly with a List of Values. 

Steps to Enable

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

Update 23C

Revision History

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

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.

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.

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.

Area of Responsibility (AOR)

Introducing Areas of Responsibility Usage

This enhancement introduces 2 main features:

1. Usage in Areas of Responsibility.
2. Eliminate the need to Include in Work Contacts for Journey task performers.   

Usage in Areas of Responsibilities

Enhance the utilization of your Areas of Responsibility (AOR) and performance of your HCM Approvals and Journeys by specifying the AOR's Usage attribute to filter to the relevant consuming product area.

Now, you must create AORs with a specific purpose and select an appropriate setting for them. Also, Journeys and Approvals don’t require the participation of all representatives. This enhancement currently supports Usage for HCM Approvals and Journeys.

The HCM Data Security evaluates and applies to all AORs regardless of the Usage setting. These examples show how Usage settings are used in various scenarios:

You can specify the Usage in any of these sections:

• Basic Info section on the Responsibility Template
• Individual representative's AOR

A new multi-select Usage LOV now captures the purpose of the responsibility. When assigned to a person, the same values will default on the person-level responsibility.

You can find the Usage attribute in the Basic Info section of the Create Responsibility Template page.

You can also find Usage in the Basic Info section of the representative’s AOR. If you create an AOR from a template, the Usage setting defaults from the associated responsibility template. 

Additionally, the Areas of Responsibility Templates homepage offers an additional filtering option for the Usage attribute that you can use to find which responsibility templates are designated for Checklist or Approval, or both. You can also find out if the responsibility templates are designated for no Usage at all.

NOTE: No Usage implies that the template is strictly used for security purposes.

The Area of Responsibility HR Data Load (HDL) and REST service are updated to support the new Usage attribute. The HDL and REST service accepts comma-separated values, such as "ORA_PER_AOR_APPROVAL,ORA_PER_AOR_CHECKLIST" to load multiple Usage values. While NULL is also accepted for security scenarios, any other values or duplicate values will produce an error message during processing.

The Refresh Representatives Data ESS process has also been updated.  This process writes AOR data to a denormalized table used for reporting purposes. Data captured from the Usage field will appear in separate columns, i.e., APPROVALS_FLAG and CHECKLIST_FLAG.

Additionally, the existing "Person Diagnostic Auto Correct" diagnostic report has been modified to allow you to verify whether all existing Usage values have been updated by the upgrade script, or if some still need to be updated. 

Eliminate the need to enable Work Contact for Journeys users

Starting with this release, you don't have to enable the "Include in work contacts" option as a Journeys user, unless the representative is truly a contact.

During checklist allocation, the individuals with the selected responsibilities are identified and designated as task performers or owners, regardless of the work contact’s flag. Journeys users must specify Usage as Checklist.

Furthermore, you can disable the “Include in work contacts” option if a representative shouldn’t be listed in Connections, Directory, Person Spotlight, or Employment and Benefits Transactions.

1. The Usage attribute improves performance as it enables users to send the appropriate Approval and Checklist related AORs to HCM Approvals and Journeys, respectively.
2. Removing the "Include in Work Contacts" constraint eliminates any confusion as to why certain representatives appear in Connections, Directory, Person Spotlight, or in Employment and Benefits Transactions.

Steps to Enable

There are no additional setup steps to display the Usage field on the Responsibility Template or Areas of Responsibility Basic Info sections.

With the 23C upgrade, a script will update existing responsibility templates and person-level responsibilities (AORs). This script will default to enable both approval and checklist Usage values so there are no regression issues. To take full advantage of this enhancement, you should review the usage and modify the usage values based on your own specific business requirements. 

When creating new AORs for your representatives, you need to first consider the intended purpose of the AOR and then set the Usage value appropriately if you expect that representative to be utilized in HCM Approvals and Journeys.

Tips And Considerations

• For any new AORs, consider the intended purpose of the AOR and choose the appropriate Usage setting. Not all representatives are involved with Checklist (which is the underlying basis for Journeys), or Approvals. Note that all AORs will be considered from an HCM Data Security perspective.

• It’s recommended to use Responsibility Templates to appropriately default the Usage values and Work Contacts setting for your representatives' assigned responsibilities. 

• The classic UI version of Manage Areas of Responsibility does not show the Usage field, so we’ll enable Usage values for both Approval and Checklist options by default.

• It’s recommended that you move to responsive Areas of Responsibility as the classic Manage Areas of Responsibility UI will be deprecated in a future release.

• The 23C upgrade will enable both Usage settings (Approval and Checklist). From the Diagnostic Dashboard, Application Diagnostic users should verify all values have properly defaulted after the upgrade using the diagnostic report, Person Diagnostic Auto Correct.
  • Input values are required for this diagnostic report. Specify the following parameters: 
    • Run Mode:  VALIDATE (or COMMIT after validation step, only if necessary)
    • Corruption Type:  41 (this value is specific to AOR Usage validation)

  • A diagnostic summary report will be created. In the Executions section, under the Execution ID column, you must choose the report link. This report identifies the number of responsibilities and the number of responsibility templates where usage has not been set. Take appropriate action, if necessary for all usage occurrences to be updated. 

• Ensure that you’ve selected Approval as the Usage option for the representative to receive an approval notification.

• Ensure that you’ve selected Checklist as the Usage option for the representative to appear in the Journeys task.

• An AOR's Usage will be included in the OTBI Areas of Responsibility subject area for reporting in a future release.

• It’s recommended to reevaluate any customizations related to displaying representatives such as those previously made to Connections, Directory, Person Spotlight, and Contact Us sections in Employment and Benefits Transactions.

Key Resources

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

• Responsibility Templates: 
  • Improved Areas of Responsibility User Experience Through Responsibility Templates, What's New (Release 20B).
  • Areas of Responsibility Templates, Areas of Responsibility chapter, Using Global Human Resources guide.

• Assign AOR:
  • How You Assign Areas of Responsibility, Areas of Responsibility chapter, Using Global Human Resources guide.

• Run Diagnostic Tests

Access Requirements

Users with the following job roles can perform the corresponding actions:

Autocomplete

Autocomplete Rules for Person Business Object

You can now default the Hirji date of birth for a person in a Saudi legal employer using a delivered rule for the Person Business Object, based on the value entered in the Date of Birth field.

The rule name is SA Default Hijri Date Based on Date of Birth and it's a Field Modification Rule Type:

If copied and activated, the rule is triggered for the following new person flows in a Saudi Arabian legal employer:

• Hire an Employee (EMPL_ADD_EMP)
• Add Contingent Worker (EMPL_ADD_CWK)
• Add Pending Worker (EMPL_ADD_PWK)
• Add Nonworker (EMPL_ADD_NWK)

Once you’ve entered the person’s date of birth and you move from the Personal Details section (either to another section, or to submit the record), the Hijri Date of Birth field is populated in the format DD/MM/YYYY.

Note:

• The Hijri date is calculated using an Oracle global function based on the Umm al-Qura calendar.
• You can optionally change the format from DD/MM/YYYY in your copy of the rule.
• The Hijri date of birth is defaulted only if the Hijri Date of Birth field is blank. Therefore, to correct an existing (Gregorian) date of birth and to recalculate its equivalent Hijri date, you must delete the existing Hijri date of birth and then correct the (Gregorian) date of birth. This will then repopulate the Hijri Date of Birth field with the recalculated date.
• You can override the defaulted Hijri date of birth.
• The delivered rule is not triggered for existing person records, so even if the Hijri Date of Birth field is left blank when you create and submit the new person record, the rule will not trigger again for this record. For example, if you find the person’s (Gregorian) date of birth is incorrect later, you’ll have to record their Hijri date of birth manually.

You can, subject to approval from Oracle, use the delivered rule as a template to create other rules for use with the new person flows listed above. For example, you could create rules for each of the following Hijri date fields using the rule type suggested:

These are the parameters to get the Hijri equivalent date from a given Gregorian date field:

You can now use the delivered rule for the Person business object for the Saudi legislation. You can use the rule to default the Hijri date of birth based on the Date of Birth field entered when a new person is added.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

To enable Autocomplete Rules in the HCM Experience Design Studio, you need to log a service request (SR). To get access, please review and follow the instructions provided in the My Oracle Support document, Enabling Oracle HCM Cloud Autocomplete Rules (Document ID 2767655.1).

Key Resources

For more information on Autocomplete Rules for HCM products, refer to these resources on the Oracle Help Center:

• Person Business Objects, Chapter 5 Business Objects in Autocomplete, Configuring and Extending HCM Using Autocomplete Rules

For more information on usage of this rule and the creation of other Hijri Date rules, refer to this resource in My Oracle Support:

• Oracle Fusion HRMS (Saudi Arabia): HR Implementation and Functional Considerations (Doc ID 1567452.1)

Access Requirements

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

Document Records

Tags to Support Document Type Classification and Grouping

You can now make use of the new Tags attribute to classify and group document types during creation and editing.

The following tags are delivered as a starting point:

• Employment
• Identification
• Legal

However, you can add additional values to the user lookup type ORA_PER_DOC_TYPE_TAGS.

To specify Tags:

1. In Setup and Maintenance, go to the Document Types task and click Create.
2. In the Document Type Information section, click the dropdown beside Tags.
3. Select the appropriate value from the list of tags.

Tags will be available on the Redwood Document Records landing page to filter records in a future release. Additionally, tags will be available as a read-only field when you add, view, edit or delete a document record using Redwood pages in a future release.

This feature allows you to classify and group related document types under the same tag for higher-level reporting as well as filtering on the Document Records landing page.

Steps to Enable

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

Tips And Considerations

• It’s recommended that you select a value for the Tags attribute when configuring a document type to further classify document records.
• The Tags attribute is also migrated when you migrate your document types configuration using the Functional Setup Manager (FSM) export/import functionality.
• The Tags attribute is available in HCM Data Loader (HDL) and HCM Spreadsheet Data Loader (HSDL).  
• You can update the value for the Tags attribute through HDL for existing document types.
• The Tags attribute will be available in the OTBI subject area in a future release.

Key Resources

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

• Document Records chapter in the Implementing Global Human Resources
• Document Records chapter in the Using Global Human Resources

Access Requirements

You must be granted the Manage HR Document Type privilege to manage document types.

Multiple Occurrences Check for Document Records at Assignment Level

When creating document records, the multiple occurrences check is done at the assignment level and not the person, thereby allowing users to create a document record per assignment when the Allow Multiple Occurrences flag is set to No and the Document Type Level is Assignment.

With this feature, you can now create one document record per assignment instead of one document record per person when Document Type Level is Assignment.

Steps to Enable

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

Key Resources

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

• Document Records chapter of the Implementing Global Human Resources
• Document Records chapter of the Using Global Human Resources

Access Requirements

You must be granted the Manage HR Document Type privilege to manage document types.

Employment

REST Support for Override Standard Working Hours in Worker Assignment

Use the Workers REST resource to update the AssignmentStandardWorkingHours and AssignmentStandardFrequency. When populated these attributes are used for FTE calculation instead of derived standard working hours. For example, if the standard working hours derived from any of the work structure objects is 40 weekly, and you specify the AssignmentStandardWorkingHours as 50 weekly, the assignment standard working hours will be taken into consideration for calculation of adjusted FTE.

This feature gives you the ability to change the standard working hours based on your requirement and control FTE calculation

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

• For the Great Britain (GB) legislation, if you enter a standard working hours override, this attribute is used to derive the standard working hours The standard working hours override frequency is considered to be the same as the assignment working hours frequency. If you enter both the Standard Working Hours Override and Assignment Standard Working Hours then the Standard Working Hours Override takes precedence.
• If you're in GB legislation and you're not using both attributes, then it's recommended you use the Assignment Standard Working Hours instead of the Standard Working Hours Override attribute.
• If the Calculate FTE and headcount automatically option is set to Yes and you change a triggering attribute, the FTE value is populated even if the calculated value is 0.

Key Resources

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

• Full Time Equivalent (FTE), Chapter Employment Information > Assignments, Work Measures, Using Global Human Resources guide
• Work Day Information, Chapter Employment > Assignments, Implementing Global Human Resources guide
• Work Hours and Duration, Chapter Jobs and Positions, Implementing Global Human Resources guide

You can also refer to the What's New for these features in Update 23C under Human Resources > Global Human Resources

• REST Support for Adjusted FTE in Employment

REST Support for Adjusted FTE in Worker Assignment

Use the Workers REST resource to update the AnnualWorkingDuration, StandardAnnualWorkingDuration, AnnualWorkingDurationUnit, AnnualWorkingRatio, and AdjustedFTE. These attributes are used to adjust the full time equivalent (FTE) value on an assignment.The AdjustedFTE is calculated by multiplying the FTE value with the ratio of annual working duration and standard annual working duration.

The annual working duration and standard annual working duration are editable attributes and this hierarchy is used to default these attribute values -  position > job > location > department > legal entity > enterprise, in that order, if a value is specified.

This feature enables you to manage an additional adjusted FTE value at assignment level, thereby giving you more flexibility to manage your statutory FTE requirements.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

• The value provided for the AnnualWorkingDurationUnits applies to both, AnnualWorkingDuration or the StandardAnnualWorkingDuration.

• If the AnnualWorkingDuration isn't available in the position, then it's copied from the StandardAnnualWorkingDuration in Create/POST flows.

• When the annual working duration attributes are null, either from the hierarchy or user has provided null values, then the AnnualWorkingRatio and AdjustedFTE will be 0.

• StandardAnnualWorkingDuration and AnnualWorkingDuration are defaulted when a new assignment is added as part of an employment transaction. For example, POST Assignment and POST Worker.

• In PATCH flows, the StandardAnnualWorkingDuration will be updated based on the change in values in the hierarchy. AnnualWorkingDuration will be derived from position and if not available in the position will be retained from the earlier record.

  • If there's a difference between the units of the derived standard annual working duration and annual working duration, an error message is displayed to provide the same unit for the annual working duration as the derived standard working hours.

  • The StandardAnnualWorkingDuration will be null if not available in the hierarchy as of the PATCH effective date.

• In Change Legal Employer or Local and Global Transfer flows, annual working duration and units are copied from the old assignment.

• If AnnualWorkingDuration, StandardAnnualWorkingDuration, AnnualWorkingRatio, and AdjustedFTE values are provided at the assignment level will override the derived value in POST and PATCH flows.

• In PATCH flows, only the StandardAnnualWorkingDuration will be updated based on the change in values in the hierarchy. AnnualWorkingDuration will retain the values from the earlier record.
• The AdjustedFTE accepts up to 10 decimals and the AnnualWorkingRatio accepts up to 5 decimals.
• The AnnualWorkingRatio and AdjustedFTE will be 0 when either the AnnualWorkingDuration or the StandardAnnualWorkingDuration is null. If AnnualWorkingRatio and AdjustedFTE isn't provided or is null, then these attributes will be automatically calculated in POST flows.

• Adjusted FTE is calculated when Calculate FTE and headcount automatically option is set to Yes and there's a change in any of these triggering attributes.
  • StandardAnnualWorkingDuration
  • AnnualWorkingDurationUnits
  • AnnualWorkingDuration
  • AnnualWorkingRatio
  • AssignmentStandardWorkingHours
  • FTE
  • Work structure attributes in the hierarchy

• The annual working ratio will be recalculated whenever there's a change in the standard annual working duration and annual working duration irrespective of the Calculate FTE and headcount automatically option setting.

• Only RangeStartDate is supported in Effective-Of headers for AnnualWorkingRatio or AdjustedFTE calculations. However, multiple date effective record or sequence changes in one REST call aren't supported. PATCH correction should be performed with 'Effective-Of' = 'RangeMode=CORRECTION'.

Key Resources

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

• Work Day Information, Chapter Employment > Assignments, Implementing Global Human Resources guide
• Adjusted FTE, Chapter Employment Information >  Assignments, Work Measures, Using Global Human Resources guide

You can also refer to the What's New for these features in Update 23B under Human Resources > Global Human Resources

• REST Support for Override Standard Working Hours in the Assignment

Journeys

Control Search on Assigned Journeys Tab

You can improve your search performance on the Assigned Journeys tab by enabling search using the person name only.

Assigned Journey Search Configured Only for Person Name

This feature improves the search performance for the Assigned Journeys page.

Steps to Enable

You need to configure the ORA_PER_JOURNEY_SEARCH_CRITERIA profile option to control the search criteria for the Assigned Journeys tab. By default, this profile option is set to Journey name or person name.

To change the default profile option value and enable search only based on the person name, 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_JOURNEY_SEARCH_CRITERIA profile option code and select the profile option in the search results.

4. In the ORA_PER_JOURNEY_SEARCH_CRITERIA: Profile Values area, select Person name only in the Profile Value field.

5. Click Save and Close.

6. Click Done.

Tips And Considerations

• If the ORA_PER_JOURNEY_SEARCH_CRITERIA profile value is set to Person name only, then the assigned journey search will be based on the person display name only. If set to Journey name or person name, the search will be based on both the person display name and journey name.

Key Resources

• For more information, refer to How You Use Journeys > Chapter Checklists and Journeys in the Using Global Human Resources guide.

Control the Send Reminder Action for Journey Tasks

You can now leverage the Display Settings to control the display of the Send Reminder action for a journey task. The default value for the action is Show. However, you can control the display of the action by selecting Hide on the task setup page when configuring checklist templates.

Send Reminder Action Set to Hide for Owner, Line Manager, and Other User

Send Reminder Button is Disabled When You Select a Task for Which the Send Reminder Setting is Set to Hide

When you select multiple tasks to send reminders, the Send Reminder button will display the count of tasks for which the Send Reminder display setting is set to Show. For example, the following screenshot shows the count on the Send Reminder button as 3 even though 4 tasks are selected. This is because the Send Reminder display setting is set to Hide for the Review Campus Map and Directions task and the same setting is set to Show for the other 3 tasks.

Send Reminder Button Displays Count Only for Tasks Having the Set Reminder Setting Set to Show

This feature prevents users from sending multiple reminders to task performers.

Steps to Enable

To control the display of the Send Reminder action, follow these steps:

1. On the application home page, click the My Client Groups tab.
2. Click Show More under QUICK ACTIONS.
3. Click Checklist Templates under the Employment category.
4. In the Checklist Templates page, click the journey name for whose task you want to change the display setting.
5. Click the Tasks tab and select the task for which you want to change the display setting.
6. Click the Display Settings tab.
7. For the Send Reminder setting, click the Edit icon.
8. Select Hide in the list for the Owner, Line Manager, and Other User columns.
9. Click Save and Close two times.
10. Click Done.

Key Resources

For more information, refer to Checklist and Journey Templates > Chapter Checklists and Journeys in the Implementing Global Human Resources guide.

Access Requirements

You must be granted the Manage HR Checklist Template function privilege to work on checklist templates.

Open External URL on Same Assigned Journey Page

You can now configure the option to open the hyperlink of an External URL task type on the same assigned journey page instead of a new browser window.

Configure Option to Open External URL on Same Assigned Journey Page

Page Before You Click to Open the External URL

External URL Opens on the Same Browser Window

You can access the external URL on the same assigned journey page instead of having to navigate to the new browser window.

Steps to Enable

Follow these steps to configure the option to open the external URL on the same page:

1. On the home page, click the My Client Groups tab.

2. Click Show More under QUICK ACTIONS.

3. Click the Checklist Templates quick action in the Employment area.

4. Click the Journey name for whose task you want to open the URL on the same page.

5. Click the Tasks tab.

6. Click the task name for which you want to open the URL on the same page.

7. On the Details tab, select the Open URL on the same page check box in the External URL area.

8. Click Save and Close two times.

9. Click Done.

Tips And Considerations

• By default, the Open URL on the same page check box isn't selected.

• The configuration option is available when you add an External URL task in the Task library.

• This feature is not supported for guided journeys. The external URL in a guided journey task will continue to open in a new browser window.

• The configuration option isn’t available when you create an External URL task type using Add Task in Journeys. The external URL in a journey task will continue to open in a new browser window.

Key Resources

For more information, refer How You Configure the URL for an External URL Task Type > Chapter Checklists and Journeys in the Implementing Global Human Resources guide.

Access Requirements

You must be granted the Manage HR Checklist Template function privilege to work on checklist templates.

Redwood Experience

These pages or flows have been recreated in the Redwood tool set Visual Builder Studio (VBS) to improve your user experience. The pages or flows look and act like Redwood pages or flows, to help create cohesiveness through the application.

Approvals Support for Transactions Initiated from Redwood Pages

You can now set up approvals for these Redwood pages:

• Employment Contracts
• Eligible Jobs
• Positions
• Share Data Access

You can either bypass approvals or configure rules for approval. In case of bypass approvals the transaction is submitted without any approval routing. When you configure rules, notifications are sent to the approvers that are set up in the approval rule, on submission of the transaction.

This feature provides the ability to route transactions for approvals.

Steps to Enable

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

Tips And Considerations

• If you have configured approval rules in the Transaction Console for these flows earlier, the same will be applicable for the Redwood pages as well.
• You may have to reconfigure any previously customized BIP notifications for positions to receive notifications for any changes done in the position Redwood pages.
• These features will be available in a future release.
  • Edit by approver
  • Simulation of approval rules
  • Save and resume
  • Addition of Request Info button
  • Alert Initiator

Key Resources

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

 Workflow Notifications and Approvals, Using Common Features for HCM guide

Redwood Experience for Pending Workers

Enrich the user experience with the new Pending Workers dashboard developed using the Redwood tool set. The dashboard is built from the ground up using Visual Builder Studio (VBS) to give you a unique experience of Oracle applications.

In this first release, not all features have been implemented. Review the Tips and Considerations section before enabling the page to ensure it meets your needs. The page will be turned off by default, but you can choose to enable it using a profile option.

You can search for a pending worker based on the name or person number. You can also sort the search results based on the name and planned start date.

Human Resource Specialists and Line Managers can also do the following using this dashboard:

• Add a pending worker: Click + Add to open the Add a Pending Worker page.

• Convert a pending worker: To convert a single pending worker, click the ellipsis for that row. The Convert Pending Worker page is displayed, where you can update the fields as required before converting the worker.

           You can also select one or more pending workers and click Quick Convert to convert them to employees.

• Include or exclude a pending worker for autoconversion: Select a pending worker and click More Actions. Click Include in Autoconversion or Exclude from Autoconversion as required.

• Edit a pending worker: Click a pending worker’s name to open the Edit Pending Worker page. On this page, you can select and edit different types of information for the worker.

• Perform all actions on a pending worker record: You can perform these actions on a pending worker by clicking the ellipsis at the end of the row and selecting an action from the menu:

  • Quick Convert: Submits an ESS process. While the application waits for the ESS process to complete, the request ID submitted is displayed. You can use the request ID to get more details from the ESS log.  

  • Include in Autoconversion, Exclude from Autoconversion: Each of these actions submits a REST POST call to change the data.  

  • Convert, Edit Pending Worker, Cancel Work Relationship, and Employment Start Dates: For now, these actions open the respective pages you know to manage the data accordingly.

The new page offers less number of clicks and better performance. By using these new pages or flows, you can take advantage of the cohesiveness through the application.

Steps to Enable

In order to work with the new Pending Workers page, you must first enable the ORA_HCM_VBCS_PWA_ENABLED profile option. In addition, check if the ORA_PER_PWK_DASHBOARD_REDWOOD_ENABLED profile option is also enabled.

By default, the ORA_PER_PWK_DASHBOARD_REDWOOD_ENABLED profile option is delivered as disabled. If you want to use the new Pending Workers page, you need to set the profile option to Yes.

1. Search for and click the Manage Administrator Profile Values task.
2. Search for and select the profile option: ORA_PER_PWK_DASHBOARD_REDWOOD_ENABLED.
3. Select the Level as Site.
4. Enter Yes in the Profile Value field.
5. Click Save and Close.

Tips And Considerations

The new page doesn’t yet have support for the following:

• Transaction Design Studio. If you modified your Pending Workers page using Transaction Design Studio in HCM Experience Design Studio, and you need to carry forward those changes to the new page, don’t enable the new page.

• Autocomplete Rules. Autocomplete Rules isn't supported for the new Pending Workers page rebuilt in Redwood. All rules built on the underlying business objects for this page must be disabled when you enable the Redwood page. Note that disabling rules on a business object will disable Autocomplete for both the Redwood and responsive pages.

• Filtering of Records. You can’t filter the records by Action and Action Reason using the new page.

• Edit Pending Worker. When you edit a pending worker from the new Redwood page, it takes you to the same page you have now for Edit Pending Worker.

• Add Pending Worker. When you add a pending worker from the new Redwood page, it takes you to the same page you have now for Add Pending Worker.

• Convert Pending Worker. When you convert a pending worker by clicking the ellipsis on the row from the new Redwood page, it takes you to the same page you have now for Convert Pending Worker.

• Cancel Work Relationship. When you cancel a work relationship by clicking the ellipsis on the row from the new Redwood page, it takes you to the same page you have now for Cancel Work Relationship.

• Employment Start Dates. When you change the start date of a pending worker by clicking the ellipsis on the row from the new Redwood page, it takes you to the same page you have now for Employment Start Dates.

Key Resources

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

• What's a pending worker?, How You Convert Pending Workers, Chapter: Hire and Manage Workers, Implementing Global Human Resources guide.  

For a listing of all profile options for the recreated pages across applications, see the following document in My Oracle Support:

• HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

Access Requirements

If you're an existing customer, then there are no changes to be made to your custom roles. New customers will have to assign the following data privileges to their custom roles to access and work with the new Pending Workers page.

Redwood Experience Enhancements to Share Data Access

The Share Data Access action has been enhanced in the Redwood Experience that was introduced in update 23B.

The page layout has been changed. A photo of the recipient is displayed, if available. And the recipient details are displayed in a section that can expand and collapse. The collapsed version is shown in the following example.

Share Data Access with recipient data collapsed, showing new expiration date field

A new field has been added to capture the expiration date. Access to the shared data will still remain after the expiration date. In other words, the access won't be revoked automatically. In this release, the field is available for reporting only. You can report on the expiration date and use it to manually revoke the access.

When the recipient details are expanded, you see additional details about the recipients and the notes about the shared data, as shown in the following example.

Share Data Access with recipient data expanded

The Edit action is now available. When you edit the recipient, you can change the expiration date and the notes. The notes will stay with the recipient data, even after approvals. Comments are used to provide information to the approvers, so the comments won't remain after the transaction is approved. The following example shows that the recipient data is edited with a later expiration date, and the revised notes explain that the transfer was deferred. The comments are added to indicate to the approver why the expiration date was changed.

Editing recipient data and submitting for approval

By using these new pages or flows, you can take advantage of the cohesiveness through the application.

Steps to Enable

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

Tips And Considerations

The page was available with update 23B. If you already enabled the page, you don't need to do anything else. If you haven't yet enabled the page, review the What's New for 23B, feature: Redwood Experience for Share Data Access

Key Resources

For information on Share Data Access, see these topics:

• How You Share Data Access With Another Person, Chapter: Person Information, Using Global Human Resources guide
• Include Shared People Information in a Person Security Profile, Chapter: Person Security Profiles, Securing HCM guide
• Approval Rules for Share Data Access and Share Personal Info, Chapter: Person Information, Using Global Human Resources guide

Summary of Changes Section on Redwood Workforce Structures Pages

You can see the summary of changes between the selected date-effective record and the prior date-effective record on these Redwood pages:

• Departments
• Job Families
• Jobs
• Locations
• Positions

The changes are grouped under After and Before enabling you to easily understand the changes.

Summary of Changes Shown on Redwood Pages

This feature enables you to easily identify the changed attributes across date-effective periods.

Steps to Enable

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

Tips And Considerations

This feature is applicable only for Redwood pages.

Key Resources

For a listing of all profile options for the pages recreated in Redwood across applications, see the following document on My Oracle Support:

• HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

History Hyperlink on Redwood Workforce Structures Pages

You can click the date links in the History section to view the date-effective data for the specific date or period. This feature is available on these Redwood pages:

• Departments
• Job Families
• Jobs
• Locations
• Positions

Date Links in the History Section That Open Date-Effective Data

Date-effective Data For the Selected Link in the History Section

This feature enables you to easily access date-effective historical data using the History section on the page.

Steps to Enable

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

Tips And Considerations

This feature is applicable only for Redwood pages.

Key Resources

For a listing of all profile options for the pages recreated in Redwood across applications, see the following document on My Oracle Support:

• HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

Enhanced Main Address Section on Redwood Locations Page

You can easily enter data in the Main Address section on the Redwood Locations page using the list of values for Country, City, and other address fields.

List of Values in the Main Address Section in the Location Page

This feature enables you to accurately enter and manage main address data in the Locations page.

Steps to Enable

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

Tips And Considerations

This feature is applicable only for Redwood pages.

Key Resources

For a listing of all profile options for the pages recreated in Redwood across applications, see the following document on My Oracle Support:

• HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

Control Defaulting of Effective Date on Redwood Workforce Structures Pages

Ensure that your users provide the correct effective date in the create and update flows when using Redwood pages for workforce structure objects like job families. This table describes how effective date is defaulted on the impacted Redwood pages:

Default Effective Date in Redwood Workforce Structures Pages

Default Effective Date on Manage Enterprise Information Page

You can configure the Default Effective Start Date on the Manage Enterprise Information page:

Default Effective Start Date Configured in Manage Enterprise Information Page

The specified date appears as the default date on the New Job Family page:

Default Effective Date on Create Page

You can choose not to configure the Default Effective Start Date on the Manage Enterprise Information page:

No Default Effective Start Date on the Manage Enterprise Information Page

The Effective Start Date appears blank on the New Job Family page:

Blank Effective Date on New Job Family Page

Some additional things to note:

• This feature doesn't apply to HCM Data Loader (HDL), HCM Spreadsheet Data Loader (HSDL), and REST.
• All workforce structures redwood pages delivered in the future will also follow the same approach for defaulting the effective date.
• The Default Effective Start Date field on the Enterprise is non date-effective. Any changes to this value will be reflected in all date-effective records.
• Even if the effective start date is defaulted from the value specified in the enterprise configuration, you can override this value in the create flows.
• You can specify a default effective start date in the future too.

Ensure that users provide the correct effective date when updating workforce structure objects using the redwood pages.

Steps to Enable

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

Tips And Considerations

This feature is applicable only for Redwood pages.

Key Resources

For a listing of all profile options for the pages recreated in Redwood across applications, see the following document on My Oracle Support:

• HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

Workforce Structures

Position Management: Route Position Approvals To The AOR Of The Parent Position Incumbent

You can now route position approvals to the representative of the incumbent of the parent position.

Applicable Processes

The approvals can now be routed to the representatives of the incumbents in the parent position for these processes:

• Request New Position
• Request Position Change
• Edit Position
• Delete Position
• Delete Date Effective Position Record

How Do Position Approvals Work

Earlier, you could route position approvals to the incumbents in the parent position and to the initiator’s hierarchy.

Now, you can also route position approvals to the representative of the incumbent of the parent position.

Suppose you want to route the Request New Position approval to the representative of the incumbent of the parent position. While configuring the approval rule for the Request New Position process, select the following:

• Representative in the Approvers list
• A value for Representative Type
• Identified Parent Position Incumbent's Representative in the Representative Of LOV

Now, when you create a new position using the Request a New Position UI by associating a parent position which has incumbents with representatives, the approval is routed to the Identified Parent Position Incumbent's Representative.

This feature enables you to route approvals to the appropriate people who should approve the position.

Steps to Enable

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

The identification of the parent position incumbent remains the same. It will continue to be based on the ORA_PER_POS_INCUMBENT_TENURE_ASG_SUP profile option.

Use the Workforce Structures Work Area to Access Its Redwood Pages

You can now use the Workforce Structures work area under My Client Groups on the Home page to access these Redwood pages:

• Positions
• Jobs
• Job Families
• Locations
• Departments

On the Workforce Structures page, you can click the respective quick links to open these Redwood pages, if you have enabled the profile options for the pages.

This feature improves the user experience by providing easy access to the Workforce Structures Redwood pages by using the quick actions in the Workforce Structures work area.

Steps to Enable

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

Tips And Considerations

This feature is applicable only for Redwood pages. 

Key Resources

For a listing of all profile options for the pages recreated in Redwood across applications, see the following document on My Oracle Support:

• HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

I-9 HireRight

Automatically Complete I-9 HireRight Journey Tasks

You can automate the completion of the I9 HireRight journey tasks by configuring the appropriate value in the Update Status in HR field. Select one of these values when you configure the I9 HireRight journey integration:

Configure Appropriate Value to Automatically Complete I9 HireRight Journey Task

You can save time by not having to manually mark the I9 HireRight journey tasks as complete and increase your compliance for task completion.

Steps to Enable

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

Tips And Considerations

• If you have selected a value to automatically mark the task as complete, then you can’t manually mark a task as done.

Key Resources

For more information, refer to Create Tasks for I-9 Process > Chapter Checklists and Journeys in the Implementing Global Human Resources guide.

Access Requirements

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

Additional Values in User Reference for Section 2 Field for I-9 HireRight Journey Integration

We have enhanced the User Reference for Section 2 attribute for the I9 HireRight journey integration by adding two new values in the LoV. You can now select the Person Identifier or Person Number value when you configure the attribute. Earlier, you only had the Primary Email value that was selected by default.

NOTE: If you plan to change the configuration for the User Reference for Section 2 field, you must let HireRight know of this change. This is to make sure that changes are in sync on the HireRight side as well.

New Values in the User Reference for Section 2 LoV

The additional attributes provide a more robust identification mechanism in organizations where the performer doesn’t have a primary email or if there are email changes.

Steps to Enable

You need to enable the ORA_PER_CHK_ENABLE_I9_USERREF_CHANGE profile option to display and use the Person Identifier and Person Number values in the User Reference for Section 2 field. By default, this profile option is set to N.

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_CHK_ENABLE_I9_USERREF_CHANGE profile option code and select the profile option in the search results.

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

5. Click Save and Close.

6. Click Done.

Tips And Considerations

• When you change the value from Primary Email to Person Identifier or Person Number, a warning message is displayed. The messages informs you that you need to make appropriate changes regarding user synchronization and other manual changes related to HireRight.

Key Resources

For more information, refer to these resources:

• Integrate with HireRight for I-9 Employment Eligibility Verification > Chapter Checklists and Journeys in the Implementing Global Human Resources guide.

• Create Tasks for I-9 Process > Chapter Checklists and Journeys in the Implementing Global Human Resources guide.

Access Requirements

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

Work Patterns and Scheduling

Shifts and Work Patterns for Workforce Scheduling

You can now create and manage shifts and work patterns, which will form the basis for building staff schedules in Oracle Fusion Cloud Human Capital Management (HCM).

A shift is a defined block of work used to create work patterns. It includes a name, work duration, and start time. It can include a total break duration. The work and break durations determine the total duration. For example, you create the Union Day shift with a start time of 8:00 a.m. The work duration is 8 hours, the total break duration is 60 minutes, and the calculated total duration is 9 hours. Work patterns that use this shift could include two 15-minute coffee breaks and one 30-minute meal break. To help people more quickly find appropriate shifts, shifts can include a category, such as Day, Evening, or Night.

To identify the shift framework for a worker at time of hire or employment or assignment changes, create a work pattern for their work assignment. The shifts can have specific start and end times or durations for specific days. If you want to derive time totals and absence information as part of your integrations with Oracle Fusion Cloud Time and Labor, Absence Management, and Global Payroll, these are the kinds of shifts and work patterns to use. Otherwise, you can use flexible shifts and patterns as appropriate. This framework is used to determine the worker's actual schedule.

Here’s an example for the same assignment and cycle, but with shifts that have flexible days and times.

• For week 1, Kris can work Monday, Wednesday, and Friday for 4 hours between 6:00 a.m. and noon and Tuesday, Thursday, and Saturday between noon and 8:00 p.m. All of the shifts include a 15-minute break that Kris can take any time during the shift.

• For week 2, Kris can work for 6 hours between 10:00 a.m. to 8:00 p.m. Tuesday, Wednesday, and Thursday. Kris can take a 15-minute coffee break between noon and 3:00 p.m. and a 30-minute meal break between 5:00 p.m. and 7:00 p.m.

Work Pattern Components

This feature lets you create and manage the shifts and work patterns that form the basis for staff schedules.

Steps to Enable

1. Create your shift categories using the Manage Common Lookups task in the Setup and Maintenance work area, and the ORA_HTS_ENT_SHIFTS_CATEGORY lookup type.
2. Create a library of shifts using the Shifts quick action under My Client Groups > Schedules.
3. Create work pattern types using the Work Pattern Type task in the Setup and Maintenance work area. Work pattern types identify the shift period type, such as duration, start and end times, or flexible days and times, to use in work patterns. They also identify the type and nature of any included breaks. For example, breaks can occur at a fixed time, any time during a specified range, or any time during the shift. And they can be paid or unpaid.
4. Create the work patterns using the Work Patterns quick action under Schedules. On the Work Patterns page, search for and select a specific work assignment to add a work pattern. You'll also be able to see the existing inactive and active work patterns here.

Tips And Considerations

A worker’s work assignment can have only one work pattern active at a time and work pattern dates can’t overlap. The work assignment can have gaps between when one work pattern ends and another pattern starts.

The fields that you see when adding shifts depend on the selected work pattern type. For example, start and end time types include time fields while duration types don’t. You can add existing shifts to the work pattern or create the appropriate shift while you’re creating the work pattern.

For flexible work patterns, the days or days and times are when the person needs to be available to work that assignment. You don’t have to schedule them to work on all the specified days and at all of the specified times. For example, Kris's manager schedules Kris to work the week 1 pattern on Mondays and Fridays from 9:00 a.m. to noon. They don’t schedule Kris to work at all on Wednesdays.

Time totals on time cards won't show any schedule deviation for flexible work patterns because there's no set schedule to identify deviations for. We can calculate schedule deviation for only fixed work patterns and published schedules.

Any reports that you create that include shift information will show the start times, end times, and work durations in only minutes because that's how the values are stored. Only the applicable Redwood pages include calculations to convert stored minutes over 59 into hours and minutes.

Access Requirements

People managing work patterns need the Manage Work Patterns Role Code (ORA_HTS_MANAGE_WORK_PATTERNS) role. This role is part of the delivered Line Manager  and Human Resource Specialist roles. You need to add it to any similar custom roles you created.

People managing shifts need these two privileges:

• Manage Shifts Privilege Code (HTS_MANAGE_SHIFTS)
• View Shifts Privilege Code (HTS_VIEW_SHIFTS)

Human Capital Management for Saudi Arabia

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

Autocomplete Rules for HCM Experience Design Studio Enhancements

Enhance your users' experience authoring new rules in Autocomplete Rules for HCM Experience Design Studio with this additional capability for Global HR: New Autocomplete delivered rule "SA Default Hijri Date Based on Date of Birth" for Saudi Arabia to populate the Hijri Date of Birth when the Date of Birth is entered when a person is added to the application. This rule uses an Oracle standard function that is based on the Umm al-Qura calendar.

This feature helps in ensuring accurate and consistent data by validating the user-entered values and allows your organizations to adjust quickly with HR compliance without relying on new release updates.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

To enable Autocomplete Rules in the HCM Experience Design Studio, you need to log a Service Request (SR). Please review and follow the instructions provided in the My Oracle Support document, Enabling Oracle HCM Cloud Autocomplete Rules (Document ID 2767655.1) to get access.

Key Resources

For additional information on Autocomplete Rules for HCM applications, refer these What's New features in Update 23C:

• Global Human Resources: Autocomplete Rules for Person Business Object

Access Requirements

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

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.

Converged Payroll Interface For ADP Global Payroll V2 Integrates With ADP Celergo

You can now use the converged Payroll Interface For ADP Global Payroll V2 to integrate with both ADP Global Payroll and ADP Celergo. Use this interface to extract information, such as the salary and earnings details of employees in the format required by ADP Global Payroll and ADP Celergo.

Configure fast formulas to return values for the Org Units required by ADP Celergo. Additional file name attributes have been delivered to address the dynamic output file naming requirements of both ADP Global Payroll and ADP Celergo.

Multinational companies using ADP Global Payroll for some countries and ADP Celergo for other countries can now use this converged interface for ease and efficiency.

Steps to Enable

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

Key Resources

For information on configuration and migration instructions refer to the following resource on the Oracle Help Center

• Implementing Global Payroll Interface

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

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

Changes have been delivered on underlying routes to extract the correct personal payment method name.

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

Perform regular data changes and extractions after the baseline extraction.

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

Steps to Enable

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

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.

Human Resources

Document of Records - New and Hidden Attributes

The new attributes related to document type are added to the following subject areas:

In addition to the above enhancements, the following attributes have been hidden from the subject areas

Enhance your reporting on documents of record subject areas with the addition of new attributes related to document type.

Steps to Enable

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

IMPORTANT Actions and Considerations for Human Resources

REPLACED OR REMOVED FEATURES

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

__________________________

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 in the Controlled Availability programs!