# Ruleset Workflow Strategy Plugin
Available in PagerDuty Process Automation Commercial products.
The 3.4.4 release includes updates to our incubating feature for visualizing the workflow strategy.
The Ruleset Workflow Strategy allows Enterprise users to provide more complex logic around job step execution. To use the Ruleset Strategy choose Ruleset on the Workflow tab when editing a Job.
# Writing Rules
Rules define how each step should run. You can add one rule per-line. Rules are additive, and you can define multiple rules for each step. Rules are in the form:
STEP [directive] [conditions...]
This indicates which step or steps the rule applies to, and any directives or conditions for the step. The rule must have a directive or condition, or both.
Specifies the step, or steps that the rule applies to. You must include the [ and ] characters:
[X]: Applies to a single step, the named or numbered step X. You can use the step number, e.g.
or the label, e.g.
[Deploy QA](case sensitive).
[X,Y,Z...]: Applies to multiple steps. Separate multiple steps with a comma, e.g.
[1-3]: Applies to steps 1 through 3
[1-3,5-7]: Applies to steps 1 through 3 and 5 through 7
[*]: Applies to all steps
Directives optionally define when a step should start. You can define a directive rule for all steps
[*] using run-at-start or run-in-sequence.
run-at-start: Run at workflow start time. The indicated steps will start immediately when the workflow starts.
run-in-sequence: Run after the previous step in sequence is run or is skipped.
run-after:X[,Y[,Z..]]: Run after one or more steps run or are skipped.
Step Numbers and Names can be used on run-after:, but in the case that the Step Name includes spaces, this condition must be encapsulated in double quotes, e.g.
[Step Two] "run-after:Step One"
Conditions can define additional checks that must pass before a step can run, or determine when a step can be skipped. For example:
expression defines a comparison or match that will be checked. Valid expressions are:
key.name==string: a context variable such as option.myoption has a certain value
key.name!=string: not-equal check
key.name=~pattern: regular expression match
key.name!~pattern: negative regular expression match
!key.namecontext: variable is unset
key.name>=number: greater than or equal to check
key.name<=number: less than or equal to check
key.name>number: greater than check
key.name<number: less than check
Note: Curly braces are not needed to reference context variable key names. Option, Global, and Workflow Step variables are accessible by the Ruleset Strategy. Node Context variables are not available to Ruleset Conditions.
# How to archive an OR condition
To achieve an OR condition you can evaluate two times the options than should be satisfied to allow the steps to be executed, as shown on the following example code this double evaluation must be done in two separate lines.
 run-at-start  run-after:1 [3,4,5] if:option.1>0 [3,4,5] if:option.2==true
In this case steps 3,4,5 will be executed if one or both conditions are satisfied.
# How to archive an AND condition
To achieve an AND condition you can apply two or more evaluations on the same line, if all conditions are satisfied the steps will be executed.
 run-at-start  run-after:1 [3,4,5] if:option.1>0 if:option.1<100 if:option.2==true
In this case steps 3,4,5 will be executed if all the three conditions are satisfied.
Run steps 2 and 5 only after step 1 is done:
Choose between 5 and 6 based on an option value:
[*] run-in-sequence  if:option.env==QA  unless:option.env==PRODUCTION
Run step 1, then steps 2 and 3 in parallel, then step 4:
 run-after:1  run-after:1  run-after:2,3
Run steps only if two different conditions are met:
 run-in-sequence  if:option.1==yes if:option.2==yes  if:option.1==yes if:option.2==no  if:option.1==no if:option.2==yes  if:option.1==no if:option.2==no
Based on the ruleset defined above, if option 1 is "yes" and option 2 is "no" then job step 3 would run after 1. If option 1 is "no" and option 2 is "yes" then job step 4 would run after 1.