As an App User, I want to view details of an entry in an App

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.3.0 CE GA1, Master
• Component/s: App Builder
• Labels:
  • 7.3-app_builder_must_have
  • 7.3-ce-ga1
  • appbuilder_test_manual
  • appbuilder_test_needed
  • appbuilder_test_poshi_sanity
  • appbuilder_test_spira
• Story Points: 5
• Epic Link: App Builder - Create Custom Objects
• Sprint: App_Builder_7.3_11, App_Builder_7.3_12

As an App Adm, I want to view details of an entry in an App in the product menu

Design Deliverable:

Mockups

Using an App deployed in the product menu

This user stories aims to let users view details of entries in a running Apps that were deployed in the product menu of Liferay.

Acceptance Criteria:

• 1-Given an App that was deployed with a Table View in the Product Menu and that there is entries for the App's object already, when the user accesses the App through the product menu, then the user must be able to access the "Details view" of a single entry in the Table View through the kebab menu;

• 2-Given an App that was deployed with a Table View in the Product Menu and that there is entries for the App's object already, when the user accesses the App through the product menu 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.

• 3-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.

• 4-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.

• 5-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;

• 6-Given that a user accessed the Edit mode of an App's entry, when the user changes values of one or more fields and clicks on the "Cancel" button, then the system must cancel the modifications made on the entry's values and go back to the "Details View" of the App in "read-only" mode.

• 7-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;

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)