When a user changes data in Multidomain MDM SaaS, the change might trigger an approval workflow. The workflow might consist of one or multiple approval tasks linked together.
Note: Effective in the October 2025 release, support for the classic experience of merge and unmerge tasks in the workflow inbox is deprecated. You can use the new experience to review merge and unmerge tasks in the workflow inbox. For more information about the key differences between the classic and new experiences, see Workflow inbox experiences.
The approvers of the task must review and approve the data before it becomes master data.
If your changes trigger a workflow, you can't view the approval task. Also, you can't approve your changes, even if you are assigned the approver role.
Note: Tasks created after the November 2023 release will expire after 365 days if they are inactive or unattended, and they will be deleted three days after expiration. Tasks created before the November 2023 release will not expire even if they are inactive or unattended.
Also, approvers can choose to send tasks back to a previous step in the workflow. Tasks that approvers send back move through the approval workflow again.
For example, as the second approver for an updated record, you can either send the task back to the task originator or the first approver. If you send the task back to the originator, the originator can either edit the record details and submit the record for review again or reject the changes. If the originator submits the record for review, the first approver can approve or reject the changes. If the first approver approves the changes, then the second approver can approve or reject the changes.
When you send a new or updated hierarchy task back to the originator, the originator can edit the hierarchy before sending the hierarchy for review again. But when you send new records, updated records, and deleted hierarchy tasks back to the originator, the originator cannot edit the asset before submitting the asset for review again.