For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Open sourceSupportFAQsDocs Home
DocumentationAPI referenceRelease notes
DocumentationAPI referenceRelease notes
  • Release notes
    • Overview
    • Changelog
      • Overview
      • Adapter Email replaced
      • AngularJS libraries removed
      • Ansible Playbook task response fixed
      • Automation Catalog deprecated and removed
      • Customizable UI not allowed in Platform 6
      • Decision task replaced by Evaluation task
      • Default adapter protocol
      • Delete Variables API removed
      • Dot notation not allowed in job variable names
      • ENC encryption deprecated
      • Form Builder removed
      • Get Server Health API changed
      • Itential Tools updated
      • OperationId tasks removed in Platform 6
      • Operational Data tab removed in Config Manager
      • Pre-Builts deprecation
      • Profiles deprecation
      • pushToArray requires preexisting arrays
      • Reduced integration responses
      • Remove default self-signed TLS certificates from container image
      • Retrieve references endpoint replaced
      • Server name property replaced
      • Service Catalog and Service Catalog Builder removed
      • Verify Config task removed
LogoLogo
Open sourceSupportFAQsDocs Home
On this page
  • What should I do?
  • Use the Evaluation task
Release notesBreaking changes

Decision task replaced by Evaluation task

Was this page helpful?
Previous

Default adapter protocol changing to https

Next
Built with

The decision task is no longer supported in the workflow canvas in Platform 6. Replace it with the Evaluation task.

What should I do?

Since the decision task acts as an evaluator, use the Evaluation task to define a set of conditionals and execute a success or failure transition in the workflow.

The decision task took in a value and matched it to conditionals to determine which task to transition to. In the example below, a decision task takes in a color (string) and matches it to either red, green, or blue to determine which stub task to transition to. Conditionals were evaluated serially, so the first task with all conditions met was selected. If no conditions were met, a default transition was used.

Decision task on the GEN 2 canvas (deprecated)
Conditional expressions on the decision task

Use the Evaluation task

To achieve the same branching effect, replace decision with a set of Evaluation tasks. For each Evaluation task, place the same condition that was used in the decision task along with a success transition (green) to the target task. A failure transition (purple) moves to the next Evaluation task. A final failure transition from the last Evaluation task creates a default transition to the end of the workflow.

Evaluation task set on the GEN 2 canvas (replacement)

The input sources (operands) for the Evaluation task use the same evaluation criteria as the corresponding condition in the decision task — for example, “Does the color job variable equal the static value red?”

Evaluation task operand data

Data for conditional expressions can come from input job variables, previous task outputs, or static values. A conditional operator is selected along with the data to compare it against. The following conditional operators are available in the Evaluation task:

  • “contains”
  • “does not contain”
  • “equals”
  • “does not equal”
  • “greater than”
  • “greater than or equal”
  • “less than”
  • “less than or equal”