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 JUN 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 |
|
||
Support for Adding Sensor Attributes in Custom Dashboards for Vehicle Types |
||||||
Fleet Monitoring REST APIs Support for Non-Default Organizations |
||||||
Support for Externalizing Inventories Data
From this release onward, you can export inventories data along with Trips from your IoT application and store it externally in your own storage for long-term persistence and advanced analytics.
You can export Trip inventory data corresponding to ship orders, equipment, ship items, and ship units.
Steps to Enable
You don't need to do anything to enable this feature.
Support for Adding Sensor Attributes in Custom Dashboards for Vehicle Types
In earlier releases, while creating custom dashboards for Vehicle Types, you could only add metrics data.
From this release onward, you can add Sensor Attributes data as well. To do so, on the Create Dashboard Item dialog box, from the Type drop-down list, select Sensor Attributes, and then continue with the rest of the procedure.
Steps to Enable
You don't need to do anything to enable this feature.
Fleet Monitoring REST APIs Support for Non-Default Organizations
From this release onward, you can include an optional request header X-ORACLE-IOT-ORG in your REST APIs to specify the organization within which you want to perform a given operation. For example, you can retrieve the list of all drivers, trips, or vehicles for a non-default organization. You can also use the REST APIs to create, update, or delete entities such as trips, vehicles, and so on.
If you include this optional header in your request, then you must specify the organization identifier (OrgID) as the header value. If you do not include this header, then the request will be performed against the default organization, ORA_DEFAULT_ORG. The following is a sample value:
X-ORACLE-IOT-ORG: 7XPDB2RR2R60
You can find the OrgID for your current organization in the application address bar of your browser.
Steps to Enable
You don't need to do anything to enable this feature.