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 |
|---|---|---|---|
| 08 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 |
|
||
Report on Article Link Anchors
Now that some of your article links are pointing to anchors you may want to expand your article link reporting to cover those anchors as well. The Knowledge Management - Article References Real Time subject area now includes both the specific values of the anchors selected as well as a new fact rolling up just how many anchors you have linked to.
This means that not only can you build a report listing out every article link (including anchor names) in every article, but you can also determine what percentage of your articles include article links point to anchors or which users are most likely to take advantage of this feature or the content types in which the feature is used most, just as a few examples.
Steps to Enable
You don't need to do anything to enable this feature.
Analyze Knowledge Workflow Activities
Analytics will now allow reporting on knowledge article workflows. Utilizing the supplied Article Workflow Dashboard you can quickly identify the articles that are stuck, the steps that take too long, and the users that are approving too slowly. This dashboard is built on top of a new subject area, Knowledge Management - Article Workflows Historical, that you can also use to build analyses specific to your business processes.
Approval processes on knowledge articles is an area where you can always find opportunities for improvements, whether that is process- or people-related. This feature introduces the tools for you to analyze how you use workflow and drive those improvements.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
As with all reporting, understanding how the application is used as well as how that is reflected in the data is critical to being successful in using analytics. Here are a few notes that may prove helpful as you get started with this data:
- Keep in mind that the same workflow can be used across many content types and that the way your users see the workflow is as either step names requiring approval (they never see workflow names), therefore the combination of content type and step name will often be necessary to accurately understand the data.
- Workflow on a single article review may take a few attempts, where the article goes into workflow, is rejected out, goes back in, gets rejected out, etc. before it is finally published.
- Workflow steps can change name, order, and quantity over time - of your analysis spans such changes make sure to take those changes into consideration as you look at the data.
- Workflow steps do not have to be assigned to be completed, so make sure to allow nulls on assignee and be careful about filtering out unassigned tasks as it may cause you to miss work that needs to be completed