Business Rules Server API
The Business Rules Server allows all the applications within the system of a financial institution to have a single decision point on which to call. It provides support for requests from multiple input channels across the system. These channels include high-speed check sorters, existing check applications, ATMs, corporate capture, and tellers.
The Business Rules Server uses customer-defined tables and customer-defined business rules to build a response to the calling application. If the Business Rules Server is asked a question, it gives an answer, being responsive to how the client wants its system to work. The calling application uses the Business Rules Server response to perform a particular action.
This concept can also be explained by using an example of an ATM and a sorter application, both running the same item for the same work type through Common Services. Both applications get the same response from the Business Rules Server, though their handling of the response may be different.
- Provides a single point of data management and control across the Common Services environment for tables, user exits, workflows, nodes, and other configuration data.
- Provides integrity and validation checking for customer data by
performing the following tasks:
- Compares XML-based customer configuration data with the appropriate Business Rules Server schema.
- Validates customer table data using the associated XML table descriptor. This validation verifies the file contents by reviewing attributes to verify requirements such as checking to see if a file size is a multiple of the record length and if keys are unique and in ascending order.
- Passes the attributes of each customer data file sent to the Business Rules Server application to a customer user exit, along with attribute information from previous versions of the file. Customers can then perform content checking against the file (for example to verify that the record count is within the expected range).
- Verifies that each customer table record has a unique key and
the keys are in ascending order.
Note: Duplicate record checking extends only to the record key.
- The client application determines how the Business Rules Server processing flow is used. The flow determination consists of data such as site identification, sort types, payment origination (check, ATM). The processing flow can be overridden by customer code running on the Business Rules Server.