InkPlayWiki

Manage releases, updates, and installers

Published: 2026-07-12 - Updated: 2026-07-13 - 9 min read - InkPlay Team

Plan InkPlay updates and installer work around venue hours so branch operation stays predictable.

When should owners update Controller, Agent, or branch tools?

The branch treats updates as scheduled operational work with testing, staff awareness, and rollback context.

Before you start

  • Know which InkPlay components the branch uses.
  • Choose a quiet update window or pre-opening time.
  • Make sure backups and branch recovery contacts are known.

Plan the update

Updates should not surprise staff during live customer sessions. Pick a window and tell the team what will change.

  • Avoid updating while many sessions are active.
  • Read release notes or owner instructions before starting.
  • Confirm who can approve the update.

Install and test

After an update, test the branch flows that matter most before opening the floor fully.

  • Open the Controller and check dashboard readiness.
  • Start a test Agent session if Agent changes were installed.
  • Check TV displays and mobile requests when those features are used.

Hand off to staff

Staff should know what changed, what to watch, and when to escalate.

  • Tell staff about visible changes in the Controller or Agent.
  • Keep installer files or version notes in the owner-approved location.
  • Report repeated post-update issues with device and time details.

Verify it worked

  • The update is installed during a planned window.
  • Core session, dashboard, and device flows are tested after the update.
  • Staff know what changed before live operation continues.

Troubleshooting

A feature behaves differently after update.

Check release notes, test on one station, and escalate with version and device details.

Installer work interrupts customers.

Pause update work, keep affected stations unavailable, and reschedule for a quiet window.

See also