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 |
|---|---|---|---|
| 22 MAR 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 |
|
||
Download All Attachments for Selected Document/Trace Using REST APIs |
||||||
Oracle Intelligent Track and Trace now supports Oracle Integration Cloud (OIC) Gen3 adapter to integrate with third-party applications, Oracle Cloud applications, and Oracle on-premise applications.
The OIC Gen 3 adapter enhances the automated integration and connectivity features between Oracle Intelligent Track and Trace instances and different data sources. It also ensures seamless promotions between the OITT Test instances and the OITT Production instances.
Steps to Enable
You don't need to do anything to enable this feature.
Download All Attachments for Selected Document/Trace Using REST APIs
This feature supports a new set of REST APIs that enables you to download all the attachments pinned with a transaction document or trace for specific business flows. Using APIs, you can export all document/trace attachments as a single archive for instant reference and tracking.
The API helps you perform the following actions:
- Trigger attachments export: To initiate export for a specific document based on the document Ledger key.
- Retrieve export details: Retrieves information about the triggered export.
- Download ZIP archive: The attachments will be downloaded in a .zip format.
- Delete attachment export: To delete an ongoing export operation.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Support for Cross-Origin Domain (CORS) Access in OITT
Cross-Origin Resource Sharing (CORS) support in Oracle Intelligent Track and Trace refers to the ability to process REST API requests coming from domains other than Oracle Intelligent Track and Trace origin domain.
The Allow Access From Domain security attribute provides flexibility to first configure multiple trusted domains in Oracle Intelligent Track and Trace application and then allows users from those domains to access Trace and Trace REST services to build customizations on top of existing Track and Trace application component pages.
The key benefits of CORS support include:
- Improved security: Your VBCS customer must be an OITT user, which means that users from trusted domains are allowed to access OITT REST services thereby preventing unauthorized access to maintain data protection.
- Increased accessibility: CORS support provides better flexibility to a wide range of users across domains to access Track and Trace REST services.
- Effective collaboration: Multiple users from different domains can work together to customize application components. This collaboration further improves the overall usability of the application to satisfy customer-centric objectives.
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 | Module | Feature | Notes |
|---|---|---|---|
| 30 JAN 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 |
|
||
Document Versioning in Track and Trace
The Document Versioning feature in Intelligent Track and Trace allows you to submit multiple versions of a document associated with any transaction in your supply chain network for efficient tracking and tracing.
Based on the timestamp of an incoming document, the application creates multiple versions and maintains a revision history of all the submitted documents for future reference.
Some of the key benefits of Document Versioning are:
- Efficient Tracking: Provides the most recent version of the document to ensure accurate and up-to-date information about the transaction data. This improves the efficiency and transparency of business flow in your supply chain network.
- Better visibility: A version history is maintained that provides increased visibility to track end-to-end information of a specific transaction submitted for a business flow.
- Improved customer experience: Provides access to the most recent transaction data available for all the stakeholders in your supply chain network for better decision-making and tracking.
- Access Control: Provides permission-based access to allow or restrict users from viewing document versions based on their organizational roles.
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 | Module | Feature | Notes |
|---|---|---|---|
| 16 DEC 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 |
|
||
Embed Custom Applications in Intelligent Track and Trace
The Custom View feature extends Intelligent Track and Trace UI to present customized views of Documents and Items. Applications built using Oracle Visual Builder or any other UI toolkit can be integrated by creating a Custom View definition, which registers the URL for the application being embedded into Intelligent Track and Trace.
Enabling Intelligent Track and Trace enriches the overall user experience as it provides permission based access to configure and view generic or context specific custom application UIs alongside Track and Trace UI pages but as one single application User Interface.
Steps to Enable
You don't need to do anything to enable this feature.