This section contains information for the following part of the toolbox in the Automation Creator:
Device did not start
As the name suggests, this block only activates, if a device does not start. This can be used in combination with other items in the toolbox. For example, you can send an alert to an email address, if a device did not start. This use case could look like this:
Instead of sending an email, the toolbox also provides other actions that can be performed, if required.
Finally
Finally is always executed no matter what happens beforehand. For example if there is an if-loop it either executes if or else, then it executes finally, no matter the previous outcome.
A finally statement could be used, for example like this: Here we send an email when an error occurs, and creates and executes a file when it succeeds. Finally reboots the device, no matter if there occured an error or not.
The next example automation patches the devices. If a patch takes too long on a device and is therefore cancelled, finally makes sure the reboot is still being done afterwards. Finally always happens, even when the runtime is out.
On Error
Executes an action when an error is thrown. In the previous example, an email gets send, upon occuring an error.
On Success
Does the opposite of On Error. It triggers only when there is no error thrown.
Summary
Summary triggers after the Automation is is done on all devices it is running on. It then gives a summary of the devices and the automation. The most common use of action is to send an email with the summary, by selecting the send email box from the toolbox, but other actions are possible.
In the email block, additional text should be entered, but as long as it’s in the event block, the email automatically adds the summary to the email text.
