App Settings

App Settings are those which Designers will set for the App. These settings are only for the apps that you create. App Settings will have four categories like Information, Settings, Security and Messaging and Reporting.

Information : This setting will provide the information related to the App. This will have two categories like General and App History.

General information will have the App Name, Unique Id and CRM Id.

App History will contain the information of history like the App Version, name of the Creator, date when the app was created, name who modified the app and the date when the app is modified.

Settings : This App Setting will have three categories – App Behavior, App Performance, and Connection Settings. App Behavior will have five check-ins through which Designers can set how an app should behave or run in Runtime.

App Behavior – This section includes five check-in points that allow Designers to configure how the app behaves during Runtime. Each option provides flexibility to define runtime interactions based on specific business requirements.

Prevent Local Save - This will prevent the app from saving it offline. By enabling this option Designers will find that the option to "Show dialog for unsaved changes when closing Runtime file" as disabled.
Show dialog for unsaved changes when closing Runtime File -
Enabling this checkbox prompts a confirmation dialog when closing the Runtime file if it is not saved locally.
Note: This option applies only to local saves of the Runtime file and does not affect Salesforce saves.
Prevent Print - This will prevent the app from print and this option will be disabled for offline mode.
Enable Offline Mode - Users will be able to open an app even when they are offline by enabling this option. Designers should save the Runtime App. Once , the app is saved they can open the app on the local desktop.
Enable Macro support for office in Mac

App Performance – This section offers two settings that help optimize how the app performs, particularly when working across Microsoft Excel and Google Sheets environments.

Apply Field format in Design Studio - This setting will help the Designer in case of any field formats applied in Microsoft Excel to be applied in Google sheets by enabling this setting. This setting will also improve the app opening experience in Runtime.
Remove Data Validation message in Google Sheets - This setting is designed for Google sheets as the Excel will have two types of data validation messages however, Google Sheets will have will merge the two validation messages from Excel and have one message. By enabling this option validation messages will not pop up in Google sheets.

Connection Settings – The "Use Specific API version" option allows the design studio users to select a specific API version supported by their Salesforce Org. By default, Fusion uses the latest API version supported by the Salesforce Org. This flexibility allows users to be on a specific version of the Salesforce API.

This app-specific setting allows users to use different API versions across different Fusion Apps.

Security : This setting will allow the Designer to provide the password and protect their worksheet. Designer can decide if the sheet will be password protect only in Design Studio or in Runtime. If Designer decides to protect the sheet in Runtime mode then, Users can only view the information.

Below is the image when the sheet is not protected.

Worksheets needs to be protected in Design Studio from Maps.

In Design Studio, select Maps, hover over Display Options, select Security.
Edit Map which needs to be protected, and check in "Secure worksheet based on field metadata".
Provide the Password, and if the sheet needs to be protected in Runtime or Design + Runtime.
User can also select the protection features available under "Allow all users of the worksheet to".
Click OK.

Below image shows when the sheet is protected. Designers can make changes to the password and also change the access level to users by just unchecking or checking the "allow all users of the worksheet to". Below image shows 2 Maps on the worksheet, we have provided password for only one map on the worksheet. Password will be applied to both the Maps but FLS settings will apply only to that Map for which Designer will select.

Messaging and Reporting : Designers through this setting will decide at what time or at which level a message should be displayed on the screen.

Below are the five check-ins for Messaging and Reporting.

Inform user when Query found no records
Inform user when Query was not attempted as Dependent Query found no records
Group CRM messages and display once workflow completes
Include success CRM messages in the CRM Audit Log
Inform user when Save task found no record to push to CRM

Last updated 3 days ago