---
schema_version: "1"
id: 472f556dc58dcaca97ff571d643c3379baa053ac9d2d8669c95aaac57c0ebfdb
title: Loyalty Program Process Rule Conditions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/promotion_setup_rule_conditions.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.promotion_setup_rule_conditions.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 87d474c5c6f648655b35d5757d20907be30127dc5f324c2d7bf6c3c51815341a
description: A condition determines whether a transaction journal is eligible for an action. You can also create a condition group and define a set of conditions together. A condition can have a child action or a child condition.
products:
  - Loyalty Management
release: "264"
---
# Loyalty Program Process Rule Conditions

A condition determines whether a transaction journal is eligible for an action. You can also create a condition group and define a set of conditions together. A condition can have a child action or a child condition.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>,&nbsp;<strong>Performance</strong>, <strong>Unlimited</strong>, and&nbsp;<strong>Developer</strong>&nbsp;Editions with Loyalty Management</td></tr></tbody></table>

## Conditions

You can associate a condition with a child step or a child condition. When a transaction journal meets the filter criteria of a condition, either the child condition evaluates the transaction journal or the child action is triggered for the transaction journal.

For each condition, ensure that you specify a name and select one of these filter criteria.

- All conditions are met (AND): A transaction journal matches the condition only when all the filter criteria match.
- Any condition is met (IS): A transaction journal matches the condition when at least one of the filter criteria matches.
- Customize the logic: Specify a logic that the transaction journal must match to be evaluated by the child condition or for the child action to be triggered.
    
    For example, a custom logic can be (1 AND 2) OR 3. This logic means that the transaction journal matches the condition when either:
    
    - The first two filter criteria are met
    - Only the third filter criteria is met

Next, define the filters of the condition. To define filters, enter the required values for these fields.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13616e104">Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d13616e107">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e104 ">Resource</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e107 ">
              <p>Select an already defined parameter or an object field.</p>
              <p style="margin-bottom:0;">When a transaction journal
                is processed, the value of the Resource field is automatically populated from the selected
                parameter. If you select an object field, its value is automatically populated based on the
                transaction journal that's processed.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e104 ">Operator</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e107 ">Select the operator based on which the transaction journal is evaluated.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e104 ">Type</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e107 ">
              <p>Select the type of value by using which you want to evaluate the transaction journal.</p>
              <ul>
                <li>Resource: Lets you select an already defined parameter or object field.</li>
                <li>Fixed Value: Lets you enter a value.</li>
                <li>Formula: Lets you create a formula.</li>
              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e104 ">
              <p>Value</p>
              <p>OR</p>
              <p style="margin-bottom:0;">Resource</p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d13616e107 ">
              <ul>
                <li>Value: Enter a value or create a formula.</li>

                <li>Resource: Select an already defined parameter or object field.</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-loyalty_management-264-0-0-production-enus/0590ce3e-5a09-45ab-8e5e-68f359c35886/images/icon_example.png)

Example A program manager wants to check whether a member has purchased a product of the Cloud Kicks brand. In the filter criteria of the condition, the program manager selects:

- Resource: TransactionJournal.Brand
- Operator: Equals
- Type: Fixed Value
- Value: Cloud Kicks

## Condition Groups

A condition group contains a set of conditions and a default path. Each condition in a condition group can contain child conditions or actions. The default path can only contain a child action.

When condition group processes a transaction journal, the transaction journal is evaluated by each condition in the sequence in which the conditions are saved. When a transaction journal satisfies the filter criteria of a condition, the transaction is no longer evaluated by the subsequent condition. The child condition or the child action of the matched condition either evaluates the transaction further or triggers the selected action. If the transaction journal doesn't match any condition, then the action associated with the default path is triggered for the transaction journal.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-loyalty_management-264-0-0-production-enus/0590ce3e-5a09-45ab-8e5e-68f359c35886/images/icon_example.png)

Example A program manager creates a condition group in which each condition verifies whether the transaction amount is within a specific range. The first condition verifies whether the transaction amount is between $1 and $10. The next condition verifies whether the amount is between $11 and $25. The third one verifies whether the amount is between $26 and $50. If the transaction amount is above $50, then the default path processes transaction journal.