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

Submitting an untyped object value via task forms should not end up in form field history

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.2.0, 7.2.0-alpha6
    • None
    • engine
    • None

      Current behavior:

      • setting a form variable to a typed value of type Object results in no history entry. This is good, since these history entries are only written for primitive variables
      • setting a form variable to an untyped value that represents a custom object (i.e. is equivalent to a typed value of type Object) results in a historic detail entry with value "object.toString()"

      Desired behavior:

      • the scenario described in the second bullet point should also not result in an entry in the historic detail table

        This is the controller panel for Smart Panels app

              sebastian.menski Sebastian Menski
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: