- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi,
Does anybody know how the "Due Date" of an Indicator Task is calculated ?
And can we influence this due date ?
My use case is that we want to have a due date which should be dependent on the indicator frequency.
For example,
Indicator frequency = annual > Indicator-due-date = creation date + 3 months
Indicator frequency = quarterly > Indicator-due-date = creation date + 6 weeks
Indicator frequency = monthly > Indicator-due-date = creation date + 3 weeks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
the due date of Indicator tasks is determined by teir respective indicator template.
There is a field "due_date_duration" on indicator templates,
where a indicator inherits his own "due_date_duration".
This field determines the days that are added to "today" if "today" a task for this particular indicator is created.
As this is automated and i suggest not to manipulate too much, you may use a business rule for your case. Either before insert or async ( i prefer asynch, as changing this fiels is not time critical).
Set the field value depending on the frequency in a "switch case"-pattern and you should be fine.
Kind regards
and "accepted solutions"This motivates others to take part, post solutions and find answers. Thanks! - Mat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
the due date of Indicator tasks is determined by teir respective indicator template.
There is a field "due_date_duration" on indicator templates,
where a indicator inherits his own "due_date_duration".
This field determines the days that are added to "today" if "today" a task for this particular indicator is created.
As this is automated and i suggest not to manipulate too much, you may use a business rule for your case. Either before insert or async ( i prefer asynch, as changing this fiels is not time critical).
Set the field value depending on the frequency in a "switch case"-pattern and you should be fine.
Kind regards
and "accepted solutions"This motivates others to take part, post solutions and find answers. Thanks! - Mat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Thanks, this solves my problem. Don't know how I missed that due-date-duration field 🙂