Details

    • Target Release:
    • Steps to Reproduce:
      Hide

      1. Create an authoring environment (RHPAM 7.5.0 OOTB) and create 2 users (developer1 and developer2) with following roles: developer,rest-all
      2. Start Business-central and open 2 different sessions (one for developer1 and another one for developer2).
      3. Developer1: create a new project (Project1) and add an asset of type business process (Legacy).
      4. Developer1: close business process (legacy) editor and build the project. You'll see compilations results for project1 in "Alerts" panel (with errors).
      5. Developer2: create a new project (Project2) and add an asset of type business process (Legacy).
      6. Developer2: close business process (legacy) editor and request a build. You'll see compilations results for project2 in "Alerts" panel.

      Result: developer1 screen is updated with "project2" results, showing developer2 compilation results and loosing it's compilation log.
      Expected: developer1 screen is updated only if the project he's working on is built.

      Show
      1. Create an authoring environment (RHPAM 7.5.0 OOTB) and create 2 users (developer1 and developer2) with following roles: developer,rest-all 2. Start Business-central and open 2 different sessions (one for developer1 and another one for developer2). 3. Developer1: create a new project (Project1) and add an asset of type business process (Legacy). 4. Developer1: close business process (legacy) editor and build the project. You'll see compilations results for project1 in "Alerts" panel (with errors). 5. Developer2: create a new project (Project2) and add an asset of type business process (Legacy). 6. Developer2: close business process (legacy) editor and request a build. You'll see compilations results for project2 in "Alerts" panel. Result: developer1 screen is updated with "project2" results, showing developer2 compilation results and loosing it's compilation log. Expected: developer1 screen is updated only if the project he's working on is built.

      Description

      When working with multiple users on a same RHPAM instance under different accounts it appears that the Alerts panel is shared - i.e. whenever I saved some erroneous process/rule , the other logged user (different user) can see the error in his Alert panel - which does not seem like desired behavior. In a shared development environment this becomes especially annoying when there are several developers working on different projects at the same time.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ederign Eder Ignatowicz
                Reporter:
                oscar.molina Oscar Molina
                Tester:
                Barbora Siskova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: