1.2.3 Technical Changes

Plato Archival Adoption (Non Business Tables)

Plato archival is being enabled for non-business tables (e.g., logging and audit tables) in the SCF domain via the integration of plato-archival-core. This provides archiving and purging capabilities for large volumes of historical data, improving system performance and data management.

Plato Rule & Configuration Screens (Maker Checker)

The Plato Rule and Configuration screens have been enhanced and converted to maker-checker screens. This introduces a formal approval workflow for changes. As part of this update, technical changes have been implemented in SCF to adopt the enhanced rule service, ensuring proper handling of rule creation, modification, and approval.

Display Product Version & Environment Name (UI/Logs)

A new change has been introduced to display the product release version and environment name in the UI and logs. This ensures that version information is verifiable, tenant-aware (for cloud deployments), and standardizes environment naming conventions across all deployment models.

Resiliency Parameters – Adding JVM arguments for Services

Added support to configure and apply additional JVM arguments at the service level, enabling more flexible tuning of runtime behavior and resiliency settings without requiring code changes.

Enhancements to workflow Audit date/timestamps

Workflow auditing has been enhanced to provide more consistent and accurate date/time capture and display for key workflow events. This improvement makes it easier to trace execution, monitor workflows, and support operational troubleshooting.

Plato Batch Framework Adoption

The Plato Batch framework has been adopted for certain End-of-Day processes, such as, Stale Invoice, Overdue Invoice, Non-performing Asset, Product Expiry, Program Expiry, Limit Structure Refresh, Limit Structure Expiry, Pre-EOD, Outstanding Transactions, Modify Contract, Batch Charges, PO Charges, Alerts.