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

As an App User, I want to add, update, view and delete entries of a standalone App

    Details

      Description

      As an App Adm, I want to add, update, view and delete entries of a standalone App

      Design Deliverable:

      Mockups

      Context

      This user stories aims to let users view and use running Apps that were deployed as standalone.

      Acceptance Criteria:

      • Given an App that was deployed in as standalone, when the user accesses the link provided for the standalone App, then the system must show and allow the user to use the App;
      • Given an App that was deployed with a Table View as standalone and that there's no entries for the App's object yet, when the user accesses the App through the standalone link, then the system must display a "No entries yet" page;
      • Given an App that was deployed with a Table View as standalone and that there is entries for the App's object already, when the user accesses the App through the standalone link, then the user must be able to see and manage the list of entries of the object using the Table view;
        • The user must be able to delete a single entry in the table view through the kebab menu;
        • The user must be able to edit a single entry in the table view through the kebab menu;
        • The user must be able to access the "Details view" of a single entry in the Table View through the kebab menu;
        • The user must be able to bulk delete entries by selecting them in the Table View and clicking in the "Delete button" of the top bar.
      • Given an App that was deployed with a Table View as standalone and that there is entries for the App's object already, when the user accesses the App through the standalone link and clicks in a existing entry in the Table View then the must open the "Details View" of the entry with its submitted values as "read-only";
        • For "Upload field types", the system must allow the user to see a preview of the file when feasible.
      • Given an user seeing the "Details View" of an entry of an App, when the user clicks on the "Next Entry Button", then the system must display the "Details View" of the next entry submitted in the Table View;
        • If technically feasible, the sequence of the "next" and "previous" must follow the order configured by the user in the Table View. If not feasible, we can use the creation date as order to follow.
      • Given an user seeing the "Details View" of an entry of an App, when the user clicks on the "Previous Entry Button", then the system must display the "Details View" of the previous entry submitted in the Table View;
      • Given an user seeing the "Details View" of an entry of an App, when the user clicks in the "Edit Button", then the system must allow the user see and edit the values submitted in the Entry using the "Form View" of the App;
      • Given an user seeing the "Details View" of an entry of an App, when the user clicks in the "Delete Button", then the system must prompt the user for a confirmation and if confirmed, delete the entry of the object;
      • Given an user seeing the "Details View" of an entry of an App, when the user clicks in the "Versions Button", then the system must show the list of existing versions for that entry;
        • The versions must be numbered (1.0, 1.1, etc.);
        • The versions must also show who created, when it was created and a change log if available;
        • The user must be able to preview a specific version;
        • The user must be able to "rollback" to a specific version;
      • Given an App that was deployed with a Form View and a Table View as standalone, when the user accesses the Table View of the App and clicks in the "New Entry" button, then the system must open the Form View of the App and let user submit a new entry;
      • Given an App that was deployed with a Form View as standalone, when the user accesses the Form View of the App, then the user must be able to access the form and submit a new entry using the Form view;
      • Given an App that was deployed with a Form View as standalone, when the user accesses the Form View of the App and fills forms, then the user must be able to cancel the form submission;
      • Given an App that was deployed with a Form View, when the user accesses the form view, fills and submit a new entry, then the system must save the new entry in the object;
      • Given an App that was deployed with a Form View and a Table View, when the user accesses the form view, fills and submit a new entry, then the system must save the new entry in the object and redirect the user back to the Table View of the App;

      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)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              alex.candido Alex Candido
              Reporter:
              eduardo.zoby Eduardo Zoby
              Engineering Assignee:
              Felipe Pires (Inactive)
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.3.0 CE GA1
                  Master