Master data services not calling custom assembly from the workflow

Question

I am working with MDS2008R2.

I have created a custom workflow (c# assembly) to validate members of a specific entity.

The MDS does not call the assembly from the workflow. Please find below the steps done

Step 1: Loaded the assembly in the application bin of MDS with the correct config details.

Step 2: Checked the assembly from the console. (loaded workflowtype extender for : MDSWFS)

Step 3: Marked the Consolidated attribute to Enable Change tracking

Step 4: Creation of Business Rule (Key greater than or equal to blank)

Step 5: Activate the new rule

Step 6: Test the new dll by executing the rule

The assembly is not called and I do not find any values in the service broker queue.

Answer 1

Hi Chandan,

In step 4, did you also create an action to call the workflow type? Also, did you install the SQL MDS Workflow Integration Service?

---

http://www.henryong.com

Answer 2

Hi Henry,

In Step 4, I have created the an action to start the WorkFlow type. Please find attached screenshot.

Thanks 

Chandan

Answer 3

Are you looking to initiate a SharePoint workflow or non-SharePoint workflow?

---

http://www.henryong.com

Answer 4

Hello Chandan,

Let me try to understand where the issue is happening.

a. If this is a SharePoint workflow, the first thing I need you to do is to go to SharePoint and try to start the workflow manually (no MDS integration at this point). This will ensure that the workflow was successfully created and deployed.

b. After coping the extender assembly to the bin folder and changing the configuration file (Step 1), run the command “Microsoft.MasterDataServices.Workflow.exe -console” (Step 2). I know you said that this works. Can you share the output of the command? Do not close the console for now.

c. After creating and activation the business rule (Step 4), execute an action that would trigger the workflow. Do you see any output in the console? Can you share the data?

The next steps will troubleshoot the service broker queue. But let’s confirm that these initial steps are working first.

---

Mario Zimmermann (Microsoft)

Answer 5

Hi Mario,

Please find below my answers.

a. I am not using a SharePoint Workflow.

b. Please find below the console output of the external assembly.

C. After creating and activation the business rule (Step 4), execute an action that would trigger the workflow there is no changes in the output.

Let me know if you need any more details.

Thanks for replying.

Chandan

Answer 6

Thanks for the information, Chandan.

Given that the console window does not show output (at least "Dispatching using extender:" should be displayed), it probably means that the business rule is not triggering the workflow at all. I noticed you are using "is greater than or equal to BLANK". I don't know if this makes a lot of sense (perhaps this should not even be available as an option). I tried this option on my box and the workflow was not triggered as well. Can you try a couple of things to replace this rule?

- If you are trying to start the workflow when the value is not blank, can you try using "is not equal to BLANK"?

- if you want to start the workflow on both cases (is greater or equal to), can try to select "Attribute Value" instead of BLANK as the value? Is it ok to leave the attribute value field empty. In the end, you should see "SurrogateKey is greater than or equal to " instead of "SurrogateKey is greater than or equal to blank".

---

Mario Zimmermann (Microsoft)

Answer 7

Thanks for the reply, Mario

I have tried the workflow with different combination of the business rule. But it does not show up in the console window.

Thanks

Chandan Bhure

Answer 8

Hi Mario,

I think we need to troubleshoot the service broker queue. Please let me know your thoughts on this.

Thanks

Chandan Bhure

Answer 9

Hi Chandan,

This can be a service broker issue (maybe permissions on the db). Can we try to run one more test? I want to make sure we are not troubleshooting something that is already working.

Preparation steps:

1. Stop the "SQL Server MDS Workflow Integration" service.

2. Ensure that the workflow console is NOT running.

Execution steps:

1. Create a new business rule.

2. Add no conditions in the IF clause.

3. In the THEN clause, add "Name defaults to test" (or something silly like this)

4. In the THEN clause, also add "start Workflow MDSWFS"

5. Apply the business rule.

6. Add a new member to the entity.

Verification steps:

1. Ensure that the value for the "Name" attribute was modified to "test" (this ensures the business rule was executed).

2. Open SQL Management Studio and query the "microsoft/mdm/queue/externalaction" service broker queue (since the service is not running, you should see at least one entry in the queue).

3. Start the workflow console (you should see something like "Dispatching using extender: MDSWFS")

4. Query the service broker queue again (the queue should be empty now)

Please, let me know the results for the verification steps.

---

Mario Zimmermann (Microsoft)