Question 1 of 3
SyncApp runs every 15 minutes. Does every entity get synced every 15 minutes?
AYes — the 15-minute cycle applies to all entities equally
BNo — each entity has its own cron job, so a doctor list might sync every 24 hours while appointments sync every 15 minutes
CNo — only patients sync every 15 minutes; all other entities sync once per hour
DIt depends on the PMS type; cloud PMSs sync all entities simultaneously
Question 2 of 3
In a cloud PMS SyncApp, where are the batch files (hash maps) stored, and why?
AIn the SyncApp pod's memory — for fastest access
BIn the Weave SQL database, managed by Data Service
CIn a Persistent Volume Claim (PVC) attached to the pod — so data survives pod restarts
DOn the customer's machine — same as on-prem
Question 3 of 3
When deploying a new SyncApp version via the Deploy UI, what does clicking 'OK' (deploy) actually do to the running SyncApp?
AImmediately restarts the SyncApp with the new version
BPushes the new version tag to the SyncApp config — the SyncApp will load it on its next 14-hour update check
CSends a restart signal to the Kubernetes pod
DRuns automated tests against the new version before making it live