Hi,
Under the advance property of a server action their is a feature to cache the data of that action for sometime by using "Cache in Minutes".
Currently if we want to use it then it needs to define it and publish the module.
For a single action somehow it's okay but if their are more action it increases the effort of developer.
We can have a feature where it could be made configurable via "site property/client variable" and by this it will reduce the effort of developer of going to each action and changing the value.
Thanks,
Lakshmi Kumar
Imagine that I have a server action called: GetSomethings(), and I want to call that action for example in a IF structure in my screen, currently, I need to call that action for example in the preparation event with Cache in Minute filled and after that use the result, but If was possible to call that ServerAction as function and pass the Cache In Minutes during the call will make our lives easier.
Something like that: GetSomethings(CacheInMinutes: 1440) - Of course, a non-mandatory parameter.
I would like to see this idea be converted to a feature soon. The ability to control the value based on different lifecycle regions is critical using a function, variable or site property. Often in development, it would be appropriate to turn the cache value to 0 in cases of highly volatile configuration or other data vs. in production. In our recent architecture and best practices review with Outsystems, this was raised as an issue for us and they suggested we elevate the importance here in the Idea forum.