Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width50%
Panel
borderColor#CCCCCC
bgColor#FFFFFF
titleBGColor#F0F0F0
borderStylesolid
titleOn the page:

Table of Contents


Column




Note
titleImportantAttention!

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 you must restart the Cassini Service utility.

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.

Change the periods for adding an item to a receipt and between checks of receipts

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: 

  1. Go to the <Axxon PSIM installation directory>\Modules\Wt2.
  2. Open the Web.config file for editing.For the 
  3. To change the time during which an item must be added to a receipt, set the SweatheartingAddTimeoutMs key

  4. specify
  5. to the required value in milliseconds. The default

  6. value
  7. is

  8. 500 (
  9. 500 milliseconds

  10. ).
    Image RemovedSave the changes in the Web
  11. .

  12. config file.

  13. Info
    titleNote

    For example, if the time

...

  1. between the alarmStartTime and alarmFinishTime events is 1000 milliseconds, and you set 500 milliseconds in the SweatheartingAddTimeoutMs key

...

  1. , then

...

  1. a sweethearting event

...

  1. is generated if the event of adding

...

  1. an item to a receipt doesn’t occur within 1500 milliseconds from the alarmStartTime event.

  2. To change the time between checks of receipts, set the SweatheartingReanalyzeTimeoutMs key to the required value in milliseconds. The default is 900000 milliseconds.

    Image Added
  3. Save changes to the edited Web.config file.

Analysis of the sweethearting events

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:

  • The receipt contains the receipt start and receipt end functions, the numbers of which you can specify in the Web.config file in the SweatheartingBeginReceiptPosFunctionNumber and SweatheartingEndReceiptPosFunctionNumber keys, respectively. See Filtering the sweethearting events.
  • The receipt contains at least one function for adding an item, the number of which you can specify in the Web.config file in the SweatheartingAddItemPosFunctionNumber key.
  • The receipt contains at least one event from the sweethearting detector that differs from the event of item addition by no more than the value in milliseconds specified by the SweatheartingAddTimeoutMs key in the Web.config file. The recommended minimum value that allows filtering out false positives is 1000 ms.

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.