Operations¶

Updates¶

New versions appear in the customer portal; the release notes are published there with every release. Applying an update:

Download the new jar from the portal (your license is embedded again).
Replace table-plan-plugin.jar in the POS's plugin folder (<POS data directory>/POSPlugins/AP/).
Restart the POS.

Layout, backups and plugin settings survive the update. Layout changes themselves need no restart; only a jar swap does.

License¶

The plugin uses the customer portal's license model:

Your personal license key is already embedded in the downloaded jar. Alternatively a file named license-table-plan-plugin.key next to the jar counts; it overrides the embedded license (the replacement path for support, without a fresh download).
Maintenance-bound licenses are checked against the build date of the installed version, never against the clock: the end of a maintenance period never stops a running installation. Only versions released after the maintenance end require extended maintenance.
Without a valid license the plugin disables itself loudly: a log entry plus a clear notice on the POS in place of the table plan tab. It never blocks the POS start and never blocks other plugins.

Backups of the layout file¶

Every save of the plan, whether at the POS, via the hub or with the editor, writes the tableplan.json atomically and creates a backup first: tableplan.json.1 (newest) to tableplan.json.5 (oldest), in the same folder. To restore, copy a backup back as tableplan.json.

If a Table Plan Hub is in use, it additionally keeps an unlimited history of all saved versions.

Behavior on FP21 and Cloud Edition¶

CCO 2.0 FP21 (on-premise) is the primary target version. There the plan updates passively and live through the POS's normal Table Service updates.
On the Cloud Edition 3.x the plugin also installs and works. The Cloud Edition, however, does not refresh its table data passively; there the plan is up to date when you open the tab and after your own actions.

Troubleshooting¶

Symptom	Cause and remedy
The TISCHPLAN (table plan) tab is missing	The POS is not running in Table Service mode, the jar is not in `POSPlugins/AP/`, or the license check failed (in that case there is a notice on the POS and in the log).
The tab shows an installation notice	No layout has been provided yet. Draw the plan at the POS or place a `tableplan.json` (see Installation).
"Plan bearbeiten" (edit plan) is missing	The logged-in user lacks the permission `SETTINGS_SCREEN`. This is intended: waitstaff do not see the button.
Saving fails with HTTP 403	The POS UI is being accessed under a foreign name (DNS alias, reverse proxy); see "Access via host name or reverse proxy" in the Configuration.
No floor dropdown at the bottom left	The dropdown is standard POS behavior and only appears once two table areas are visible. Check the assignment on the manager.
Saving reports "Hub nicht erreichbar" (hub unreachable)	The configured hub is not running or not reachable. The POS deliberately does not save locally while a hub is configured. Either make the hub available again or clear `hubUrl`.
A save is rejected ("veralteter Stand", outdated state)	Someone else has saved in the meantime. "Verwerfen" (discard) fetches the current state; then apply your change again. This way nobody's work is overwritten.
An occupied table is missing from the plan	It has no position in the layout. It appears as a chip ("Nicht im Plan", not on the plan) below the plan and stays clickable there.

The plugin's messages appear in the normal POS log; they start with tableplan.