Specifications

2-2 Point-of-Sale Administrator Guide
Each parameter belongs to one and only one group, and there is a security role for each group, so
parameter access can be restricted to particular groups if desired. See “Defining Security with Roles” on
page 2-6.
Your choice of how to change a parameter matters: if you change a parameter with the Point-of-Sale
interface, the value of that parameter is not loaded on other registers. You can address this by copying
parameter XML files from one register to another, or by making parameter changes in Back Office or
Central Office and then distributing the parameters to registers.
Understanding Parameter XML Tags
Parameters XML files store parameters in <GROUP> tags that contain <PARAMETER> tags; the <PARAMETER>
tags contain properties that describe the parameter. The following example shows the parameter that
determines the maximum traveler’s check value that the system accepts:
<GROUP name="Tender" hidden="N">
...other parameters omitted here...
<PARAMETER name="MaximumTravelersCheckAmount"
type="CURRENCY"
final="N"
hidden="N">
<VALIDATOR class="FloatRangeValidator"
package="com.extendyourstore.foundation.manager.parameter">
<PROPERTY propname="minimum" propvalue="0.00" />
<PROPERTY propname="maximum" propvalue="99999.99" />
</VALIDATOR>
<VALUE value="1000.00"/>
</PARAMETER>
...other parameters omitted...
</GROUP>