Create a Custom Workflow (Master Data Services)

Article
03/08/2017

Master Data Services uses business rules to create basic workflow solutions, such as to automatically update and validate data and have e-mail notifications sent, based on conditions you specify. When you require processing that is more complex than what the built-in workflow actions provide, use a custom workflow. A custom workflow is a .NET assembly that you create. When your workflow assembly is called, your code can take whatever action your situation requires. For example, if your workflow requires complex event processing, such as multi-tiered approvals or complicated decision trees, you can configure Master Data Services to start a custom workflow that analyzes the data and determines where to send it for approval.

How Custom Workflows Are Processed

There are three main components involved to process custom workflows: the Master Data Manager web application, SQL Server MDS Workflow Integration Service, and the workflow handler assembly. These components process a custom workflow as follows:

You use Master Data Manager to validate an entity that starts a workflow.
Master Data Manager sends members that meet the business rule conditions to a Service Broker queue in the Master Data Services database.
At regular intervals, SQL Server MDS Workflow Integration Service calls a stored procedure in the Master Data Services database.
When this stored procedure finds records in the Service Broker queue, it returns them to SQL Server MDS Workflow Integration Service.
SQL Server MDS Workflow Integration Services routes the data to your workflow handler assembly.

Note

Note: SQL Server MDS Workflow Integration Service is meant to trigger simple processes. If your custom code requires complex processing, complete your processing either in a separate thread or outside of the workflow process.

Configure Master Data Services for Custom Workflows

Creating a custom workflow requires writing some custom code and configuring Master Data Services to pass workflow data to your workflow handler. Follow these steps to enable custom workflow processing:

Create a .NET assembly that implements Microsoft.MasterDataServices.WorkflowTypeExtender.IWorkflowTypeExtender.
Configure SQL Server MDS Workflow Integration Service to connect to your Master Data Services database and to associate a tag with your workflow handler.
Start SQL Server MDS Workflow Integration Service.
Create a business rule in Master Data Manager that starts a workflow that is tagged with the name of your workflow handler.
Apply the business rule to a member that triggers your custom workflow.

Create the Workflow Handler Assembly

A custom workflow is a .NET class library assembly that implements the Microsoft.MasterDataServices.WorkflowTypeExtender.IWorkflowTypeExtender interface. SQL Server MDS Workflow Integration Service calls the Microsoft.MasterDataServices.WorkflowTypeExtender.IWorkflowTypeExtender.StartWorkflow* method to run your code. For example code that implements Microsoft.MasterDataServices.WorkflowTypeExtender.IWorkflowTypeExtender.StartWorkflow*, see Custom Workflow Example (Master Data Services).

Follow these steps to use Visual Studio 2010 to create an assembly that SQL Server MDS Workflow Integration Service can call to handle a custom workflow:

In Visual Studio 2010, create a new Class Library project that uses the language of your choice. To create a C# Class Library, select the Visual C#\Windows project types and select the Class Library template. Enter a name for your project, such as MDSWorkflowTest, and click OK.
Add a reference to Microsoft.MasterDataServices.WorkflowTypeExtender.dll. This assembly can be found in <Your installation folder>\Master Data Services\WebApplication\bin.
Add 'using Microsoft.MasterDataServices.Core.Workflow;' to your C# code file.
Inherit from Microsoft.MasterDataServices.WorkflowTypeExtender.IWorkflowTypeExtender in your class declaration. The class declaration should be similar to: 'public class WorkflowTester : IWorkflowTypeExtender'.
Implement the Microsoft.MasterDataServices.WorkflowTypeExtender.IWorkflowTypeExtender interface. The Microsoft.MasterDataServices.WorkflowTypeExtender.IWorkflowTypeExtender.StartWorkflow* method is called by SQL Server MDS Workflow Integration Service to start your workflow.
Copy your assembly to the location of the SQL Server MDS Workflow Integration Service executable, named Microsoft.MasterDataServices.Workflow.exe, in <Your installation folder>\Master Data Services\WebApplication\bin.

Configure SQL Server MDS Workflow Integration Service

Edit the Master Data Services configuration file to include connection information for your Master Data Services database and to associate a tag with your workflow handler assembly by following these steps:

Find Microsoft.MasterDataServices.Workflow.exe.config in <Your installation folder>\Master Data Services\WebApplication\bin.
Add the Master Data Services database connection information to the "ConnectionString" setting. If your SQL Server installation uses case-sensitive collation, the name of the database must be entered in the same case as in the database. For example, the complete setting tag might look like this:
```
<setting name="ConnectionString" serializeAs="String">  
    <value>Server=myServer;Database=myDatabase;Integrated Security=True</value>  
</setting>  
```
Below the "ConnectionString" setting add a "WorkflowTypeExtenders" setting to associate a tag name with your workflow handler assembly. For example:
```
<setting name="WorkflowTypeExtenders" serializeAs="String">  
    <value>TEST=MDSWorkflowTestLib.WorkflowTester, MDSWorkflowTestLib</value>  
</setting>  
```
The inner text of the <value> tag is in the form of <Workflow tag>=<assembly-qualified workflow type name>. <Workflow tag> is a name you use to identify the workflow handler assembly when you create a business rule in Master Data Manager. <assembly-qualified workflow type name> is the namespace-qualified name of your workflow class, followed by a comma, followed by the display name of the assembly. If your assembly is strongly named, you also have to include version information and its PublicKeyToken. You can include multiple <setting> tags if you have created multiple workflow handlers for different kinds of workflows.

