Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3406

Align time offset properties for event import source

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Done
    • L3 - Default
    • 3.0.0
    • 3.0.0
    • backend
    • None

    Description

      We currently keep track of a few timing properties for an event import source for a given publish state. They are used for mediator pagination and publish progress calculation. However, firstEventForSourceAtTimeOfPublishTimestamp
      and lastEventForSourceAtTimeOfPublishTimestamp keep the time offset of the engine, while lastImportedEventTimestamp and lastImportExecutionTimestamp use the offset of Optimize. It doesn't appear to have an effect of publish progress state but is confusing anyway.

      ATs:

      • All four properties should use the same offset, as set in Optimize

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Activity

            People

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce