My Outstanding Work refresh - write performance summary to System Log

[philipfrench]

We know that we can make massive performance improvements in My Outstanding Work, by focusing on Condition scripts, and pre-filters.

However, which workspace to focus on first?

Which workspace is contributing the performance hit? Which is the slowest to evaluate?

When Refresh of My Outstanding Work completes, could you please write a very brief summary to System Log…

“Refresh completed – top 3 workspaces: #123 took 10 secs, #456 took 5 secs, workspace #888 took 2 secs.”

Either actual seconds, or some percentage, or some indication, that could help us focus on the workspace the is the worst culprit.

If we could effectively identify which workspaces need most attention, that would help Implementers, Users and the load on the tenants too 🙂

The impact of writing a summary entry to System Log would be trivial compared to the processing effort to re-calculate MoW.

[niklas_svevar]

Good, go for it.

[giliar.defriesperez]

Hi all,

This is not in our immediate radar because the time to calculate the My Outstanding Work varies greatly by user, and it depends heavily on a user-by-user config. It's not out of the question, just something that we don't have in our immediate radar. Moving to Future Consideration.

Thanks,

Giliar

[philipfrench]

I know it varies user-by-user, hour-by-hour.

That's the point of this - when a particular user reports slow response times, we want to be able to dig down to find the particular issue affecting him.

That is where we are struggling - to find the particular workspace / condition script that is the problem.