Server Scripts
Server scripts are processed, served and executed by Corredor server.
Server scripts should be used when:
-
interaction with the user is not required,
-
response latency is not as important,
-
execution consistency is important,
-
automation script produces a heavy load on system resources
Example use case
-
insert additional record fields based on an external data source,
-
send an email when a new user signs up,
-
run statistic operations once a month for reporting purposes.
Trigger types
Server scripts support a few different trigger types; explicit, implicit, deferred, iterators and sink.
Explicit
Explicit triggers execute on a specific user invocation, such as a button press. These include:
- Manual
-
Manual automation triggers are defined as buttons inside the user interface. They most commonly appear inside Low Code automation page blocks or inside Low Code record list toolbars. They are invoked in UA and executed inside Corredor.
Implicit
Implicit triggers execute as a collateral to another system event such as record creation. These triggers include before/after events. For a full list of available events refer to [ext-resevt].
Deferred
Deferred automation triggers are executed at a specific point in time; once or multiple times, such as a reminder. These include:
- Scheduled
-
scheduled triggers are executed at an exact time specified by a time stamp in ISO 8601 format (
YYYY-MM-DDTHH:mm:ss.sssZ). This trigger is executed exactly once, - Interval
-
interval triggers are executed periodically in an interval defined by a cron expression (see robfig/cron package for details).
|
Deferred automation triggers are executed at most once every minute, so you should not define an interval or timestamp that uses higher precision (seconds or milliseconds). |