Just wanted to share some of my Idea Lab posts for EDM that Oracle has made available in the 24.03 release. Please take a few minutes to see what Oracle has done and as always, remember to vote and comment on idea lab posts you like as Oracle is listening and responding to the community.
Allow for exclusion of archived objects when creating a template
Ask: We need the ability to exclude archived or draft objects when creating templates.
Use Case and Business Need: When migrating to production, we need to ensure there is no left over work in progress or "dead" objects that cannot be deleted but have been archived. These archived objects will not have been tested and cannot be migrated to production. They must be excluded from the template.
In addition, this feature would allow for the clean up of unwanted archived objects in lower environments as well. By exporting the template without the archived objects and the associated data via exports, the application can be archived and deleted. Then it can be re-created with the template and data exports where the old archived objects will no longer exist.
Oracle Delivered: EXCLUDE ARCHIVED OBJECTS DURING TEMPLATE IMPORT
When importing a template file, you can prevent archived objects in the template from being imported into a target Enterprise Data Management environment if the objects are not already present. An Exclude Archived Objects option is available for template preview and import to control whether archived objects in the template will be created in the target environment. For objects which are depend on an archived object, those dependent objects will also be excluded from the template import if they do not exist in the target environment. In cases where a dependent object would be partially excluded, the object will appear in the template preview and import with a warning message indicating it cannot be imported.
Business Benefit: Archived objects that were created for an application or dimension in a source environment but are not needed in a target environment can be excluded during a template import process to ensure those objects are not migrated.
Need multi-select option for subscription top node selection
Ask: When selecting Included Top Nodes on a subscription filter, we would like the option to be able to select multiple items at once from the hierarchy instead of one at a time.
Use Case and Business Need: The user experience is very clumsy when multiple top nodes have to be configured in a subscription filter. need the ability to display all top nodes defined.
Oracle Delivered: SELECT MULTIPLE TOP NODES FOR A VIEWPOINT SUBSCRIPTION FILTER
When defining an Included Top Nodes filter for a viewpoint subscription, multiple nodes can be selected at the same time rather than having to select each top node separately. In cases where several nodes need to be selected, this can significantly reduce the effort required to configure the filter for the subscription.
Business Benefit: For viewpoint subscriptions which are filtered using many top nodes, the ability to multi-select those top nodes provides an efficient way to configure the subscription filter.
Allow INSERT Orphans from Node Set to associated Hierarchy Set via UX (not request upload)
Ask: Need the ability to INSERT, using the UX node selector, an orphan node in the node set not in the hierarchy set.
Use Case and Business Need: When a node has become an orphan, the ADD function in the UX does not work as it returns the error: A node with the name '****' already exists in node type '****'.
If you select 'INSERT HERE' instead of ADD, the Select a Node prompt will not find the orphan member from the node set.
We would like to have the Node Selector have an option to select from orphan nodes to insert to the hierarchy set without having to create custom list views for every node set.
Oracle Delivered: QUERY ORPHAN NODES FOR HIERARCHY VIEWPOINTS
Viewpoint queries can be used to identify nodes of particular node types that have not been included in the hierarchy set for a viewpoint. An Orphan Nodes query scope is available to determine which nodes have been excluded and may potentially need to be inserted into the viewpoint. Additional filters can be specified for an orphan nodes query to reduce the results to particular orphans of interest. Nodes from orphan query results can be inserted into the hierarchy viewpoint using drag-and-drop or the node selector dialog when in the context of a request.
Business Benefit: Orphan node queries can be used to ensure nodes of specific node types are included in a hierarchy viewpoint for reconciliation purposes. They also provide a way to identify nodes which may have been indirectly removed from a hierarchy and need to be re-inserted for completeness reasons.
No comments:
Post a Comment