Product Documentation

Automated Actions

Mar 09, 2015
You create automated actions in XenMobile to program a reaction to events, user or device properties, or the existence of apps on user devices. When you create an automated action, you establish the effect on the user's device when it is connected to XenMobile based on triggers in the action. When an event is triggered, you can send a notification to the user to correct an issue before more serious action is taken.

For example, if you want to detect an app that you have previously blacklisted (for example, Words with Friends), you can specify a trigger that sets the user's device out of compliance when Words with Friends is detected on their device. The action then notifies them that they must remove the app to bring their device back into compliance. You can set a time limit for how long to wait for the user to comply before taking more serious action, such as selectively wiping the device.

The effects that you set to happen automatically range from the following:
  • Fully or selectively wiping the device.
  • Setting the device to out of compliance.
  • Revoking the device.
  • Sending a notification to the user to correct an issue before more severe action is taken.
Note: Before you can notify users, you must have configured notification servers in Settings for SMTP and SMS so that XenMobile can send the messages, see Notifications in XenMobile. Also, set up any notification templates you plan to use before proceeding. For details on setting up notification templates, see To create or update notification templates in XenMobile.
This topic explains how to add, edit, and filter automated actions in XenMobile.
  1. From the XenMobile console, click Configure > Actions. The Actions page appears.


    Select actions

  2. On the Actions page, do one of the following:
    • Click Add to add a new action.
    • Select an existing action to edit or delete. Click the option you want to use.
      Note: When you select the check box next to an action, the options menu appears above the action list; when you click anywhere else in the list, the options menu appears on the right side of the listing.


      Edit action


      Edit action

    The Action Information page appears.


    Add actions page 1

  3. On the Action Information page, enter or modify the following information:
    1. Name: Type a name to uniquely identify the action. This field is required.
    2. Description: Describe what the action is meant to do.
  4. Click Next. The Action details page appears.
    Note: The following example shows how to set up an Event trigger. If you select a different trigger, the resulting options will be different from those shown here.


    Action details page

  5. On the Action details page, enter or modify the following information:
    1. In the Trigger list, click the event trigger type for this action. The meaning of each trigger is as follows:
      • Event: Reacts to a predefined event.
      • Device property: Checks for a device attribute on the device gathered in MDM mode and reacts to it.
      • User property: Reacts to a user attribute, usually from Active Directory.
      • Installed app name: Reacts to an app being installed. Requires the app inventory policy to be enabled on the device. The app inventory policy is enabled on all platforms by default. For details, see To add an app inventory device policy.


      Action trigger

    2. In the next list, click the response to the trigger.


      Select trigger response

    3. In the Action list, click the action to be performed when the trigger criterion is met. With the exception of Send notification, you choose a time frame in which users can resolve the issue that caused the trigger. If the issue is not resolved within that time frame, the selected action is taken.


      Event action

      The remainder of this procedure explains how to send a notification action.

    4. In the next list, select the template to use for the notification. Notification templates relevant to the selected event appear.
      Note: Before you can notify users, you must have configured notification servers in Settings for SMTP and SMS so that XenMobile can send the messages, see Notifications in XenMobile. Also, set up any notification templates you plan to use before proceeding. For details on setting up notification templates, see To create or update notification templates in XenMobile.


      Select notification template

      Note: After you select the template, you can preview the notification by clicking Preview notification message.
    5. In the following fields, set the delay in days, hours, or minutes before taking action and the interval at which the action repeats until the user addresses the triggering issue.


      Select delay and repeat interval

    6. In Summary verify that you created the automated action as you intended.


      Add action summary

    After you configure the action details, you can configure deployment rules for each platform individually—iOS, Android, Windows 8.1 Tablet, Windows Phone 8.1, and Symbian. To do so, follow steps 6 through 9 for each platform you choose.


    Deployment rules by platform

  6. Expand Deployment Rules. The Base tab appears by default.


    Deployment rules

    1. In the lists, click options to determine when the action should be deployed.
      1. You can choose to deploy the action when all conditions are met or when any conditions are met. The default option is All.
      2. Click New Rule to define the conditions.
      3. In the lists, click the conditions, such as Device ownership and BYOD, as shown in the preceding figure.
      4. Click New Rule again if you want to add more conditions. You can add as many conditions as you would like.
    2. Click the Advanced tab to combine the rules with Boolean options.


      Advanced deployment rules

      The conditions you chose on the Base tab appear.
    3. You can use more advanced Boolean logic to combine, edit, or add rules.
      1. Click AND, OR, or NOT.
      2. In the lists that appear, choose the conditions that you want to add to the rule and then click the Plus sign (+) on the right-hand side to add the condition to the rule.

        At any time, you can click to select a condition and then click EDIT to change the condition or Delete to remove the condition.

      3. Click New Rule again if you want to add more conditions.

        In this example, the device ownership must be BYOD, the device local encryption must be True, the device must be passcode compliant, and the device mobile country code cannot be only Andorra.

        Advanced deployment rules

  7. When you are done configuring the platform deployment rules for the action, click Next. The Actions assignment page appears, where you assign the action to a delivery group or groups. This step is optional.
  8. Next to Choose delivery groups, type to find a delivery group or select a group or groups in the list to which you want to assign the policy. The groups you select appear in the right-hand Delivery groups to receive app assignment list.


    Policy assignment page

  9. Expand Deployment Schedule and then configure the following settings:
    1. Next to Deploy, click ON to schedule deployment or click OFF to prevent deployment. The default option is ON. If you choose OFF, no other options need to be configured.
    2. Next to Deployment schedule, click Now or Later. The default option is Now.
    3. If you click Later, click the calendar icon and then select the date and time for deployment.
    4. Next to Deployment condition, click On every connection or click Only when previous deployment has failed. The default option is On every connection.
    5. Next to Deploy for always-on connection, click ON or OFF. The default option is OFF.
      Note: This option applies when you have configured the scheduling background deployment key in Settings > Server Properties. The always-on option is not available for iOS devices.
    Note: The deployment schedule you configure is the same for all platforms. Any changes you make apply to all platforms, except for Deploy for always on connection, which does not apply to iOS.


    Deployment schedule

  10. Click Next. The Summary page appears, where you can verify the action configuration.
    Add actions summary page

  11. Click Save to save the action.