Hi Yizuhi,

As far as you are doing this activity just to change the application's look and feel based on the user's choice, your approach looks good to me. Sometimes, hitting  database multiple time to perform different operations creates performance issue.  So, it is also a good idea to store it in Client variables to reduce the hits to database to get the setting values on every new screen they browse.

As per my experience with OS, I did not see any issue with your approach. However, it would be better to take some more feedback from other community members.

Thanks & Kind Regards,

Sachin

Hi Yizuhi,

Depending on the type of data, you may not want to store them in client variables because they can be tempered and it is not secure. For instance, if you have a flag CanEdit or a role that may be changed by an attacker, or a password to access confidential data, you DO NOT want to have this information as a client variable.

In that case, you want to save them in the database.

You can read more about client variables and the above information in the OutSystems documentation here.

If it is a simple query you should not have a problem of performance. You also can decide to cache the query if the settings are rarely changed to avoid going to the database every time. You would need to invalidate cache when you change those settings. You can read about how caching works in OutSystems here.

Hope it helps.

Kind Regards,

João