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

As an App Admin, I want to include Form Views of previous steps in "Ready-Only" or "Editable" mode

    Details

      Description

      As an App Admin, I want to include Form Views of previous steps in "Ready-Only" or "Editable" mode

      Design Deliverables

      Mockups

      Context

      One of the main values provided by the App Builder is the automation of business operations. Once the creation of Standard Apps aren't well driven for this use case, we decided that we should offer a separate and special experience for users that wants to create Apps to automate a business process, in way that we can leverage on the Apps tools that we have (Data Objects, Form and Table Views) and enhance it with Workflow capabilities.

      The result is what we are calling "Workflow Powered Apps". A special type of App with an intuitive interface that can create Apps integrated to a Workflow, making any data gathered from Form Views flow through different steps of a process to be reviewed or even complemented with more information.

      In the scope of this Story, we want to allow users to define if a Form View of a Step should be displayed in the running App as "read-only" or "editable".

      This Story's scope includes:

      1. When a user adds a new step, automatically bring all Form Views used in the previous Step in "read-only" mode;
      2. Allow users to either Form Views that he doesn't want to be shown in that step;
      3. Define if each Form View of the Step should be displayed in the running App as "read-only" or "editable".
        • If read-only, all fields of the Form View should be displayed as read-only when a instance reaches this step;
        • If Editable, all fields of the Form View should be displayed as enabled to edition when a instance reaches this step.

      Acceptance Criteria

      1- Given that a user has configured the Form View as "Read-only" in a Workflow App Step,
      when a user opens an instance of the running Workflow App in that Step,
      then the Form View should be displayed in "Read-only" mode.

      2- Given that a user has configured the Form View as "Editable" in a Workflow App Step,
      when a user opens an instance of the running Workflow App in that Step,
      then the Form View should be displayed in "Editable" mode.

      3- Given that a user is adding a new Step in his Workflow App,
      when the user access the "Data and Views" configuration of the new step,
      then the system should automatically include the Form Views used in the previous Step by default.

      • The Form Views from last step should be included marked as "Read-only", but the user should be able to change it to "editable" or even remove it from this new step.
      • Users should still be able to add more Forms Views on top of those from the previous step.

      4- Given that a user has removed a Form View from a Step in the Workflow App,
      when a user opens an instance of the running Workflow App in that Step,
      then the system should not display the removed Form View.

      5-Given that a user has configured multiple Form Views in Read-only and/or Editable modes in one same Step of the Workflow App,
      when a user opens an instance of the running Workflow App in that Step,
      then the system should display a concatenation of all Form Views selected in that step, each being displayed accordingly to the Editable or Read-only configuration set in the builder.

      • If one of the Object's fields was already filled in a Form View of a previous step, then if any Form View of the current Step has that same field, it should be opened with this field already filled with the data.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Verify if the test labels were added;
      • 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

          Issue Links

            Activity

              People

              Assignee:
              rodrigo.cunha Rodrigo Cunha
              Reporter:
              matheus.xavier Matheus Xavier (Inactive)
              Engineering Assignee:
              Product Team Workflow
              Recent user:
              Rodrigo Cunha
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master