Overview of Tasks

Tasks in Caseblocks represent actions or operations that can be performed on a case (or multiple cases). They can execute custom JavaScript code, track manual activities, or even delete a case entirely. By grouping tasks into Tasklists, you gain a flexible way to manage both permissions and execution flows for different teams or scenarios.

Tasks

Tasklists and Permissions

  • Container for Tasks: Each Tasklist contains one or more tasks.
  • Permission Control: Tasklists can be configured with permissions, allowing or restricting access to specific teams. This way, only authorized users can view, modify, or run tasks in certain contexts.

Types of Tasks

  1. JavaScript Task
  2. Manual Task
    • Represents an external or offline activity completed outside of Caseblocks.
    • Lets you mark or record the completion of a real-world task.
  3. Delete Task
    • Deletes the current case when executed.
    • Useful when you need to remove a case as part of a process, while keeping the action trackable and permission-based.

Ways to Run Tasks

  1. Individual Case Execution
    • A task can be exposed as a button on a fieldset within a case. Users click the button to execute that task against the currently opened case.
    • Alternatively, tasks can be run from the Tasklist interface, typically found in the case’s configuration or detail view.
  2. Bulk Execution (via Bucket Batch Action Task)
    • If you have a bucket of multiple cases, you can run tasks in batches.
    • This feature saves time by applying the same task across many cases at once, such as bulk updates or status changes.
  3. Scripting Environment or API Calls
    • Tasks can be executed programmatically from within a script or via an API call.
    • This allows for highly automated scenarios where certain triggers or events will run tasks without manual intervention.

Tracking and Visibility

  • Status of the Last Run: Each task on a case shows whether it succeeded, failed, or is pending. This status is visible in the user interface to keep stakeholders informed.
  • Timeline Records: All executions of the task are stored in the case’s timeline. This means you have a full audit trail showing who ran the task, when they ran it, and the outcome.

Table of contents


Copyright © 2024 Caseblocks Limited.