Types of Automations
There are four main types of automations in ERPLite:- Screen Transitions: Automations that are executed during screen transitions, allowing you to perform validations or integrate with external systems as users navigate between screens.
- Screen On Load: Automations that control the appearance and behavior of a screen when the screen is loaded. This can include fetching data from REST APIs or databases, hiding or showing specific screen components, and other dynamic adjustments.
- In-Screen: Automations that modify screen components based on user interactions, such as controlling the visibility of components or loading data from external systems during screen interactions.
- Task Events: Automations that can be configured to trigger by task-level events, such as task assignment, unassignment, creation, deletion, update, or changes to a task’s scheduled slot.
Automation Components
Every automation in ERPLite consists of the following components:- Trigger: At least one trigger is required for each automation. Triggers define the event for which the automation will be executed, such as a specific user interaction or a task event.
- Validation (optional): A validation determines whether an automation should be executed or not. If a validation is specified, the automation will only be executed if the validation returns true. See more details about validations here
- Action Blocks: An automation can have one or more action blocks, each containing multiple conditions and actions. All conditions within an action block must be met (return true) for the actions in the action block to be executed.
Creating Automations
The entry point for each of the automation different based on the type of automation. Refer to the individual automation page for more details To create an automation in ERPLite, follow these steps:- Navigate to the ERPLite app editor and select the screen or task event where you want to add an automation.
- Click on the “Automations” tab, and then click the “Add Automation” button.
- Configure the trigger(s) for your automation.
- Optionally, define a validation for your automation.
- Create one or more action blocks, specifying the conditions and actions for each block.
Automation Flow
For AI Agents
Automation Structure
Trigger Types
| Type | API Key | When Fired |
|---|---|---|
| Screen Transition | SCREEN_TRANSITION | User navigates between screens |
| Screen On-Load | SCREEN_ON_LOAD | Screen is loaded |
| In-Screen | IN_SCREEN | Component event (onChange, etc.) |
| Task Event | TASK_EVENT | Task lifecycle events |
API: List Automations
UI Components
| Component | Location | Purpose |
|---|---|---|
| AutomationBuilder | /src/views/automations/ | Main automation editor |
| TriggerConfig | /src/views/automations/Trigger/ | Trigger configuration |
| ValidationConfig | /src/views/automations/Validation/ | Validation setup |
| ActionBlockEditor | /src/views/automations/ActionBlock/ | Action block configuration |