I can migrate activity instances with timer boundary events such that the elapsed time is respected

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: engine

      Example:

      • Source process definition: timer boundary event with 30 days duration
      • Target process definition: timer boundary event with 50 days duration

      When setting the instruction configuration flag #updateEventTrigger, it should be possible to migrate the existing timer job such that its due date is extended by 50 - 30 = 20 days. Currently, the timer starts over, so fires 50 days after migration.

      Note: The complexity here is that we do not have the creation time of the job in the runtime tables and that a timer may be configured via an expression that may resolve to something different at different times, so it is not so easy to figure out the original configuration.

            Assignee:
            Unassigned
            Reporter:
            Thorben Lindhauer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: