Watch the walkthrough
Create scheduled events that run workflows automatically.
Recorded with an earlier Twidget interface. Names, control locations and available options may differ; use the linked documentation for current guidance.
Watch tutorial (2:35)
Browse all video tutorials
Introduction to Events
Events run server workflows automatically. An event can run once, repeat at an interval, run on selected weekdays at a local time, or be invoked by a database change trigger. Its schedule and database trigger settings are separate.
Types of Scheduled Events
One-Time Events: These events are scheduled to occur at a specific date and time.
Recurring Events: These events trigger at regular intervals, e.g., every hour, day, week, etc.
Calendar Events: Select weekdays and a local time, such as Monday to Friday at 09:00, in the event's timezone. See Event Builder for timezone and daylight-saving behaviour.
How Events Work
Schedule: Define when the event should trigger. This could be a specific date and time or a recurring interval.
Commands List: Specify the sequence of commands that the event should execute. These commands are run in the order they are listed.
Creating an Event
Define the Schedule: Set the exact time or recurring interval for the event.
Add Commands: List the commands to be executed by the event.
Characteristics of Events
- Inputs and results: A scheduled run has no caller-supplied input payload. Events can define inputs for supported invocation paths; a database change trigger supplies an Object input named
trigger. Events do not return an HTTP response to the person who configured them. Review execution results and errors in Event History.
Examples of Scheduled Events
Example 1: Morning Report Generation
Description: An event that generates a daily report every morning at 7 AM.
Schedule: Every day at 07:00 AM
Commands:
Fetch latest data from the database.
Compile the data into a report.
Send the report via email to the management team.
Example 2: Hourly System Health Check
Description: An event that performs a health check on the system every hour.
Schedule: Every hour
Commands:
Run system diagnostics.
Log the result of the diagnostics.
If an error is found, send an alert to the support team.
Example 3: Weekly Backup
Description: An event that backs up the system data every Sunday night at 11 PM.
Schedule: Every Sunday at 11:00 PM
Commands:
Initiate data backup
Verify backup integrity
Notify IT team
Conclusion
Creating scheduled events in Twidget allows you to automate routine tasks efficiently. By defining a precise schedule and listing the necessary commands, you can ensure that critical processes are executed timely without manual intervention.