• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.15.0-alpha3, 7.15.0
    • None
    • engine
    • None

      AT

      • Annotations are
        • editable in Runtime incidents (can be edited and cleared via RuntimeService API)
        • propagated to the corresponding historic incident immediately
        • require the same rights that the resolution of incidents does, so any of
          • UPDATE permission on resource "Process Instance"
          • UPDATE_INSTANCE permission on resource "Process Definition"
      • retrieved by querying the (historic) incident itself
      • there is a new column ANNOTATION_ of type VARCHAR(4000) for incident and historic incident
      • User Operation Log entries are written when annotations are modified

      Hints

        This is the controller panel for Smart Panels app

            [CAM-13060] In Java API, I can add/edit/delete an annotation for an incident

            There is a specific bug on Oracle with 7.15.0-alpha3:
            Setting an annotation on a standalone (read: not related to an execution but rather to a batch job) incident will fail since we are querying for an execution with a null id.

            This has been fixed with commit 01b04d2 and will be released with 7.15.0-alpha4

            Tobias Metzke-Bernstein added a comment - There is a specific bug on Oracle with 7.15.0-alpha3: Setting an annotation on a standalone (read: not related to an execution but rather to a batch job) incident will fail since we are querying for an execution with a null id. This has been fixed with commit 01b04d2 and will be released with 7.15.0-alpha4

              Unassigned Unassigned
              tobias.metzke Tobias Metzke-Bernstein
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: