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

Not possible to migrate process with Custom type containing "<>" characters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 7.7.0.GA
    • jBPM Designer
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • Workaround Exists
    • Hide

      Remove "<" and ">" characters from Custom Type of all process variable definitions before you start migration.

      Show
      Remove "<" and ">" characters from Custom Type of all process variable definitions before you start migration.
    • Hide
      1. Import multiple-instance-process.bpmn2 process.
      2. Try migrate the process.

      Actual result

      It is not possible to migrate legacy process to Stunner.
      Migration error window is shown (migration-error.png).

      Expected result

      It is possible to migrate legacy process to Stunner.
      In case the process is broken, error messages what needs to be fixed are shown in dialog window.

      Show
      Import multiple-instance-process.bpmn2 process. Try migrate the process. Actual result It is not possible to migrate legacy process to Stunner. Migration error window is shown ( migration-error.png ). Expected result It is possible to migrate legacy process to Stunner. In case the process is broken, error messages what needs to be fixed are shown in dialog window.

      Not possible to migrate process with Custom type containing "<>" characters.

      The issue is probably caused and blocked by the bug in Stunner editor: RHPAM-2773.

        1. migration-error.png
          24 kB
          Lubomir Terifaj
        2. multiple-instance-process.bpmn2
          10 kB
          Lubomir Terifaj

            romartin@redhat.com Roger Martinez
            lterifaj@redhat.com Lubomir Terifaj
            Lubomir Terifaj Lubomir Terifaj
            Lubomir Terifaj Lubomir Terifaj
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: