This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 17 SEP 2021 | 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 |
|
||
Track Article Updates using Major and Minor Versioning
The article version numbering system uses major and minor increments to track editing and publishing. When authors edit an article, each edit is recorded as a minor increment in the article's version number. Publishing an article is recorded as a major increment. Knowledge managers can easily distinguish between minor and major updates to articles, version numbering is more intuitive and manageable, and authors can edit articles as frequently as needed, without increasing the major version number.
Knowledge authoring teams are often concerned that high version numbers will reflect negatively on them. Minor versioning enables authoring teams to track every saved version, but only increment the version that end users see when articles are re-published. An article that was edited ten times, but published only once will appear to end users as version 1.0, which is a more accurate indicator of the article's history. Minor versioning also supports future workflow features.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Minor versions increment by 0.1 when you edit and save an article. When you first publish an article, the major version will be set to 1, and the minor version will reset to 0, so that the first published version of an article will be 1.0.
Key Resources
- See the "Use Knowledge Authoring" chapter in the Using Knowledge Management guide.
Role Information
- Authors and knowledge managers will automatically use minor versions when they create, edit, and publish articles.
Report on Article Version Detail in Knowledge Analytics
Knowledge authoring uses minor and major revision numbers to indicate that articles have been updated. You can report on minor, major, and combined article versions in knowledge analytics, making it easier to understand when articles have been incrementally and significantly updated.
Article version dimensions include Article Major Version, Article Minor Version, and Version, which combines the major and minor article versions into a single value. These dimensions are available in all subject areas that report article version information.
Reporting on article versions provides information about the number of updates that authors are making to articles, and their frequency. Knowledge managers can use this insight to better understand how knowledge articles change over time.
Steps to Enable
Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).
Key Resources
- See the "Analyze Knowledge" chapter in the Administering Knowledge Management guide and the "Subject Areas" chapter in the Subject Areas for Transactional Business Intelligence in CX Sales and B2B Service guide.
Role Information
- Users with the Knowledge Analytics Duty Role can use Knowledge Analytics.