seemed to introduce a deal of confusion around the supported formats for temporalConstraint durations. The following code will throw a DateTimeParseException: OPENIDM-6712
In the code above, the duration string has the format produced by the UI. The only way to obtain the LocalDateTime corresponding to the duration start is via dateUtil#getStartOfInterval. However, when a simple trigger is scheduled with a startTime, the ScheduleConfig class will set the start time using:
The String produced by dateUtil#formatDateTime(LocalDateTime instance) will generate a DateTimeParseException. This means that the intuitive path to use the DateUtil class to generate startTimes for triggers enforcing temporal constraints will blow up when these jobs are scheduled. This previously worked because temporal constraints were enforced by cron triggers, which have a different parsing regimen.
Currently, triggers with startTimes only work when the startTime is generated by the millisecond instance format (e.g.
Using this knowledge, a work-around is the following code: