As an App Adm, I want to create a new table view for an object

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 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_4, App_Builder_7.3_5

As an App Adm, I want to create a new table view for an object. so that I can customize the table/listing views that my App's user are going to use.

Design Deliverables:

Mockups

Context

App Builder:
In this first version of the product, we are proposing a feature that allow user to create CRUD applications. That being said, each object will represent a new App that will be able to insert new entries, see the listing, delete and view existing entries.
Table Views:
To view the list of existing entries of an Object, the App admin will need to create Table Views that will be published and consequently, used by the App's final users to see the listing of entries and get access to the basic actions of the App (add, update, delete, view details).
The Table View Builder:
In order to give the user the right tool and environment to build and update the listing screens that his App is going to use, we need to create a new feature that will let the user configure things like:

• Name the Table View;
• Which columns will be available in each Table View (won't be implement here, it will have a specific User Story for it;
• Customize the width order of each column (won't be implement here, it will have a specific User Story for it);
• Fixed entries filters (won't be implement here, it will have a specific User Story for it);
• Which columns the user can use to filter and/or order by (won't be implement here, it will have a specific User Story for it).

In this story, we aim to create just the basic "structure" of the Table View Builder, in which will be later further increment to add the features listed above.

Acceptance Criterias

• Given a user in the "Table View Listing" screen of an object, when the user clicks in the "New Table View" button, then the system must redirect the user to the "Table View Builder" screen.

• Given a user in the "Table View Builder" screen of an object, when the user inserts a name in the "Table View Name" field and presses enter/return, then the system must rename the current "Table View" to the name inserted by the user.
  • Obs: Restrictions for the "Table View Name":
    • Should not be empty;
    • Should not have only spaces (" ").

• Given that a user is in the "Table View Builder" of an object and has already named it, when the user clicks on the "Save" button, then the system must save the new "Table View" and associate it with the current object.

• Given that a user is in the "Table View Builder" of an object, when the user clicks on the "Cancel" button, then the system must cancel the creation of the "Table View" and redirect him to the "Table View Listing" screen of the object.

• Given that a user in the "Table Views Listing" screen of an object, when the user accesses the "Table View Builder" screen, then the user must be able to identify where is the area containing the available fields/columns/filters of the Table View and where is the stage area that will allow him to see and build the Table View.

• Given a user in the "Table View Builder" screen with the right menu bar open, when the user clicks in the ">" button of the right menu bar, then the system should close/hide the right menu bar from the user.

• Given a user in the "Table View Builder" screen with the right menu bar closed, when the user clicks in the "<" button of the right menu bar, then the system should open/show the right menu bar for the user.

• Given that a user in the "Table Views Listing" screen of an object, when the user accesses the "Table View Builder" screen, then the system must give a tip to the user that it's possible to drag multiple columns to the table at once.
• Given a user in the "Table View Builder" screen, when the user clicks in the "<" button of the top left navigation bar, then the system should redirect him to the "Table View Listing" screen of the object.**
• Given a user in the "Table View Builder" screen, when the user clicks in the "Save" button, then the Table view is saved and the the new table will shown in the table list.
• Given a user in the "Table View List" screen, when the user clicks on a Table View item or clicks on the edit action menu item, then user will be able to edit table view name.

 

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