Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Events allow create creating tasks for server-side scripts script executing, immediate or scheduled, or notification sending at a specified point of in time. These are the most common use cases of system events using. Also, it is possible to . You can also use one event register for both the needs listed above.
To use the system events in your tasks, you need to :
Createcreate an event register record.
After thisThen, you can handle it in one of these the following ways:
- Define a server script for a system event ( by creating a record in the Event Script Action Actions (sys_event_script_action) dictionary) dictionary.
- Define a notification rule to to send notifications.
- You can combine the options listed above, so your event register record will be able to trigger can trigger actions and send notifications cooperatively , if you bound bind them with this record.
Event structure
Creating an event
To create an event, use the server-side API methods methods ss.eventQueueor ss.eventQueueScheduled should be used. Create an event as described in the referenced articles, and as referenced articles. As a result, records in the the Event (sys_event) table will be created.
Note |
---|
You cannot create, edit, or delete records in the Events (sys_event) table manually. Only users with the admin role can read them. |
The example of such record is described below.
Tip |
---|
Role required: admin. |
Anchor | ||||
---|---|---|---|---|
|
form fields
Field | Description | ||
---|---|---|---|
Name | The name of the record called from the Event Register (sys_event_register) table. | ||
Instance | The ID of the Record object. When creating an event via calling methods ss.eventQueueor ss.eventQueueScheduled, you have to pass on the Record object. The object ID will be saved in this field. You 'll be able to can call on this value in the the Event Script Action (sys_event_script_action) script body: event.instance | ||
Table | This field contains a reference to the record table that was passed at the time when the event has been was created. This field is populated automatically. | ||
Process started at | The date and time of the system event execution start. As for scheduled events, this field is populated with the value passed by the third parameter of the ss.eventQueueScheduled method. The date and time of the Event (sys_event) script execution. | ||
Process finished on | The date and time of the system event execution finish. | ||
Param_1...Param_ 5 | The string parameters that can be transmitted to the specified Event (sys_event) record via the SimpleOne server-side API (ss.eventQueue and ss.eventQueueScheduled methods). | ||
State | Event state:
| ||
Processing duration, ms | The system event processing duration (Duration of the system event processing in milliseconds). | ||
User | The script specified in the Event Script Action record will be executed with the permissions of this user, and the ACL restrictions will also be also taken into account.
|
Related lists area are bound with the event record contains containing the following lists:
- The list of all related event register records from the Event Register (sys_event_register) table.
- The list of all scripts all the scripts from the Event Script Action (sys_event_script_action) table are referenced to the current record.
Anchor | ||||
---|---|---|---|---|
|
Field | Description |
---|---|
Name |
Name of the event register record. Events (the Event (sys_event) table records) called for this register |
contain this value in the Name field. | |
Table | Starts with only those events that contain a record related to a specified table. If you are going to trigger email sending with this record, then |
ensure that the value in the Table field in the Notification Rule record is the same |
as in this event register record. | |
Description | Event register record description. |
Disable script logging | Select |
the checkbox to disable script execution logging (to the Script Logs (sys_log_script) table) when the related event |
starts up. |
Related lists area lists area bound with the event register record contains containing the following lists:
- The list of all scripts all the scripts from the Event Script Action (sys_event_script_action) table are referenced to the current record.
- The list of all Notification Rules triggered by the record of the current event register record.
Anchor | ||||
---|---|---|---|---|
|
Field | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | The name Name of the event script action. | ||||||||||||||||||||||
Event Register Record | The reference to the record in the Event Register (sys_event_register) table. | ||||||||||||||||||||||
Active | Select this checkbox to make the script action active or inactive. | ||||||||||||||||||||||
Execution order | Specify the event script action execution order if there are more than one record for is more than one record for the related Event Register (sys_event_register) table. Actions are executed in ascending order. | ||||||||||||||||||||||
Script | The script is executed when the event is firedoccurs.
You can also update the parameters (Param_1...Param_ 5) of the event object with the Event Script Action.
|
Table of Contents | ||||
---|---|---|---|---|
|
...