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 |
|---|---|---|---|
| 25 JAN 2023 | Created initial document. |
The table includes a chronological listing of document changes.
Overview
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.
Feature Summary
Column Definitions:
Features Delivered Enabled
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. |
Action is Needed 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 |
|
||
Define a Primary Contact as a Recipient for Notifications to Employees |
||||||
Oracle Me Employee Experience
HR Help Desk
Define a Primary Contact as a Recipient for Notifications to Employees
In the case of an HR Help Desk request or an internal service request, the primary point of contact on a service request is an employee. This feature lets users define the primary point of contact as a recipient of a notification (defined using Notification Preferences Manager) when a change has been made to the associated help desk request.
As an employee, after I've submitted a request for assistance, I'll receive notifications about important updates on my issue.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
When defining notifications through Notification Preferences Manager, the ability to define the primary contact as the recipient for a notification is only available when you select the object of HR Help Desk Request or Internal Service Request. Notifications of this type don't support the ability to enable users to "follow" a service request.
Access Requirements
In order to define a primary point of contact as a recipient for a notification, you must have the correct privileges to access the Notification Preferences Manager under the Tools menu.