Basic technology

One part of the OfficeLine 3.5 server is a special table reserved for the storing of copies of recurring transactions such as so-called persistent messages. Upon its being received, the recurring transaction is thus saved in the table of received messages and later copied into the table of persistent messages. The bank can itself select the type of messages which will be processed in this way.
The table of persistent messages can be updated using the following methods:
 Manually, through any distribution channel; the client enters a new recurring transaction or, as the case may be, changes or cancels an existing transaction.

  Automatically, in the off-line regime; the server reads data from the import file generated by the banking system.

  Automatically, in the on-line regime; the server continuously updates the table by sorting data from the banking system.
Automatic updating requires implementation of a corresponding interface (file interface for batch updating, or customer on-line interface, established on the XML format, for example). Persistent messages can then be delivered to any other system via the implemented interface.
Messages saved in the table of persistent messages are not archived – they figure in the OfficeLine database as long as they are not deleted.

User interface

For working with the table of persistent messages, the same operating elements are available (on the OfficeLine server or, more precisely, at the workstations) as those for use in the case of the table of received messages.
Individual distribution channels enable the use of configurable user interfaces for working with persistent messages (the configuration possibilities depend on the specific technology). Among the configuration possibilities of these interfaces can be found, for example, a choice of filters by which the offer of accessible views of recurring transactions is provided.

Compatibility

Processing messages as persistent generally does not require modification of the form. Using the table of persistent messages, the bank can administer earlier well-established types of transactions.
Once the service is set up, the table of persistent messages can be filled out:
 on the basis of the entry of a new transaction by the client,

 by the acceptance of data (already existing recurring transactions) for the banking system.
The client applications (OfficeLine 2.5 – Client, OfficeLine 3.0 – Client and OfficeLine 3.1 Corporate Banking) do not include a special table for persistent messages. Here messages – entry of recurring transactions, their changes or cancellations – will be stored in the table of sent messages and archived according to the established regulations.

24/7 Regime

With a view to the maintenance of persistent messages in the OfficeLine table, summaries of recurring transactions and operations with these transactions can be made accessible to the client in the off-line regime, even in a period of inaccessibility of the banking system (in a period of inaccessibility of the banking system, OfficeLine processes client requests using only its own databases). Summaries of recurring transactions are thus continuously accessible to clients.

Synchronization with the banking system

Synchronization of recurring transactions (persistent messages, requests to change or cancel recurring transactions, etc.) with the banking system depends on the capabilities of the banking system and its interface.