Business Logic Layer

The business logic layer of an eSpace implements the behavior of the eSpace, through elements called Actions. An action must be parameterized according to the conditions that lead to its execution.

The element types in the business logic layer are:

Action: Implements a specific behavior.
Variable: Writable element in the scope of your screen or of your action that holds non-persistent data. See About Variables.
Parameter: Used to exchange information between Screens and Actions.

Action

In Service Studio, actions can be built-in or user-defined. Examples of built-in actions are: Login, Logout, and Commit Transaction. The behavior of the built-in actions is not accessible and you cannot change them. See Overview of built-in actions.

To develop your user-defined actions, Service Studio provides a specific editor that can be used to graphically code them. The graphical representation of a user-defined action is called an Action flow. See Overview of building actions.

An Action flow has the following elements:

Action elements: Control statements, invocation of other actions (built-in or user-defined) and exceptions handlers.
Connectors: These represent the sequence of execution.

Besides being built-in or user-defined, actions have an orthogonal classification:

Screen actions: Actions that only exist in the scope of the Screen where they were created.
Actions: Actions that exist independently of the screens and that represent business logic that is reusable in all the eSpace, either in other action flows or in any expression (as long as they're defined as user functions).