Webapp manifest
A webapp manifest is a JSON structure used to build webapps. The target audience for this is developers. In an ideal world developers should be able to build any application by constructing a webapp manifest.
Root level
Variable | Required | Description |
---|---|---|
version | Yes | Signifies which parser to use for this manifest. If it's decided to change the structure of manifests, it will be required to bump this to |
schema | Yes | Contents of the manifest. |
Schema level
Variable | Required | Example | Description |
---|---|---|---|
config.initial_screen | Yes |
| Unique identifier (path) of the initial screen. |
config.currency_template | No |
| See currency configuration article for more information. |
config.date_format | No |
| See date configuration article for more information. |
config.default_values | No |
| Object of default values applied to the form. |
config.overwrite_values | No |
| Overwrite |
config.computed_values | No |
| Computes values and applies them into input state. See computed values guide for more information. |
config.requests | No |
| An array of requests that should be performed for this webapp along with frontend specific field definition (validation rules). If, for example, there are some frontend only specific validation rules, they should be defined here. Other, both backend and frontend validation rules should be defined in the root field definition object (it's not stored in the manifest). More on this in the api requests guide. |
layout | No |
| Definitions of the layouts that can be used in webapp flow. See layout guide for more information. |
flow | Yes |
| An array of component definitions. See building the flow article for more information. |
Last updated