Configuration¶
Configuration has two parts: you maintain the message texts centrally on the articles in the CCO Manager, and on the POS you select, once, which field the messages come from.
Maintaining messages in the CCO Manager¶
Store the message text in a UDF string field of the article (user-defined fields in the article master data). Supported fields:
| Field | Note |
|---|---|
udfString1, udfString2 |
short fields, only suitable for brief texts |
udfStringXL1 … udfStringXL4 |
long fields, recommended for real message texts |
Recommendation: use one of the XL fields for messages. The fields
udfString1/udfString2 are dimensioned short in the database; longer
texts do not fit into them.
All articles use the same single configured field: articles with text in this field trigger the warning, articles with an empty field book without a popup. The text is shown on the POS exactly as entered; you control language and wording through the master data.
The message is only shown for active articles, and the master data must have reached the POS through the usual synchronization.
Plugin setting on the POS¶
In the configuration UI of the POS, the plugin settings of the Popup Message Plugin contain exactly one setting:
| Setting | Meaning | Example |
|---|---|---|
| UDF to use | Name of the UDF field the message is read from | udfStringXL1 |
- The value must match one of the field names above exactly (case-sensitive). An unsupported value is noted as a warning in the POS log, and no popups appear.
- If the setting is left empty, the plugin is effectively inactive; no popups appear.
- The setting is stored on the POS and survives restarts. It applies per POS; if you run several POS systems, set it on each one.
Enabling sound¶
The alert sound when the message opens (and the error tone for blocked keyboard input) requires sound output to be enabled on the POS (POS configuration, Allgemeines → Ton aktivieren, "General → Enable sound"). Without sound the message still appears, just silently.