<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shivangi Singh on Medium]]></title>
        <description><![CDATA[Stories by Shivangi Singh on Medium]]></description>
        <link>https://medium.com/@singh.shivangi2808?source=rss-aa74bca8ef7f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kA_8yH8exFnxR1oDEB2ePA.jpeg</url>
            <title>Stories by Shivangi Singh on Medium</title>
            <link>https://medium.com/@singh.shivangi2808?source=rss-aa74bca8ef7f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:42:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@singh.shivangi2808/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[26.09 EDM Cloud Update: Smarter Node Count Insights for Administrators]]></title>
            <link>https://medium.com/@singh.shivangi2808/26-09-edm-cloud-update-smarter-node-count-insights-for-administrators-e599f958fd96?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e599f958fd96</guid>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 15:54:16 GMT</pubDate>
            <atom:updated>2026-10-23T15:54:16.508Z</atom:updated>
            <content:encoded><![CDATA[<p>Oracle Fusion Cloud Enterprise Data Management’s 25.12 release brings two practical improvements to the Node Count dashboard that make it easier to track enterprise data volume over time.</p><p><strong>What’s new:</strong></p><p>🔹 <strong>Node count added to the Weekly Trend chart</strong> — The chart now plots node count alongside record count, so you get both views in a single trend line instead of switching between metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*1PzT7Tp6b7fUHvzD-7VO_g.png" /></figure><p>🔹 <strong>New Grouping option for Time Frame</strong> — When you select a longer Time Frame, you can now choose a Grouping interval (weekly, every 2 weeks, every 4 weeks, and beyond) to control how data points are aggregated, keeping long-range charts clean and readable.</p><p><strong>Why it matters:</strong></p><p>Service administrators and application owners finally get a single, clear view of how enterprise data volume is growing and why. Seeing node and record count together on the same trend makes it much easier to interpret shifts in your data footprint, whether you’re onboarding a new application, completing a large data conversion, or just keeping an eye on overall growth.</p><p>The Grouping option really shines during annual planning and capacity conversations reviewing a full year of growth at a monthly interval tells a much cleaner story than a year of daily noise.</p><p>Small enhancement, real operational value: better visibility into data growth means better-informed capacity and governance decisions.</p><p>📎 Learn more: <a href="https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/dmcaa/dashboard_node_count.html">Node Count Dashboard — Oracle Documentation</a></p><p>Read more about Node Count Dashboard — <a href="https://medium.com/@singh.shivangi2808/node-count-dashboard-in-oracle-edmcs-4ff3fee5ffcf">https://medium.com/@singh.shivangi2808/node-count-dashboard-in-oracle-edmcs-4ff3fee5ffcf</a></p><p>#OracleEDM #EnterpriseDataManagement #EDMCS #DataGovernance #OracleCloud</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e599f958fd96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting All Level-0 Descendants of a Node in Oracle EDM (A Practical Workaround)]]></title>
            <link>https://medium.com/@singh.shivangi2808/getting-all-level-0-descendants-of-a-node-in-oracle-edm-a-practical-workaround-0e624a65d241?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e624a65d241</guid>
            <category><![CDATA[edmc]]></category>
            <category><![CDATA[oracle-edmcs]]></category>
            <category><![CDATA[edm]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 13:16:08 GMT</pubDate>
            <atom:updated>2026-09-09T13:16:08.458Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve spent any time building expressions in Oracle Enterprise Data Management Cloud Service (EDMCS), you’ve probably run into this wall: you want a single node’s <strong>entire level-0 (base) descendant list, </strong>as a string, a set, anything usable and the built-in tools just don’t hand it to you cleanly.</p><p>I hit this exact problem and posted it on the Oracle Cloud Customer Connect community. The short answer from the thread: <strong>this isn’t a native capability today.</strong> The Descendant object gives you FIND and ANY, but:</p><ul><li><strong>ANY</strong> only tells you whether <em>at least one</em> descendant matches a condition , it returns a Boolean, not the list you actually want.</li><li><strong>FIND</strong> iterates through descendants but only surfaces the <em>last</em> value it lands on, not the full set.</li></ul><p>Neither gets you a usable, complete string of level-0 descendants hanging off a given node. So instead of fighting the Descendant object, I flipped the problem around and it turns out the fix is refreshingly simple once you stop trying to go <em>down</em> the hierarchy and instead have every leaf node describe its own path <em>up</em> the hierarchy.</p><h3>The core idea: invert the traversal</h3><p>Instead of asking “what are node X’s level-0 descendants?”, have every level-0 (base) member answer a different question: <strong>“who are all of my ancestors?”</strong></p><p>If every base-level member stores its full ancestor chain, then finding “all level-0 descendants of node X” becomes trivial; you just filter the base members whose ancestor chain contains X. You’ve traded a top-down traversal problem (which EDM’s expression functions don’t handle well) for a bottom-up lookup (which they handle just fine).</p><h3>Step 1: Create a derived property called “Ancestors”</h3><p>On the dimension in question, add a new <strong>derived property, </strong>I named mine Ancestors. The expression uses the built-in positional/ancestor functions available in the EDM Expression Builder, walking up from the current node to the root and concatenating each ancestor&#39;s name into a single delimited string (comma-separated works well).</p><p>The important design choice: only populate this property <strong>for level-0 nodes</strong>. Every other level doesn’t need it, you only care about the ancestor chain at the leaf, because that’s the level you’re ultimately trying to extract.</p><p>At a high level, the expression logic is:</p><ul><li>Check whether the current node is at level 0.</li><li>If yes, walk up the hierarchy from the node to the top, collecting each ancestor’s name.</li><li>Concatenate the collected names into one string using the <strong><em>join </em></strong>function, separated by a comma delimiter.</li><li>If no (the node isn’t level 0), return blank/null- you don’t need this property populated above the base level.</li><li>If required, you can still configure it for all levels of node.</li></ul><p>Once this derived property is set up, every base member in the hierarchy carries its own “breadcrumb trail” of every ancestor above it, all the way to the top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vOQIA4QR14T_4pRgHrr3ZA.png" /></figure><h3>Step 2: Build an EDM Extract on the dimension</h3><p>With the Ancestors property in place, create a new <strong>Extract</strong> in EDM against the dimension:</p><ul><li><strong>Columns to include:</strong> Name and Ancestors</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6grhBNk5rH72VSpT3erbNA.png" /></figure><ul><li><strong>Filter logic:</strong> restrict the extract to only pull nodes where Level = 0</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ei19iNFQw81BeNqHDgA_Gg.png" /></figure><p>This gives you a clean, flat export: one row per base member, with a column showing that member’s name and a second column listing every ancestor above it.</p><h3>Step 3: Pivot on the Ancestors column</h3><p>The final step is to <strong>pivot the extract output on the Ancestors column</strong>. Because Ancestors is a delimited string containing every ancestor for that base member, pivoting effectively regroups the flat extract into an ancestor-centric view for any given ancestor/node, you can now see the full list of level-0 members that sit beneath it.</p><p>In other words: what the Descendant object couldn&#39;t give you directly (a complete, filterable list of level-0 descendants for any node), you now get for free by reading the pivoted extract and filtering on the node you care about.</p><h3>Why this works</h3><p>The FIND/ANY limitation exists because those functions are built to answer &quot;does a condition hold somewhere in this set&quot; or &quot;give me one matching value&quot; ; they&#39;re not designed to accumulate and return a <em>collection</em>. Ancestor traversal from a leaf node, by contrast, is a single deterministic walk up a tree, there&#39;s no branching, no aggregation logic needed, so a derived property script can build that string reliably in one pass.</p><p>By pushing the aggregation work down to property derivation (which runs per-node and is good at building strings) and pushing the “which nodes go with which ancestor” logic into the extract/pivot layer (which is good at reshaping tabular data), you sidestep the part of the Expression Builder that isn’t built for returning sets.</p><h3>A few practical notes</h3><ul><li><strong>Performance:</strong> if your hierarchy is deep or has a very large number of base members, the derived property will recalculate on every relevant change. Keep an eye on extract/sync times if this is a large enterprise dimension.</li><li><strong>Delimiter choice:</strong> pick a delimiter that will never appear in your actual member names, or your pivot/filter logic downstream can get messy.</li><li><strong>Shared members:</strong> if your hierarchy uses shared members, remember a level-0 node can have more than one ancestor path; make sure your derived property (and downstream pivot) accounts for that, or you’ll silently drop valid ancestor relationships.</li><li><strong>Maintenance:</strong> this is a workaround, not a native feature. If Oracle adds proper set-returning support to the Descendant object down the line, this derived-property approach can likely be retired in favor of a native expression.</li></ul><h3>Wrap-up</h3><p>Until Oracle EDM natively supports returning a full set of level-0 descendants from the Descendant object, flipping the direction of the query from &quot;find descendants&quot; to &quot;record ancestors&quot; is a clean, low-maintenance workaround. A derived property, a targeted extract, and a pivot get you exactly the same end result: a complete, filterable list of level-0 descendants for any node in your hierarchy.</p><p>If you’ve found a cleaner way to solve this (or Oracle ships a native fix), I’d love to hear about it, drop a comment on the <a href="https://community.oracle.com/customerconnect/discussion/975726/how-can-we-retrieve-all-level-zero-descendants-of-a-given-node-in-oracle-edm">original Customer Connect thread</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e624a65d241" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oracle EDM 26.09: Change Management Assistant just got smarter!]]></title>
            <link>https://medium.com/@singh.shivangi2808/oracle-edm-26-09-change-management-assistant-just-got-smarter-693b10da3dd7?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/693b10da3dd7</guid>
            <category><![CDATA[edm]]></category>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Tue, 08 Sep 2026 16:24:53 GMT</pubDate>
            <atom:updated>2026-09-08T16:24:53.701Z</atom:updated>
            <content:encoded><![CDATA[<p>Oracle continues to make <strong>Enterprise Data Management (EDM)</strong> more conversational and intuitive with the latest <strong>26.09 update</strong>. The newest <strong>Change Management Assistant enhancements</strong> focus on a simple idea:</p><p><strong>Less navigation. More conversation.</strong></p><p>Here are the key improvements:</p><ol><li><strong>Context-aware prompt guidance</strong><br>A new welcome message provides examples to help users get started. Even better, users can ask for additional prompts that are <strong>context-sensitive to the selected viewpoint, node types, and properties</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zR-g5P_7dYFT5T4g1KgWYA.png" /></figure><p><strong>2. Model After across related viewpoints</strong><br>Model After is no longer limited to the current viewpoint. Users can now model a node after a node in a <strong>related viewpoint</strong>, making it easier to reuse existing structures and maintain consistency across connected data.</p><p><strong>3. Rename nodes conversationally</strong><br>Need to rename a node? Just ask. Users can now perform node renames using <strong>natural-language instructions</strong>, reducing the need for manual navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xY35L3C8yANioJwpzPieIA.png" /></figure><p><strong>4. Smarter string searches</strong><br>When an <strong>Equals</strong> search doesn’t return results, the assistant can fall back to <strong>Contains</strong>. And when users ask for values that “start with” something, the assistant guides them toward the supported search approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l-Vg3ws8Hs0QGFTI576VTw.png" /></figure><p><strong>5. Better context in request comments</strong><br>Comments now include the <strong>request item name</strong>, making it much easier to understand conversations when a request contains multiple items.</p><p><strong>Why does this matter?</strong></p><p>These enhancements aren’t just about adding features, they improve the overall <strong>user experience and adoption of EDM</strong>.</p><p>Users can:</p><ol><li>Get started faster</li><li>Discover relevant actions more easily</li><li>Make changes across related viewpoints</li><li>Perform common maintenance activities conversationally</li><li>Find data more successfully</li><li>Collaborate more effectively on requests</li></ol><p>And from an EDM implementation perspective, I think the bigger story is the continued shift from:</p><p><strong>“Where do I click?”</strong></p><p>to</p><p><strong>“What do I want to accomplish?”</strong></p><p>That shift can significantly simplify how business users interact with enterprise data governance platforms.</p><p><strong>Oracle EDM 26.09 is another step toward making enterprise data management more conversational, contextual, and user-friendly.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=693b10da3dd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oracle EDMCS Change Management Assistant: Bringing Generative AI to Metadata Management]]></title>
            <link>https://medium.com/@singh.shivangi2808/oracle-edmcs-change-management-assistant-bringing-generative-ai-to-metadata-management-18af9c3ce709?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/18af9c3ce709</guid>
            <category><![CDATA[edmc]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 10:34:56 GMT</pubDate>
            <atom:updated>2026-08-31T10:34:56.661Z</atom:updated>
            <content:encoded><![CDATA[<p>Generative AI is rapidly changing how users interact with enterprise applications. But in a platform like <strong>Oracle Enterprise Data Management Cloud (EDMCS)</strong>, the real value of AI is not just answering questions, it is helping users <strong>understand, manage, and make governed changes to enterprise data</strong>.</p><p>With the <strong>Change Management Assistant</strong>, Oracle is bringing a generative AI-powered conversational experience directly into Oracle Fusion Cloud Enterprise Data Management.</p><p>Instead of navigating through multiple screens, building viewpoint queries manually, or searching through request details, users can interact with EDM using <strong>natural language</strong>.</p><p>And what makes this particularly interesting is that the assistant works within EDM’s existing security, workflow, validation, approval, and audit framework.</p><h3>What is the Change Management Assistant?</h3><p>The Change Management Assistant is an embedded, generative AI-powered chat experience available directly from a view in EDM.</p><p>Users can ask questions or provide instructions such as:</p><blockquote><em>“Find all cost centers without an assigned manager.”</em></blockquote><p>or</p><blockquote><em>“Show me all changes to Texas in the last 30 days.”</em></blockquote><p>or even:</p><blockquote><em>“Move department 425 from Sales Director 1 to Sales Director 2.”</em></blockquote><p>The assistant interprets the user’s intent and performs the appropriate EDM action.</p><p>This means users don’t necessarily need to know <strong>which EDM function to use or how to construct the query</strong>. They can describe what they want to accomplish, and the assistant translates that intent into the appropriate EDM operation.</p><p>That’s where this feature becomes particularly interesting.</p><h3>1. Query Your Viewpoints Using Natural Language</h3><p>One of the simplest but potentially most useful capabilities is querying viewpoints through natural language.</p><p>Instead of manually configuring filters and conditions, users can ask questions such as:</p><ul><li>Find members where Email contains “gov”.</li><li>Show all nodes with the revenue account type.</li><li>Find all cost centers without an assigned manager.</li><li>Find orphan nodes.</li><li>Find nodes containing “111” below node “10000”.</li><li>Show me nodes containing “111” in the Entity viewpoint.</li></ul><p>The assistant interprets the prompt, executes the appropriate viewpoint query, and provides the results.</p><p>But Oracle doesn’t stop there. The generated query can be opened in the <strong>Viewpoint Query</strong> tab, where users can review and refine it using the standard EDM query functionality.</p><p>This creates an interesting combination:</p><p><strong>Natural language → AI-generated query → Standard EDM query tools</strong></p><p>So users can start with conversational interaction but still rely on the familiar EDM interface for detailed analysis.</p><h3>2. Explore Nodes Without Searching Through the Hierarchy</h3><p>Another powerful capability is node exploration.</p><p>Users can ask questions about a node’s:</p><ul><li>Properties</li><li>Locations</li><li>Parents</li><li>Relationships</li><li>Links</li><li>Lineage</li><li>History</li></ul><p>For example:</p><blockquote><em>“What is the tax code for Product 555?”</em></blockquote><blockquote><em>“What are the parent nodes for ANS?”</em></blockquote><blockquote><em>“Show me the updates for Texas in the last 30 days.”</em></blockquote><blockquote><em>“What is the lineage for cost center 140?”</em></blockquote><p>This can be especially useful when working with complex enterprise hierarchies where finding a particular piece of information may otherwise require navigating through multiple viewpoints, properties, and hierarchy locations.</p><p>Instead of asking:</p><p><strong>“Where do I find this information?”</strong></p><p>users can simply ask:</p><p><strong>“What is this information?”</strong></p><p>That is a subtle but important shift in how users interact with EDM.</p><h3>3. From Asking Questions to Making Changes</h3><p>This is where the Change Management Assistant becomes much more than a search tool.</p><p>The assistant can help users <strong>create and modify requests using natural language</strong>.</p><p>For example:</p><blockquote><em>“Add a new node Texas under USA.”</em></blockquote><blockquote><em>“Insert Credit Services under Financials.”</em></blockquote><blockquote><em>“Move department 425 under Sales Director 2.”</em></blockquote><blockquote><em>“Update all cost centers in region EMEA to status Active.”</em></blockquote><blockquote><em>“Clear Account Type from node 408.”</em></blockquote><p>The assistant translates the user’s intent into structured request actions. If successful, EDM creates the corresponding request and request items.</p><p>Users can then open the request and continue working with it through the standard EDM process. This is important because AI is not replacing EDM’s change-management framework.</p><p>Instead, it becomes another way to <strong>initiate governed changes</strong>.</p><h3>4. AI Does Not Bypass EDM Governance</h3><p>For me, this is one of the most important aspects of the Change Management Assistant.</p><p>When introducing generative AI into an enterprise data-management platform, one of the obvious questions is:</p><p><strong>“Can AI bypass our existing controls?”</strong></p><p>The answer is no.</p><p>The assistant operates within EDM’s existing:</p><ul><li>Security and permissions</li><li>Data access rules</li><li>Request workflow</li><li>Validations</li><li>Approvals</li><li>Commit controls</li><li>Audit history</li></ul><p>If a user doesn’t have permission to perform an action, the assistant cannot be used to bypass that restriction.</p><p>The user remains the actor of record when changes are performed through the assistant.</p><p>So the model is essentially:</p><p><strong>AI assists → EDM governs</strong></p><p>rather than:</p><p><strong>AI changes data independently</strong></p><p>That distinction is critical for enterprise environments.</p><h3>5. Review Requests Conversationally</h3><p>The assistant can also help users understand existing requests.</p><p>Instead of manually opening different sections of a request, users can ask:</p><blockquote><em>“Summarize the items on this request.”</em></blockquote><blockquote><em>“Who needs to approve this request?”</em></blockquote><blockquote><em>“How many approvals are outstanding?”</em></blockquote><blockquote><em>“How many validation issues are on this request?”</em></blockquote><blockquote><em>“Who is the current assignee?”</em></blockquote><blockquote><em>“Summarize the comments and attachments.”</em></blockquote><p>This can make request management considerably easier, particularly for users who need to review a large number of requests. Think of it as a conversational layer over request information.</p><h3>6. Follow-Up Suggestions Make the Interaction More Natural</h3><p>Another interesting capability is that the assistant can suggest relevant follow-up actions based on the current context and results.</p><p>For example, after retrieving a set of nodes, the assistant can help guide the user toward the next logical step; such as refining the query, exploring related data, or taking action on the results.</p><p>This is important because users don’t always know the exact question they should ask next.</p><p>Instead of treating every interaction as an isolated prompt, the assistant can help create a more <strong>contextual conversation around metadata</strong>.</p><h3>7. There Are Still Some Boundaries</h3><p>As impressive as the feature is, it is important to understand what it does <strong>not</strong> currently support.</p><p>For example, the assistant does not currently support:</p><ul><li>Renaming nodes</li><li>Reordering nodes under a parent</li><li>Modeling after nodes in a related viewpoint</li><li>Creating request actions from screenshots, spreadsheets, or uploaded files</li><li>Comparison use cases</li><li>Querying result outside the capability of Viewpoint query</li></ul><p>These limitations are important when evaluating the feature for real-world implementations.</p><p><strong>The Change Management Assistant should be viewed as an additional interaction layer, not a replacement for every EDM capability.</strong></p><h3>8. What Does This Mean for EDM Implementations?</h3><p>From an implementation perspective, I see several interesting possibilities.</p><h3>For Business Users</h3><p>The learning curve can potentially be reduced.</p><p>Instead of requiring users to understand every EDM navigation path, they can start with natural-language questions.</p><h3>For Data Stewards</h3><p>Common activities such as searching for nodes, investigating properties, reviewing history, and understanding requests can become faster.</p><h3>For EDM Administrators</h3><p>The assistant could reduce some of the repetitive questions and navigation tasks that typically come up during metadata maintenance.</p><h3>For Governance Teams</h3><p>The biggest advantage is that AI assistance remains within the existing EDM governance framework.</p><p>That means organizations can explore generative AI without creating a completely separate change-management process.</p><h3>The Bigger Picture</h3><p>The Change Management Assistant represents an interesting direction for Oracle EDM.</p><p>Historically, interacting with an enterprise metadata-management platform required users to understand the application’s terminology, navigation, and available functions.</p><p>Generative AI changes that interaction model.</p><p>Instead of:</p><p><strong>“I need to create a viewpoint query.”</strong></p><p>A user can simply say:</p><p><strong>“Find all cost centers without an assigned manager.”</strong></p><p>Instead of:</p><p><strong>“I need to create a request and add a move action.”</strong></p><p>A user can say:</p><p><strong>“Move department 425 from Sales Director 1 to Sales Director 2.”</strong></p><p>The complexity of <em>how</em> to perform the task increasingly becomes abstracted from the user.</p><p>And that is where I think the real potential lies.</p><h3>My Take</h3><p>The Change Management Assistant is not just another chatbot added to EDM.</p><p>Its real value is the combination of:</p><p><strong>Generative AI + Natural Language + Metadata + Change Management + Governance</strong></p><p>The most important part is that AI doesn’t replace EDM’s governance model.</p><p>It sits on top of it.</p><p>Users can interact with enterprise data more naturally, while EDM continues to control <strong>who can make changes, what changes are valid, how changes are approved, and how those changes are audited</strong>.</p><p>For organizations already using Oracle EDM, this could be an interesting step toward making metadata management more accessible to business users while maintaining enterprise-grade governance.</p><p>And as Oracle continues expanding the capabilities of AI within EDM, I think the bigger question will become:</p><p><strong>How much of our day-to-day metadata management can we accomplish simply by asking EDM what we want?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18af9c3ce709" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oracle EDM 26.09: A Feature-Packed Update for Enterprise Data Management]]></title>
            <link>https://medium.com/@singh.shivangi2808/oracle-edm-26-09-a-feature-packed-update-for-enterprise-data-management-e2914ae83111?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2914ae83111</guid>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 09:55:37 GMT</pubDate>
            <atom:updated>2026-08-31T09:55:37.544Z</atom:updated>
            <content:encoded><![CDATA[<p>Oracle Enterprise Data Management (EDM) continues to evolve with every monthly update, and <strong>26.09 brings several enhancements that caught my attention from an implementation and administration perspective.</strong></p><p>The September 2026 release focuses not just on new capabilities, but also on improving <strong>usability, integration, governance, migration, and operational visibility</strong>.</p><p>Here are some of the features I’m most excited about :</p><h3>1. Contextual Properties for Nodes in Viewpoints</h3><p>One of the most interesting enhancements in this release is <strong>Contextual Properties</strong>.</p><p>Properties displayed for a node can now dynamically change based on the value of a designated controlling property.</p><p>In practical terms, this means users don’t necessarily need to see every possible property for every node.</p><p>For example:</p><p>➡️ Node Type / Category = A → Show properties relevant to A<br>➡️ Node Type / Category = B → Show properties relevant to B</p><p>As the context changes, the Properties tab automatically adapts while still respecting the configured property groups.</p><p><strong>Why does this matter?</strong></p><p>For EDM implementations with a large number of properties, this can significantly improve the user experience and make viewpoints much cleaner and easier to maintain.</p><p>It also opens up interesting possibilities for designing more <strong>business-friendly EDM applications</strong>.</p><h3>2. Execute and Monitor Oracle Integration Cloud Processes from EDM</h3><p>This is another feature that immediately stands out.</p><p>With 26.09, users can now <strong>register, run, monitor, and audit Oracle Integration Cloud (OIC) processes directly from the EDM web interface or REST API.</strong></p><p>The integration history provides visibility into:</p><p>• Jobs<br>• Tasks<br>• Statuses<br>• Messages<br>• Integration execution history</p><p>There is also a granular access-control role to govern who can manage and execute integrations.</p><p><strong>Why I think this is significant:</strong></p><p>For organizations using EDM as part of a broader EPM integration architecture, this can reduce the need to switch between multiple applications just to monitor integration activity.</p><p>It brings integration execution and monitoring closer to the place where metadata governance is happening.</p><h3>3. New Artifact Types for Granular Template Export</h3><p>Migration between EDM environments is another area receiving a useful enhancement.</p><p>Granular template exports can now include individually selected:</p><p>✅ Views<br>✅ Viewpoints<br>✅ Compare Profiles<br>✅ Extract Packages</p><p>These artifacts can also be combined with other artifact types within the same granular template.</p><p>This provides administrators with more control over <strong>what exactly gets migrated between environments</strong>.</p><p>For projects with DEV → TEST → PROD migration cycles, this can help reduce unnecessary artifact movement and make migration packages more targeted.</p><h3>4. Change Management Assistant Enhancements</h3><p>The <strong>Change Management Assistant</strong> also receives enhancements in 26.09.</p><p>For EDM administrators managing frequent application changes, this is an area worth exploring because change management becomes increasingly important as EDM environments grow in complexity.</p><p>The broader direction is clear: Oracle is continuing to improve the tools available for <strong>understanding, managing, and migrating EDM configuration changes.</strong></p><h3>5. Better Navigation for Node Data Type Properties</h3><p>Another usability improvement is the introduction of <strong>Navigation Links for Node Data Type Properties</strong>.</p><p>This is particularly interesting for implementations where node properties reference other nodes or objects.</p><p>Anything that makes it easier for users to navigate through metadata relationships can reduce the amount of manual searching required when working with complex hierarchies.</p><h3>6. More Visibility into EDM Jobs and Requests</h3><p>26.09 also introduces several improvements around operational visibility, including:</p><p>a) Extended visibility to previous Import, Export, Load, and Extract jobs</p><p>b) Submitted Date and Submitted By columns in Request Activity</p><p>c) Node Count Dashboard improvements</p><p>d) REST API for System Events Audit</p><p>These may look like smaller enhancements individually, but collectively they improve the <strong>administration and monitoring experience</strong>.</p><p>For EDM support teams, better visibility into what happened, when it happened, and who initiated an action can make troubleshooting and audit activities much easier.</p><h3>7. Additional Improvements Worth Exploring</h3><p>The 26.09 release also includes:</p><p>• Default Property Groups for Viewpoints<br>• Disable Workflow at Application Level<br>• Include Management Hierarchy for Ownership Approval Policies<br>• Relaxed Permission Check During Resubmit of Enriched Requests<br>• Access Token URI for OAuth 2.0 Cloud EPM Connections<br>• Additional audit capabilities through EPM Automate and REST APIs</p><p>Oracle lists these as small-scale changes, but depending on your EDM architecture, some can have a meaningful impact on implementation design and administration.</p><h3>My Take on EDM 26.09</h3><p>What I like about this release is that Oracle isn’t focusing only on adding more functionality.</p><p>There is a clear focus on making EDM:</p><p><strong>More contextual → More integrated → More manageable → More auditable</strong></p><p>The combination of <strong>Contextual Properties + OIC integration management + granular migration capabilities</strong> is particularly interesting for enterprise implementations.</p><p>From an implementation perspective, I would recommend reviewing 26.09 not only from a <em>“What new feature do we have?”</em> perspective, but also from:</p><p><strong>&gt; Can this simplify our current EDM design?</strong><br>&gt; <strong>Can this reduce custom automation?</strong><br>&gt; <strong>Can this improve our migration process?</strong><br>&gt; <strong>Can this make the EDM experience easier for business users?</strong></p><p>Those are often where the real benefits of a monthly Cloud EPM update become visible.</p><p>Oracle’s full <strong>Enterprise Data Management 26.09 What’s New</strong> documentation is available on the Oracle Help Center.</p><p><a href="https://docs.oracle.com/en/cloud/saas/readiness/epm/2026/epm-sep26/26sep-epm-wn-f51187.htm#epm-sep26-f51187">https://docs.oracle.com/en/cloud/saas/readiness/epm/2026/epm-sep26/26sep-epm-wn-f51187.htm#epm-sep26-f51187</a></p><p><strong>Which EDM 26.09 feature are you most interested in exploring?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2914ae83111" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Out of Office Warnings and My Take on What’s Next]]></title>
            <link>https://medium.com/@singh.shivangi2808/out-of-office-warnings-and-my-take-on-whats-next-bd9436921fc1?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd9436921fc1</guid>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 10:41:34 GMT</pubDate>
            <atom:updated>2026-07-28T10:41:34.085Z</atom:updated>
            <content:encoded><![CDATA[<p>When you work closely with Oracle EDMCS implementations, you start noticing how even the smallest product updates can make a real difference in day-to-day administration. Not every feature solves a major challenge sometimes it is about adding thoughtful guardrails that make processes smoother and prevent small issues from snowballing.</p><p>The 25.09 update is a good example of this. Oracle has introduced the “Out of Office Warning During Request Assignment” feature. It may not have been a pressing pain point for most teams, but it is still a valuable improvement that promotes better awareness and accountability during request management.</p><p><strong>What’s New in 25.09?</strong></p><p>With this update, when you attempt to assign a request, the system now displays a warning if the assignee has marked themselves as Out of Office. It is a simple improvement, but one that helps ensure assignments land with someone who is available to act, instead of being delayed unnecessarily.</p><p>What makes this release especially exciting for me is the personal connection: this idea first began as a suggestion I shared on Oracle’s Customer Connect. <a href="https://community.oracle.com/customerconnect/discussion/853311/restrict-the-interactive-request-assignment-to-out-of-office-users">Link to my Idea</a></p><p><strong>Why This Matters</strong></p><p>From an implementer’s perspective, the impact is clear:</p><ul><li>Improved Visibility — Users are informed immediately if the selected assignee is not available.</li><li>Smarter Routing — Requests can be reassigned before they risk becoming stalled.</li><li>Faster Turnaround — By ensuring requests remain active, organizations can continue meeting delivery timelines.</li></ul><p><strong>How to Mark Yourself Out of Office in EDMCS</strong></p><p>If you have not tried this yet, here is a quick guide to mark yourself Out of Office in EDMCS:</p><ol><li>Login into your EDMCS application.</li><li>On the top right, click on your Username.</li><li>Select User Preference.</li><li>Click Edit.</li><li>Check the Out-of-Office box.</li><li>Select your Delegate User (this user will act on your behalf).</li><li>Click Save.</li></ol><p><em>Important note:</em> Ensure your selected Delegate User has the appropriate permissions to action requests.</p><p><strong>My Enhancement Idea: Extending This Feature Through APIs</strong></p><p>While this feature works well in the user interface, many organizations rely on automated workflows through APIs.</p><p><strong>Here is the current limitation:</strong></p><ul><li>The Out of Office warning is only triggered for manual assignments in the interface.</li></ul><p><strong>My proposal:</strong></p><ul><li>With this enhancement, I propose extending the logic so that when an Admin/User marks themselves as Out of Office (OOO), the request is automatically routed to their designated Delegate User (selected during the OOO setup). This will prevent requests from remaining in Draft status for long periods while waiting for an unavailable Admin to return. Additionally, the API should validate the user’s OOO status at the time of assignment. If the user is marked OOO or has a warning status, the system should either:</li></ul><ol><li>Trigger another API to reassign the request to the Delegate User, or</li><li>Skip the assignment and instead send an email notification indicating that the user is OOO based on business requirements.</li></ol><p>This would ensure requests are never left in draft status and would maintain continuity in automated flows.</p><p>I recently shared this idea on Oracle Customer Connect: <a href="https://community.oracle.com/customerconnect/discussion/905452/enhancement-prevent-assigning-requests-to-ooo-users-via-ui-and-rest-api#latest">Link to my idea</a>.</p><p><strong>Call to Action</strong></p><p>I would be interested in hearing your thoughts:</p><ul><li>Have you ever had requests delayed because the assigned user was unavailable?</li><li>Would extending this functionality into the API layer make your automated processes more resilient?</li></ul><p>Let us continue the conversation. Enhancements like these, though small, add up to a stronger and more efficient Oracle EDMCS experience for everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd9436921fc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Generative AI in Oracle EDMCS Application Registration]]></title>
            <link>https://medium.com/@singh.shivangi2808/generative-ai-in-oracle-edmcs-application-registration-9f55662539fe?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f55662539fe</guid>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Fri, 03 Jul 2026 08:03:33 GMT</pubDate>
            <atom:updated>2026-07-03T08:03:33.351Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever spent hours defining properties for node types in your applications, only to second-guess your data types, configurations, or miss a critical parameter?</p><p>A few days ago, I was working to add new Universal application into Oracle Enterprise Data Management Cloud Service.</p><p>We had everything ready — data files, structure, business requirements. But then came the familiar bottleneck:</p><p><em>“We need to define all the node type properties…”</em></p><p>If you’ve worked with Universal application registration, you know what that means — manual effort, constant validation, and a lot of back-and-forth.</p><p>That’s exactly the challenge this new innovation is solving. In today’s data-driven landscape, speed and accuracy in application setup are critical. With the latest innovation in Universal Application Registration, Oracle introduces a powerful new capability in 25.12 release: Application Registration Assistant: Generate Properties — a Generative AI-driven feature designed to simplify and accelerate how properties are created and configured.</p><h3>Enter: Application Registration Assistant — Generate Properties</h3><p>Instead of manually defining properties, we uploaded a simple CSV sample file.</p><p>Within minutes, the Generative AI assistant:</p><ul><li>Analyzed the data</li><li>Created custom property definitions (in the <em>Custom namespace</em>)</li><li>Suggested data types and configurations</li></ul><p>And just like that, we had a strong starting point.</p><p>Not perfect — but incredibly fast.</p><h3>Introducing: Application Registration Assistant — Generate Properties</h3><p>This feature brings Generative AI directly into the application registration process, helping teams quickly create and configure properties based on real data — no guesswork, no heavy manual effort.</p><p>A Quick Story from the Field</p><p>Imagine a data steward onboarding a new application. Traditionally, they would:</p><ul><li>Analyze sample datasets manually</li><li>Identify required properties</li><li>Decide on data types</li><li>Configure parameters one by one</li></ul><p>Now, with the AI assistant:</p><ul><li>They upload a simple CSV file</li><li>The system analyzes the data</li><li>Properties, data types, and configurations are suggested instantly</li></ul><p>Instead of hours, it takes minutes.</p><h3>How It Actually Works (Step-by-Step)</h3><p>The Application Registration Assistant leverages Generative AI to automatically generate and configure properties for node types within Universal applications.</p><p>Once you’re on the Properties for Dimension Node Type page (while adding/modifying a node type or property):</p><ol><li>Click Generate</li><li>Upload a CSV file (must include column headers)</li><li>The AI assistant analyzes the file <em>(typically within a few minutes)</em></li><li>Generated properties are displayed for review</li></ol><p>Generate Property in Application registration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9_YYAKPfwd0uhi04" /></figure><p>Sample CSV file</p><p>Property Generated based on File loaded</p><h3>You can then:</h3><ul><li>Edit property parameters</li><li>Navigate across data type tabs or by clicking on Actions</li><li>Refine properties from available drop-down options</li><li>Apply changes or close without saving</li></ul><p>Property Parameters</p><p>Data Type Tab</p><p><em>Note: The Generative AI setting must be enabled in Enterprise Data Management to use this feature.</em></p><h3>How to Enable Generative AI</h3><p>Before using this feature, make sure Generative AI is enabled:</p><ol><li>Navigate to Tools &gt; Settings</li><li>Locate the Generative AI configuration section</li><li>Enable the feature toggle</li><li>Save and refresh your session</li></ol><p>Gen AI Enable Configuration</p><p>Once enabled, the assistant becomes available during application registration.</p><h3>Sample File Tips (These Matter More Than You Think)</h3><p>From experience, the quality of your output depends heavily on your input:</p><ul><li>✅ Only the first 10 rows are analyzed → make them meaningful</li><li>✅ Ensure clear column headers</li><li>✅ Use CSV format (not XLSX)</li><li>⚠️ Existing properties won’t be duplicated</li><li>⚠️ Name conflicts with different data types will trigger validation errors. Meaning, If a property in your sample file already exists with the same name but a different data type, when you apply your changes a Name Uniqueness validation error is displayed. To resolve this, in the Generate Properties dialog box you can either rename or delete the new property, or else you can change the new property’s data type to be the same as the data type of the existing property.</li></ul><p><em>Pro tip:</em> If you download a viewpoint, remember to convert it to CSV before uploading.</p><h3>What the AI Does (and Doesn’t Do)</h3><p>The assistant is powerful, but it’s not magic.</p><p>It will:</p><ul><li>Recommend properties and data types</li><li>Suggest basic configurations</li><li>Organize outputs by data type</li></ul><p>It will NOT fully define:</p><ul><li>Invalid characters</li><li>Allowed values</li><li>Default values</li></ul><p>These still require human review and that’s important.</p><p><em>⚠️The AI assistant is a starting point, not the final authority. Always review and validate before applying.</em></p><h3>Reviewing &amp; Applying Properties</h3><p>Once generated, properties are presented in a structured interface:</p><ul><li>All Tab → Overview with common parameters</li><li>Data Type Tabs → Type-specific configurations</li><li>Edit → Modify parameters anytime</li><li>Search → Quickly find properties</li></ul><p>Before applying:</p><ul><li>You can change data types (defaults will adjust automatically)</li><li>Delete unnecessary properties</li><li>Adjust configurations</li></ul><p>When ready: Click Apply → System validates everything before finalizing</p><h3>Important Configuration Notes</h3><ul><li>By default, all generated properties are set at Node level &gt; Need Relationship-level? Change it <em>before applying</em></li><li>Some advanced settings (like Address subtype configurations) are handled after generation in the registration wizard</li></ul><h3>What Changed for Us?</h3><p>What used to take hours… Now takes minutes.</p><p>But more importantly:</p><ul><li>We reduced manual effort significantly</li><li>Improved consistency across properties</li><li>Enabled faster onboarding of applications</li></ul><p>And the team? They spent less time configuring and more time thinking strategically.</p><h3>Final Thought</h3><p>This isn’t just a feature, it’s a shift in how we approach data management.</p><p>With Generative AI in Oracle Enterprise Data Management Cloud Service, we’re not replacing expertise, we’re accelerating it.</p><p>If you’re still manually defining properties, it might be time to try a smarter approach.</p><p><em>Have you explored this feature yet? What was your experience?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f55662539fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Role of EDMCS in Oracle EPM Valid Intersections]]></title>
            <link>https://medium.com/@singh.shivangi2808/the-role-of-edmcs-in-oracle-epm-valid-intersections-4ad5c5e2a724?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ad5c5e2a724</guid>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Wed, 01 Jul 2026 21:20:09 GMT</pubDate>
            <atom:updated>2026-07-01T21:20:09.521Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve worked on Oracle EPM, you’ve probably used Valid Intersections to tackle one of the most common issues; users entering data into combinations that should never exist.</p><p>We’ve been there too.</p><p>On one of my projects, team implemented Valid Intersections to bring control into the application. And honestly, the results were immediate:</p><ul><li>Forms looked cleaner</li><li>Data errors dropped significantly</li><li>Users didn’t need constant guidance</li></ul><p>For a while, everything felt “fixed.”</p><p>Then Things Started Changing….</p><p>A few months down the line, the business started evolving:</p><ul><li>New members were added</li><li>Hierarchies were updated</li><li>Structures changed</li></ul><p>And that’s when the cracks started to appear.</p><p>Those same Valid Intersection rules that worked so well initially:</p><ul><li>Started needing frequent updates</li><li>Missed some new valid combinations</li><li>Occasionally blocked the right ones</li></ul><p>That’s when it really clicked -</p><p>The problem wasn’t just about controlling intersections, It was about how the underlying metadata was being managed</p><h3>A Quick Refresher: What Valid Intersections Do</h3><p>Valid Intersections allow you to define logical relationships between dimensions, controlling where data can and cannot be entered.</p><p>They’re not about security.</p><ul><li>Security says: <em>Who can access data?</em></li><li>Valid Intersections say: <em>Does this combination even make sense?</em></li></ul><p>And that distinction is what makes them so powerful.</p><h3>Valid Intersections: Powerful, But Dependent</h3><p>Valid Intersections work by defining relationships between dimension hierarchies.</p><p>Most implementations follow best practices:</p><ul><li>Use parent members instead of individual nodes</li><li>Leverage functions like IDescendants() for scalability</li></ul><p>This keeps rules dynamic — but only as long as the underlying hierarchies are well managed.</p><p>If those hierarchies change in an uncontrolled way, your rules:</p><ul><li>Become incomplete</li><li>Allow unintended combinations</li><li>Or worse, block valid ones</li></ul><h3>How We Typically Configure Them</h3><p>The setup itself is quite straightforward:</p><ol><li>Navigate to Application → Valid Intersections</li><li>Create a rule (e.g., <em>Valid_Intersection</em>)</li><li>Define: Anchor Dimension (driving dimension)Target Dimension (dimension to restrict)</li></ol><p>Most of us follow the same best practices:</p><ul><li>Use parent members instead of individual nodes</li><li>Use IDescendants() to keep rules dynamic</li></ul><p>And this works well…</p><p>…but only if your hierarchies are stable.</p><h3>The Most Important Behavior (Often Overlooked)</h3><p>One key concept that drives everything:</p><p>Anything not explicitly defined as valid is automatically invalid</p><p>So your rule is only as good as what it includes and what your hierarchies support.</p><h3>Where Things Break Down</h3><p>Valid Intersections depend entirely on dimension hierarchies.</p><p>If those hierarchies:</p><ul><li>Change frequently</li><li>Are updated without control</li><li>Lack clear ownership</li></ul><p>Then your rules:</p><ul><li>Become outdated</li><li>Allow incorrect combinations</li><li>Or block valid business inputs</li></ul><h3>This Is Where EDMCS Changes the Game</h3><p>Enterprise Data Management Cloud Service (EDMCS) brings structure and governance to the one thing Valid Intersections depend on the most hierarchies.</p><p>Instead of managing metadata directly inside EPM:</p><ul><li>You manage it centrally in EDMCS</li><li>You control how changes are introduced</li><li>You ensure alignment across applications</li></ul><p>Valid Intersections then become simpler and far more reliable.</p><h3>How EDMCS Strengthens Your Design</h3><h3>1. Stable Anchors for Your Rules:</h3><p>Valid Intersections are most effective when built on stable parent nodes.</p><p>EDMCS ensures:</p><ul><li>Those parent nodes are well-defined</li><li>Ownership is clear</li><li>Structural integrity is maintained</li></ul><p>So when new members are added, they naturally fall into the correct logic without rewriting rules.</p><h3>2. Controlled Change Management:</h3><p>One of the biggest risks in EPM is unmanaged hierarchy updates.</p><p>With EDMCS:</p><ul><li>Every change goes through a request workflow</li><li>Approvals are enforced</li><li>Updates are intentional ; not accidental</li></ul><p>This protects the logic you’ve built into Valid Intersections.</p><h3>3. Built-In Impact Awareness:</h3><p>Hierarchy changes don’t happen in isolation.</p><p>EDMCS helps you understand:</p><ul><li>What is changing</li><li>Where it is used</li><li>What downstream processes could be affected</li></ul><p>This is critical when your Valid Intersections depend on those structures.</p><h3>4. Consistency Across the EPM Landscape:</h3><p>In most organizations, the same dimensions are shared across:</p><ul><li>Planning</li><li>Consolidation</li><li>Reporting</li></ul><p>Without EDMCS, inconsistencies creep in.</p><p>With EDMCS:</p><ul><li>A single version of the hierarchy is maintained</li><li>Valid Intersections align with enterprise-wide structures</li><li>Data integrity improves across the board</li></ul><h3>What This Looks Like in Practice</h3><p>When EDMCS is not part of the picture:</p><ul><li>Valid Intersections require frequent maintenance</li><li>Admin effort increases over time</li><li>Logic becomes harder to track</li></ul><p>When EDMCS is embedded into the process:</p><ul><li>Valid Intersections become lean and scalable</li><li>Rules rarely need rework</li><li>Governance becomes part of the system, not an afterthought</li></ul><h3>Final Thoughts…</h3><p>Valid Intersections are often seen as the solution to bad data entry.</p><p>But in reality, they are only as strong as the metadata they rely on.</p><p>If you want them to work not just today but six months or a year from now you need to focus on how that metadata is created, maintained, and governed.</p><p>That’s exactly what EDMCS brings to the table.</p><p>Because in a well-designed EPM environment:</p><ul><li>Valid Intersections control behavior</li><li>EDMCS ensures that behavior stays correct over time</li></ul><p>And that’s the difference between a working solution… and a sustainable one.</p><p>Curious to know if have you faced similar challenges with Valid Intersections? Have you used EDMCS to solve them?</p><p>If you’re looking at how EDMCS can support your EPM design and help manage valid intersections within EDM, I’d be happy to connect and share insights from my experience on how EDM can be effectively used for this purpose.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ad5c5e2a724" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node Count Dashboard in Oracle EDMCS]]></title>
            <link>https://medium.com/@singh.shivangi2808/node-count-dashboard-in-oracle-edmcs-4ff3fee5ffcf?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ff3fee5ffcf</guid>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Wed, 01 Jul 2026 21:16:38 GMT</pubDate>
            <atom:updated>2026-07-01T21:16:38.196Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s data-driven landscape, one of the biggest challenges organizations face is not just managing enterprise data but understanding how it grows, where it resides, and how it impacts licensing and performance.</p><p>The Node Count Dashboard in Oracle Fusion Cloud Enterprise Data Management, introduced as part of the <em>25.12 feature release</em>, is designed to address exactly this challenge by providing a centralized, insightful view of both current and historical data volumes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GZuY_RtNmes0mE2j" /></figure><p>Node Count Dashboard</p><h3>Understanding the Basics: Nodes vs. Records</h3><p>Before diving into the dashboard, it’s important to clarify two key terms:</p><ul><li>Nodes: Total count of nodes across all applications</li><li>Records: Count of <em>unique</em> nodes across all applications</li></ul><p>This distinction is critical because records directly impact subscription limits in EDMCS. While nodes may appear multiple times across applications, records represent the true footprint of your enterprise data.</p><h3>How Node Count is Calculated in EDMCS</h3><p>From a technical perspective, the dashboard is built on committed data within EDMCS and reflects:</p><ul><li>Only committed requests (excludes draft or in-flight changes)</li><li>Aggregated node counts across applications, viewpoints, and dimensions</li><li>De-duplicated record counts based on unique node identifiers</li></ul><p>This ensures alignment with Oracle’s licensing model, making the dashboard a reliable source for subscription monitoring and audit readiness.</p><h3>What the Dashboard Offers?</h3><p>The Node Count Dashboard provides a comprehensive, multi-dimensional view of data:</p><p><strong>1. Current Snapshot (Node Count Tab)</strong></p><p>Get an instant, point-in-time view of total node count based on selected filters.</p><ul><li>Reflects committed data only</li><li>Updates after request commits, not during staging</li><li>Provides a reliable baseline for operational monitoring</li></ul><p><strong>2. Weekly Record Count Trend</strong></p><p>Track how your data evolves over time with historical trends. Users can analyze growth across multiple timeframes:</p><ul><li>Last 6 to 52 weeks</li><li>Or full historical view</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*I7opCNi1OAgXKJHq" /></figure><p>Weekly Record Count Trend</p><p>Identify:</p><ul><li>Sudden spikes due to bulk loads or integrations</li><li>Gradual growth from ongoing data onboarding</li><li>Seasonal or cyclical data patterns</li></ul><p><strong>3. Node Count Distribution</strong></p><p>Visualize how nodes are distributed across:</p><ul><li>Applications</li><li>Dimensions</li><li>Node Types</li></ul><p>This helps quickly identify:</p><ul><li>High-volume applications driving data growth</li><li>Dimensions with excessive hierarchy expansion</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/0*shBGyw5QqoKlPwxK" /></figure><p>Data Chain Filter</p><h3>Data Chain Filter: Advanced Analysis Capability</h3><p>The dashboard includes a flexible Data Chain filter that enables deeper analysis:</p><ul><li>Select multiple applications (up to 15) for cross-application insights</li><li>Drill down into dimensions when a single application is selected</li><li>Refine further by node type</li></ul><p>Important behavior:</p><ul><li>Dimension-level filtering is only enabled for single application selection</li><li>Multi-application selection prioritizes aggregated consistency</li></ul><p>Users can also save filter combinations, allowing standardized and repeatable analysis for governance and audit.</p><h3>Why This Matters for Organizations?</h3><p>The Node Count Dashboard is more than just a reporting tool, it’s a strategic decision-making enabler. In subscription-based environments, where record limits are tied to licensing, having clear visibility into data volume is essential.</p><h3>Practical Use Cases</h3><ul><li>License Monitoring: Track record count against subscription limits to avoid overages</li><li>Data Governance: Identify duplicate or redundant nodes across applications</li><li>Environment Optimization: Detect unused or excessive dimensions contributing to data volume</li><li>Release Impact Analysis: Assess how integrations, hierarchy loads, or transformations impact node growth</li></ul><h3>Key Considerations</h3><p>To use the dashboard effectively, keep the following in mind:</p><ul><li>Only committed data is reflected (no draft changes)</li><li>Historical trends depend on available snapshot data</li><li>Large environments may experience minor refresh latency</li><li>Node count ≠ Record count — always rely on record count for licensing decisions</li></ul><h3>Pro Tips</h3><ul><li>Create saved filters for application-specific governance views</li><li>Monitor trends after major data loads or restructuring activities</li><li>Regularly review high-growth areas to prevent data sprawl</li></ul><h3>Conclusion</h3><p>As enterprise ecosystems grow more complex, having clear visibility into data volume is no longer optional — it’s essential.</p><p>The Node Count Dashboard in Oracle EDMCS (25.12 release) bridges the gap between data governance and subscription management by combining real-time visibility with historical trend analysis.</p><p>It empowers data stewards and administrators to move beyond reactive monitoring toward proactive data optimization, capacity planning, and informed decision-making, ensuring a scalable and future-ready data landscape.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ff3fee5ffcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Request Monitoring Dashboard]]></title>
            <link>https://medium.com/@singh.shivangi2808/request-monitoring-dashboard-fc0107f27f74?source=rss-aa74bca8ef7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc0107f27f74</guid>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[oracle-edmcs]]></category>
            <dc:creator><![CDATA[Shivangi Singh]]></dc:creator>
            <pubDate>Wed, 24 Jun 2026 10:16:39 GMT</pubDate>
            <atom:updated>2026-06-24T10:16:39.503Z</atom:updated>
            <content:encoded><![CDATA[<p>In large enterprises, data governance isn’t just about managing hierarchies or attributes, it’s about orchestrating collaboration. Every metadata update, hierarchy realignment, or data policy change starts with a request. And managing those requests effectively determines how agile and compliant your data operations truly are.</p><p>That’s where the Request Monitoring Dashboard in Oracle EDMCS plays a key role ; bringing visibility, accountability, and control to one of the most critical aspects of governance: the request lifecycle.</p><h3>From Audit to Insight — Continuing the EDMCS Dashboard Journey</h3><p>In this series, we’ve already explored how the Change Management Dashboard offers visibility into what’s changing, and how the Workflow Analysis Dashboard helps identify where delays and bottlenecks occur.</p><p>The Request Monitoring Dashboard builds on that foundation offering a process-centric view focused on who is doing what, when, and how efficiently requests progress through the governance pipeline.</p><p>Together, these dashboards complete the story connecting <em>change tracking</em>, <em>workflow performance</em>, and <em>request visibility</em> into a unified, data-driven governance ecosystem.</p><h3>What the Request Monitoring Dashboard Delivers ?</h3><p><strong>1. Real-Time Request Tracking</strong></p><p>The dashboard provides a consolidated view of all active and completed requests, displaying key details such as request name, owner, creation date, current status, and approval stage. This live snapshot enables governance teams to stay on top of request queues and identify where attention is needed.</p><p><strong>2. Status-Based Filtering and Monitoring</strong></p><p>Users can filter requests by status — <em>In Progress</em>, <em>Pending Approval</em>, <em>Rejected</em>, or <em>Completed</em> — to quickly assess workload across teams. This helps approvers prioritize tasks, while administrators can monitor overall governance throughput.</p><p><strong>3. Ownership and Accountability</strong></p><p>Each request is clearly associated with its submitter, approver, and assigned workflow. This ensures traceability and accountability, reducing the risk of requests being stalled or overlooked.</p><p><strong>4. Performance Metrics and Volume Trends</strong></p><p>The dashboard surfaces key metrics such as the number of requests submitted, average completion time, and distribution by user or application. These insights allow governance leads to identify process patterns, balance workloads, and optimize resource allocation.</p><h3>Final Thoughts</h3><p>The Request Monitoring Dashboard is more than a reporting feature — it’s a reflection of how Oracle EDMCS continues to evolve toward intelligent, insight-led governance.</p><p>By shining light on request patterns, user efficiency, and process bottlenecks, it helps organizations move beyond managing data changes to optimizing the way those changes happen.</p><p>In a world where data agility defines business agility, that visibility makes all the difference.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc0107f27f74" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>