Is it Christmas in April? The Enterprise Data Management (EDM) update for 21.04 brought a ton of new features and functionality (and bug fixes…) that I am excited to bring to implementations. 27 features, to be exact!

The EDM patch notes below will provide my quick thoughts on each feature and why it will bring value to my customers (or myself during development!). The EDM updates in Oracle-speak and other EPM Cloud updates can be found here.

1.     Access Current Date/Time and Calculate Date Offset in Expressions

HB POV: This is helpful for my clients that need time-based properties and attribution. Oftentimes, operational and management reporting have hierarchy needs at different times; this allows us to generate exports or attributes based on a timestamp or date instead of only the live values.

2.     Appearance Option to Display Business Process Name

HB POV: While we love seeing “Enterprise Data Management” in the top left corner, this can be disabled from view if the client would like to include it in their logo instead.

3.     Arithmetic Methods for Integer and Float Data Types in Expressions

HB POV: For some attribution, we need to be able to calculate data elements or attributes based off of other integers or settings the data steward inputs about a member. The introduction of these calculation methods give us more flexibility in deriving these calculations. We can now Add, Subtract, Multiple, Divide and Modulo (remainder of a division).

4.     Create Unbound Dimensions for Custom Data Sets

HB POV: This feature gives us the power to derive code combinations for Oracle cloud ERP customers, ARCS profiles, and other related data that needs to be generated or maintained within EDM. Coupled with the recently released (20.12) Extracts functionality; we can automate the feeds of this data to Oracle cloud or other target systems. Excited to try this out!

5.     Custom Validations Report

HB POV: While this feature is a great way for us to keep track of status during development; it is an important value for administrators when they need to research or tweak validations on Node Types and Hierarchy Sets. The report has the Validation name, the data chain object where it is enabled, application and dimension, trigger actions, trigger properties, and the failure message. The report also shows if it is enabled or disabled.

6.     Derived Values and Property Transformations for List Data Type Properties

HB POV: This feature helps us help data stewards and administrators with maintenance. As developers, we are now able to derive list-properties with expression logic; if a property should be set because it is a base-level (think UDAs) we can pre-populate for eased user experience.

7.     Disable Existing Subscriptions for Viewpoint

HB POV: This is a great usability feature for troubleshooting. Prior to this, when testing or making mass updates to a source of a subscription, the subscription (and its filters or expression logic) had to be deleted. Now a subscription can be easily disabled for maintenance and then re-activated.

8.     Download Subscriptions Report to File

HB POV: The list of subscriptions is a very important detail when understanding what source and target viewpoints are aligned in the application. This information is useful for administrators, developers, and business users that need to understand the innerworkings of data moving in the system.

9.     Enrich Request Items During Approval ***

HB POV: This is one of our highest value-add feature of 21.04 – approvers can enrich on approval (if given permission). This allows for fewer collaborators or assignees during the workflow process, and the final approver can make any edits; even if it is in approval stage. This will be a process improvement and time savings for many customers that have administrators as final approvers for metadata updates.

This is my HyperionBarbie “Favorite Feature” of this release drop!!!

10.  Filter Archived Dimension and Viewpoints

HB POV: This is another usability update that can streamline functional user interface – only items that are active are displayed; but inactive items are optionally reviewed.

11.  Global Connections to Oracle Enterprise Resource Planning (ERP) Cloud and Oracle Enterprise Performance Management (EPM) Cloud

HB POV: This is the expansion of the native “Connections” on adapters to be more global in nature. The target locations in cloud ERP and EPM are the same (UCM location, inbox/outbox), but can also extract additional files to these locations that are not natively a part of the adapter export. This allow for Extracts (think multi-dimensional Data Management mappings, or code combinations for GL) to be sent to those connections, as well.  

12.  Inspect Request Items and Delete Individual Request Actions

HB POV: This is helpful when you have multiple users collaborating together on a request. We hope that collaboration and assignment on requests becomes a part of our customer’s master data culture; and this feature allows for increased visibility on “who made what change” even before the changes are live in the system (request is in draft mode).

13.  Match Nodes Across Viewpoints using Alternate Name

