locked
SQL Server MDS Workflow Integration"-service cannot handle more than one "custom workflow". Only the last one from the Config-file is loaded RRS feed

  • Question

  • MDS og Custom Workflow

    "SQL Server MDS Workflow Integration"-service cannot handle  more than one "custom workflow". Only the last one  from the Config-file is loaded.

    The Config-file of MDS-workflow service with 3 workflows is shown below:

        <applicationSettings>

         <Microsoft.MasterDataServices.Workflow.Properties.Settings>

            <setting name="ConnectionString" serializeAs="String">

              <value>Server=.;Database=MDS;Integrated Security=true</value>

            </setting>

            <setting name="WorkflowTypeExtenders" serializeAs="String">

              <value>EMAIL=EmailWorkFlow.EmailOnDataChange,EmailWorkFlow

               </value>

            </setting>

            <setting name="WorkflowTypeExtenders" serializeAs="String">

              <value>A=TableWorkflow.WriteTableOnDataChange,TableWorkflow

               </value>

            </setting>

            <setting name="WorkflowTypeExtenders" serializeAs="String">

    <value>VARSEL=NotifyWorkflow.SendNotificationToBoss,

                                                                         NotifyWorkflow</value>

            </setting>

          </Microsoft.MasterDataServices.Workflow.Properties.Settings>

        </applicationSettings>

     

    We get the following when we apply “Business rules” that trigger some of the workflows. That is, only the workflow tagged as "VARSEL", which is the last one, is loaded and can be run but the two other workflows, tagged as "EMAIL" and "A" are not loaded. As a result, the workflow with tag “A” cannot be run.

     

    If we remove the last "setting"-element from the Config-file, then tag “A” becomes the last workflow-tag as shown below.

    <applicationSettings>

        <Microsoft.MasterDataServices.Workflow.Properties.Settings>

            <setting name="ConnectionString" serializeAs="String">

              <value>Server=.;Database=MDS;Integrated Security=true</value>

            </setting>

            <setting name="WorkflowTypeExtenders" serializeAs="String">

              <value>EMAIL=EmailWorkFlow.EmailOnDataChange,EmailWorkFlow

               </value>

            </setting>

             <setting name="WorkflowTypeExtenders" serializeAs="String">

               <value>A=TableWorkflow.WriteTableOnDataChange,TableWorkflow

                </value>

             </setting>

        </Microsoft.MasterDataServices.Workflow.Properties.Settings>

    </applicationSettings>

    When applying the “Business rules” that triggers the workflow corresponding to tag “A”, we see that the workflow with tag “A” is loaded and run (shown below)

    Thursday, March 22, 2018 1:56 PM