Payment Validation Rules

Business Rules supports a process referred to as payment validation rules (PVR). It is collaboration of database tables and workflows. The database tables are managed by the Business Rules user interface, described in Business Rules user interface. The workflows and tables are used by the Business Rules Server to power the decision process. The Business Rules Manager performs the merging of the workflow (XMLs) and the database table during the activation process. This chapter describes the workflow and the nodes that configure the PVR process.

The PVR workflow requires that the normalized payment fields be used; these are described in Normalized Payment Record. For each decision request, the client application (either through use of the Business Rules API’s transformation features or its own transformation mechanism) must send a set of IBM® normalized payment fields to the Business Rules Server.

In effect, only one set of tables is used for all workflows. The workflow can be modified to behave differently for each type of work. For details about the workflow XML layout, see Workflow Setup.

For example, an in-clearing workflow is not expecting to receive credit items. If a credit item is detected, the workflow should specify that the item be marked with a specific record ID and be rejected. Other examples of this kind of workflow control would exist for transit items.

It is not possible to create connections between nodes for all conceivable circumstances. As a result, a predefined set of connections is available for standard processing, and a set of user exits may be used to control more complex rerouting of the workflow.