Task_SLA workflows transferred into an Update Set with the condition match "Run the Workflow" can cause duplicate workflows if user changes condition from "Run the Workflow" to "None."

Within our instances, a business rule named SLA Workflow Condition Check runs on the Workflow Version [wf_workflow_version] table. The business rule then makes a call to the SLAvalidation script-include, which validates whether the workflow version has a condition type set. If the condition match on a workflow to run on the table is changed from "Run the Workflow" to "None," two different workflows are published.

Steps to Reproduce

  1. Create a workflow to run on the Task_SLA table with the condition match is set to Run The Workflow.

    For more information, see the product documentation topic Workflow Editor.

  2. Transfer the workflow to an update set.

  3. Acknowledge that two workflow_contexts are associated to one Task_SLA record, due to the Task_SLA workflow being specified within Service Level Management > SLA > SLA Definitions.

  4. Check out the workflow, make the change to the condition match from Run The Workflow to None, and publish it.

    Two different workflow versions are published.

    --------WORKFLOW 1----------------------------------------

    Workflow Name: [insert workflow name here]
    Table: Task SLA [task_sla]
    If Condition Matches: --None--

    --------WORKFLOW 2----------------------------------------

    Workflow Name: [insert workflow name here]
    Table: Task SLA [task_sla]
    If Condition Matches: Run the Workflow


If you are updating a workflow related to the Task SLA table, always set If condition matches to None.

Related Problem: PRB602017

Seen In

Calgary Patch 2 Hot Fix 5
Dublin Patch 3 Hot Fix 1
Eureka Patch 5 Hot Fix 1
Fuji Patch 7 Hot Fix 5

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-07-03 06:40:27