Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-111002

As an App Admin, I want to reorder workflow steps of my App

    Details

      Description

      As an App Admin, I want to reorder workflow steps of my App, so that I can update and make adjustments in my Workflow Steps without problems or re-work.

      Design Deliverables

      Mockups
      Prototype

      Context

      When building Workflow Apps, users must be able to change the order of steps in the Workflow without losing it's configurations (assignees, Form Views, etc.).

      Users should be able to move a specific Step to any position in the Workflow (as long as it's isn't before the Start-node or after the End-node). When this happens, the system must:

      • Keep the Name, Assignee and Form Views of the reordered Step;
      • Dynamically update the Next and Previous transition actions to point to the new steps that are after and before the new position.

      Acceptance Criteria

      1- Given a user in the builder of a Workflow App with multiple steps,
      when the user drags a Step and drops it in a different position in the Workflow,
      then the system must reorder the Step to the new position chosen by the user.

      • The position cannot be before the Start-node or after the End-Node

      2- Given that the scenario of Acceptance Criteria 1 was successfully met,
      when the reordering occurs with success,
      then the Step Name, Assignees and Data & Views of the reordered step should all be kept.

      3- Given that the scenario of Acceptance Criteria 1 was successfully met,
      when the reordering occurs with success,
      then the Previous and Next transition actions should be dynamically updated accordingly to the new position of the step.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Code with peer review completed;
      • Validated by QA, Product Designer and/or PM;
      • No critical bug related to Story scope (ex.: similar of FP4, FP5);
      • Make sure that all system documentation were updated (if necessary)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)

        Attachments

          Activity

            People

            Assignee:
            team-workflow Product Team Workflow
            Reporter:
            matheus.xavier Matheus Xavier
            Engineering Assignee:
            SE Support
            Recent user:
            Rodrigo Cunha
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package