Product delivery
Input presets
Let installers pick the data a packaged app runs on.
A packaged app can declare installation inputs: a dataset, a sync or a virtual table it reads. When the product is installed, the chosen value is bound to the app's variable, so each installation runs on its own data.
Define presets
In the New version dialog, under Input presets, add one preset per input kind:
| Setting | Meaning |
|---|---|
| Allowed values | The values installers may pick. |
| Default value | Used when the installer picks nothing. |
| Allow other values | When off, only the listed values are accepted. |
| Required | The install needs a value, from the installer or the default. |
Converge refuses a preset for an input kind no packaged app takes, a default outside a closed list, a closed list with no values, values that do not exist, and values the publisher cannot read.
Install with inputs
The Install dialog shows a field for each preset of the newest version the chosen channel sees: a list for closed presets, free text with suggestions otherwise. Install stays disabled until every required input without a default has a value.
Datasets are checked with your own access: you can only bind a dataset you can read.
Upgrades
The values you chose are recorded on the install and bound again after every upgrade, because an upgrade copies the app definition again. Values that came from a default are not recorded, so a new default in a later version reaches those installs. If a later version no longer takes an input, the recorded value is dropped instead of blocking the upgrade.