- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hello,
One thing I've found quite easy is to do it this way:
1- create a filter on a workflow view
identify all finished workflow with attribute memo (xml data) containing the string keepResult="true"
In each workflow, disable the "keep result of the interim population" option and then start & stop the workflow:
each time you'll start the workflow it will refresh its context with the keepResult="false" and it will delete all worktables when you'll stop it (this is the runWF process that is asking the DB to drop the tables)
2- create a filter on a workflow view
identify all running workflow with attribute memo (xml data) containing the string keepResult="true" and a process id (@pid) equal to 0
same process as before but just restart each workflow as a pid 0 usually means that the workflow is waiting for a scheduler task (carefull about workflows with a wait task)
Of course, you could create a generic workflow to do that using queries and js activities (check that API function for example: Restart (adobe.com) Start (adobe.com) Stop (adobe.com)
But in any case, setting such processes in place should never be a free card for bad AC hygiena: educating the users should be a priority
Views
Replies
Total Likes