The App settings include the following categories:
•Events
•Layout Events
•Privacy Policy Settings
Events
Field |
Description |
|---|---|
Application Initializing |
The command to run when the app starts to initialize. A command is an action the app should perform. Some commands have additional settings you can configure. The Application Initializing command runs before any other event occurs. To view the order in which initialization events occur, see Order of Initialization Events. The command (or workflow) must not contain blocking actions, such as alerts or user-facing forms, as these will prevent the layout from loading in Designer. |
Application Initialized |
The command to run when the app finishes initializing. A command is an action the app should perform. Some commands have additional settings you can configure. The Application Initialized command runs after any command is run via the Application Initializing event configured in App settings, but before any Launch Link Workflow is run or any command is run via the Map Initialized event configured in Map settings. To view the order in which initialization events occur, see Order of Initialization Events. The command (or workflow) must not contain blocking actions, such as alerts or user-facing forms, as these will prevent the app from loading in Designer. |
Layout Events
Contains a list of layouts in your app. You can specify commands to run with regard to each layout by clicking the name of the layout.
Field |
Description |
|---|---|
Layout Loading |
The command to run when the layout starts to load. A command is an action the app should perform. Some commands have additional settings you can configure. To view the order in which initialization events occur, see Order of Initialization Events. The command (or workflow) must not contain blocking actions, such as alerts or user-facing forms, as these will prevent the layout from loading in Designer. |
Layout Loaded |
The command to run when the layout finishes loading. A command is an action the app should perform. Some commands have additional settings you can configure. To view the order in which initialization events occur, see Order of Initialization Events. The command (or workflow) must not contain blocking actions, such as alerts or user-facing forms, as these will prevent the layout from loading in Designer. |
Privacy Policy Settings
Field |
Description |
|---|---|
Location Slot |
Select a location for the privacy policy link: •Application Top Beginning: Place the privacy policy link at the beginning of the top of the application. •Application Top End: Place the privacy policy link at the end of the top of the application. •Application Bottom Beginning: Place the privacy policy link at the beginning of the bottom of the application. •Application Bottom End: Place the privacy policy link at the end of the bottom of the application. •Application Footer: Place the privacy policy link in a footer at the bottom right. •Map Top Beginning: Place the privacy policy link at the beginning of the top of the map. •Map Top End: Place the privacy policy link at the end of the top of the map. •Map Bottom Beginning: Place the privacy policy link at the beginning of the bottom of the map. •Map Bottom End: Place the privacy policy link at the end of the bottom of the map. •User Component: Place the privacy policy link directly within the User component. The default location is the User component. If the configured location is not available, the privacy policy link is placed in the application footer. |
More Info |
Additional information to display with the privacy policy link. This field supports rich text. |
