You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed the new forecast of how many course will be triggered (workflowoverview).
I really like the idea of the new workflowoverview but there is a buggy implication.
Specificdatetrigger determines if it is already used by the 'timelastrun' setting.
Since the get_count_of_courses_to_trigger_for_workflow Function calls get_course_recordset_where() of the trigger,
'timelastrun' is set at now.
Therefore after the trigger showed once in the overview how many courses will be triggered, it will not trigger again today.
(assumed we want to set the specific date as Today).
This could also influence other triggers which should only run once in a day.
In my opinion either the logic of the workflowoverview needs to be changed or we need to change 'specificdatetrigger'.
What do you think?
Greetings
Felix
The text was updated successfully, but these errors were encountered:
I noticed the new forecast of how many course will be triggered (workflowoverview).
I really like the idea of the new workflowoverview but there is a buggy implication.
Specificdatetrigger determines if it is already used by the 'timelastrun' setting.
Since the
get_count_of_courses_to_trigger_for_workflow
Function callsget_course_recordset_where()
of the trigger,'timelastrun' is set at now.
Therefore after the trigger showed once in the overview how many courses will be triggered, it will not trigger again today.
(assumed we want to set the specific date as Today).
This could also influence other triggers which should only run once in a day.
In my opinion either the logic of the workflowoverview needs to be changed or we need to change 'specificdatetrigger'.
What do you think?
Greetings
Felix
The text was updated successfully, but these errors were encountered: