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 |
|---|---|---|---|
| 05 SEP 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 |
|
||
View/Download Documents Using Public REST API
As a Founder or a Trading Partner, you can now access transaction documents of a business flow/step by using an external REST API. The API provides various endpoints that enable you to search, view, and/or download document resources from Oracle Intelligent Track and Trace server and integrate those with your application in your supply chain network.
All the API calls to the Track and Trace server are controlled based on the user roles and the associated access permission assigned to that role.
The API exposes the following REST endpoints:
- Get metadata document for the latest document version
- Get metadata document for the specific document version
- Get source document for the latest document version
- Get source document for the specific document version
- Search all documents
- Search document references for the latest document version
- Search document references for the specific document version
Some of the key benefits of this feature are:
- Index-based search: A seamless index-based search to filter and retrieve documents referenced by the latest version of the document or referenced by the specific version of the document. The query parameters in the API endpoint are mapped to the OpenSearch API framework to access relevant information.
- Retrieve additional document artifacts: The API provides specific endpoints to retrieve the metadata and source documents for the latest document version or for any specific document versions associated with a business flow/step.
- Role-based access: Based on your user role, you must have the necessary privileges to execute the required API calls.
Steps to Enable
You don't need to do anything to enable this feature.