An exception is a way of escalating to the user when a particular situation arises within the running of a process.

For example, an exception is raised if the system is unable to connect to a remote server to download important data, or if no resource is available to pick up a particular job.

You can handle an exception by assigning a process map as an escalation process. For example, configure an Insurance Premium Policy process to automatically send an email if customers do not submit their insurance premiums by the due date.

TotalAgility provides predefined exception-handling codes. Each exception code is a placeholder for a particular type of exception (process map). You can use these processes in your map to address unexpected events, such as throughput, capacity and workload changes, without manual intervention or process termination.

You must create the process map to run whenever the exception code is called. For example, the exception code EXP0001 is called whenever a resource has been inactive for an excessive period of time.

Some of the most frequently used examples of exceptions:

  • EXP0013—Activity Due: Triggers whenever an activity due date is passed.

  • EXP0005—Job Duration Overrun: Triggers whenever a user takes longer than expected to complete a job.

The maps associated with predefined exception codes belong to the following categories.

  • Workload exception maps: These maps can handle business exceptions, such as costing or timing that run outside normal business tolerance, such as job duration overrun or activity overdue.

  • System fail exception maps: These maps run when some element of the system process fails. For example, if a connection cannot be made to a remote server to download information, or if a script object fails to execute.

    You must assign variables as initialization parameters to track the source of an exception. See Exception maps and initialization parameters.

You can configure exception handling at the server level. See Configure exception handling at the server level.

A map assigned to an exception at the server level is, by default, assigned to that exception at the process level. You can override the default process map and select a different map for the exception. See Configure exception handling for a process.

For more information on exception handling, refer to Business calendar in Kofax TotalAgility Best Practices Guide.