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

Process diagram images are hardcoded to large sizes

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.4.0.GA
    • 7.2.1.GA
    • Kie-Server, Usability
    • None

    • Local and Openshift

    • CR1
    • Workaround Exists
    • Hide

      The returned application svg/xml needs to be manually parsed and edited to remove height and width. You basically need to redraw the image.

      Show
      The returned application svg/xml needs to be manually parsed and edited to remove height and width. You basically need to redraw the image.
    • Hide
      • Integrate the process diagram via the image rest endpoint
      • The returned svg/xml has a height and width hardcoded to a very large size 2800x1400
      • This is fine in business central, but in external web apps the image needs to be relative
      Show
      Integrate the process diagram via the image rest endpoint The returned svg/xml has a height and width hardcoded to a very large size 2800x1400 This is fine in business central, but in external web apps the image needs to be relative
    • 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16

    Description

      Attempting to include the process diagram and current process step in an external application is extremely difficult.

      The image is an asynchronous call so including the url in image tags does not work. Additional code is required to inject the image asynchronously which is tough

      The returned svg has a hardcoded height and width to a very large size. Instead the image size should not be hardcoded so that it can be scaled within external web applications. By making its size relative (percentage) the image can be included in pages and not blow out page layouts

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPM-8306 Process diagram images are hardcoded to large sizes

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              nmirasch@redhat.com Neus Miras Chueca
              mechevarria Michael Echevarria (Inactive)
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: