AH ok, I missed that part… so then your only option is to use Goal? In this scenario, there is no configuration for repeat.
In which case, could you not make goal time dynamic? Using a property, you could set the goal time and urgency to “level 1”, when that time hits, have an action that:
- Increases the property to “level 2”
- Recreates the assignment in question (via say ‘change stage’ or another activity)
- Then the assignment starts again, with ‘level 2’ urgency - deadline remains unchanged
The XY problem
The above is a classic example. @Kamil_Janeczek will no doubt pull me up on (see Uncovering the XY problem ).
If we take a step back, the business need is “I want to user the deadline is achieved”. The solution, incrementing urgency, using a custom approach to SLA is one way. But could you not look at how work is assigned or ordered in worklists?
- Assignments could be sorted / prioritised (get next work) by deadline date, so the closer to the deadline the more likely it is worked?
- Create a “time to deadline” field in your data model, to make this even more implicit or enforced?
- Education - deadline isn’t a bad thing, its about work allocation. If we see deadline ensuring work completion on time, and past deadline as a way of prioritising then the OOTB approach might work? We see all kinds of requests for custom SLA’s, when some education on the mechanisms to help see this as more than “Red-Amber-Green” and to set the right values, could achieve a satisfactory outcome?
- Case Deadline vs Assignment Deadline - these can be different, perhaps looking at these to help set the right values and triggers could help?
Personally, I would be looking at 1 and 3 first.