Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-422

After import /api/process-definition/xml returns no or partial definitions

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 1.0.0
    • None
    • backend
    • None

      Steps to reproduce:

      1. import data
      2. go to process selection screen

      Actual:

      1. some or all of definitions xml are not displayed, because they are not returned by /api/process-definition/xml

      Expected:

      1. After import is finished all process definitions xml are returned by /api/process-definition/xml

      Workaround:

      1. Go to any definition page which will trigger /api/process-definition/ {id}

        /xml

      2. Go back to PSS... now /api/process-definition/xml returns all data.

        This is the controller panel for Smart Panels app

            [OPT-422] After import /api/process-definition/xml returns no or partial definitions

            Askar added a comment -

            mariusz.sielski is this a get or POST request we are talking about here?
            Right now there is no get request without IDs existing and POST request requirest list of process instance IDs. Could you attach a curl command that you are using?

            Askar added a comment - mariusz.sielski is this a get or POST request we are talking about here? Right now there is no get request without IDs existing and POST request requirest list of process instance IDs. Could you attach a curl command that you are using?

            Johannes added a comment -

            Review hint:

            • instead of doing an extra request, you should use the method .setRefreshPolicy(WriteRequest.RefreshPolicy.IMMEDIATE) in the bulk request

            Johannes added a comment - Review hint: instead of doing an extra request, you should use the method .setRefreshPolicy(WriteRequest.RefreshPolicy.IMMEDIATE) in the bulk request

            Johannes added a comment -

            Review hint:

            • now the refresh is done on every single request within the bulk request. We should rather set the refresh policy on the bulk request itself so the refresh is done only once

            Johannes added a comment - Review hint: now the refresh is done on every single request within the bulk request. We should rather set the refresh policy on the bulk request itself so the refresh is done only once

            Mariusz added a comment -

            johannes.heinemann I don't think you should close it, as this is bug that can and should be tested, because it affects UI greatly.

            Mariusz added a comment - johannes.heinemann I don't think you should close it, as this is bug that can and should be tested, because it affects UI greatly.

            Johannes added a comment -

            Agreed! Thanks for the hint

            Johannes added a comment - Agreed! Thanks for the hint

              michael.schoettes Michael Schoettes
              mariusz.sielski Mariusz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: