SharePoint
Feedback by UserVoice

I suggest you ....

Find another way to handle workflow history in the long-term.

I'm aware that keeping the history (for its table joins) in the long run is harming to the farm, so just disabling the workflow auto cleanup timer job is not an option.

You should offer a way look for workflow history by demand, in a way the table joins are made at the moment, and not kept. Even if that takes minutes, final user will understand. Maybe if that can be made/hosted on a separate database in order not to stress out both config and content databases.

Another option is to have workflow actions audit-able and, that way, it can be analyzed and reported as audit information (which it is, in the end).

7 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

Marcos Babu shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base