Element path <cwt><CORE><dataCollection>
It is possible to store printed tickets, and receipts as bitmaps in the CWT database on the terminal.
It is possible to store aborted purchases data in the CWT database on the terminal.
attributes
storeAbortedCardTransactionsForRefund
| Description: | It is possible to store aborted card transactions in the CWT database on the terminal. The data can be sent to WebOffice and be used to refund card transaction when card transactions are acquired at validation.
true = enabled |
| Example: | This turns on storage of aborted purchases data: |
<CORE>
<dataCollection>
<purchaseData storeAbortedCardTransactionsForRefund ="true"/>
</dataCollection>
</CORE>
storeAbortedPurchases
| Description: | true = enabled |
| Example: | This turns on storage of aborted purchases data: |
<CORE>
<dataCollection>
<purchaseData storeAbortedPurchases="true"/>
</dataCollection>
</CORE>
storeMonetaryItems
| Description: | Used to store monetary items, typically the number of each coin denomination in a purchase, in the database in the CWT. The monetary items data can be sent to WebOffice. |
true = enabled.
| Example: | This turns on storage of monetary items data: |
<CORE>
<dataCollection>
<purchaseData storeMonetaryItems="true"/>
</dataCollection>
</CORE>
storeReceipts
| Description: | It is possible to store printed tickets and receipts as bitmaps in the CWT database on the terminal.
true = enabled |
| Example: | This turns on storage of ticket and receipt bitmap data: |
<CORE>
<dataCollection>
<purchaseData storeReceipts="true"/>
</dataCollection>
</CORE>
storeTickets
| Description: | It is possible to store printed tickets as bitmaps in the CWT database on the terminal.
true = Printed tickets are stored as bitmaps |
| Example: | This turns on storage of ticket and receipt bitmap data: |
<CORE>
<dataCollection>
<purchaseData storeTickets="true"/>
</dataCollection>
</CORE>
timeLimit
| Description: | The time limit attribute defines after how many days the saved data in the database should be considered “old” data and be removed with the CleanDatabase attribute (see SCHEDULE element for more information). |
The value specifies the number of days after which the data is purged from the database.
Warning:
Setting the time limit attribute to “0” removes ALL data from the database. To disable the attribute remove it from the configuration file.
|
| Example: | <CORE …="">
<dataCollection timeLimit="10">
</dataCollection>
</CORE> |
