In my earlier blog I talked about the archive feature as a way to bring in hygiene, maintenance; eventually leading to better end user response times. The platform has granular controls at several layers when it comes to permissions and what fields one could see, whilst the row level security feature controls ticket data access. Permissions defined on request ID in combination with the assignee group(s) allow these controls to be enforced.
The 19.02 release of the Remedy Action Request system brought in the subquery algorithm targeted to provide performance benefits for user facing operations. Design time support was made available in 19.08. Take a read at .
Look through the attached performance numbers, especially the ones which show up for Smart Reports. As an example an Asset Details report which used to take 4 mins [0.2 million records result set] now takes 21 seconds OR in case of a end user trying to get results off WorkOrder:SLMDetails [result set 0.1 million] now shows 2x improvement.
Combined with the auto discovery feature which is being made available as a hot fix in prior releases, the platform will now pick for you which are the forms on which the subquery algorithm will give you efficiencies. The way the discovery happens is by comparing execution time against a configurable interval, which is 5 seconds by default. This will allow recommendations come up for your database, for your use cases; not needing you to look at heuristics or needing you to extrapolate for these use cases.