The client-side external user exits are designed to give implementers flexibility and power to extend the user interface of a OUAF products. Implementers have the ability to add additional business logic without changing OUAF product HTML files. These user exits were developed such that developers can create an include-like file based on external user exit templates.

There are two types of client user exits available. There are process-based user exits that wrap the similar product user exit code with pre- and post- external user exit calls, and there are also data-based user exits that simply allow the implementer to add/delete data from the product returned data.

Both types of external user exit are only called if the function exists in the implementers external include JSP file. All available user exits are listed online in the system through the relative URL: /code/availableUserExits.jsp, with definition examples and links to the framework code that executes the call.

The location of the external JSP file is the \cm directory under the web application root directory:

This document assumes that you are familiar with the framework architecture and its UI program component templates (XSLT) and that you know how the base exits work. It also assumes that you are proficient in JavaScript and HTML.