---
schema_version: "1"
id: e852544a0cb0434e7803b2bc92f0807ec49f4c2a88cc1d8846bec93aee890f97
title: Orchestration Item Conditions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_orchestration_item_conditions_231876.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_orchestration_item_conditions_231876.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: dac665ed6141c74a577566e97780e5390b9c6d7bac1ff68d56dd6c8ce5cb6d43
description: As part of an orchestration item definition, you can specify conditions that control whether the item should execute if the condition is met, or skipped if the condition is not met.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Orchestration Item Conditions

As part of an orchestration item definition, you can specify conditions that control whether the item should execute if the condition is met, or skipped if the condition is not met.

In addition, for Push events, you can specify an event condition that defines when a push event is triggered.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/images/icon_note.png)

Note

When an orchestration item is defined with certain conditions, then those conditions apply to every associated order item, rather than just one. If any associated order item meets the condition, then that condition is met.

A push event is activated when an external system or a Salesforce user makes a specific change to the order item associated with a push event orchestration item. When a change of state happens, a trigger is invoked and the change is evaluated against an event condition associated with the orchestration item.

For Push Events, you can do the following things:

1. Define conditions for the Push event item-type.
2. Define conditions for an orchestration item. Condition data is case-sensitive.

A condition for an attribute that is unavailable on the line item evaluates as True instead of False. The reason is that if the attribute exists and the value is null, the condition may still evaluate to True. If the attribute itself is missing, then the condition evaluates to False.

You can choose **Single Condition** for simple situations, but conditions can also be nested so that they allow complex boolean structures, such as AND, OR, and NOT. Choose the attribute and value and then save the conditions.

![Orchestration Item Conditions example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/order_management/images/om_conditions.png)

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/images/icon_note.png)

Note

If you don't see the option to add an AND, OR, or NOT condition as a nested condition, then you should add the following new custom setting to XOM settings: `Feature.EnableComplexConditions` See [Enable Complex Conditions in Custom Settings](https://help.salesforce.com/s/articleView?id=ind.comms_t_enable_complex_conditions_in_custom_settings_240121.htm&release=264.0.0&type=5 "From Spring '21 and later, complex conditions are enabled by default, so you don't need to create the custom setting described in this topic. For earlier releases than Spring '21, you must create the custom setting.")