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 |
|---|---|---|---|
| 06 JAN 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 |
|
||
Add Links to Third Party Applications from Service Request Messages |
||||||
Drive Service Request Milestones Using Additional Covered Levels |
||||||
Define Screen Pop Configuration by Copying Rules, Pages, and Filters |
||||||
Define Data Security Policies for Work Orders Based on Access Groups |
||||||
Personalize Notification Preferences for Custom Objects
You can personalize your notifications for custom objects. For notifications that are sent by Notification Preferences Manager, you can select your preferred delivery channel and disable notifications that you don’t want to receive.
Users can now personalize notifications that are triggered against custom objects. This feature lets users define which channels they want to receive their notifications on, and disable the notifications that they determine to be of no use to them.
Steps to Enable
For a user to personalize notifications that are triggered against a custom object, the custom object must be already defined within Application Composer. In addition, notifications must already be defined against this custom object using Notification Preference Manager. These steps are typically performed by an Administrator or Business Manager.
Key Resources
- See the "Configure Notifications" chapter in the Implementing B2B Service guide.
Role Information
Standard users can use notification personalization. Administrators and Business Managers can set up and configure this feature.
Add Links to Third Party Applications from Service Request Messages
You can provide dynamic links to third party applications within the service request message content. The user can drill down directly from dynamic links in a service request message into specific records in non-Fusion applications.
By adding dynamic links to third party applications into service request messages, you can drill in to related records directly from service request messages.
Steps to Enable
In the Setup and Maintenance work area, go to the following:
- Offering: Service
- Functional Area: Productivity tools
- Task: Manage Manage Dynamic Links
Configure the third party link.
Key Resources
- See the "Service Requests" chapter in the Using B2B Service guide.
Role Information
Administrator setup is required.
Drive Service Request Milestones Using Additional Covered Levels
Use new subscription covered levels for party, location, product group, and asset group to drive milestone creation and due dates. Companies that require more flexible terms for contract coverage can now match the account or contact of a service request, and the location or asset group of the installed base asset, to newly supported covered levels on subscription contracts. In addition, the product group hierarchy can also be supported so that if the product of the asset, or the product or product group on the service request, rolls up to a covered product group on a subscription contract, those coverages will also apply.
Companies that require more flexible terms for contract coverage have numerous additional options to drive entitlements.
Steps to Enable
- Promote algorithm.
- Redo configuration changes pertaining to custom milestones.
- Set EnableManualPricedCoveredLevel if customers need hierarchy match for product groups.
Tips And Considerations
Before promoting algorithm, take note of the changes made for custom milestones as you will need to re-apply to the new algorithm.
Key Resources
- See the "Service Entitlements" chapter in the Implementing B2B Service guide.
Role Information
- Service Administrator
Define Screen Pop Configuration by Copying Rules, Pages, and Filters
Define screen pop configuration by copying the ready-to-use rules, pages, and lookup filters that are provided on the Manage Screen Pop Configuration page, and then edit them to suit your business needs. You can't directly edit the ready-to-use rules, pages, and filters that are supplied in the Manage Screen Pop Configuration page.
The ready-to-use screen pop configuration rules are made read-only, so that you can revert to the default values whenever needed. You can copy the default values and customize them according to your requirement, without impacting the default (baseline) values.
Steps to Enable
- As an Administrator, navigate to the Manage Screen Pop Configuration page in the Setup and Maintenance work area.
- Use the read only configuration rules as a template to define your own configuration rules.
- Select the configuration rule that you would like to use as a baseline, and use the new copy feature to create a new rule which you can then modify to meet your business needs.
Tips And Considerations
If you modified any ready-to-use rules, pages, and lookup filters under the Manage Screen Pop Configuration page previously, they will also appear as read-only. If you need to modify these settings, you can duplicate the existing configuration and set it to Active. You will also need to set the existing configuration to Inactive.
Key Resources
- See the "Computer Telephony Integration (CTI)" chapter in the Implementing B2B Service guide.
Role Information
- Administrator
Define Data Security Policies for Work Orders Based on Access Groups
You can define access-group-based data security policies on work orders. You can also define additional data security policies based on access groups. The predefined data security policies will continue to be available.
Access groups are an alternative way of granting data permissions to users as compared to the SQL-based data security policies. Instead of creating security policies using SQL, you can use object-sharing rules in Sales and Service Access Management UI to define your visibility criteria.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Customers wanting to create new data security policies can follow the access group documentation setup data security policies. If you are replacing existing SQL based data security policies with access groups then remember to end date your SQL based data security policies.
Key Resources
- See the "Users and Security" chapter in the Implementing B2B Service guide.
Role Information
Customer Relationship Management Application Administrator or Sales Administrator