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

Can't create a new scesim file in VSCode when workspace contains multiple folders

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 7.11.0.GA
    • DMN
    • None
    • VSCode 1.55.2 with Kogito Bundle v0.9.0

    • False
    • False
    • Release Notes
    • Undefined
    • Workaround Exists
    • Hide

      Keep just a single folder inside your workspace. If you need to work over several projects, open those in separate VSCode instance each.

      Show
      Keep just a single folder inside your workspace. If you need to work over several projects, open those in separate VSCode instance each.
    • Hide

      1. create a VSCode with a single folder in it.
      2. Create a valid DMN file.
      3. Create a scesim file for that DMN file - should succeed.
      4. Add a new folder within workspace by right-click + select Add Folder To Workspace
      5. Create a different scesim file for the same DMN file - should fail.

      Show
      1. create a VSCode with a single folder in it. 2. Create a valid DMN file. 3. Create a scesim file for that DMN file - should succeed. 4. Add a new folder within workspace by right-click + select Add Folder To Workspace 5. Create a different scesim file for the same DMN file - should fail.

    Description

      When there are multiple folders within one workspace then the Scenario Simulation editor fails at creating a new scenario for given DMN model.

      The DMN model is correctly shown in dropdown menu when opening a new .scesim file. But upon selecting the model and confirming dialog a similar error appears:

      Referred DMN file 'smarthouse-01-quarkus/src/main/resources/try.dmn' is invalid or not present. Please provide a valid DMN file and update Settings dock in the right. Message: 'Error Error: Argument [undefined] must be a string.'
      

      When the additional folder is remove from within the VSCode workspace all works fine.

      Attachments

        Activity

          People

            yamer@redhat.com Yeser Amer
            jstastny@redhat.com Jan Stastny
            Jan Stastny Jan Stastny
            Jan Stastny Jan Stastny
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: