User Field Persistence

When Payment Repair validates operator input, it can pass the updated item data to the Business Rules Server. The Business Rules Server validates and updates the item and returns these results to Payment Repair. When the Business Rules Server finds the item to be valid, Payment Repair saves these results and advances to another item. When the updated item is not valid, Payment Repair presents the item to the operator again for further correction. Under the operator’s control, Payment Repair then validates the revised operator input.

Sophisticated Business Rules Server workflows may need information about previous validation attempts to control item validation in the Business Rules Server. Since Payment Repair uses pools of Business Rules Server connections, it must save such information and provide it with subsequent validation requests. To accomplish this, Payment Repair saves information returned by the Business Rules Server. All returned user fields are saved. This information is saved in the Payment Repair HTTP session. Payment Repair discards the information if:
  • The operator moves on to another item
  • The operator logs out
  • The HTTP session times out

When the operator inputs and validates updated item data, Payment Repair supplies any saved user fields along with the item data to Business Rules Server. This allows the Business Rules Server workflow to return user fields that are available in immediately subsequent validation decision attempts by the same operator for the same item.