Overview of System Actions

When designing your eSpace, you can use System actions that are predefined by Service Studio. These action can also be called system actions.

System actions have the characteristic of being executed automatically by Platform Server, as described below. However, they can also be executed explicitly, just like any user-defined action.

The available system actions are:

OnSessionStart: executed when the session is created by Platform Server. How?
OnDeliveryReport: executed when a delivery report is received from the SMS gateway. How?
OnMobileOriginatedMessage: executed when the eSpace receives an SMS. How?
OnMobileTerminatedMessage: executed when the eSpace sends an SMS. How?

How to Use a System Action:

Right-click on the Resources folder at the eSpace tree;

Design the behavior of the system action in the Action flow (Collection of elements that graphically implements the behavior of an action. You can have assign and control elements, exception handlers or you can invoke other actions. The elements are linked through Connectors.), through a specific editor.

A system action can have:

Input parameters: instantiated automatically by Platform Server. You don't have to handle them.
Output parameters: you can access the output parameters of a system action in the same way you access the output parameters of any action. How?

Executing a system action

If you want to explicitly execute a system action, simply drag it from the User Actions folder, at the Tools tree, and drop it in your action flow.