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 |
|---|---|---|---|
| 28 JUL 2023 | 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 |
|
||
Manage Related Knowledge Via APIs
If you are migrating knowledge or syncing knowledge into Knowledge Advanced you may also want to be able to update manually related links via APIs calls, now you can. Once both articles you want to relate exist you can use POST /content/docId/:docId/documentLinks/manual to create the related link between them. Additionally, it is possible to remove related links using DELETE /content/docId/:docId/documentLinks/manual/:linkId.
Related links give your users a well defined location to look to for other potentially useful information. For example, they might be looking at an article on updating a subscription and you want them to be able to easily get to an article about their account's privacy settings, creating a related link between those articles is a good solution. Having APIs for maintaining these related links makes it easier for you to create or remove large numbers of related links.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Remember that if your UIs are presenting both manual and learned links in their list of related links that manual links (which is what these APIs will be creating) will come above learned links in the list.
Access Requirements
All API calls must include a valid integration user token and account token. The account user must have sufficient privileges to edit the articles being linked in order to create related links between them. In other words, if the user can create manual links in the authoring ui, that same user will be able to via the API.
Filter Subscriptions by Interface
If you have users that work across multiple interfaces, such as in multiple customer portals, it is possible that they are creating subscriptions to articles that are unique to those different interfaces. Those users will now enjoy a list of subscriptions that are specific to the interface they are working in. Additionally, if you have a custom UI utilizing the subscriptions API you will experience the same filtering there.
Users will have smaller, easier to use lists of subscriptions in which all of the links go to articles that can be viewed in the active interface.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
If you are using the subscriptions API make sure to use the correct interfaceId in your kmauthtoken.