Stadium
  • Home
  • Academy
  • How it works
    • Designer
    • Application Manager
    • Application users and roles
    • Designing applications
    • User API
  • Features
    • Application
    • Create a Form
    • Embedded Files
    • Events
    • Expression Editor
    • Pages
    • Preview
    • Publish
    • Scripts and Event Handlers
    • Session Variables
    • Settings
    • Styles
    • StyleSheet
    • Templates
    • Types
    • Validations Cheat Sheet
  • Connectors
    • Database Connector
    • File System Connector
    • Web Service Connector
  • Controls
    • Button
    • Chart
    • Checkbox
    • Checkbox List
    • Container
    • Data Grid
    • Date Picker
    • Drop Down
    • Flexbox
    • Grid
    • Image
    • Label
    • Link
    • Menu
    • Panel
    • Radio Button List
    • Repeater
    • Table
    • Text Box
    • Upload File
  • Actions
    • Async
    • Call Web Service
    • Decision (If/Else)
    • Display Message Box
    • Download File
    • For Each
    • Java Script
    • Navigate To Page
    • Notification
    • Set Value
    • Variable
    • While
  • Release Notes
    • 6.12.3272
    • 6.12.3270
    • 6.12.3268
    • 6.12.3264
    • 6.11.3223
    • 6.11.3221
    • 6.11.3220
    • 6.11.3218
    • 6.11.3210
    • 6.10.3155
    • 6.10.3151
    • 6.9.3102
    • 6.8.3100
    • 6.7.3096
    • 6.6.3082
    • 6.6.3081
    • 6.6.3080
    • 6.6.3075
    • 6.5.3055
    • 6.4.3036
    • 6.4.3034
    • 6.4.3033
    • 6.3.3019
    • 6.2.2999
    • 6.2.3001
    • 6.1.2990
    • 6.0.2972
    • 6.0.2970
    • 6.0.2969
Powered by GitBook
On this page

Was this helpful?

  1. Features

Settings

PreviousSession VariablesNextStyles

Last updated 8 months ago

Was this helpful?

A Setting is a constant value that you can use throughout your application. The application can never change a setting's value, only you can.

You can also mark a Setting as "secret", which will ensure that any personal or sensitive data stored in that Setting will remain secure, e.g passwords, usernames, ID numbers, etc.

The use of Settings will contribute to quick and easy maintenance of your application and is especially useful when you want to publish one application in multiple environments and need different values. This could, for example, be folder or file names.

Another benefit of using Settings is that their values can be changed on Application Manager, without having to redesign or redeploy your application.



How to use Settings

  1. Provide a name and value for a setting.

  2. Select the Secret checkbox if required.

  3. Assign Settings to relevant properties (e.g. a control's property).

  4. If required, change setting values as part of the application publishing process or on Application Manager after publishing.

Note: Stadium will not export the value of a secret from the Designer to Application Manager when the Application is deployed. The value of secrets must be provided as part of the publishing process or on Application Manager.


Add a Setting