--- title: "About Configuration Folders" slug: "configuration-folder" tags: ["Folder Actions", "Case Entities", "Validation Rules", "User Actions", "Configuration Folder", "Visibility Rules", "Entities", "Flow Execution Extension"] updated: 2025-06-24T17:47:16Z published: 2025-06-24T17:47:16Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # About Configuration Folders ## Overview The **C****onfiguration Folder** is a Designer Folder behavior that allows users to create additional configurations on Data Structures. The types of configurations could be**Entity Actions, Visibility Rules, and Access Patterns**. The Data Structures that can use Configuration Folders are: - [Database Structures](/v9/docs/creating-a-database-structure) (must be enabled) - [Entities](/v9/docs/creating-using-folder-entities) (Internal and External) - [Flow Execution Extensions](/v9/docs/creating-flow-execution-extension-data-structure) (deprecated in v9.5) - [Case Entities](/v9/docs/creating-a-case-entity-data-structure) Do Not Store Data In Configuration FoldersConfiguration Folders are meant to store designer elements that add additional abilities to the Data Structures they are tied to. They are not for storing process data. Do not use them for data storage. --- ## Configuration Folder Action Bar **Configuration Folders** can contain **Actions**. Users may configure actions to modify the data within the Data Structure and/or to better organize their data. Certain **Actions** within the **Configuration Folder Action Bar** may/may not be present depending on its Data Structure. Below is a table stating every Action visible throughout each variation.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Screenshot%202024-12-13%20135847.png) | Action Name | Supported Data Structures | Brief Description | | --- | --- | --- | | **Add Access Pattern** | Database Structures and Entities | Generates a custom step to retrieve data based on a criteria. | | [**User Actions**](/v9/docs/creating-user-actions) | All supported Data Structures | Creates custom right-clickable user actions. | | [**Validation Rule**](/v9/docs/using-validation-engine-for-entities-2) | Case Entities, Database Structures, and Entities | Allows for Rules to ensure created data is valid. | | [**Entity Events**](/v9/docs/hooking-entity-events-for-custom-handling-of-entities) | Case Entities, Database Structures, and Entities | Flows created for notification on the deletion or creation of an Entity. | | **State Triggers** | All supported Data Structures | Flows that run when an Entity enters a particular state. | | [**Generate Descriptions**](https://documentation.decisions.com/projects/docs/creating-custom-descriptions) | Case Entities and Entities | A defined message description to generate from a Flow. | | [**Action Visibility Rule**](/v9/docs/action-visibility-rules) | All supported Data Structures | Rules created to hide user Entity actions. | | **Create Reporting Data Flow** | Database Structures and Entities | Used to create Flows that can be used as report data sources. | | [**Create Page**](/v9/docs/create-pages-dashboards) | Case Entities | Create a variety of Pages for the Case Entity | --- ## Add Access Pattern **Add Access Patterns** are similar to querying a database; a user may define a custom Fetch for the Entity. The **Access Pattern** retrieves a list of field results that fulfill user-specified criteria with search conditions such as **Equals, Contains, Greater Than, Less Than**, etc. For example, if a user passes the default **Fetch by Id**, then the corresponding Entity will be returned. To set up the Add Access Pattern: 1. Select ADD ACCESS PATTERN from the Action Bar in a supported Data Structure. 2. A dialog will display requesting the user to configure which fields to filter on and the step name. Access Pattern Configuration Restrictions - Access step names cannot contain **spaces** or **special characters**. Use pascal or camel casing when naming access pattern steps. - Access patterns can only be used with **primitive types,** such as **I****nt32, String, DateTime, Decimals, and Boolean**types. User composite types cannot have access patterns because they are serialized in the database. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-02_11h30_17.png) 3. After saving the Access Pattern, a new step is under **User Defined Types > Data Structure Name**. For this example, an Entity Data Structure was used. 4. The Flow step now exists under **User Defined Types** > **ExampleEntities****.** 5. Inputs need to be configured to use Access Pattern steps. QueryTypeQueryType performs the same function as Match Type. If both are configured, the system will use the Match Type selection and ignore the QueryType. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1750787200633.png) --- ## State Triggers State Triggers are [Flows](/v9/docs/flows) auto-triggered when a specific state is in place. When something moves from one state to a specified state, a Flow can be triggered to run as soon as that application or assignment moves to a specific stage. - Create Auto Trigger Flow: Runs a Flow when a specific state is in place. - Use Shared Auto Trigger Flow: Runs a Flow that is used for multiple specified states. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-02_11h26_27.png) --- ## Feature Changes | Description | Version | Release | Developer Task | | --- | --- | --- | --- | | Changed the icon for configuration folders. | [9.5](https://documentation.decisions.com/v99/docs/version-95x-release-notes) | November 2024 | [DT-042291] | For further information on Data Structures, visit the [Decisions Forum](https://community.decisions.com/categories/Datastructures).