AppConfig

Only newly created experience (unpublished) configurations have this property.

Configure multiple portal connection information

Floating panels for controller widget

Data sources within an experience

Windows (dialogs) within an experience

The framework version when the experience is created/updated.

When an old experience is opened in a new version code, this version will be set as the new code version.

The footer of an experience

These attributes are used by builder only.

The header of an experience

History labels are saved here because the labels may be used in URL. This can avoid link broken. This is done while publishing, which means all labels in the published app will be saved here.

Layouts within an experience

User can configure an experience for multiple size modes, and the default size mode is saved here. The config user interface is not available yet.

The message configs of an experience

As the exbVersion will be replaced with the code version when app is launched, we save the origin version in config here.

The structure of pages

Pages within an experience

The widgets uri in this array will be loaded when the app loads, rather than dynamically loading the widget.

Screen groups within an experience

Screens within an experience

Sections within an experience

The template that an experience created from.

The theme uri, should end with "/".

UTC timestamp for specific app config version. It's used for app's update.

Whether adjust tab order automatically in the fixed layout.

If true, will read widget's manifest from widgetsManifest . This value is false by default

Views within an experience

Widgets within an experience

The manifest here are raw manifest, need to be processed before use. We save raw manifest here to save some network requests.

When add a widget in builder, the manifest is not saved here because we need to fetch the latest manifest to check version info. However, we can do this manually.

Type declaration

• [widgetUri: string]: WidgetManifest