Business Function Properties
This section explains all core properties used to configure a business process. These settings define how, when, and under what conditions a process runs.
1. Type
Type function defines the nature of the process which can be either Business or UI.
2. CRON Job
Runs automatically based on time rules. Use this section only if the process is time-based.
CRON jobs are ideal for:
- Nightly Syncs – Automatically synchronize data between systems at a set time during the night, when traffic is low and performance impact is minimal. For example, syncing customer records from an external CRM into your platform every night at 2:00 AM, ensuring data is always up to date by the start of the business day.
- Scheduled Reports – Automatically generate and distribute reports at defined intervals without any manual trigger. For example, sending a weekly sales summary every Monday morning at 7:00 AM to all managers, or generating a monthly invoice report on the 1st of each month.
- Cleanup Tasks – Automatically remove outdated, redundant, or temporary data to keep the system clean and performant. For example, deleting all records with a "Draft" status that haven't been updated in over 30 days, or clearing temporary log files every Sunday night.
- Periodic Recalculations – Automatically recalculate field values or aggregated data on a schedule, especially useful when real-time calculation would be too resource-intensive. For example, recalculating each client's total spending based on their order history every night, so the value is ready to display instantly without querying large datasets on demand.
2.a) Schedule Type
Controls how the schedule is determined.
- Fixed - Runs at a predefined, static time.
- Dynamic - Schedule is calculated at runtime, usually based on data or logic.
2.b) Scheduled
Master switch for scheduled execution.
- On - The process will run automatically according to its schedule.
- Off - The schedule is ignored, even if defined.
2.c) Schedule Time
Specifies the exact time when the process should execute.
This applies only when:
- Scheduled is enabled
- Schedule Type is Fixed
3. Trigger
Used when the process should react to data changes instead of time.
This turns the process into an event-driven automation.
Typical use cases:
- Status Changes – The process fires automatically whenever a record's status field changes to a specific value. For example, when a ticket's status changes from "In Progress" to "Resolved", a trigger can automatically send a notification email to the client, or when an order is marked as "Shipped", it can update the delivery tracking record accordingly.
- Record Creation – The process fires whenever a new record is created in a specific entity. For example, when a new user registers, a trigger can automatically create a default profile record for them, send a welcome email, or assign them to a default user group - all without any manual intervention.
- Field Updates – The process fires whenever a specific field's value is changed on an existing record. For example, when the "Assigned To" field on a task is updated, a trigger can notify the newly assigned team member, or when a contract's expiry date is changed, it can automatically reschedule a reminder notification.
3.a) Event
Event function efines what kind of change will activate the process.
3.b) Entity
Entity function pecifies which entity the trigger listens to. The process will run only when changes occur on this entity.
3.c) Custom Timeout
Custom Timeout overrides the default execution timeout.
Use this when:
- The process runs long operations
- External APIs are involved
- Large datasets are processed
Be practical. Increasing timeout hides performance issues if abused.
4. Library
A collection of reusable code blocks with built in logic designed for specific tasks. Helps to visually separate complex logic so it is easier to follow and understand.