Streamlining Asset Configuration in Informatica Metadata Command Center BPMN Workflows

BPMN Based Workflow Design and Asset Creation (April 2025 Update)

Introduction:

In modern data governance and metadata management systems, establishing a robust approval workflow ensures that asset creation and modifications adhere to organizational standards and compliance protocols. With the April 2025 update of Metadata Command Center (MCC), users can now configure and deploy custom approval workflows using BPMN (Business Process Model and Notation). BPMN provides a standardized graphical representation for designing workflows, enabling collaboration among business analysts, technical users, and stakeholders. This document outlines the step-by-step process to create a single-approver workflow and associate it with asset creation and approval, ensuring control, traceability, and streamlined governance.

Workflow is a series of tasks, events and interactions where each step is reliant on the previous action. This series of tasks, events and interactions build a workflow process that define business rules and procedures. Once a workflow process has been established it will help an organisation to operate efficiently and effectively.

1. A graphical notation for specifying business processes.
2. Maintained by the Object Management Group (OMG).
3. Designed to be understood by all business stakeholders: business analysts, developers, and business users.

To create approval workflow, MCC allows new feature from April2025 update. Follow below steps.

Step 1: Open Metadata Command Center, Click on New –> Workflow –> Workflow –> Create

Step 2: Workflow name & Description

Step 3: Workflow designing pane

Once name and description given, below Workflow designing pane displayed.

There you can see Role with many partitions. Each partitions indicates different role for Human task. We may create using single role as well.

Here we going to use single partition to design workflow. For that roll over partitions you see delete button to delete that partition. Here I deleted and having only one partition to create workflow.

Step 4: Creating workflow using task, Properties and Outcomes.

Click on User Task 1, In property tab give your name (First Approver), Description, Task Priority and Due In Days.

Click User Task and click on Decision task and next click End task,

Click Outcomes tab, then enter values as below.

now click that link for which connects from Decision task to End. Now click that link for you can choose for which outcome this used for. In this case I used it for Approved. Also add another end task from decision task for Reject decision. If decision is returned means ticket must be assigned to user again. So, I’m taking flow to another swim lane like below.

No click on outcomes tab then Add those buttons. After changes we need to decide to Re-summit or Reject.

Also add Decision task and End for Editor task as shown below. And Re-summit goes to First Approver as shown below.

Now single step workflow approval is completed, just save it. Once published we are unable to edit flow changes in workflow. Make sure Due days values and Role given. Now Go to MCC –> Explore –> Workflows, Our created workflow listed there with lifecycle.

*Note: We may click on link which joins Decision task and End Task to change outcome.

Now hit Publish button to publish this workflow. Once published we can’t edit this workflow. After this MCC –> Configure –> Workflow tab, then click + button to add Event.

Name : Enter event name

Event Type : Select type of approval event like Approval Request for Create or Change

Description : Add your description here.

In Select Assets pane use (+) button to select/add asset. Business asset or technical asset both can added here. Once selected click Next button select workflow. You may select multiple assets but be aware that for all of you need to get approval as per workflow.

Click next button to Select workflow.

Select Custom workflow then select role for swim area.

Enable this event and save this and start creating asset for selected one.

Now for User Task and End we need to select Lifecycle status.

1. For First Approver Task select Lifecycle as “In Review”
2. For Editor task select Lifecycle as “Draft” (Editor lifecycle need to be change. So, we keep this as Draft)
3. End task’s Lifecycle can changed as “Discard Draft” (End task from First approver’s Reject wing and Editor’s Reject might be Discard Draft – because we don’t need that Draft)
4. End task from Aproved will be “Published” (End task lifecycle for direct case should be published)

After these changes hit Save. Now event can be created without error (if errored means check that particular task’s lifecycle)

Step 5: Creating Asset

Now Goto –> Data Governance and Catalog –> New –> Business Data –> System

Try to create System.

After Click Save button, Also add necessary stakeholders with relevant Roles.

Now can see Submit button.

Step 6: Creating ticket.

Click on Submit button, you get pop-up to create ticket

Here you may select severity, urgency and description to create ticket and assign to your approver.

After creating ticket, mail triggers to all stakeholders

Once started, ticket assigned to Approver

Step 7:

In manager login, you can open tickets using notification icon.

Click on Open ticket.

Click start button to Start this ticket.

Now hit Approve to Approve this ticket, then this Asset got published (Straight case)

Reject means Draft will be discarded. Return to Assign again to developer/editor who will be in stakeholder in Action button.

Here, I’m returning this back to the user with Governance Administrator role.

Step 8: Now this ticket reassigned to Developer/Editor again.

Asset we created also in Draft, so we can make our changes in asset and resubmit the ticket again. Here I added description in asset and re-submit it to my approver.

Now it resubmitted again to my approver.

If we click, Approve means it directly publish our asset with recent changes, as this event is Single Approver.

We have permission to Reject in editor level also, if asset changes reject means Draft changes will be discarded.

Conclusion:

By following the outlined steps, users can successfully create and configure a BPMN-based (single) approver workflow in the Metadata Command Center, link it to asset events, and implement a full approval lifecycle. This approach ensures assets undergo proper validation and review before publication, supporting data quality and governance objectives. The ability to approve, reject, return and re-submit assets based on role-based decisions adds a layer of control and accountability. Once configured and tested, this automated workflow enhances operational efficiency and enforces organizational compliance for all asset-related processes.

Please reach out to us for your Informatica solution needs. We are an Informatica Platinum Partner with extensive experience with Informatica implementations and data integration.