User guide
Quick Start Guide
Dashboard
Overviews
Case detail (Caseoverview)
Case - event
Tasks
Case notes
Documents
User settings
Favorites
Table component
FAQ
Administrator Guide
Platform guide
Administration
Crons
Authentication and Synchronization
Mobile App Setup for Your Environment
Scheme
Dynamic tables
Archiving
Scripts
Service console
Scheduled Tasks
HR Agenda
Sequences
CSP Headers
Logs
Access Token Settings & Session Expiration
Template
Roles
Planning
Users
Organizational structure
Events
Translations
AXIOS API
Calculations & Functions
Integrations
TAS Forms
TAS Forms
Activating the module on the environment
TAS Forms - secret creation guide for Docker Swarm
Advanced Features & Tips
Partners
Product
Business Changelog
Technical Changelog
Version Upgrade Guide
Upgrading to 5.9
Upgrading to 5.3
Dynamic conditions migration
PDF printing adjustment
Editing Task Description vs Task Instructions
Transpiling forEach to a for loop
Rendering HTML on Caseoverview
Upgrading to 5.7
Lodash upgrade v4.17.x (>v5.5)
Main changes and deprecated features (v5.3 > v5.7)
Using validation functions
Differences between TAS4 and TAS5 - a complete overview
Best Practices for Upgrading from v4 to v5
Technical details
News / Important information
- All Categories /
- User guide /
- Case - event
Case - event
Events are closely tied to cases and are configured within process templates. They provide a way to control the flow of a case or process based on specific triggers. You can use events to either interrupt or continue a process in different ways depending on the situation.
How to initiate event
- Find the case on which you want event to be performed
- Go to Event / or more options on list of cases
- Choose the Event you want to perform
Some common uses of events include:
- Canceling a Case: An event can be configured to cancel an entire case. For instance, if certain conditions are met, the event will terminate the case early, preventing any further actions or tasks from being executed.
- Changing the Initial Request: Events can be used to modify or update the initial request or data within a case. For example, an event can adjust the values or status of a case based on new information or changes that occur during the workflow.
- Bypassing Scheduled Tasks: You can configure an event to skip or override scheduled tasks. For example, if a task is scheduled to occur at a later time but certain conditions are met earlier, the event can trigger the task immediately, without waiting for the scheduled time.
These event-driven actions allow for dynamic control over the process flow, making it more flexible and responsive to real-time changes and needs.
Updated
by Anna Gernát