Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-5822

Show detailed error reporting for failed migrations

      AT:

      • in the last page of the migration pageflow (Observe Progress)
      • the failure report of a migration is displayed in a structured way
      • As a user, I can cleary distinguish between "Invalid Migration Plan" and "Migration failed"

        This is the controller panel for Smart Panels app

            [CAM-5822] Show detailed error reporting for failed migrations

            Sebastian Stamm created issue -
            Daniel Meyer made changes -
            Description Original: AT:
             - in the last page of the migration pageflow (Observe Progress)
             - the failure report of a migration is displayed in a structured way
            New: AT:
             - in the last page of the migration pageflow (Observe Progress)
             - the failure report of a migration is displayed in a structured way
             - As a user, I can cleary distinguish between "Invalid Migration Plan" and "Migration failed"
            Daniel Meyer made changes -
            Assignee New: Sebastian Stamm [ sebastian.stamm ]
            Sebastian Stamm made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Sebastian Stamm made changes -
            Assignee Original: Sebastian Stamm [ sebastian.stamm ] New: Roman Smirnov [ smirnov ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Sebastian Stamm made changes -
            Status Original: Resolved [ 5 ] New: In Progress [ 3 ]

            There is a problem displaying errors affecting transition instances

            Sebastian Stamm added a comment - There is a problem displaying errors affecting transition instances
            Sebastian Stamm made changes -
            Assignee Original: Roman Smirnov [ smirnov ] New: Sebastian Stamm [ sebastian.stamm ]
            Sebastian Stamm made changes -
            Assignee Original: Sebastian Stamm [ sebastian.stamm ] New: Roman Smirnov [ smirnov ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            Roman Smirnov added a comment - - edited

            I observed the following exception:

            Error: [$interpolate:interr] Can't interpolate: {{diagram.getNameForId('source', instruction.sourceActivityIds[0])}}
            Error: no diagram loaded
            http://errors.angularjs.org/1.2.29/$interpolate/interr?p0=%7B%7Bdiagram.get…uction.sourceActivityIds%5B0%5D)%7D%7D&p1=Error%3A%20no%20diagram%20loaded
                at angular.js:78
                at Object.fn (angular.js:8937)
                at Scope.$digest (angular.js:12682)
                at Scope.$apply (angular.js:12955)
                at options.done (HttpClient.js:42)
                at http-client.js:68
                at Request.callback (client.js:857)
                at Request.<anonymous> (client.js:501)
                at Request.Emitter.emit (index.js:134)
                at XMLHttpRequest.xhr.onreadystatechange (client.js:934)
            

            To reproduce this behavior follows these steps:
            1) create migration
            2) execute the migration (sync)
            3) go back to "Define Mapping"
            4) Change one of the selected process definition

            Roman Smirnov added a comment - - edited I observed the following exception: Error: [$interpolate:interr] Can 't interpolate: {{diagram.getNameForId(' source', instruction.sourceActivityIds[0])}} Error: no diagram loaded http: //errors.angularjs.org/1.2.29/$interpolate/interr?p0=%7B%7Bdiagram.get…uction.sourceActivityIds%5B0%5D)%7D%7D&p1=Error%3A%20no%20diagram%20loaded at angular.js:78 at Object .fn (angular.js:8937) at Scope.$digest (angular.js:12682) at Scope.$apply (angular.js:12955) at options.done (HttpClient.js:42) at http-client.js:68 at Request.callback (client.js:857) at Request.<anonymous> (client.js:501) at Request.Emitter.emit (index.js:134) at XMLHttpRequest.xhr.onreadystatechange (client.js:934) To reproduce this behavior follows these steps: 1) create migration 2) execute the migration (sync) 3) go back to "Define Mapping" 4) Change one of the selected process definition

              michael.schoettes Michael Schoettes
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: