Operations¶

Updates¶

You obtain new versions from the customer portal, where you also find the release notes. An update is a jar swap:

Download the new jar from the portal (your license key is embedded again at download time).
Replace the old popup-message-plugin.jar in POSPlugins/AP/ with the new one.
Restart the POS.

The plugin setting UDF to use survives the update; the message texts live in your article master data anyway.

The license key is embedded directly in the jar from the portal download. Alternatively, a key file license-popup-message-plugin.key next to the jar applies; if present and non-empty, it takes precedence (the swap-in route, for example via support, see Installation). The environment variable CCO_PLUGIN_LICENSE_DIR relocates the directory of the key file if needed.
Maintenance-bound license keys are checked against the release date of the installed build, never against the current time: an expired maintenance period does not stop a running installation; it only affects the use of newer versions.
Without a valid license the plugin disables itself, visibly: a notice banner appears on the POS and an error entry in the log, and the warning-message feature is then off. POS startup and other plugins are never blocked by this. Remedy: download the jar fresh from the portal (the download embeds the license) or put a valid key as a file next to the jar.

The plugin writes to the normal log of the POS:

At startup, a license banner with product name, version, and license information. This is the quickest way to check which version is running and whether the license is in effect.
With a missing or invalid license, an unmissable DISABLED error with a remedy hint.
For an unsupported value of the UDF to use setting, a warning (Unsupported value …).

The plugin is freeware and comes without a support obligation. Feedback and bug reports are welcome: mail@stefanbaust.de