Manuel sending of documents

The "mandatory billing measures" of the province of Québec requires a function which triggers the manuel sending of transactions to the WEB-SRM system after offline situations.

This is also checked in test case FO-105 of SW-78 (Test Cases for SRS developers: Proof of compliance).

During regular use the RetailForce Fiscalisation Service automatically tries to send all unsent transactions, as a batch, at each document it receives from the upstream system.

Process

1. upstream system sends document payload to the RetailForce client but internet connection is not available;
2. client tries to send the "transaction" request concerning the transaction to WEB-SRM,
   1. as this fails it switches to offline-mode and
   2. adds the document to the batch of unsent transactions;
3. upstream system sends next document payload, internet connection is still down;
4. client again tries to send the "transaction" request to WEB-SRM,
   1. if it fails again is continues in offline-mode and 
   2. again adds the document to the batch of unsent transactions,
   3. Steps 3. and 4. are repeated until the internet connection is available at sending;
5. internet connection is available again,
6. upstream system sends next document payload, and internet connection is available again;
7. client sends all unsent transactions as a batch to WEB-SRM;

In case that the internet connection is available again but no transactions are being sent afterwards to the RetailForce client, the batch of open transactions also remains unsent.

This means, that when there is a disruption between step 5 and 6 a manual transmission of the documents must be initiated.

A manual transmission can be triggered via the Endpoint: POST /api/v1/management/canada/sendQueuedDocuments/{clientId}. Details are explained in the linked article.