The most recent release of new features for Oracle Enterprise Data Management contain some great capabilities. Continue reading below to find out more!

 

Viewpoint Querying

The ability to search for nodes within Oracle EDM has been greatly enhanced with the recent addition of Viewpoint Queries. Now, users can easily find nodes within a viewpoint where properties match specified criteria. Below are some important considerations for those users looking to use this feature.

All of the nodes in any viewpoint or only those below a selected node in a hierarchy viewpoint can be queried.

Filters can be added to narrow the scope and limit the number of query results returned for each query.

Queries are limited to the following properties:

Properties with defined values which use a Default Type = None
All property data types except for the Node data type
Certain properties in the Core and CoreStats namespaces which have stored values (e.g., WHO columns, name, description, alternate name)
Derived and Inherited properties are not available for selection  (bummer! hopefully this is enhanced in later releases)

 

User-Friendly History for Data Integrations

Logging the execution of data integrations is a long-standing best practice for any data management solution. Oracle has taken EDM’s ability to the next level by displaying the historical executions of imports, exports, and extracts directly to the end user.

 

Uniqueness Constraint Expanded to Node Types

Oracle EDM now provides the ability to ensure property values are unique across Nodes Types (previously uniqueness constraints were available for only application and dimensions). This feature can be used to prevent duplication across descriptions, aliases, or any other defined property.

A few things to note:

Planning, Planning Modules, and Financial Consolidation and Close applications already have application-specific validations that check for node name uniqueness across node types at the application level. Customers do not need to create a constraint to enforce this data rule for those application types.
Oracle Financials Cloud General Ledger applications already have application-specific validations that check for node name uniqueness across node types at the dimension level. Customers can add a constraint at the application level if desired to apply the node name uniqueness rule across segment value sets.
Properties referenced by constraints must be a node level property, must be string data type, cannot have a derived default value nor be an inherited value.

 

Subscription Requests Item Limit Increased

Until now, the item limit within a request, regardless of request type (interactive or subscription-generated) was been 10,000. However, the limit for requests generated from subscriptions is now 12,000. This will help to ensure the synchronization of descendant nodes between source & target viewpoints when parent nodes are moved/inserted.


Enhanced Controls on Email Notifications

There’s few things more annoying than being flooded with emails/notifications which you care little about. This is especially true in our professional lives. EDM now provides several new system settings to help organizations better manage emails originating from requests in the application.

Enabled/disabled emails entirely.
Auto-add a prefix to email subjects to identify the environment from which a notification has been sent.
Identify a substitute recipient who should receive all notifications instead of the primary recipient(s). (Really useful for testing workflows within a development environment and helps to avoid confusion for end users).