Milestone XProtect Transact - Manual (Page 25)

Milestone XProtect
®
Transact
Administrator's Guide
www.milestonesys.com 25 Administration
In this example, the line break is all the formatting we require. In most cases, omissions
(removal of certain content) and substitutions would be required as well. They are applied in a
similar way, by dragging to select the required characters in the Raw data field, then clicking
the relevant button. See also: How to omit characters (see "Omit characters in a source's
configuration" on page 29), How to use substitutions (see "Use substitutions" on page 30) and
How to add line breaks (see "Add line breaks" on page 31).
3. When the required filters (omissions, substitutions or line breaks) are in place, add a start
mask (see "Use start and stop masks" on page 31). The start mask defines when a new
transaction begins, and helps keep individual transactions separate.
For each transaction, a start mask followed by a new line is compulsory – otherwise no date will be
recognized and fed into the system.
In this example we have noticed that all new transactions begin with the characters TEXT. We
therefore type TEXT in the Start Mask field. In the Filtered data field, XProtect Transact automatically
inserts a horizontal line above occurrences of the start mask, as an indication of the beginning of a
new transaction:
Note that start and stop masks are case sensitive; there is a difference between typing TEXT
and Text.
1. Add a stop mask. The stop mask defines the end of a transaction.
A stop mask is not compulsory, but can be useful if the received data contains irrelevant
information
—perhaps information about opening hours or special offers—between actual
transactions.