Client Actions

Client Actions can define a set of actions executable by the client in the following scenarios:

•User clicks a button or selects an option within the displayed page resulting in a request being sent to the server. For example, user clicks Next or Click to Continue.

•User clicks a button or selects an option, invoking a local client method. For example, initiate a call, send email or open a camera.

•Enables invoking Remote Functions in an end-unit.

An example is where a server instructs the client to go back to the “Cover App” when a script is done.

In some cases, the server can directly call an action without user intervention (invocation). For example, when a script reaches its end, the server automatically sends a Back to Cover Application command, resulting in closing the Interaction.

The clientAction element structure is as follows:

<xs:element name="clientAction">

   <xs:complexType>

      <xs:sequence>

         <xs:element name="action" type="xs:string"/>

         <xs:element name="delayMillisecond" type="xs:long"/>

      </xs:sequence>

   </xs:complexType>

</xs:element>

The action is defined as a URL scheme, with the following definitions:

•URI Scheme Function—Provides the parameters defining client actions.

•Server Request Functions—Provides server navigational functionality.

•Local Functions—Provides client request functions.