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

As an App Adm, I want to search for an table view in the table views list

Details

    Description

      As an App Adm, I want to search for an table view in the table views list, so that when I have a huge list of available table views, I can still easily find the table that I need to work on.

      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 Views Search:
      In some cases, it's possible that a user may need to create lots of Table Views to attend his business needs and when that happens, it may become very hard to search for specifics Table Views among the dozens of others that may exist. To solve this problem, we need to let facilitate the user's life by adding tools that will let him easily find what he is looking for, those tools are:

      • A search field that will filter the listing screen with the Table Views based on the terms chosen by the user;
        • The search must be a approximate match (aka "LIKE search type" or "character by character comparison");
        • The search doesn't need to be a "live search", we can apply and retrieve the results after the user fills the field and press "enter/return" or the "magnifier Icon" button.
      • Ability to sort using the columns available in the table (Name, Created Date and Modified Date).
        • The default order of the screen (if a user enters for the first time) must be to order the most recently modified on top.

      Acceptance Criteria:

      • Given a object with multiple "Table Views" defined, when a user accesses the "Table View" listing screen of that object, then the user must be able to search and retrieve all table views that has a specific "term" defined by him;
      • Given an object with multiple "Table Views" defined, when a user accesses the "Table View" listing screen of that object, then the user must be able to order the list of "Table Views" by Name (Asc or Desc);
      • Given an object with multiple "Table Views" defined, when a user accesses the "Table View" listing screen of that object, then the user must be able to order the list of "Table Views" by Created Date (Asc or Desc);
      • Given an object with multiple "Table Views" defined, when a user accesses the "Table View" listing screen of that object, then the user must be able to order the list of "Table Views" by Modified Date (Asc or Desc);
      • Given an object with multiple "Table Views" defined, when a user accesses the "Table View" listing screen of that object, then the user must be able to combine a search for Table Views by term and also order by Name, Created Date or Modified Date.
      • Given that an user has submitted a search in the "Table Views" listing screen, when the search doesn't retrieve any results, then the system must show a "no results found" screen.
      • Given that an user has submitted a search in the "Table Views" listing screen, when the user clicks in the "Clear" button of the "search results" banner, then the system must clear the search field and show again all the Table Views available for the object.
      • Given that an user has submitted a search in the "Table Views" listing screen, when the user looks at the "Search results" banner, then the user must be able to identify how many "Table Views" were retrieved in the search results.

      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

              alex.candido Alex Candido
              eduardo.zoby Eduardo Zoby
              Felipe Pires Felipe Pires (Inactive)
              Kiyoshi Lee Kiyoshi Lee
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Packages

                  Version Package
                  Master