iPass Help
 
 
 

Event Actions

Available for: Windows clients, Mac OS X clients.

Event Actions enable you to configure automatic launching actions that will be executed when a connection event occurs. For example, you can set an event action to launch a mail application that is triggered by a change in network status, like the establishment of an Internet connection.

Event actions may come in these types (depending on your client version):

Type Action Will Run…
On Startup of User Interface When the client’s graphic user interface is opened.
Before Establishing an Internet Connection Before Open Mobile establishes a connection to the Internet.
Before Detecting the Internet on a New Connection After the Internet connection has been initiated but before the Internet connection is complete
After Establishing an Internet Connection After Open Mobile establishes a connection to the Internet. Note: Mac OS X clients support only this action type.
Before Establishing a VPN Connection After the VPN connection has been initiated but before the VPN connection is complete.
After Establishing a VPN Connection After the VPN is connected.
After Establishing a Corporate Network Connection After connecting to a Corporate Network.
Before Disconnecting a VPN Connection After the VPN has been disconnected but before the VPN disconnection is complete.
After Disconnecting a VPN Connection After the VPN has been disconnected.
Before Disconnecting an Internet Connection After an Internet connection has been disconnected but before the Internet disconnection is complete.
After Disconnecting an Internet Connection After Open Mobile disconnects from the Internet. Note: Only supported by Windows 1.4.1 and later clients for non-DSL connections.
When the User Cancels a Connection Attempt After the user cancels a connection attempt.
When User Exits the User Interface After Open Mobile is exited.

Action Settings

iPass runs as a 32-bit process to ensure event actions are supported on 32-bit and 64-bit machines.

The following settings apply to event actions.

Settings Description
Application Path Path of the selected application, script, or URL. Path supports Windows environmental variables, but these must be specified in the format $$ENV:<VARIABLE NAME>$$, where <VARIABLE NAME> is the name of the environmental variable. Examples, $$ENV:systemroot$$\system32, $$ENV:USERPROFILE$$, $$ENV:PROGRAMDATA$$ (on Windows Vista or Windows 7).
Executable File Name Name of the executable to be launched.
Arguments Applicable command-line arguments, if any.
Frequency Decide on the frequency at which the action should be executed: every time Open Mobile connects, once per day, or each time Open Mobile is started.
Run Context Specify system or user context for the action to run in.
Run Mode Wait: wait for the configured application to exit before establishing the connection.
Don’t Wait: don’t wait for the configured application to exit before establishing the connection.
Connection Type Event actions can be triggered on specified connection types.

Adding a New Event Action to a Profile

To add a new event action:

  1. Click Add New Event Action.
  2. In Action Name, enter the name of the action.
  3. In Description, type a short description of the application.
  4. In Application Path, enter either a local application path, or a complete URL (which will open in the end user’s default browser). Note (Environmental Variables): For Windows clients, Application Path supports Windows environmental variables, but these must be specified in the format $$ENV:<VARIABLE NAME>$$, where <VARIABLE NAME> is the name of the environmental variable. Examples, $$ENV:systemroot$$\system32, $$ENV:USERPROFILE$$, $$ENV:PROGRAMDATA$$ (on Windows Vista or Windows 7).
  5. In Executable File Name, enter the executable file name.
  6. In Arguments, enter any arguments the application needs to run. If there is more than one argument, separate them by space characters.
  7. In Event Type, select an event type.
  8. In At frequency of, select how often the event will be triggered.
  9. In Run Context, select a run context for the application (user or system context) from the drop-down list.
  10. In Run Mode, pick a run mode from the drop-down list.
  11. If available, select one or more connection types that the action will apply to, by selecting the corresponding checkbox for each. If you select Wi-Fi, you can also select particular Wi-Fi connection types.
  12. If you would like the Event Action to launch in a hidden window, select the checkbox next to Run Hidden.
  13. Click Save.

Event Sequence

The sequence in which actions of the same type will run is initially determined by the order that they were added to the profile.  However, if you have more than one action of the same type, you can re-define the sequence in which the actions are run. For example, if you define a set of three Post-Connect actions, you can choose which Post-Connect action to run first, which to run second, and which to run third.

To set the sequence of an event action:

  1. In the list of event actions, click Change Sequence.
  2. Actions are shown by type, in sequence from top to bottom. Select an action for which you wish to change the sequence. Using the arrow keys, move the action up or down in the sequence of actions for that type.
  3. Click Save.

For example, if you wished to change an action from second to first, select the action numbered 2 and drag it to the row of the action numbered 1.

Create a New Profile > Configuration Settings > Integration

,
 

©2015 iPass Inc. All rights reserved. Terms of Use