Note

Depending on the configuration of your server, you may see an "Access is denied" error when you try to save the Microsoft.MasterDataServices.Workflow.exe.config file. If this occurs, temporarily disable User Account Control (UAC) on the server. To do this, open Control Panel, click System and Security. Under Action Center, click Change User Account Control Settings. In the User Account Control Settings dialog, slide the bar to the bottom so that you are never notified. Restart your computer and repeat the preceding steps to edit your configuration file. After saving the file, reset your UAC settings to the default level.

Start SQL Server MDS Workflow Integration Service

By default, SQL Server MDS Workflow Integration Service is not installed. You must install the service before it can be used. For the greatest security, create a local user for the service and grant this user only the permissions needed to perform workflow operations. To create a user, install the service, and start the service, follow these steps:

Use the Local Users and Groups manager to create a local user named, for example, mds_workflow_service.
Use SQL Server Management Studio to grant the mds_workflow_service user permission to execute the [mdm].[udpExternalActionsGet] stored procedure. To do this, create a new login for the mds_workflow_service account, create a new user in the Master Data Services database, map this user to the mds_workflow_service login, and grant the user EXECUTE permission to the [mdm].[udpExternalActionsGet] stored procedure.
Grant the mds_workflow_service user permission to execute the workflow handler assembly. To do this, add the mds_workflow_service user to the Security tab of the Properties of the workflow handler assembly and grant the mds_workflow_service user READ and EXECUTE permission.
Grant the mds_workflow_service user permission to execute the SQL Server MDS Workflow Integration Service executable. To do this, add the mds_workflow_service user to the Security tab of the Properties of Microsoft.MasterDataServices.Workflow.exe, in <Your installation folder>\Master Data Services\WebApplication\bin and grant the mds_workflow_service user READ and EXECUTE permission.
Install SQL Server MDS Workflow Integration Service by using the .NET installation utility, named InstallUtil.exe. InstallUtil.exe can be found in the .NET installation folder, such as C:\Windows\Microsoft.NET\Framework\v4.0.30319\. Install SQL Server MDS Workflow Integration Service by entering the following in an elevated command prompt:
```
C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil Microsoft.MasterDataServices.Workflow.exe  
```
Specify the mds_workflow_service user when prompted during installation.
Start SQL Server MDS Workflow Integration Service by using the Services snap-in. To do this, find SQL Server MDS Workflow Integration Service in the Services snap-in, select it, and click the Start link.

Create a Workflow Business Rule

Use Master Data Manager to create and publish a business rule that will start the workflow when applied. You should ensure that your business rule contains actions that change attribute values, so that the rule evaluates to false after it has been applied once. For example, your business rule might evaluate to true when a Price attribute value is greater than 500 and the Approved attribute value is blank. The rule can then include two actions: one to set the Approved attribute value to Pending and one to start the workflow. Alternatively, you may want to create a rule that uses the "has changed" condition and add your attributes to change tracking groups. For more information about business rules, see Business Rules (Master Data Services).

Create a business rule that starts a custom workflow in Master Data Manager by following these steps:

In the business rule editor of Master Data Manager, after you have specified the conditions of your business rule, drag the Start Workflow action from the External actions list to the THEN pane's Action label.
In the Edit Action pane, in the Workflow type box, type the tag that identifies your workflow handler assembly. This is the tag you specified in the configuration file for your assembly, for example, TEST.
Optionally, select the Include member data check box. Choose this to include attribute names and values in the XML that is passed to the workflow handler.
In the Workflow site box, type the name of a website. For your custom workflow this may not apply, but can be used for added context.
In the Workflow name box, type the name of your workflow from Visual Studio. For your custom workflow this may not apply, but can be used for added context.
Save and publish the business rule.

Apply Business Rules to Start a Workflow

Apply the business rule to your data to start the workflow. To do this, use Master Data Manager to edit the entity that contains the members you want to validate. Click Apply business rules. In response to the business rule, Master Data Manager populates the Service Broker queue of the Master Data Services database. When SQL Server MDS Workflow Integration Service checks the queue, it sends the data to the specified workflow handler assembly and clears the queue. The workflow handler assembly performs whatever actions you have coded into it.

Troubleshoot Custom Workflows

If your workflow handler assembly doesn't receive data, you can try debugging SQL Server MDS Workflow Integration Service or viewing the Service Broker queue.

Debug SQL Server MDS Workflow Integration Service

To debug SQL Server Workflow Integration Service, take the following steps:

Use the Services snap-in to stop the service.
Open a command prompt, navigate to the location of the service, and run the service in console mode by entering: Microsoft.MasterDataServices.Workflow.exe -console.
In Master Data Manager, update your member and apply business rules again. Detailed logs are displayed in the console window.

View the Service Broker Queue

The Service Broker queue that contains the master data passed as part of the workflow is: mdm.microsoft/mdm/queue/externalaction. Queues can be found in the Object Explorer of SQL Management Studio under the Service Broker node of the Master Data Services database. Be aware that, if the service cleared the queue properly, this queue will be empty.

Share via