Notifications
Complete the following steps to generate the Notifications
1. The Notifications page will appear after Asset Information.
 |
To send notifications about deployment status, you need to have the Mail Extension installed and configured.
|
2. Sending notifications to users, user groups, or email address is an optional step. Complete the following steps to send notifications:
a. Under the Notification Recipients section, depending on your requirement, do the following:
▪ Click the Enable error notification check box to send an error notification to the selected users, user groups, or email addresses.
▪ Click the Notify people below when deployment to all assets has finished to send a notification to the selected users, user groups, or email addresses when deployment completes.
b. Under the Notify User, Notify User Groups, or Notify These Email Addresses sections, complete the following steps to select the user, user group, or email address that you want to receive notifications about package deployment:
i. Click 
to search for and select users, user groups, and email addresses.
to search for and select users, user groups, and email addresses.ii. Click 
to add the user, user group, or email address to the appropriate list.
to add the user, user group, or email address to the appropriate list.Alternatively, if you do not want the selected user, user group, or email address to receive a notification, select it from the appropriate list, and click 
3. Once you have confirmed that the deployment is configured correctly, click Start. The Track Deployment By Package page appears. For more information about tracking deployments, see Track Package Deployment.
| | On each SCM-capable thing, the maxConcurrentUpdatesproperty controls how many concurrent updates a thing can process. By default, this property is set to 1. If a deployment is attempted for an asset and it exceeds the value of the maxConcurrentUpdates property, that deployment will be in the Pending state until it can proceed. To set the number of concurrent deployments that an agent can handle, login to the ThingWorx Composer and update the value of the maxConcurrentUpdates property. Regardless of the value of this property, deployments take place within the threshold of the capability of the agent. |