May 2020 Update

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

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.

Enterprise Data Management Cloud

Collaborate with Users on Requests in Submit Stage

To facilitate multiple users participating on a request, the request assignee can ask additional users to collaborate on Draft and Pushed Back requests in the Submit stage. Collaborators can be added or removed from a request. Collaborators are notified of requests in which they were asked to collaborate.

Concurrent Editing of Requests

When multiple users are collaborating on the same request, those users may be working on the request at the same time. Concurrent editing allows users to work simultaneously on the request while ensuring data integrity and alerting users of changes made by others.

Configure Binding Keys for Import and Export

Binding keys are configurable to allow for customization of how data is imported into and exported from bound viewpoints. Binding keys are displayed and edited in the Binding Inspector.

Custom Branding, Appearance Options, and New Default Theme

Appearance options are available to customize the look and feel of the Enterprise Data Management Cloud user interface. Service administrators can upload their own logo image and background image as well as choose a theme. These custom settings are applied to the user interface for all users.

Data Type Parameter Overrides for Name and Description Properties

Data type parameters for the core Name and Description properties can be edited at the application or node type level to override the original values set during application registration. This is helpful to customers who need to ensure that these data values conform to their business rules.

Default and Alternate Assignees for Subscriptions

Subscriptions can be configured with default and alternate assignees to allow subscription requests for target viewpoints to be assigned to multiple users. The default assignee is a single user who has subscription requests normally assigned to them. Alternate assignees are users or groups who can be assigned requests when there is no default assignee for a subscription, or the user is out of office.

Inspect Property Definition from Property Pane

A property can be inspected directly from the property pane for a selected node in a viewpoint. A link is available in the Property Details popup window to inspect the property. This allows the property inspector to be easily accessed in order to verify and make changes to property parameters.

Process Deletes and Reordering Options for Merge Import

Additional options are available for the Merge import mode, giving the user the ability to process deletes and reordering of nodes which may happen in an import source. These actions do not happen during a normal merge import process but are sometimes necessary for Enterprise Data Management to match the import source.

Remove and Delete Trigger Actions for Custom Validations

Custom validations can be configured with Remove and Delete as trigger actions to enable the validations to run for request items which include those actions. This allows specific custom validations to run only for nodes which are removed or deleted from a viewpoint in a request. This is helpful when you want to prevent nodes from being removed or deleted, or to prevent invalid data resulting from a removed or deleted node.

Request Item Validations for Derived Properties

Derived property values are now validated for request items in a request to prevent invalid values resulting from changes made in a request. System, application-specific, and custom validations are run for derived properties of nodes in viewpoints where request actions were performed. Derived properties can be validated for any type of request including interactive, subscription, and import requests.

Resizable Property Pane

The property pane for a selected node in a viewpoint can be resized using a drag and drop splitter located between the grid/tree and property pane for the viewpoint. This enables properties with long labels or values to be more easily viewed in the property pane.

User Mentions in Request Comments

Users can be mentioned in request and request item level comments providing a way for collaborators to ask questions or make other users aware of what they did to a request. When @ is entered into a comment, a list of request users is available to select from. After the comment is saved, mentioned users are notified of the comment so they can review it and take immediate action on the request.

User Preferences for Profile Image, Language, and Out of Office

Users can configure their own preferences for profile image, language, and out of office. The Profile Image is displayed for the user on pages where an avatar is used. The Language preference controls the language for labels and messages displayed in the user interface for the user. The Out of Office preference signifies the user is unavailable and requests should not be assigned to them. User preferences are accessible for a logged in user from the Settings and Action menu.

Validations Disabled for Predefined Members in EPM Cloud Dimensions

For Planning or Financial Consolidation and Close viewpoints, many application-specific validations have been disabled for nodes imported as predefined members (Enterprise Predefined Member = True).

REST API to Manage Permission for Manual Access to Database

You can now use a REST API to manage permission for manual access to database by Oracle. This gives you the ability to allow or disallow Oracle personnel to manually access your database in emergency situations when an environment is unresponsive and you have not yet created a service request to investigate the issue.

New Topics in EPM Cloud Operations Guide

The EPM Cloud Operations Guide has been enhanced with these additional topics:

• Best practices for designing business rules
• How to avoid the functional errors in business Rules.
• Managing Content Upgrade Issues
• Handling Issues with Cross-Environment Connections
• Troubleshooting ERP Integration Functional issues
• Requesting Merge Back of Environments
• Requesting Oracle to Apply Monthly Update to Production Environments Prior to the Third Friday

New Role Assignment Report Format

The Role Assignment Report has been modified to include ional information such as the user login, first name, last name, email address, pre-defined and application roles of EPM Cloud users, and how these roles are granted. Previously, the Role Assignment Report listed user logins, roles, and how the roles were granted only.

EPM Automate Updates

A new version of EPM Automate with these changes is available:

• The roleAssignmentReport command now generates a report that lists the first name, last name, email address and pre-defined and application roles of EPM Cloud users. Previously, the Role Assignment Report listed user names and roles only.

• The replay command now accepts an optional parameter to encrypt all passwords included in the replay file.The replay command works only with Planning, Financial Consolidation and Close, and Tax Reporting business processes.

Pre-defined Role Names as EPM Keywords

Starting with this update, Oracle will treat certain pre-defined role names as EPM Cloud key words, which cannot be used in the name of any artifacts that you create; for example, as a group name in Access Control.

Address for Outgoing Emails

Starting with this update, emails originating from EPM Cloud applications will use no.reply@oraclecloud.com instead of oraclecloudadmin_ww@oracle.com as the from address. Emails from other Oracle Cloud sources, for example, New Account email sent from the Identity Domain, will continue to use the current From email addresses, for example, oraclecloudadmin_ww@oracle.com.