An App can travel to another NIZU workspace: for example, a consultant builds it in their own workspace and sends it to a client's. It goes in its published...
App transfer, updates and maintenance
An App can travel to another NIZU workspace: for example, a consultant builds it in their own workspace and sends it to a client's. It goes in its published version. Nothing secret travels: no keys, no connection addresses or headers, no people, teams or roles of your workspace.
Two ways to send an App
Deliver it: you keep building it and send new versions. In the other workspace the design is locked; they decide who uses it, how it notifies, its texts and connections. Each new version you send arrives there as an update, with a preview of what changes.
Hand it over: the other workspace becomes its owner and can change everything. Tick Include its records and their files if they should come along.
Send it
Publish the App.
Open Settings → Publish & versions → Send to another workspace and choose Deliver it or Hand it over.
Click Get a transfer code. Give the code (for example 7KQ4-M2XD-9PRT) to the other workspace's administrator. It works once and for 7 days.
You can also click Download the App file and send the file (it ends in .nizuapp) instead.
Receive it
In AI App Design, click Install an App.
Type the transfer code (or choose the file) and click Check the code.
Read what it contains: its lists and screens, records that come with it, connections it expects. Click Install the App.
A new App arrives closed to clients; stylesheets and scripts arrive switched off until you trust them. Every file inside is checked again. Then give your team access (Settings → Access) and set up its connections and Settings page.
Updates
When the builder of a delivered App sends a new version, its banner says Version N is ready. Click See what changes, read the preview, and click Update the App. You can also click Look for a new version. Your records, access rights, texts, connections and Settings page stay as they are. An older or equal version is refused.
Taking over a delivered App
Click Take it over on a delivered App to make it yours: you can change its design, and it no longer receives versions from its builder.
Maintenance
Versions: every design change is kept (Settings → Publish & versions); go back to any of them without touching records.
Safe changes: publishing only adds tables and fields; it never deletes or converts data. Removing a field hides it and keeps its data.
Deleted records go to a bin and can be brought back; so can a deleted App's records.
What happened: the list of automatic steps (Settings → Publish & versions), What was sent (Notifications), Calls made (Connect), and each record's History.
Pause an App to take it away from your team while you fix something.
Languages: after a change, translate the missing texts again.
