This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 25 MAR 2022 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
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.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Edit Comments in History of Candidates and Submissions
Recruiters can edit comments in the History tab for candidates and submissions.
There are two permissions that determine what level of editing a recruiter can do. They are:
- Edit comments in history summary without restriction
- Edit comments in history summary only if comments were entered by this user
While there aren't any steps to enable this feature, you can find and configure these permissions by following these steps:
- Go to Configuration and click Administration under the SmartOrg section.
- Click User Types under the Users section.
- Click the name of a User Type to select it.
- In the Functional Domains section, click on the arrow next to Recruiting, then click Edit next to Candidates.
- Go to the Edit comments in the history summary setting and select your preference.
- Click Save.
Enables you to specify permissions for recruiters that allow them to either edit only their own comments or all comments in the History tab.
Steps to Enable
You don't need to do anything to enable this feature.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 10 FEB 2022 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
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.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
More Information Provided to Candidates Using a Screen Reader |
||||||
Rich Text Format Available for Disability Self-Identification Form |
||||||
More Information Provided to Candidates Using a Screen Reader
More information is announced to candidates using a screen reader as they work their way through several areas within Career Section.
When a candidate uses a screen reader and:
- uses faceted search or filters while searching for jobs, the resulting number of jobs is announced.
- accesses the Profile menu, the menu items under the profile are announced.
- attempts to log in to Career Section and is unsuccessful, the specific error message is announced.
Increases the amount of audible information and guidance to candidates using screen readers.
Steps to Enable
You don't need to do anything to enable this feature.
Rich Text Format Available for Disability Self-Identification Form
A new Rich Text document format is available to select in the properties of the Disability Self-Identification Form.
The Rich Text format improves overall accessibility in all aspects of how a screen reader and, a browser user, interacts with the Disability Self-Identification Form.
The new Rich Text format is available for the following two forms:
- USA_DISABILITY_WITHEEID_EXP.31-05-2023
- USA_DISABILITY_WIHTOUTEEID_EXP.31-05-2023
While there aren't any steps required to enable this feature, follow the steps below to display the rich text layout of the Self-Identification Form:
IMPORTANT: The document must be inactive to enable editing.
- Go to Configuration and click on Administration under the Career Section section.
- Click on Documents under the Documents section.
- Click on either USA_DISABILITY_WITHEEID_EXP.31-05-2023 or the USA_DISABILITY_WIHTOUTEEID_EXP.31-05-2023 to select which you'd like to configure.
- Click Edit next to Properties.
- Select Rich Text as the Document Format and click Save.
Selecting Rich Text in the properties of the Disability Self-Identification Form improves accessibility for candidates.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
At upgrade, this feature is ready for you to implement.
We suggest you audit branding work that's been done to see if it's impacted by the Rich Text format.