Outsystems site properties

A site property is a global variable that has a constant value, or a value that doesn't change often. By design, site property values have a limit of characters.

Site Properties are global variables that have constant values. They are typically used to implement configuration values for the application - such as a maximum value for an application parameter - since they can be set at runtime for each environment with no need to republish the application. You can set a Site Property to a default value on its creation. At runtime, someone with privileges can change the Site Property value for a specific environment through the environment management console Service Center. Use the Site Property in your server-side code by referring to it as Site. If you want to use the value of a Site Property in the client-side logic of a mobile application, you must add a Server Action to get the Site Property value and use that Server Action in your client-side logic.

Outsystems site properties

Sign up. Sign in. Tiago Agostinho. The Site Property is a feature from Outsystems Platform and the main goal is to store data without a lot of changes. Much of the time they are used to store configurable variables, normally API Key, Client Id, Client Secret values, and so on… We can use them for other types of configurations needed to build our application. A Site Property is a global variable to store primitive data types, that has a value without changing very often. More than just give you a definition of what the site properties are, I want to show you how to use them, where they are stored and the impact of changing them. Stick with me! For this example, we are creating a timer to process a bunch of transactions and we will use one site property to set the number of records to process and another one to control the soft timeout of our timer. This scenario is used to avoid an unexpected timeout of the timer. You can check more about it on this link. The next picture is about the timer already created and prepared to process the transactions. You can see the two site properties created and used in the comments. Our site properties are stored in the Outsystems database.

Offline Data Sync Patterns.

Site properties, loaded by the server and then cached for faster access, are used to hold data that has to be available across the module. It's a configuration-related information that should be updated manually in Service Center. For example, don't hold the timestamp of the last sync or a counter for processed elements in these properties. Every time you update a site property, the cache of the module and its consumers will be invalidated and reloaded from the database again. This causes unnecessary database overhead for all parts of the application using site properties. Place non-configuration information that needs to be changed in a specific database table.

OutSystems low-code platform. Uniting design, code, and deployment, OutSystems delivers the high-performance needed for innovation to flourish. Low-code basics. Schedule a Demo. Contact Sales.

Outsystems site properties

Sign up. Sign in. Tiago Agostinho. The Site Property is a feature from Outsystems Platform and the main goal is to store data without a lot of changes. Much of the time they are used to store configurable variables, normally API Key, Client Id, Client Secret values, and so on… We can use them for other types of configurations needed to build our application. A Site Property is a global variable to store primitive data types, that has a value without changing very often. More than just give you a definition of what the site properties are, I want to show you how to use them, where they are stored and the impact of changing them. Stick with me! For this example, we are creating a timer to process a bunch of transactions and we will use one site property to set the number of records to process and another one to control the soft timeout of our timer. This scenario is used to avoid an unexpected timeout of the timer.

Ben 10: alien force

Lifecycle Management and Data Protection. Close Wait Action. Developer cheat sheet. Refresh an Entity. Static Entities. End Users Authentication. Possible Data Loss Warning. Process Flow Editor. Create an Entity Index. How to update the AI Mentor Studio probes. Role Exception. Invalid Public Structure Error. Service Studio Tips and Tricks.

OutSystems OutSystems Language. Handling Data.

Invalid Parameter Error. Harden the protection of mobile apps with AppShield. Run Client Action. Site Properties are global variables that have constant values. Exception Handling Mechanism. Considering everything we read about site properties, the most important part to take into consideration is: Do not change site properties programmatically and bear in mind that every time you change one or more site properties on the Service Center, the cache of this module will be invalidated and reloaded again. Vivek verma wrote:. Modify the App Icon. Stream logs to Dynatrace. Expression Widget.