Go to documentation repository
| Section | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Note | ||
|---|---|---|
| ||
The You must configure the Web.config config file configuration must be performed on the computer where it is planned you are going to work with the the Sweethearting report report. After making you make any changes in the to the Web.config config file, it is necessary to restart the Cassini Service utility.you must restart the Cassini Service. |
The Sweethearting module generates two events for each item: alarmStartTime and alarmFinishTime. If the event of adding an item to a receipt doesn’t occur between the alarm start and alarm end events, a sweethearting event is generated and included in the report.
To increase the time during which an item must be added to a receipt, change the value of the SweatheartingAddTimeoutMs key.
To change the time between checks of receipts, change the value of the SweatheartingReanalyzeTimeoutMs key.
To do thisYou can set the timeout between the sweethearting detector event and the POS event. If this timeout is exceeded, the sweethearting event will be added to the report. To set the timeout, do the following:
To change the time during which an item must be added to a receipt, set the SweatheartingAddTimeoutMs key
to the required value in milliseconds. The default
is 500
milliseconds.
| Info | ||
|---|---|---|
| ||
For example, if the time between the alarmStartTime and alarmFinishTime events is 1000 milliseconds, and you set 500 milliseconds in the SweatheartingAddTimeoutMs key, then a sweethearting event is generated if the event of adding an item to a receipt doesn’t occur within 1500 milliseconds from the alarmStartTime event. |
To change the time between checks of receipts, set the SweatheartingReanalyzeTimeoutMs key to the required value in milliseconds. The default is 900000 milliseconds.
Sweethearting events in the report are displayed from the date selected in the report parameters up to the current moment. Only the analyzed events are displayed.
An event is added to the report if:
All receipts that fail this check are deferred until the next check, after which, if they also fail, they are considered false.
The check runs once at a specific time interval, specified by the SweatheartingReanalyzeTimeoutMs key in the Web.config file and set to 900000 ms by default.
If the check runs longer than the specified SweatheartingReanalyzeTimeoutMs timeout, it starts immediately after the previous check completes.
| Tip |
|---|
The parameters of the Web.config file are described on the page XML file parameters reference guide. |