Update 24C
Revision History
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 |
|---|---|---|---|
| 07 JUN 2024 | Created initial document. |
Overview
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.
Feature Summary
Column Definitions:
Features Delivered Enabled
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. | Action is Needed 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 | |||
Risk Common | ||||||
Transactional Business Intelligence for Risk Management | ||||||
Enhanced Question Responses | ||||||
New Advanced Controls Job History Dimensions | ||||||
Common Risk Management | ||||||
Job Type Is Displayed on Job Listing | ||||||
Ability to Edit Non-Fusion Data Source Credentials | ||||||
Ability to Disable Non-Fusion Data Sources | ||||||
Risk Common
Transactional Business Intelligence for Risk Management
Enhanced Question Responses
In the Risk Management Cloud - Assessment Results Real Time subject area, Survey> Question Response now supportslarge-scale text-based responses.
Business Benefit
To get valuable insights from survey responses, it's crucial to support longer text-based answers. This allows users to give more detailed feedback, leading to a better understanding. Ensuring these long responses are displayed accurately in reports and analysis tools helps capture the full context of what users are saying. This comprehensive view can improve the quality of your analysis and decision-making.
Steps to Enable
You don't need to do anything to enable this feature.
New Advanced Controls Job History Dimensions
To meet the demand for tracking history of advanced controls, we've enhanced OTBI (Oracle Transactional Business Intelligence). Now, users can seamlessly report on job history on their access and transaction controls. This enhancement updates two subject areas, with each having a new dimension:
- Risk Management Cloud - Advanced Financial Controls Real Time > Access Job History
- Risk Management Cloud - Advanced Access Controls Real Time > Transaction Job History
The new job history dimensions can give you an overview of information like incident status across all your controls, the frequency at which controls are run, and duration.
New Access Job History Dimension
New Transaction Job History Dimension
For access controls, you can also report on users analyzed and the number of roles assigned across users.
Example of Access Job History Report
Job history for transaction controls can include business objects associated to each control and the number of records synchronized from the data source.
Example of Transaction Job History Report
Business Benefit
The new job history dimensions give you valuable insights into how frequently controls are executed, the current status of all incidents, and the trends in control incidents over time.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
As is currently required for reporting on current Advanced Controls data, you need to run the Report Synchronization job.
Key Resources
- For more information on creating analyses, see the Analytics chapter in Oracle Fusion Cloud Risk Management: Creating Analytics for Risk Management.
Common Risk Management
Job Type Is Displayed on Job Listing
The Risk Management job listing now displays what the job type is. This information is displayed for all job types and is a searchable value in the job filters panel.
Job Type Display
Business Benefit
Displaying the job type information in the job listing UI will help users find the right job without having to open the job details as previously required.
Steps to Enable
You don't need to do anything to enable this feature.
Ability to Edit Non-Fusion Data Source Credentials
The data source credentials for non-Fusion data sources can be updated. All of the requirements and validations required during initial setup are applicable and required. Editing credentials will open the Enter Authentication Details page in edit mode and can involve anything from API credentials to authorization information.
Edit Non-Fusion Data Source Credentials
Business Benefit
Users can either update or change the credentials of the non-Fusion data source. This might be because credentials have changed for the data source, the configured data source was the wrong one, or another data source is desired.
Steps to Enable
You don't need to do anything to enable this feature.
Ability to Disable Non-Fusion Data Sources
If a non-Fusion data source has been set up, it can be inactivated. The inactivation process performs a validation to ensure there are no related records (entitlements, models, controls) related to the data source. If the validation fails, the job details provide information on what needs to be addressed for the data source to be inactivated. If the validation passes, the data source is made inactive and the related model library is once again hidden.
The data source can be reactivated at any point in the future.
Inactivating a Non-Fusion Data Source
Business Benefit
The ability to disable non-Fusion data sources will help customers remove processes and content noise from their environment when analysis of the data source is no longer desired.
Steps to Enable
You don't need to do anything to enable this feature.
