Task Event Processor
A model that allows you to process task events
Slug: task-event-processor
Version: 1.0.0
Infer: No
Event Aware: Yes
Overview
Task Event Processor Model
The Task Event Processor model automates document workflow management by monitoring task events and taking configurable actions based on task status changes. It enables automated document transitions, task coordination, and status synchronization within your document processing pipelines.
How It Works
- The model listens for task status change events
- When a task status changes, it examines related tasks for the document
- Based on your configuration, it can:
- Update document status when all tasks are complete
- Cancel all other document tasks if a task is rejected
- Enforce status transition rules and dependencies
Options Configuration
Option | Description |
---|---|
document_store | The document store containing documents to process |
should_update_document_status | When enabled, updates document status when all related tasks are complete |
document_status | The status to set documents to when all tasks are complete |
is_current_status_required | When enabled, only updates documents that are in a specific status |
required_current_status | The status documents must be in to qualify for status updates |
should_cancel_all_tasks_if_task_is_rejected | When enabled, cancels all other tasks when one is rejected |
rejected_status | The task status that indicates rejection |
task_status_if_task_canceled | The status to set other tasks to when a task is rejected |
Process Flow
Typical Use Cases
The Task Event Processor model is particularly useful for:
- Automated Workflow Transitions: Move documents to the next status when all tasks are complete
- Task Dependency Management: Automatically cancel dependent tasks when a primary task is rejected
- Status Rule Enforcement: Ensure documents follow proper status transitions
- Process Optimization: Reduce manual status updates and task management
- Multi-step Approvals: Coordinate complex approval workflows with multiple tasks
Example Configurations
Document Completion Workflow
To automatically move documents to “Complete” status when all tasks are finished:
Rejection Handling Workflow
To cancel all other tasks when a document is rejected in review:
Conditional Status Transition
To only update documents from “In Review” to “Approved” when all tasks are complete:
Technical Considerations
- The model examines all tasks related to a document before updating status
- Status updates only happen when ALL tasks reach “DONE” status type
- The task cancellation feature uses the task status you specify, typically “Canceled”
- You must select existing status values from your project configuration
Inference Options
The following options can be configured when using this model for inference:
Name | Label | Type | Description | Default | Required |
---|---|---|---|---|---|
should_update_document_status | If all tasks are done, update the Kodexa document status | boolean | Toggle on to update the Kodexa document status when all tasks have a status type of DONE | False | No |
is_current_status_required | Is a specific current status also required in order to update the Kodexa document status? | boolean | Toggle on to also require a specific current status to exist on the document in order to update the Kodexa document status | False | No |
required_current_status | Required current Kodexa document status | documentStatus | The Kodexa status to check for before updating the document status | - | No |
document_status | New Kodexa document status | documentStatus | The Kodexa status to update the document to when all tasks have a status type of DONE | - | No |
should_cancel_all_tasks_if_task_is_rejected | Update the status of all other document tasks if the task is rejected? | boolean | Toggle on to update the status of all other document tasks if the task is rejected | False | No |
rejected_status | Rejected Status | taskStatus | Select the rejected status to test for | - | No |
task_status_if_task_canceled | Status to set the other document tasks to if the task is rejected | taskStatus | The status to set the other document tasks to if the task is rejected | - | No |
document_store | Document Store | documentStore | The document store to update the document status in | - | Yes |
Model Details
- Provider: Kodexa AI