Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-5151

Long variable value name blows up variable history log

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • 7.4.x, 7.5.x
    • None
    • cockpit
    • None

      What are the steps to reproduce your problem?
      Add a new object variable to a process instance.
      Give it a very long Object Type Name: java.util.ArrayList<blaw.blaw.blaw.blaw.blaw.blaw.blaw.blaw.blaw.blaw.blaw>

      What is the problem?
      When observing the new variable in the instance history variable log (click action menu) the modal view is disrupted.

      What would be the expected behavior:
      the name in the value column is shortened

        This is the controller panel for Smart Panels app

          1. variable_log.png
            variable_log.png
            36 kB

            [CAM-5151] Long variable value name blows up variable history log

            Michael Schoettes created issue -
            Michael Schoettes made changes -
            Attachment New: variable_log.png [ 21268 ]
            Michael Schoettes made changes -
            Fix Version/s New: 7.4.x [ 14196 ]
            Thorben Lindhauer made changes -
            Workflow Original: camunda BPM [ 32099 ] New: Backup_camunda BPM [ 55716 ]

            Thorben Lindhauer added a comment -

            We are closing this ticket as part of our backlog grooming. Reasons:

            • This problem does likely not exist anymore

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: This problem does likely not exist anymore
            Thorben Lindhauer made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

              Unassigned Unassigned
              michael.schoettes Michael Schoettes
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: