An Event Activity is the execution of an activity when an event occurs on specific devices, group of devices or classes of devices. When an activity is associated to a group/class of devices, the command will be applied to all the devices belonging to that group/class at the moment of the activity execution.
Event Activities are shown in the ThinMan Console interface under the Event Activities on the tree Area panel.
Scheduled and Event Activities:
You can create an event activity that is triggered by an scheduled activity. E.g. if you need to update Agile. You can create an scheduled activity to startup the devices at 6:00 a.m. and then an event activity to update Agile on the startup event.
The table below shows the available commands depending on the device O.S.
| Command | Event | Notes | |
|---|---|---|---|
| ThinOX ThinOX4PC |
Update (firmware, also to install Add-Ons) | Shut Down Reboot |
For more information read ThinOX Firmware Update |
| Custom Command | ThinMan Login ThinMan Logout ThinMan Notify |
A custom command is a specific command file that Praim provides to customers in need of a particular configuration. For more information read Custom Command Repository | |
| Praim Windows 10 IoT | Update (Praim Update/Praim Service Pack/Hotfix/Agile Update) | Startup | For more information read Praim Update, Praim Service Pack, Praim Hotfix Installation |
| Update(Third-party Software Installation) | Startup | When installing a third-party software, additional parameters might be asked to insert. Be sure that the installer can run in silent mode For more information read Third-party Software Installation |
|
| Apply Device Image | Startup | It allows to automatically apply a Device Image or a Device Backup Image For more information read Capture and Apply Windows Image. |
|
| Agile4PC | Update (Agile Update) | Startup | For more information read Agile Update |
| Update(Third-party Software Installation) | Startup | When installing a third-party software, additional parameters might be asked to insert. Be sure that the installer can run in silent mode For more information read Third-party Software Installation |
|
| Check for and install Windows updates | Startup | For more information read Automatically Check for and Install Windows updates. | |
| Set automatic Windows updates | Startup | For more information read Activate/Deactivate automatic Windows updates. |
¶ Adding an Event Activity
Right-click on the Event Activities tree and select Add... from the contextual menu.
Select the activity from those available on the list and follow the wizard to complete the definition of the event activity.
¶ Managing an Event Activity
An Event Activity can be enabled or disabled, modified or deleted.
Right-click on the activity and select one of the following operation:
- Activity Enabled: when selected(with the mark) it indicates the activity is enabled otherwise it is disable.
- Move Up or Move Down: to change the priority of the activity by moving one position up/down.
- Delete: to remove the activity.
- Properties: to edit the activity properties.
When selecting an activity of the tree (left panel), the list of all devices associated to the activity will be shown in the working area of the ThinMan console.
The Details Window shows all the parameters of the selected activity.
¶ Properties of an Event Activity
¶ Activity tab
This tab contains:
- The name and description of the activity.
- The type of activity, which is decided at the beginning of the activity creation and cannot be modified.
¶ Action tab
It shows the command to be executed by the activity.
The parameters shown on this tab depends on the type of Action configured. On the example below (update activity), the "Models" list shows the device models present in the network that are compatible with the update package. It is possible to select only certain models to be updated.
¶ Event tab
It shows the event that triggers the activity. In the example below, the event is the device's startup. The events listed in this window depend on the activity type.
¶ Time tab
It allows to define the time interval when the activity can be executed. In the example below, from 8 PM to 6 AM are, an event that occurs outside this interval will not start the action.
The Always On option will always start when the event occurs.
¶ Classifier tab
It allows to associate the activity to certain classes. The activity will be applied to the devices beloning to those classes.
For more information on classifier see Classifier.
¶ Group tab
It allows to associate the activity to certain device groups. The activity will be applied to the devices belonging to those groups.
For more information on groups see Group Properties.
¶ Devices tab
It allows to associate the activity to certain devices.
Every device associated with these last tabs to the action will be used by the action when the event occurs.
¶ Condition tab
It allows defining whether the activity has to be:
- Apply only once on each device: this is particularly useful when updating. The update will be applied only once on each device.
- Apply only to new devices (currently not listed on ThinMan): when associating an event activity to groups/classes, it will be applied only to the devices that were not listed on the group/class the moment the event activity was created.
- Apply only to devices with Device Profile Status "Applied": when the devices associated to the activity are under a Device Policy that applies a Device Profile, the activity will be executed on the devices that have already been configured.
¶ Classify devices depending on activity result
When creating an Event Activity, it is possible to select the option "Use automatically generated classes and values" (see image below).
When selecting this option, a class will be created in the Classifier with the name of the activity with the following values:
- TO-DO: All devices selected for the activity will be classified as "TO-DO".
- SUCCESS: All devices that completed the Scheduled Activity successfully will be classified as SUCCESS.
- NOT-SUCCESS: All devices that did not complete the Scheduled Activity will be classified as NOT-SUCCESS.
Note that, when opening the properties of an already created event activity (right click on the event activity to access the contextual menu) the conditions tab will look like the image below.
¶ Examples
¶ Updating ThinOX on Shutdown or Reboot
To create an activity of this type you have to:
- Add an activity of type Update
- Select from the Package Repository a ThinOX firmware package. Be aware, the Update Event Activity does not perform to downgrade.
- Assign a name to this activity (e.g. "update_thinox_1162"),
- Select the event that triggers the activity: Device Shut Down (or Device Reboot),
- Set a time-slot in case it is necessary. E.g. the device can be updated outside working hours (e.g. from 11:00p.m. to 6:00 a.m.)
- Associate the event activity to specific classes, groups or devices .
- Conditions:
- By default, the Apply Once option is already selected, in this way the update will happen only once.
- Select the "Use automatically generated classes and values" to track the result of the activity. It will be created a class under the classifier tree with the same name of the event activity including 3 class values: TO-DO, SUCCESS, NOT-SUCCESS.
Once the activity is defined, when a device associated to the activity is powered off, the device will be updated automatically right before the shutdown.
¶ Updating Agile on Startup
The Update Event Activity can also be used to execute a command or PowerShell file (*.bat, *.ps1) on a device.
To create an activity of this type you have to:
- Create an activity of type Update.
- Select from the Package Repository the installation package. Be aware, the Update Event Activity does not perform to downgrade.
- Assign a name to this activity (e.g. "update_agile_2910").
- On the Action tab, section "Apply to Models", it is possible to select specific models to apply the update.
- The only Event that triggers the update is Startup.
- Set a time-slot to update the devices outside working hours. E.g. from 11:00 p.m. to 6:00 a.m.
- Associate the event activity to specific classes, groups or devices.
- Conditions:
- By default, the Apply Once option is already selected, in this way the update will happend only once.
- Select the "Use automatically generated classes and values" to track the result of the activity. It will be created a class under the classifier tree with the same name of the event activity including 3 class values: TO-DO, SUCCESS, NOT-SUCCESS.
Once the activity is defined, when a device associated to the activity is powered on, the device will be automatically updated.