Cases: Module Actions

Overview

There are a few ways one can configure Actions for a case template or an account type. By default, when you add an action to a case template or an account type through Settings, they show up in the overflow menu at the very top of the case or account. You can set visibility or enablement setting per action to make it conditionally visible or disabled.

However, there are other ways you can add actions in a Layout. You can add a Button component in a layout and select an action to take when a button is clicked. You can also add an action in a Data Table Module so that you can take those actions on an object specified per row. You can select a custom action you have configured or a system action that is pre-built for each type of object.

When an action is configured on a module, it appears as under … menu anchored to rows in the data table module's table. A user selects one or more rows, clicks the action button, and the associated workflow fires (passing the row's ID as a parameter). The Action begins it’s run, with a success or failure notification once the workflow completes.

All data table modules and Resource modules can configure the following prebuilt System Actions:

System Action Supported object types
Update fields Case, Account, Transaction
Update tags Case, Account, Transaction, Inquiry, Report, Verification
Update queue Case only
Flag issue Inquiry, Verification, Report
Run report Report only
Pause continuous monitoring Report only
Resume continuous monitoring Report only
Redact Case, Account, Transaction, Inquiry, Report, Verification
💡For resource modules added to a case template, the module action can also be set to one of the configured Case Actions.

Which layout modules support Actions?

Module Actions can be configured on the following module types:

  • Data Table — any Data Table module with rows.
  • Resource modules set to "table" view (powered by Data Table module) — the following resource module types support actions when their view layout is set to Table (not List):
    • Inquiries
    • Verifications
    • Reports
    • Report Runs
    • Transactions
    • Accounts
    • Cases
    • Documents
    • Assignee History
💡Resource modules in List view do not support module actions.

How to create a Module Action

  1. Go to Dashboard > Cases > Templates, then click the template or type you want to edit.
  2. Click the module you want to add an action to (a Data Table, or a Resource module with "Table" view selected).
  3. In the right-side configuration panel, scroll down to the Actions section.
  4. Click the + button to add a new action.
  5. A new action entry appears. Select it to open the action editor panel.
  6. In the Action dropdown, choose either a case action (from your configured case actions) or a system action (Update fields, Update tags, Redact, etc.).
  7. Enter a Label. This is the button text reviewers will see.
  8. If the action requires parameters (for example, an object ID to pass to the workflow), configure them in the Params section. The default for most system actions is id, which passes the row's ID automatically.
  9. Optionally, configure Visibility rules to conditionally show or hide the action based on case or user context (available on Cases Enhanced and Enterprise).
  10. Click Save at the top right to publish the change.

How to edit an existing layout module Action

  1. Go to Dashboard > Cases > Templates, then click the template or type you want to edit.
  2. Click the module that contains the action you want to change.
  3. In the right-side configuration panel, find the Actions section. You'll see a list of all configured actions for that module.
  4. Click the action you want to edit, which will open the action editor panel.
  5. Make your changes: update the Action.
  6. To remove an action entirely, click the X button next to it in the actions list.
  7. Click Save on the case template to publish the change.
💡System actions (Update fields, Update queue, Redact, etc.) currently only support Single selection mode. Multi-row dispatch for system actions is not yet available.