The Web.config file configuration must be performed on the computer where it is planned to work with the Sweethearting report.

After making any changes in the Web.config file, it is necessary to restart the Cassini Service utility.

You can filter the sweethearting events in order to build the Sweethearting report only by the events which occured while the check was open.

To filter the sweethearting events, do the following:

  1. Open the POS database in the SQL Server Management Studio software (1).

  2. Open the dbo.FuncDic table (2).

  3. Copy to the clipboard or memorize the function numbers in the FunctionNumber column (3) which will indicate the start and end of the check.

    For example, the Document start function with the corresponding function number 2000 can be used as the check start, and the Result function with the corresponding function number 2022 can be used as the check end.


  4. Go to the <Intellect installation directory>\Modules\Wt2.
  5. Open the Web.config file for editing.
  6. For the SweatheartingBeginReceiptPosFunctionNumber key (1) specify the value corresponding to the function number used as the check start (3).
  7. For the SweatheartingEndReceiptPosFunctionNumber key (2) specify the value corresponding to the function number used as the check end (3).
  8. To enable filtering, specify the 1 value for the SweatheartingFilterByReceiptIntervals key (3). The default key value is 0 (filtering is disabled).

  9. Save the changes in the Web.config file.

    As a result, only the events which occured while the check was open will be displayed in the Sweethearting report. If the sweethearting event occured when the check was closed, such event will not be displayed in the report.


    The checks which do not have their start and end specified in the Web.config file will be considered incorrect and will not be processed. Meanwhile, the check with several starts and ends specified will be processed.