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

As an App Adm, I want to search for an object in the object list

    Details

      Description

      As an App Adm, I want to search for an object in the objects list, so that when I have a huge list of available objects, I can still easily find the object 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.
      Custom Objects:
      The purpose of custom objects is to allow the user to represent his business needs that aren't supported by Liferay's native objects. This way, if some kind of entity is needed, but not already in Liferay (e.g. Product Orders, Quotes, Vacation Request, etc.), he can create a custom object, gather and centralize the information in his app using different forms and tables.
      The Objects Search:
      It's expected that a user may need to create lots of custom objects to attend his business needs and when that happens, it may become very hard to search for specifics objects 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 objects 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 DXP instance with multiple custom objects created, when a user accesses the custom object listing screen, then the user must be able to search and retrieve all custom objects that has a specific "term" defined by him;
      • Given a DXP instance with multiple custom objects created, when a user accesses the "Custom Objects" listing screen of that instance, then the user must be able to order the list of "Custom Objects" by Name (Asc or Desc);
      • Given aa DXP instance with multiple custom objects created, when a user accesses the "Custom Objects" listing screen of that instance, then the user must be able to order the list of "Custom Objects" by Created Date (Asc or Desc);
      • Given a DXP instance with multiple custom objects created, when a user accesses the "Custom Objects" listing screen of that instance, then the user must be able to order the list of "Custom Objects" by Modified Date (Asc or Desc);
      • Given a DXP instance with multiple custom objects created, when a user accesses the "Custom Objects" listing screen of that instance, then the user must be able to combine a search for Custom Objects by term and also order by Name, Created Date or Modified Date.
      • Given that an user is searching for "Custom Objects" in the listing screen and that his search has retrieved one or more "Custom Object", when the user clicks on the "select all checkbox" of the top bar, then the system must select for the user all (and only) the Custom Objects that were retrieved by the search.
      • Given that an user has submitted a search in the "Custom Objects" 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 "Custom Objects" 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 Custom Objects available for that DXP Instance.
      • Given that an user has submitted a search in the "Custom Objects listing screen, when the user looks at the "Search results" banner, then the user must be able to identify how many "Custom Objects" were retrieved in the search results.
      • Given a DXP instance with several custom objects registered, when a user enters the App Builder's objects screen through the Control Painel, then the list of object should be ordered by the "last modified date" (most recent on top) as the default order.

      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
                Recent user:
                Clarissa Velazquez
                Participants of an Issue:
                Engineering Assignee:
                Felipe Pires
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  7.2.10 DXP FP2
                  7.2.10.1 DXP SP1
                  Master