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

As an App Admin, I want to view and edit existing Form and Table Views during my App creation experience

    Details

      Description

      As an App Admin, I want to view and edit existing Form and Table Views during my App creation experience

      Design Deliverables

      Updated Mockups: https://www.figma.com/file/S75CVxXBMzWDQ69Aoymmaz/03-LPS-111683-view-and-edit-form-and-table-views-during-app-creation?node-id=1%3A61

       

      Prototype: https://www.figma.com/proto/S75CVxXBMzWDQ69Aoymmaz/03-LPS-111683-view-and-edit-form-and-table-views-during-app-creation?node-id=1652%3A3170&viewport=-1064%2C457%2C0.2433912456035614&scaling=min-zoom

       

      Old Mockups: https://www.figma.com/file/g8cyvPMR9g8UAt3qlYfo0A/25-view-edit-form-table-views?node-id=1%3A61

      Context

      One of the main values provided by the App Builder is the automation of business operations. Once the creation of Standart 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 the user to check/view the Form and Table Views that he chose on LPS-111266 and make adjustments if desired.

      Acceptance Criteria

      1- Given that a user has selected a Form View in the Workflow App Creation experience,
      when the user clicks in the "Open" button,
      then the system should open the Form View Builder for the selected Form View.

      • It should use the same Form View Builder already implemented in App Builder portlet.

      2- Given that a user has selected a Table View in the Workflow App Creation experience,
      when the user clicks in the "Open" button,
      then the system should open the Table View Builder for the selected Table View.

      • It should use the same Table View Builder already implemented in App Builder portlet.

      3- Given that a user has selected and opened a Form View in the Workflow App Creation experience,
      when the user makes changes on the Form View through the builder and clicks on the "Save" button,
      then the system should save and apply the changes made on the Form View selected.

      4- Given that a user has selected and opened a Table View in the Workflow App Creation experience,
      when the user makes changes on the Table View through the builder and clicks on the "Save" button,
      then the system should save and apply the changes made on the Table View selected.

      5- Given that a user has selected and opened a Form View in the Workflow App Creation experience,
      when the user makes changes on the Form View through the builder and clicks on the "Cancel" button,
      then the system should drop any changes made on the Form View selected.

      6- Given that a user has selected and opened a Table View in the Workflow App Creation experience,
      when the user makes changes on the Table View through the builder and clicks on the "Cancel" button,
      then the system should drop any changes made on the Table View selected.

      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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jon.wood Jon Wood
              Reporter:
              matheus.xavier Matheus Xavier
              Engineering Assignee:
              SE Support
              Recent user:
              Marta Elicegui
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.4.X
                  Master