Table of Contents
This screen can be utilized to modify settings that are specific to the web application. The screen is available through pressing Edit on the Designer Home Page.
The name of the web application can be modified from the Application Name textbox. Depending on the navigation bar configuration for the user's current page, the application name will be displayed as follow:
- Top: If no branding image is selected, the name will be displayed at the left-most position of the top navigation bar.
- Left: Is no branding image is selected, the name will be displayed the the top-most position of the left navigation bar.
- None: If no navigation bar is present, then the name will not be visible within the application itself.
Further, the application name will be utilized when generating the URL for your application. The default naming structure will be as follows:
Be default, this will look something like:
Note: Since the application name is used in the generation of the application URL, any special characters will be URL encoded in the name when accessing via URL. For example, default encoding for whitespace characters is %20, so all whitespace characters will be replaced with the URL-encoded version.
Google Analytics Support
Designer applications include support for Google Analytics. First, you will need to retrieve a new tracking ID for your application using the Google Analytics control panel. The domain address of your application should be entered correctly in order for Google Analytics to function as expected. Secondly, you will need to check the Enable Google Analytics checkbox and enter the tracking ID to the Google Analytics Key input.
After the application is saved and published, you will be able to monitor your application's hits from the Google Analytics tracking site.
Designer applications can be configured to use different color sets in visualizations. The desired color set can be set by clicking Edit Default Colors button. Color manager window will allow you to select a color set from the pre-defined sets. You can also set your own color set.
Designer applications support different Culture settings which can be used to set how the thousands and decimal separators will be shown. Currently, there are three Culture settings you can choose from:
- Thousands Comma Delimiter, Decimal Period Delimiter.
- Thousands Period Delimiter, Decimal Comma Delimiter.
- Thousands Space Delimiter, Decimal Comma Delimiter.
This setting will affect both runtime and the design process for all applicable numeric fields.
Web Service Key
When using a Designer-type application, your underlying model is also exposed as a web service, both for consumption through the Designer-generated user interface, as well as for your own external calculations as necessary.
The Web Service Key textbox is an information-only field that displays the unique identifier for your application when utilizing the SpreadsheetWeb API for consumption.
Note that - in the current state - the saving functionality configured within the Designer is not accessible from the raw API. This level of integration will be built out and detailed in future revisions of the Designer.
Your Designer-based web application can be customized to include your own branding. Both the navigation bar and favicon branding can be updated using the corresponding sections. For more information, see the Edit Favicon Branding and Edit Navigation Bar Branding pages of the Designer Help module.
Enable Record Locking
If your designer application has Save Event this feature will help you to lock record during user editing it.
Inactive Record Locking Timeout
If Enable Record Locking is enabled you need to set this value with following format "hh:mm". For example if you set value to "00:15" that record will be locked for user wich opened first, for 15 minutes.
Updating the Excel Model
The underlying Excel model for your application is where all of your calculations occur. In order to update this model, simply select your file by clicking on the Spreadsheet File dropzone or drag and drop your file into the browser window.
Upon updating the model and pressing the Update button, all of your named ranges will be updated and our internal system validation will run to ensure that your new model is compatible with your existing user interface, database, and page design. If there are any incompatibilities, the system will redirect you to the Validation Messages screen, where these issues will be further detailed.
Note that - as with all changes made in design mode - updating the Excel model will not affect any published versions of your application. The published version will continue to utilize your existing calculation engine until the new version is published, at which point the new Excel model will be the production version.
However, you will be able to see the I/O changes from your Excel model applied to the designer components themselves (e.g. user interface, page, and database designer will reflect updated named ranges), as well as within the preview of your current transaction (i.e. previewing your transaction will use the new Excel model for calculations).