The Kofax AP Agility user exit framework provides extension points that enable you to plug in custom business logic to various actions. For example, this includes custom validation logic, modifying loaded data such as vendor addresses or purchase orders, or modifying data before export.

1. User exits can be implemented in a custom .NET assembly that is supported for all user exits.

   1. The assemblies for extraction can either be deployed

      1. into the Global Assembly Cache (GAC) that is supported by on-premise environments only.

      2. added to the extraction group which is supported by on-premise, OPMT, and Azure environments.

   2. Assemblies for validation, line pairing, and export must be deployed to the GAC. As a result, these user exits are not supported in multi-tenant or Azure environments.

2. As an alternative, a selected subset of user exits can be implemented as Kofax TotalAgility business rules. These business rules are supported by on-premise, OPMT, and Azure environments.

If an on-premise installation uses a mix of implementations where the user exit is registered in code and there is a user exit business rule, and there is a conflict, the code implementation is given priority.

Depending on your environment, different options are available:

• User exits in on-premise environments

• User exits in all environments including OPMT and Azure