---
title: "About Logic Blocks"
slug: "building-logic-blocks"
updated: 2026-10-30T20:21:00Z
published: 2026-10-30T20:21:00Z
canonical: "docs.interprose.com/building-logic-blocks"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.interprose.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Building Logic Blocks

## How do I create Logic Blocks?

In ACE, Logic Blocks enable users to retrieve specific groups of accounts based on stored field values. Once created, a Logic Block can be saved for future use in the following ways:

- As a report: Run the Logic Block and export the results.
- In a job: Use it within an action path workflow.
- In an action path: Apply Logic Block conditions to limit parts of the action path.
- In the account manager: Perform one-time actions on the group of accounts.

### Understand Apply, Test, and Save

A Logic Block stores the criteria ACE uses to select accounts. Jobs, worklists, Action Paths, and Account Manager can reuse those criteria.

> [!NOTE]
> Caution
> 
> Selecting **Test** on an unlocked Logic Block saves its current definition before displaying the matching accounts. Workflows that use the block can use those saved changes. Selecting **Cancel** afterward does not restore the earlier definition.

| Button | What It Does |
| --- | --- |
| **Apply** | Saves the definition and keeps you in the Logic Builder. |
| **Test** | Saves an unlocked definition, then opens the matching account results. |
| **Save** | Saves the definition and returns through the applicable navigation flow. |
| **Cancel** | Leaves the screen. It does not undo a definition already saved by Apply, Test, or Save. |
| **Clone** | Saves a separate, unlocked copy. Changes to the copy do not change the original block. |

### How to Create a Logic Block

1. Go to **Workflow → Logic Blocks → New**
2. Enter Label
3. Description
4. View Role ID (Optional): Specify a role if you want to limit which users can view and use this Logic Block. Only users with the selected role will be able to access it from various ACE menus, such as Account Manager, Jobs, Action Paths, Bundle Groups, and VA 2.0 Profiles. If left blank, all users with Logic Block access can view and use it.
5. Edit Role ID (Optional): Specify a role if you want to limit who can edit this Logic Block. Only users with the selected role will be able to make changes to it in the Logic Builder. If left blank, all users with edit permissions can modify the Logic Block.
6. Return Primary Account Only: check if yes/leave blank if no
7. Add Field: specify the logic and conditions to be applied to the accounts
8. Select **Apply** to save the definition.
9. Select **Test** to save the unlocked definition and review the matching accounts. If you change the criteria, test again and review the updated results.
10. Select **Save** when the selection is correct. If the block is already used by a workflow, remember that **Apply** and **Test** have already saved the definition.

> [!NOTE]
> Permission Roles
> 
> Only users having a permission role with the "LOGIC_MANAGE" permission will be able to see, populate and save role selections to:
> 
> - View Role ID
> - Edit Role ID

![](https://cdn.document360.io/6c7303ca-5ffc-4149-8868-8ea498eee635/Images/Documentation/Screenshot 2024-09-13 100859.png?sv=2026-02-06&spr=https&st=2026-10-31T15%3A35%3A06Z&se=2026-10-31T16%3A35%3A06Z&sr=c&sp=r&sig=Gm0BVg7TPb2RI8prlX47uZcO%2BbqCGeDxu8D7HeYZwZs%3D)

Image Display Example Logic Block

### Test Changes to an Existing Logic Block

1. Select **Clone**, if available, or create a separate Logic Block with the same starting criteria. Give the test block a descriptive label.
2. Keep active jobs, worklists, and Action Paths pointed at the original block while you test.
3. Change the fields or conditions in the test block. Select **Apply**, then **Test**, and review the accounts included and excluded.
4. Revise and test again as needed. Each successful test of the unlocked block saves its definition.
5. When the selection is correct, select **Save**. Update the intended workflow to use the approved block when you are ready to use the new criteria.

Testing the selection does not run a job or perform Account Manager actions. Those are separate steps.

> [!NOTE]
> Please Note
> 
> **Test** does not save a locked Logic Block. Use a separate test block when trying editable changes; do not rely on a locked block to test changes without saving.

For query troubleshooting, see [Troubleshooting Custom SQL in Logic Blocks](https://docs.interprose.com/docs/troubleshooting-custom-sql-in-logic-blocks).

### 

In ACE, Logic Blocks allow a user to return a specific group of accounts based on stored field values associated with accounts. Once a Logic Block has been built, it can be stored and available for future use as follows:

- as a report (run the logic block and export)
- in a job (action path workflow)
- in an action path (logic block limitation for parts of the action path)
- in the account manager (one time actions against the group of accounts)