--- title: "Configuring a Selection Rule" slug: "configuring-a-selection-rule" description: "Learn how to create Static and Dynamic Selection Rules to automate field population based on conditions, enhancing your output generation process." status: "update" updated: 2026-09-28T08:16:35Z published: 2026-09-28T08:16:35Z canonical: "documentation.encodify.com/configuring-a-selection-rule" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.encodify.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring a Selection Rule ## Overview --- A **Selection Rule** automatically populates fields with either predefined or dynamically mapped values when specific conditions are met. There are two distinct types of selection rules: - **Static** assigns a predefined field value that you select in the rule's configuration. This occurs when the rule's conditions are met. For example, if the Format field equals A4, you can set the **Template** field value to "Template A4." - **Dynamic** populates fields by matching the field values of a source item to items in a linked module. This means the field values from the source item are used as search criteria to find corresponding items in the linked module. For example, this type of rule can be used to link images to a product based on its Format and Brand values. Static and Dynamic rules can be applied in [Creative Automation Print Studio](/v1/docs/creative-automation-print-studio) during the Output Generation step. No additional configuration is required. The rules are automatically applied when assigning templates to the input items during output generation. > [!WARNING] > **IMPORTANT:** *Selection* automation rules are executed under the **System user** context. This means: > > - **Group and Status restrictions** are ignored when populating options through a selection rule. > - **Filter by Current User** cannot be applied. > [!NOTE] > **Note:** Selection rules respect **filters on Module Link fields**. This means that only the options allowed by the filter restrictions will be populated by a Selection rule. ## How to Create a Static Selection Rule --- ### Rules Configuration To configure a Static Selection rule, follow these steps: 1. Navigate to **Automation Rules** (see [Automation Rules Overview](/v1/docs/automation-rules-overview) for more details) 2. Click the **Add Rule** button 3. Complete the **Basic Info** section: 1. Enter a **Name** and, optionally, a **Description**. 2. From the **Type** dropdown, select **Selection**. 4. In the **Conditions** section, select a **Module.** If needed, specify **Filter Criteria** to configure the conditions that will trigger the rule. 5. Configure **Actions**: 1. Select **Static** as the **Selection Type**. 2. Specify the **field** and **field value** that should be set when all configured conditions are met. 3. Enter a **custom value** using regular text, velocity templates, or concatenated text. Leave the field empty to remove values from the field. 4. Repeat for each additional action you want to configure. 6. Click **Save** to confirm your settings and create a rule. ![](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/image(215).png) > [!NOTE] > **Note:** Static Selection rules with custom values have the following characteristics: > > - It is not possible to assign multiple custom values. You can only remove all values or assign a single custom value. > - When duplicate values exist, the most recently created value is assigned by default. > - When a text field is selected, only 'Custom Value' is available; 'Field Value' is disabled. > - Custom value matching is case-insensitive. ### Supported Mapping Field Types The following field types are supported within field mapping: - Module link - Text option fields - Status fields - User fields - Email - URL > [!NOTE] > **Note:** When configuring Selection Rules for target fields, syntax validation and character length limits are deliberately bypassed at rule setup. > > - Dynamic Expressions (Velocity): Static analysis of runtime expressions (e.g., `$currentItem.field('Email')`) at configuration time is technically unfeasible. > - Static Literal Inputs: Plain text values are accepted without pre-execution format or length checks. > - Deferred UI Behavior: If an invalid or over-limit value is saved via a rule, it silently populates the target item. Validation is deferred until a user manually opens and edits the item form in the UI. > > This behavior is documented as a known platform design constraint. **Administrators should ensure static inputs adhere to standard URL/Email formats and field length limits prior to saving rules.** ## How to Create a Dynamic Selection Rule --- ### Rules Configuration To configure a Dynamic Selection rule, follow these steps: 1. Navigate to **Automation Rules** (see [Automation Rules Overview](/v1/docs/automation-rules-overview) for more details) 2. Click the **Add Rule** button 3. Complete the **Basic Info** section: 1. Enter a **Name** and, optionally, a **Description**. 2. From the **Type** dropdown, select **Selection**. 4. In the **Conditions** section, select a **Module.** If needed, specify **Filter Criteria** to configure the conditions that will trigger the rule. 5. Configure **Actions**: - Select **Dynamic** as the **Selection Type**. - In the **Field Mapping** section: - Select the **Module Link field** that should be populated as a result of rule execution. - The **Module** value is automatically prefilled with the current module. - The **Lookup Module** value is automatically prefilled with the module that the selected Module Link points to. - In the **When** section, select the **fields in the source and target modules** that will be used to match items or options in the Lookup Module. 6. Click **Save** to confirm your settings and create a rule. ![](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/image(192).png) ### Supported Mapping Field Types The following field types are supported within field mapping: - Module link - Text - Decimal numeral - Integer - Fields taking options from site configuration (Country, Region, etc) - User fields - Searchable text concatenation - Automatic Numbering - Email - URL > [!NOTE] > **Note:** When executing a Dynamic Selection Rule, field values from the source item are used as search criteria to find matching records in the lookup module. > > - This behavior applies across all supported field types. System administrators should ensure source items contain valid matching criteria before executing dynamic rules. > - **Multiple Matches**: When multiple items in the lookup module match the source criteria, the rule assigns the first available item. > - **Empty Source Fields**: If a source field is blank (`null` or empty), the system queries the lookup module using the empty criteria. This matches records in the lookup module that also have empty fields, resulting in the rule assigning an arbitrary lookup item to a source record with no field value present. ## How to Configure Linked Action --- For **Automation Rules** to be available in the user interface, the relevant module must have **Actions** configured in **Manage Modules**. ### Configuring an Action for Rules on the Current Module To allow execution of rules on items within the same module: 1. Go to **Manage Modules → {Module Name} → Actions**. 2. Click **Create Action**. 3. From the **Event** dropdown, select **Create and Update**. 4. From the **Action** dropdown, select **Execute Task**. 5. From the **Task Name** dropdown, select **Execute selection rules**. 6. Click **OK** to save. ### Configuring an Action for Rules on Another Module To allow execution of rules on items in a different (linked) module: 1. Go to **Manage Modules → {Module Name} → Actions**. 2. Click **Create Action**. 3. From the **Event** dropdown, select **Create and Update**. 4. From the **Action** dropdown, select **Execute Task**. 5. From the **Task Name** dropdown, select **Execute selection rules**. 6. From the **Field with Items in Remote Module for Executing Rules** dropdown, select the relevant **Module Link field**. Rules will be executed for each related item in this field. 7. In the **Rules** multi-select field, choose one or more **active selection rules** that will be applied to all items identified by the selected field. 8. Click **OK** to save.