Conditional control
Conditional control allows us to build alternative flow paths through which the task will flow depending on the fulfillment or non-fulfillment of specific criteria. Thus, we can say that conditional processes contain decision logic, based on which the process behaves in a certain way.
If we use the vacation requests as an example, using conditional control, on the form we can place a field (in Dew-X a plugin) with a selection list containing three answers: holiday leave, unpaid leave, special leave.
Depending on the decision made by the requestor, the process will flow either to the supervisor to the acceptance step with the option to reject/revoke or directly to HR with the option to verify and reject, and only then, informatively to the supervisor. Similarly, the selection of “requires replacement” can force a course that takes into account finding a replacement person, before forwarding to acceptance.
Conditional operators can be many. In Dew-X we used: “=” equal and “!=” different, which are useful for both text and numbers, and best suited for numbers: “>” greater, “>=” greater-equal, “<” less, “<=” less-equal. The criteria can also be other, such as the passage of time.
This makes it possible to build a definition, such as this one:
Conditional process control is only available in the PRO business.
What are the differences between the PRO business versions:
