Action Visibility Rules in Decisions: Changing how users interact with data

Action visibility rules in Decisions software allow users to selectively filter and hide actions related to specific data types, ensuring only relevant and permitted actions are visible in the action menu. These rules function across three key areas: data structures, configuration folders, and reports/pages.

1. **Data Structures**: Default and custom actions can be configured for different entities. For example, actions such as delete, edit, or manage permissions can be enabled or disabled within the entity's data structure. Configuration folders are used to add visibility rules, allowing actions to be shown or hidden based on the state of the entity (e.g., started, completed).

2. **Configuration Folders**: Visibility rules can apply to individual states within an entity, filtering actions based on specific conditions like entity state or other criteria, such as total cost. User actions can trigger workflows (like showing a popup) and be restricted depending on conditions such as cost thresholds or user group membership.

3. **Reports and Pages**: Action visibility can also be managed at the report and page levels. For instance, a dashboard may disable all user actions for certain users, while different visibility rules can be applied based on conditions like the state of a record. This provides flexibility in controlling which actions are available depending on the user's role or the context of the data.

These rules can be customized to fit business needs, providing control over who can see and perform certain actions based on predefined criteria.

0:00 Introduction to Action Visibility Rules
1:00 Structure Actions
2:11 What is an action?
2:38 Configuration Folder overview
3:52 User Actions by State
5:30 Visibility Rules in the Configuration Folder
11:16 Locally Filtering (Reports and Pages)
12:48 Filtering By Action Name or Category