These two commands allow UI and script changes to the internal settings used by the POS. UI designers should be very careful when using these commands as changing settings should not be a normal action, and may lead to the POS not enforcing the required business rules.

Related Information

To learn more about settings, see the Operator Settings Information

Review individual settings names and functions Settings Reference Information

Syntax

name

The setting name to change. This can optionally be prefixed by lane and location selectors.

value

The value to store into the setting. For the settings() form, this value is stored as an absolute, for the settingset() form, the value is translated before being stored.

command

A subcommand of how what action should be performed. The only valid action is set.

To specify lane and location, the name argument for settingset(), or the command argument for settings(), can be prefixed with lane:N and location:N. The default lane and location is the current system values. Typical use of this value will be to set the lane to 0. If you specify both lane and location, lane must be specified first.

If you are transmitting this command from head office servers, remember that it will be executed on each lane/location transmitted to, so values for lane and location are typically not required.

Examples

   settings(set,PastSalesSearch:2)

Set PastSalesSearch to 2 on this lane.

   settings(lane:0:set,PastSalesSearch:2)

Set PastSalesSearch to 2 on all lanes.