Every App has a Settings Entity. The fields available can be anything your App needs, so there is no pre-defined set of fields.
Edit/Configure App Settings
This is where you can find the App Settings:
On 2 you can configure the fields you need, just like any other Entity:
On 3 you can set the values you need
Why would you use this?
Imagine a Gallery App where each instance (Module) has settings like animation speed. You would place the default values in the App Settings so that by default all instances would behave the same, and you can still change this in one central location.
Example from the Content App
In newer versions, the Content-App has some App-Settings to store
- Google-Maps API keys
- Bootstrap versions (CSS Framework) to load if the Theme doesn't have Bootstrap activated
Difference App Configuration / App Settings
The App Configuration is a system Entity and 2sxc needs it for the App to work properly.
The App Settings can contain any information you configure it to have, and the values are only used in the App itself.
Use in C# Code (Razor / WebAPI)
Use in Token Templates
Tokens templates are much more limited, but you can access these values using
[App:Settings:...] - for example
The new v12 Settings-Stack is not available in tokens. If you think you need it, please post an issue on github.
Use in VisualQuery
You can also access these properties in VisualQuery, also using tokens like
The new v12 Settings-Stack is not available in Visual Query. If you think you need it, please post an issue on github.
Using Settings in Multi-Language Scenarios
Settings are normal Entities, and as such can be multi-language. We strongly recommend to limit the use of multi-language settings, as it can often lead to unexpected results.
Don't Use Settings for Labels
Remember to use App Resources for button-labels, titles etc. and not Settings, as this would confuse the users.