Question

Feature Request: Display Scheduled WF Rules on a Calendar

Workflow

Updated June 21, 2020

asked on June 21, 2020

The other day we were going through our WF starting rules to see:

a) which ones run on a schedule

b) when those scheduled workflows run, and at what frequency

This was pretty painful because we have several hundred active starting rules. So we had to click through each and every single one, then take note of when and how often they run.

It seems that information should be displayed on a calendar.

1 0

Replies

replied on June 21, 2020

Hi Ege!

This isn't a calendar, but may speed up your investigation: when you create a scheduled workflow, Laserfiche actually creates a scheduled task on the server, prefaced by "WF". From there you can focus only on the scheduled ones, and have fairly quick overview of what's going on. Highlighting each one will tell you its name in the description. Word of caution - I have seen instances where the scheduled workflow was removed, but the scheduled task was not - usually when I've deleted a workflow. You'll see an error in the Event Viewer that the workflow was not found.

Hope this helps!

3 0

replied on June 21, 2020

You could also save a little time by doing a SQL query against the starting rules and pull out the timed rules. It won't display in a calendar but it will prevent you from needing to click on every rule.

SELECT b.[workflow_name], a.[rule_name], a.[rules], a.[rule_type]
FROM [dbo].[starting_rules] as a
JOIN [dbo].[index_workflow_name] as b
ON a.[workflow_id] = b.[workflow_id]
WHERE a.[rule_type] = '1'
AND
a.[is_active] = '1'

If you want to see all the timed rules whether they are active or not, just remove the AND a.[is_active] = '1'.

Under the column "rules" you will see near the beginning Type="RunWeekly" or once or daily depending on what it is set to. That could help you sort them out.

3 0

You are not allowed to follow up in this post.

Question

Question

Feature Request: Display Scheduled WF Rules on a Calendar

Replies

Sign in to reply to this post.