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

Long Value of a variable is getting trimmed in Cockpit

    Details

    • Type: Bug Report
    • Status: Ready
    • Priority: L3 - Default
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: cockpit
    • Labels:
      None

      Description

      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?

        Activity

        Hide
        martin.stamm Martin Stamm added a comment -

        Hi Akanksha,

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

        Cheers,
        Martin

        Show
        martin.stamm Martin Stamm added a comment - Hi Akanksha, We can confirm the bug and will now decide how we continue with it. Cheers, Martin
        Hide
        thorben.lindhauer Thorben Lindhauer added a comment -

        Hi Akanksha Jain,

        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

        Show
        thorben.lindhauer Thorben Lindhauer added a comment - Hi Akanksha Jain , 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
        Hide
        akkujain93 Akanksha Jain added a comment -

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

        Regards,
        Akanksha Jain

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

          People

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

            Dates

            • Created:
              Updated:

              Development