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

Save conflicts doesn't appear for changes made by git push

XMLWordPrintable

    • ER5
    • +
    • Hide
      1. Open any process in browser and start to modify it.
      2. Clone git repo with process, modify it and push.
      3. Try to save process in browser

      Actual Result:
      Save dialog will be shown, in ER4 you can see Conflict Resolution dialog instead.

      Expected Result:
      User will be notified about change and asked rewrite changes/rewrite it or ignore as it was for ER4.

      Alternative steps to see correct behavior using different browsers:

      1. Open any process with USER_A in any browser, made changes
      2. Open same process with same USER_A in another browser, made any change and save
      3. Try to save process in first browser

      Result:
      You will see Conflict Dialog as expected.

      Show
      Open any process in browser and start to modify it. Clone git repo with process, modify it and push. Try to save process in browser Actual Result: Save dialog will be shown, in ER4 you can see Conflict Resolution dialog instead. Expected Result: User will be notified about change and asked rewrite changes/rewrite it or ignore as it was for ER4. Alternative steps to see correct behavior using different browsers: Open any process with USER_A in any browser, made changes Open same process with same USER_A in another browser, made any change and save Try to save process in first browser Result: You will see Conflict Dialog as expected.

      User won't be notified about changes made by git push for active process.

      If parallel changes made in another browser (by same business central user) you will see notification about made changes.

            rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
            kgaevski@redhat.com Kirill Gaevskii
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: