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):

<note important>iPass runs as a 32-bit process to ensure event actions are supported on 32-bit and 64-bit machines.</note>

+

+

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$$<nowiki>\</nowiki>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. |

- 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).

+

- In **Executable File Name**, enter the executable file name.

+

- In **Arguments,** enter any arguments the application needs to run. If there is more than one argument, separate them by space characters.

+

- In **Event Type**, select an event type.

+

- In **At frequency of**, select how often the event will be triggered.

+

- In **Run Context,** select a run context for the application (user or system context) from the drop-down list.

+

- In **Run Mode,** pick a run mode from the drop-down list.

+

- 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.

+

- If you would like the Event Action to launch in a hidden window, select the checkbox next to **Run Hidden**.

+

- 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:**

+

+

- In the list of event actions, click **Change Sequence.**

+

- 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.

+

- 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.