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 |
|---|---|---|---|
| 11 APR 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 |
|
||
Whenever a Content Review task is closed, whether through the Authoring Console or through the API, an entry will be added to that article's history showing that the article has been reviewed.
Viewing an article's history will now allow you to see when and by whom an article was reviewed, giving you a view into this aspect of an article's lifecycle. Previously there was no traceability around review activities on articles.
Steps to Enable
You don't need to do anything to enable this feature.
Access Requirements
No new roles or privilege updates are required.
Tables have been exposed within reporting that will allow you to join your articles to the knowledge views you have assigned to them. This makes it possible to create reports that display the knowledge view(s) you have assigned to each article version.
Sample Report
You can now build reports that show the distribution of your articles across your views and see the change of views assigned to articles at a glance in a report.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
How to Join
Start from okcs_content_version and then join okcs_content_version_views to okcs_views to okcs_view_names in order to make the names of the views available to your report.
Understand the Data
- Because an article can be connected to many views, make sure you are using a group_concat to turn it into a single string.
- Note that the repository itself will be included which probably is not of value to you, so you may want to use a fixed filter that excludes it.
- Whenever working with data that can change from version to version, make sure that you are filtering your reporting data to the specific article versions you are interested in.