Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
@Thomas Hampel
Can you please "review" that idea´s status?
@Thomas Hampel
If the user who causes the index update does not have rights, then you can return a Boolean or generate an error.
@Thomas - I agree with the other comment, the app developer needs to be in full control of the index. The default refresh timeframe is "Automatic" but if the developer ever decides to use e.g. hourly/daily/etc. then they are doing so for performance reasons. Please be careful about constraining developers on behalf of admins - IBM did this in many occasions and over time it crushed the ability of the platform to organically grow.
If such an API call does become a major performance issue, then there could be a DB-level property or INI setting added at the server level to disable it by admins.
I do not agree. That a view index should not be updated instantly is a architectual decision of the developer for performance purpose. So the developer also needs a "tool" to refresh the view index, when the application logic needs it to be done.
The fundamental question is if app developers should be allowed to manage the server behaviour/resource usage. Of course it is reasonable to expect that a view index is up to date, so maybe it is a better approach to change the server behaviour instead of writing code to work around?