You decide what goes to the screen

Why controlled deployments?

In many systems content goes to the screen the moment you save it. So does a half-finished edit, a wrongly uploaded image or a line of test text. In MIA a change waits in the panel first and reaches the screen only when you deploy it.

Step by step

1. Add content to a folder, or change a program or a screen setting.
2. Watch the "Dağıtım bekleniyor" (waiting for deployment) counter at the top of the panel go up.
3. Review the changes and deploy them with one click.
4. Open the new record on the Deployments page and follow each screen's status.

Offline screens and large installations

A screen that is not connected at deployment time stays "Bekliyor" (pending) and fetches the update itself when it reconnects. In large installations deployments go out gradually so the server and network are not overloaded. The emergency program skips the queue and goes out at once.

If a screen shows "Başarısız" (failed), check its network connection and the device storage first. You can retry for that screen with the "Programı güncelle" (update program) command in the control centre.

Why records are kept

Numbered deployment records work like a logbook. When wrong content shows up on a screen, you can find which deployment brought it, when it was sent and which screens received it. The answer to who made the change is in the audit log.