Manage Exceptions

Service Studio allows you to manage errors or exceptional conditions that can occur in your eSpace. This is accomplished through the use of exceptions. An exception, by definition, causes an interruption in the execution of the flow.

Raising Exceptions

There are two ways how exceptions are raised: exceptions automatically raised by the platform due to system error conditions and exceptions explicitly raised by the developer on specific business conditions. To raise an exception use the Raise Error element 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.) where you want to raise the exception.

The exceptions are divided into exception types, of which, one is special: the User Exceptions.

User Exceptions

A User Exception is one type of exception that allows you to add your own exceptions to your application. This is very useful to specifically raise an exception according to your application logic, as well as, to design specific handling flows for that same raised exception. Learn more about User Exceptions.

Handling Exceptions

The exceptions raised in your eSpace are handled in a screen flow (Collection of objects that define the user interaction; you can have screens, entry points, external sites, etc, depending on the type of your flow. The objects are linked through Connectors.) or in an 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.) by the Error Handler. How

When an exception is raised, the current execution flow is aborted. The flow restarts in the Error Handler element that handles that exception.

In Agile Platform, there is a hierarchy associated with exceptions. An exception can be raised in any point of your eSpace. If, in the current flow, there is no Error Handler that handles that exception or any parent exception, the exception is transferred to the caller flow and successively. If there is no Error Handler at all, your application aborts and the end-user will get a generic error.

This is why you should have, at least, one Error Handler in your eSpace flow that smoothly handles all the exceptions, providing a friendly message to the end-user. How