• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.0.0
    • 3.0.0
    • frontend
    • None

      Context:

      See OPT-3497: the process instance suspension state is currently only accurate for suspensions that happened before Optimize was started because the engine filters out suspension operations from the user operations log. We have updated the documentation accordingly and added a limitations section the the upgrade notes explaining this issue. This documentation should be referred to when the User uses the suspension state filters.

      AT:

      When either of the suspension related filters are applied on a report, a warning appears that links to the limitations section of the documentation.

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: