One of the strengths of Oracle Enterprise Data Management (EDM) is its governance framework. Organizations can design approval workflows that ensure changes are reviewed, validated, and approved before they are committed to downstream systems. As EDM adoption matures, however, governance workflows often become significantly more sophisticated than the simple submit-review-approve model many organizations start with.
This raises an important question:
What happens when an approver finds an issue that should be corrected by a previous governance stage, but not by the original submitter?
Today, Oracle EDM provides a Push Back action that returns a request directly to the submitter. While this works well for straightforward workflows, it creates inefficiencies in larger enterprise governance processes.
The Challenge with Complex Governance Workflows
Consider a workflow that includes multiple approval layers:
Data Steward Review
Domain Owner Approval
Regional Approval
Global Governance Approval
Executive Approval
At first glance, this seems like a typical enterprise governance model. However, real-world reviews are rarely linear.
Imagine an Executive Approver identifies a concern with the business justification provided during Global Governance Approval. The issue does not require the request to return to the submitter. It simply requires clarification or adjustment from the Global Governance team.
Unfortunately, EDM's current workflow model offers only one push-back destination: the original submitter.
As a result:
The request must restart unnecessarily.
Previously completed approvals are repeated.
Governance teams spend time re-approving work they already reviewed.
Cycle times increase.
Users become frustrated with redundant approval activity.
In highly regulated environments, these inefficiencies compound quickly as request volumes grow.
A Better Approach
Oracle EDM would benefit from the ability to push a workflow back to a specific prior approval stage or policy.
Instead of returning every rejected request to the submitter, EDM could allow approvers to select from previously completed workflow stages.
For example:
Executive Approval → Global Governance Approval
Global Governance Approval → Domain Owner Approval
Regional Approval → Data Steward Review
The workflow would resume from the selected stage while preserving completed workflow history and maintaining a full audit trail.
Why This Matters
This enhancement would provide several significant benefits:
Reduced Rework
Organizations would avoid repeating approvals that remain valid and unaffected by the requested change.
Faster Governance Cycles
Requests would move directly to the team best positioned to resolve the issue, reducing overall processing time.
Better User Experience
Approvers could collaborate more effectively without forcing unnecessary workflow restarts.
Support for Enterprise Governance Models
Many organizations operate complex governance frameworks with multiple serial and parallel approval policies. EDM should provide workflow controls that align with these realities.
Preserved Auditability
Every push-back action could be fully logged, including:
User initiating the push back
Destination stage
Timestamp
Required comments or justification
This maintains EDM's strong governance and compliance posture while increasing flexibility.
Configuration Options Oracle Could Consider
To support different governance requirements, Oracle could make the capability configurable.
Possible options include:
Allow push back to any prior completed stage
Allow push back only to the immediately preceding stage
Define approved push-back destinations by workflow stage
Require comments when pushing back
Include push-back activity in workflow reporting and analytics
This would give organizations the flexibility to balance efficiency with control.
Alignment with Modern Workflow Platforms
Targeted push-back capabilities are common in enterprise BPM and workflow management solutions. Users expect workflows to move to the appropriate point of correction rather than restarting entirely.
As Oracle continues to enhance EDM governance capabilities, this feature would represent a natural evolution of the platform's workflow engine.
The goal is not to weaken controls. The goal is to make governance smarter.
When an issue is identified, organizations should be able to route the request back to the team responsible for resolving it—not automatically back to the beginning of the process.
For enterprises managing thousands of governed changes each year, that distinction can significantly improve governance efficiency, user adoption, and overall workflow effectiveness.
As an Oracle ACE working with EDM implementations across complex governance environments, this is one enhancement that would deliver immediate value while preserving the auditability and control that make Oracle EDM such a powerful governance platform.
No comments:
Post a Comment