Through the App service, you can customize the state of your app when it loads.
For example, you could configure your app to run a workflow to verify the user's device type and screen size. If the information matches the parameters for the iPhone 6/7/8 Plus, the layout will automatically switch to the iPhone 6/7/8 Plus layout when the app loads.
You can also select the command you want to run when a specific layout loads.
For example, you could configure the Desktop Landscape layout to switch to the German locale when it has finished loading.
Events
Do not configure any actions that require user input, such as the Notification tool or workflows with alerts or forms. This will cause Designer to become unresponsive. If unsure, test your command in a different app before setting this value.
The Events section is where you configure the commands you want to execute when Web prepares to launch (Application Initializing) and after Web has launched (App Initialized).
If you want to configure an Event that interacts with the map rather than the layout (for example, pan and zoom to a specific feature when the map loads), you must configure the Map Initialized setting in the Map component.
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. |
For more information, see App Initialization Events.
Layout Events
Do not configure any actions that require user input, such as the Notification tool or workflows with alerts or forms. This will cause Designer to become unresponsive. If unsure, test your command in a different app before setting this value.
Layout Events lists the layouts configured 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
Every Web app shows customizable privacy information, which must appear somewhere in your app. Although it displays at the bottom of the app by default, you can control where it appears.
The privacy policy in Default templates appear in the User component.
Field |
Description |
|---|---|
Location Slot |
Select a location where the privacy policy icon or content will be located. 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. |
Portal Settings
You can configure the Platform API key so Esri services are accessible without requiring someone to sign in with an identity.
For instance, if you were to embed Web in another application or web page and you wanted to include functionality that requires Esri access (such as, the online geocoder, routing, data enrichment), you can create and register the API key so the user can access those Esri services without having to register and sign in.
Field |
Description |
|---|---|
Platform API Key |
Enter the platform API key to access location services and premium content in your public application. For more information, see API Key Authentication. |
