To ensure that relevant stakeholders review and approve data before it becomes master data, define business events with native workflows that you configure in Business 360 Console. To share business events with external targets after you define the business events, configure publishing events.
You can define business events for user-triggered actions, such as changes that users make to records, relationships, or hierarchies through business applications, ingress, and REST API. You can also define business events for actions that MDM SaaS performs, such as identifying potential matches that require manual review.
The review tasks that the events create require human intervention. Stakeholders provide input for review tasks in the workflow. A workflow ensures that the right people can provide input, challenge, and approve actions on business events. A business process is considered complete only when the assigned users complete the review tasks by taking appropriate actions.
When you define an event for an asset, you can configure event conditions to trigger any published workflow that you select. When you configure business events for create and update actions on record data, you can choose to skip workflows for data that rule associations have successfully validated or enriched. If the data validation or enrichment fails, MDM SaaS routes the changes to the workflow.
Tasks created for native workflows expire after 90 days if they are inactive or unattended and the respective workflows are aborted. If you want to extend the duration, contact Global Customer Support. However, if you don't complete tasks or extend their expiration and the task inbox becomes full, then new tasks aren't created.
When multiple business events are configured for the same triggering actions and event sources, MDM SaaS uses the most recently updated business event. To manage which business event is used, enable or disable business events as needed.
Configure business events for create and update actions on record data to skip workflows when rule associations successfully validate or enrich the record data.
You can configure workflow skip check in one or both of the following ways:
•Reuse the configuration from the workflow. Use rule associations from the evaluation criteria configured for Read Rule Association Status service tasks. You can also specify which objective groups and objectives to use.
•Add custom configuration. Add the objective groups that you want to use. You can also specify whether to use all or some of the objectives in the objective group.
If all the rule associations succeed, the workflow is skipped. If the changes meet the event conditions for other business events, the respective workflows might be triggered. If any rule association fails to validate or enrich data, the changes are routed to the configured workflow.
Create a business event
You can create business events for actions that users perform, such as creating, updating, and unmerging records, or creating and updating relationships. You can also create events for the actions that MDM SaaS performs, such as identifying potential matches for manual review.
For example, you might want to trigger a workflow when users create or update a business entity record or hierarchy. You can also trigger a workflow for changes related to specific fields, field groups, and attributes. You can create rules for the selected fields and field groups or attributes so that the workflow is triggered only when the field, field group, or attribute meets the specified criteria.
For create and update actions on record data, configure business events to skip workflows when rule associations successfully validate or enrich the data.
5Click the asset picker icon, select an asset to trigger a workflow, and click OK.
If you select a business entity, you can add actions taken on record data and relationships as event conditions. If you select a hierarchy, you can add actions taken on the hierarchy as event conditions.
6In the Event Details section, select the status of the business event.
To use the business event when the event conditions are met, set it to the enabled status. To use the event in future, disable it.
You can enable an event on the Business Events page or on the Events tab of the selected business entity.
7In the Event Conditions section, specify when to trigger a workflow.
Options
Description
Required
Sends the updates to reviewers for approval. When users click Send for Approval, MDM SaaS creates a review task.
You can trigger a workflow when users edit specific fields of a record or attributes of a relationship. If you don't specify any fields or attributes to trigger workflows, all changes require approval.
If you specify any fields or attributes, the workflow is triggered only when users make changes to those fields or attributes. Users can save changes to other fields or attributes without approval.
Optional
Allows users to save their changes without approval or send their changes to reviewers for approval. When users click Submit, users can save their changes without approval. When users click Send for Approval, MDM SaaS creates a review task.
Note:
When workflow trigger is optional and users delete a record, users see the Delete and Send for approval buttons.
Note:
You can't configure optional workflow trigger option for the Resolve Potential Matches triggering action for record data. For match pairs, stakeholder review is mandatory.
8Click Add an event condition for an asset.
9Configure event conditions for the selected asset.
- Add actions taken on record data, relationships, or both record data and relationships as event conditions when you select a business entity as the asset.
10Optionally, to skip workflows when rule associations successfully validate or enrich record data, perform the following steps to configure workflow skip check:
aTo use the configuration from the Read Rule Association Status service tasks in the workflow, select the option in the Workflow Skip Check section.
bTo add custom configuration, click Add objective group and select the relevant objective groups.
cOptionally, specify which objectives from the objective group to include.
dSpecify whether to consider rule associations without statuses as successful or failed.
eSpecify the severity levels of the rule associations to be considered for workflow skip check.
fSpecify whether to consider rule associations with exception status as failed.
11Click Next.
The Workflow page appears.
12Click the asset picker icon, and select a workflow.
13Perform one of the following steps based on the business event configuration:
- Click Next if you configured workflow skip check using the configuration from Read Rule Associations service tasks.
- Click Save if you didn't configure workflow skip check or added only custom configuration for workflow skip check.
If you configured workflow skip check using Read Rule Association Status service tasks, configuration details appear on a new page.
If you didn't configure workflow skip check, the new business event is saved.
14Review the configuration details for workflow skip check.
15Optionally, click Edit to select which objective groups and objectives from Read Rule Association Status service tasks to include, then click Save.
Configuring an event condition for a record
When you configure a business event for a business entity, you can specify event conditions based on actions taken on record data, relationships, or both. You can also specify the event sources, such as business applications, REST APIs, and ingress jobs, through which these actions are performed.
1In the Record Data section on the Event page, select the triggering actions and event sources.
The following table describes the user and system actions on record data that can trigger workflows:
Triggering Action
Event Sources
Description
Create
Business Applications
REST API
Ingress
When users create records, the event triggers a workflow. By default, the event applies to all fields, but you can configure it to trigger the workflow only when users enter values in specific fields or field groups.
Update
Business Applications
REST API
Ingress
When users update records, the event triggers a workflow. By default, the event applies to all fields, but you can configure it to trigger the workflow only when users enter values in specific fields or field groups.
Delete
Business Applications
REST API
When users delete records, the event triggers a workflow.
Unmerge
Business Applications
REST API
When users unmerge source records from master records, the event triggers a workflow.
Manual Merge
Business Applications
REST API
When users merge two records, the event triggers a workflow.
Resolve Potential Matches
Match Pairs
When MDM SaaS identifies potential matches for manual review, the event triggers a workflow.
2If you select business applications or REST API as an source, select the affected user roles.
3If you selected the Create action, Update action, or both the actions, click Customize in the Fields column.
The option to configure specific fields for which you want to trigger a workflow is also available if you selected the Delete action along with the Create or Update action.
4 To add specific fields for which you want to trigger a workflow, perform the following tasks:
aSelect the fields and dynamic field values to trigger a workflow for the selected actions, and click Next.
You can't select dynamic field definitions or fields from field groups nested within other field groups.
Note:
If you add multiple fields, the workflow is triggered when users modify any of those fields.
bIn the Select Dynamic Fields dialog box, select the dynamic fields that you want.
cTo trigger a workflow only when the value of a selected field meets a specific criteria, click Add a rule.
dFrom the list of fields, select the field for which you want to create the rule.
eFrom the Operator list, select an operator for the rule.
fEnter a value to complete the rule.
Values aren't case-sensitive.
A green checkmark appears next to the selected field when the rule is complete and valid.
gOptionally, add additional rules.
Note:
If you add multiple rules for a field, a workflow is triggered when the conditions of all the rules are met. For example, you set two rules for the Tax field, such as Country equals USA and State equals California. When the Tax field value changes and both conditions match, the event triggers a workflow.
hTo add the fields and apply the rules, click Finish.
Note:
When you configure rules for fields that are enriched with data from Dun & Bradstreet, MedPro, and Global Legal Entity Identifier Foundation (GLEIF) through extensions, MDM SaaS business applications don't trigger workflows for these fields.
5If you selected ingress as an event source, select the source systems and taskflows used for ingress.
If you don't select any source systems or taskflows, all ingress jobs trigger workflows. Select specific source systems or taskflows to trigger the workflow only for those source systems or taskflows.
6Optionally, add more conditions.
If you select the merge, unmerge, or delete triggering actions for record data, you can't add additional conditions.
Configuring an event condition for a relationship
When you configure a business event for a business entity, you can specify event conditions based on actions taken on record data, relationships, or both. You can also specify the event sources, such as business applications, REST APIs, and ingress jobs, through which these actions are performed.
1In the Relationships section on the Event page, select the triggering actions and event sources.
The following table describes the user actions on relationships that can trigger workflows:
Triggering Action
Event Sources
Description
Create relationship
Business Applications
REST API
Ingress
When users create non-hierarchical relationships between records, the event triggers a workflow. By default, the event applies to all attributes, but you can configure it to trigger the workflow only when users enter values in specific attributes.
Update relationship
Business Applications
REST API
Ingress
When users update non-hierarchical relationships between records, the event triggers a workflow. By default, the event applies to all attributes, but you can configure it to trigger the workflow only when users enter values in specific attributes.
Delete relationship
Business Applications
REST API
When users delete non-hierarchical relationships between records, the event triggers a workflow.
2Select all relationships or a specific relationship type.
The list of relationships appear based on the selected business entity.
3If you select business applications or REST API as an source, select the affected user roles.
4If you selected the Create relationship action, the Update relationship action, or both for only a specific relationship type, click Customize in the Attributes column.
The option to configure specific fields for which you want to trigger a workflow is also available if you selected the Delete relationship action along with at least one of the other actions.
5To add specific attributes for which you want to trigger a workflow, perform the following tasks:
aSelect the attributes to trigger a workflow for the selected actions, and click Next.
Note:
If you add multiple attributes, the workflow is triggered when users modify any of those attributes.
bTo trigger a workflow only when the value of a selected attribute meets a specific criteria, click Add a rule.
cFrom the list of attributes, select the attribute for which you want to create the rule.
dFrom the Operator list, select an operator for the rule.
eEnter a value to complete the rule.
Values aren't case-sensitive.
A green checkmark appears next to the selected attribute when the rule is complete and valid.
fOptionally, add additional rules.
Note:
If you add multiple rules for an attribute, a workflow is triggered when the conditions of all the rules are met.
gTo add the attributes and apply the rules, click Finish.
6If you selected ingress as an event source, select the source systems and taskflows used for ingress.
If you don't select any source systems or taskflows, all ingress jobs trigger workflows. Select specific source systems or taskflows to trigger the workflow only for those source systems or taskflows.
7Optionally, add more conditions.
Configuring an event condition for a hierarchy
When you configure a business event for a hierarchy, you can specify event conditions based on actions taken on the hierarchy. You can also specify the event sources, such as business applications, REST APIs, and ingress jobs, through which these actions are performed.
1In the section for hierarchies on the Event page, select the triggering actions and event sources.
The following table describes the user actions on hierarchies that can trigger workflows:
Triggering Action
Event Sources
Description
Create association
Business Applications
REST API
Ingress
When users create hierarchies, the event triggers a workflow.
Update association
Business Applications
REST API
Ingress
When users update hierarchical relationships between records, the event triggers a workflow.
Delete association
Business Applications
REST API
When users delete hierarchical relationships between records, the event triggers a workflow.
2If you select business applications or REST API as an source, select the affected user roles.
3If you selected ingress as an event source, select the taskflows used for ingress.
If you don't select any source systems, all ingress jobs trigger workflows. Select specific source systems to trigger the workflow only for those source systems.
4Optionally, add more conditions.
Viewing and editing business events
You can view all the business events for your organization and their details on the Business Events page.
You can filter the events by name, type, affected business entity and roles, and workflow. You can also sort the events by name, event type, workflow, and when they were updated.
To edit an event, navigate to the event from the list. You can edit the properties and details of the events, such as the name, affected user roles, and event conditions. You can also update the workflow that the business event uses.
Enabling and disabling business events based on native workflows
When multiple business events have the same triggering actions and sources, MDM SaaS uses the most recently updated business event. To manage which business event is used, enable or disable business events. To control which business event MDM SaaS uses, you can enable or disable business events.
Business events are enabled by default. However, you can disable business events when you create them.
You can disable business events in the following cases:
•You have multiple business events for the same triggering actions and event sources, and want to prioritize a specific one. In this case, disable the other business events, especially those that are more recently created or updated than the business event you want to keep.
•You configure a new business event but want to use it later.
To enable or disable an existing business event, select the appropriate option on the Events tab of the business entity or on the Business Events page.
When you enable a disabled business event, MDM SaaS uses it only if it's the most recently updated business event applicable for the changes.