HB POV: I’m hoping this is the solution to our pain of the “FCCS_” account parents in the FCCS hierarchies! You’d assign an “alternate name” to the FCCS_ members and then be able to align them to other applications across viewpoints (like your EPBCS structure that does not have FCCS_ members!).  

14.  Original Request and Subscription Links in Request Inspector

HB POV: This is another huge usability enhancement for end-users that are assigned subscriptions. Having the details to the original request can add a lot of value when making decisions on attribution or placement in the subscription owner’s request. I will be testing how this works with security to the source request’s Viewpoint/Application when it comes to provisioning of the data and what the assignee can see.

15.  Participant Permission and Granular Data Access by Action and Property

HB POV: This is a big change that has a usability impact. Instead of having two user roles, this common role will have different permissions on the data based on the activity needing to be performed. This is more on-par with other Oracle EPM applications’ read/write security.

16.  Recall Requests Awaiting Approval ***

HB POV: From a workflow perspective, if a user accidentally submits a request, prior to 21.04, they’d have to message the approver to push back the request. Recalling a request is a basic governance activity and we are happy to see it as an option for customers to ease workflow processing. Note, if there are no approval policies in place – you can’t recall! (it would be submitted, and the user would have to make a subsequent request to fix the mistake).

This is my HyperionBarbie “2nd Favorite Feature” of this release drop!

17.  Reconnect Parents, Header/Footer, and .ZIP file Options in Dimension Extracts

HB POV: The Extract features continue to be expanded, which gives us more and more options for additional targets outside of Oracle. Headers and footers are extremely helpful for legacy application integration (think HFM) without creating anything custom or taking up record space.

18.  Reference Node Data Type Properties in Expressions

HB POV: In 20.12, we were given the functionality to build properties that referenced other Node Types – useful for mapping or associated members. Now we can use those node’s Name and Description properties in calculations, giving us more flexibility in user experience with mapping.

19.  Request Object in Expressions for Validations, Policies, and Subscriptions

HB POV: This will give more flexibility routing requests based on their attributes. If we want a specific owner or request title to be routed differently based on logic, we can drive those workflows accordingly.

20.  Request Title Included in Transaction History

HB POV: This is again a much needed enhancement; especially if your organization uses a naming convention standard for Request Titles. This information is extremely useful for auditing and researching request activities.  

21.  REST API to Dimension Import, Export, and Export Mappings by Name

HB POV: Prior to this update, the integrations called for unique “UUIDs” or randomly generated 16-byte unique codes that were only available by using REST “GET” calls. This is more user-friendly and should enhance customers’ integrations requiring less maintenance.

22.  REST API to Download Transaction History

HB POV: This has been a feature we have asked for in Cloud Customer Connect – We can now automate the extraction of the Transaction History, which is helpful for retrieving data and also for analytical purposes. Watch for more on this – Working on accelerator to provide analytics to your governance processing based off of this feature: who are your most active users? How long do workflows take? What dimensions change most? DRM Analytics, who?

23.  REST API to Upload, List, and Delete Files in the Staging Area

HB POV: The inclusion of additional REST API commands for EDM allows for more mature processing of automations; especially if EDM is ingesting data from a source. These functions will allow for us to keep the staging area tidy and only include necessary files for processing.

24.  Subscription Indicator on ViewPoints

HB POV: Another one the asks from Cloud Customer Connect has come to fruition: there is now an indicator on Viewpoints that depicts an icon showing it is a target of a subscription. In addition to the Subscription report, this is very useful for end-users to understand where the Subscriptions have been configured.

25.  Set Archived View Back to “Active” Status

HB POV: In the past, if a View had been archived; it was not able to be re-activated. This will help with re-use and avoiding clutter in the Views card.

26.  Suffix for Node Type Qualifiers

HB POV: Prior, prefixes were supported for this purpose. Customers now have the option of using a suffix and still be able to use EDM’s inherent compare functionality to align the suffixed members with those that maybe do not have a suffix but have the same code & meaning.

27.  Tools Cluster Home Page

HB POV: This is the first ‘clustering’ of the EDM application, compared the rest of its EPM siblings (Consolidation & Close, Planning & Budgeting, etc.). The Tools card now opens into sub-cards with additional administrative options.