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

Long Value of a variable is getting trimmed in Cockpit

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • cockpit
    • None

      I started a process Instance with a variable of type long with a value of 643460295255150592.
      But when I am looking the variable value into cockpit, getting 643460295255150600
      But in the DB value is getting saved correctly.
      Is this a cockpit limitation with long variable value or am I doing something wrong?

        This is the controller panel for Smart Panels app

          1. CockpitLongVariable.JPG
            CockpitLongVariable.JPG
            31 kB

            [CAM-10461] Long Value of a variable is getting trimmed in Cockpit

            Martin Stamm added a comment -

            Hi Akanksha,

            We can confirm the bug and will now decide how we continue with it.

            Cheers,
            Martin

            Martin Stamm added a comment - Hi Akanksha, We can confirm the bug and will now decide how we continue with it. Cheers, Martin

            Thorben Lindhauer added a comment -

            Hi akkujain93,

            The root cause of the problem is that numbers in JS are stored as double-precision floating-point, making the biggest save value 9007199254740991. In consequence, when deserializing larger numbers from JSON, they get not processed correctly.

            As a fix for this would require a larger effort, we will not be able to work on this any time soon won't schedule it for a future release. For workarounds, you could consider storing the value as a String variable in the engine.

            Best regards,
            Thorben

            Thorben Lindhauer added a comment - Hi akkujain93 , The root cause of the problem is that numbers in JS are stored as double-precision floating-point, making the biggest save value 9007199254740991. In consequence, when deserializing larger numbers from JSON, they get not processed correctly. As a fix for this would require a larger effort, we will not be able to work on this any time soon won't schedule it for a future release. For workarounds, you could consider storing the value as a String variable in the engine. Best regards, Thorben

            Akanksha Jain added a comment -

            Sure Thorben Lindhauer.
            I am using workaround as of now.

            Regards,
            Akanksha Jain

            Akanksha Jain added a comment - Sure Thorben Lindhauer. I am using workaround as of now. Regards, Akanksha Jain

            Thorben Lindhauer added a comment -

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

            • It is very unlikely that we will implement this
            • We did not receive sufficient evidence that this ticket is important

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: It is very unlikely that we will implement this We did not receive sufficient evidence that this ticket is important

              Unassigned Unassigned
              akkujain93 Akanksha Jain
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: