1.2.2 Non-Functional Features

This topic provides the information about the non-functional features added to the product in this release.

Plato Batch Framework Adoption

The Plato Batch framework is used for specific tasks, including future dated disbursements, auto-debit transactions, invoice and purchase order acceptance, retrying finance transactions, reconciliation transactions, and processing refunds. This framework offers extra configuration options for running batch jobs, such as commit frequency, stream size, and skip policy.

Plato Archival Adoption

The Plato Archival framework has been implemented for event logs in Finance service for archiving and purging the logs based on configuration.

Plato Field Configuration

A new service is introduced to provide the capability to make user interface extensible. This includes the ability to hide/show fields, enable/disable switches, set default values, or make non-mandatory fields as mandatory.

Customer Address Length Correction

Customer addresses have been enhanced to incorporate structured and unstructured fields. Shipment addresses for invoice and purchase orders have also been enhanced in line with address fields across the application.

New Business Process Maintenance Adoption

The new business process maintenance user interface is adopted to create and define Domain Specific Language work flow.

Common Core Enhancements

Additional fields have been brought into common core for OBMA based products inline with ODT common core.