Constants are used to define configuration values. These can differ per environment.
When running the application on a licensed Mendix Cloud environment, SAP BTP, or Private Cloud you can configure the constant values for each environment separately using the Model Options tab of the Environment Details page to set your constants.
For other cloud environments – for example, IBM Cloud or MindSphere – the constants can be accessed as Environment Variables in, for instance, Cloud Foundry. The constant is exposed with the name module + . + constant (for example,
When running the application locally or in a Free App environment, the values defined in Studio Pro are used.
The value for a constant can also be overridden in a configuration. This allows you to run locally using different values for one or more constants, without having to change the default value for the constant every time.
Constants can be used in the following:
- Expressions – by prefixing the full name of the constant with
- Consumed web services – in this case, the constant is a URL that specifies where the web service is located; this can vary based on the environment in which the application is running, so that you can, for example use different web services for development and production
2 Common Properties
The name of the constant. This name is used to refer to it.
This field is for documentation purposes only: end-users will never see it, and it does not influence the behavior of your application
3 Type Properties
The data type of the constant. This determines what kind of values a constant can hold. Supported data types are string, Boolean, date and time, decimal, and integer/long.
4 Value Properties
4.1 Default Value
This property is the default value of the constant. This value is used when running locally or in a Free App environment. When running locally, the value can be overridden in the currently selected configuration.
4.2 Exposed to Client
|Yes||The constant will be sent to the client and will be accessible from client-side expressions|
|No (default)||The constant will not be sent to the client and will be only accessible from microflow expressions|
When a constant is exposed to the client, Mendix Runtime sends its value to the client so that in addition to microflow expressions, it will also be accessible from nanoflows and page expressions. This means that you should not use sensitive data or secrets such as passwords when a constant is exposed to the client.
For a web app, changes to a constant’s values are reflected when the end-user refreshes the browser or restarts the app. For an offline-first PWA or native application, the app stores the constants’ values for offline use. The app updates the constant’s values in the following cases:
- When an end-user logs in or logs out in the app
- When you deploy a new version of the app that contains domain model changes used in the offline-first app