> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-platform/2023-2/release-notes/deprecations/decision-task-replaced-gen-2-workflows/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Decision task replaced in GEN 2 workflows

> Deprecation notice that the decision task is deprecated in 2023.2 and must be replaced with the Evaluation task in GEN 2 workflows.

The `decision` task is deprecated and no longer supported in the GEN 2 workflow canvas in the 2023.2 Platform release. Replace it with the `Evaluation` task.

| Task name  | Description                                                                         | Deprecation release | Scheduled removal release | Replacement                                                             |
| ---------- | ----------------------------------------------------------------------------------- | ------------------- | ------------------------- | ----------------------------------------------------------------------- |
| `decision` | Used to create branches within a workflow to validate if specified variables exist. | 2023.2              | Platform 6                | [Evaluation task](/itential-platform/studio/tasks/reference/evaluation) |

### What should I do?

Use the `Evaluation` task instead. The `Evaluation` task allows you 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. The example below shows a `decision` task that 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.

![](/_fern-img/2f96eb5d0574b1c33724c62ed54dd3d8233fdbe8f232a8b5e465af956f6812f0.webp)![](/_fern-img/5c8cb2fa9acedaf4ee81af9f06a458ce88ba2019bdc5d976156bee90099fabd9.webp)

## Use the Evaluation task (GEN 2)

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.

![](/_fern-files/itential.docs.buildwithfern.com/8e4d70a1c74b1f6f760e3557ee6038664ddf9d28c573692fd5bef2411547491c/docs/assets/images/platform/03_evaluation_task_set.png)

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`?"

![](/_fern-img/77122c22acd45ebef5d3d654a3a617cb4a27eb5379cf8df22644e66e983588fe.webp)

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"

> Deprecation notice that the decision task is deprecated in 2023.2 and must be replaced with the Evaluation task in GEN 2 workflows.