Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-3183

Convert to XLS functionality generates incorrect result

XMLWordPrintable

    • 3
    • False
    • False
    • Release Notes
    • CR1
    • +
    • Undefined
    • Hide

      1. Import the attached test.xlsx
      2. View the source tab
      3. Convert to gdst format
      4. Open the gdst file, use the 'Convert to XLS' button
      5. Open the converted xlsx, view the source tab
      => The source is different from the original xlxs file

      Show
      1. Import the attached test.xlsx 2. View the source tab 3. Convert to gdst format 4. Open the gdst file, use the 'Convert to XLS' button 5. Open the converted xlsx, view the source tab => The source is different from the original xlxs file
    • ---
    • ---
    • 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15), 2021 Week 10-12 (from Mar 8), 2021 Week 13-15 (from Mar 29)

      Using the 'Convert to XLS' functionality leads to incorrect rules and compilation errors. Eg when converting the attached spreadsheet from xlsx -> gdst -> xlsx, we can see the following difference in the source tab:

       

      • original:
         when
        $line : LocateLineRuleData(securityType  == ("BOND"), ...
         
      • converted:
         when
        $line : LocateLineRuleData( counterPartyCode == "" , accountCode == "" , subType == "" , securityType == "BOND" , ...
         

        1. LocateLineRuleData.java
          3 kB
        2. MySpace_conversion.zip
          23 kB
        3. RuleExecutionHelper.java
          0.5 kB
        4. test.xlsx
          13 kB

              trikkola Toni Rikkola
              rhn-support-mputz Martin Weiler (Inactive)
              Jozef Marko Jozef Marko (Inactive)
              Jozef Marko Jozef Marko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: