My Tasks

The My Tasks section shows all pending activities that require user review or action before payouts can continue. It is directly linked to policies and workflows, meaning whenever a rule requires approval, it will appear here as a task.

This ensures every payout action—like creating, updating, or executing—is properly reviewed and validated according to your business rules.

Task Overview

Displays all tasks generated by workflow or policy requirements.

Approval and Rejection

Users can approve or reject operations such as beneficiary creation or execution updates.

Filters

Narrow tasks by date, status, or other parameters.

This diagram illustrates how tasks are automatically generated and resolved within an approval workflow. When an object is created or updated, the system evaluates applicable policies. If approval is required, a task is created and assigned to the relevant users or roles, appearing in My Tasks. Users can then approve or reject the task. Approvals move the process to the next step until completion, while rejections either stop the workflow or return it to a previous step based on the workflow configuration.

Each row represents a task generated by a workflow step that requires user action.

  • Object ID The unique identifier of the object associated with the task (for example, a payout intent, execution, or sanction check).

  • Current Step Indicates the current workflow step awaiting action.

  • Created On The date and time when the task was generated.

  • Modified On The last time the task was updated.

  • Created By The user or system that initiated the workflow.

  • Modified By The user who last interacted with the task.

  • Actions Contextual actions available for the task.

From the Actions menu, users can perform workflow-specific operations, such as:

  • Apply Sanction Approval Operation Approves the task and allows the workflow to proceed to the next step.

  • Apply Sanction Rejection Operation Rejects the task, stopping or redirecting the workflow based on its configuration.

The available actions depend on:

  • The workflow definition

  • The current step

  • The user’s role and permissions

Last updated