The logic of your eSpace is implemented through Actions. Actions are coded into an action flow, where you can use control tools, queries, etc. The flow of an action is defined by using a specific editor.

In Service Studio, you can have:

• Screen Actions: Actions associated with a screen that reacts to the feedback from the end-user. How?

• Screen Preparation: Actions executed before the rendering of the screen. How?

• User-defined actions: Actions defined by the end-user available in any flow or expression (in a case where they're defined as functions) of your eSpace. How?

See Also

Design Actions | Action Flow Editor | Use an Action Reference | Find and Replace Action Usages