As an App Adm, I want to search for a deployment in the deployments list

• 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_poshi_sanity
• Story Points: 2
• Epic Link: App Builder - Usability Features
• Sprint: App_Builder_7.3_3, App_Builder_7.3_4

As an App Adm, I want to search for an deployment view in the deployment list, so that when I have a huge list of available deployments, I can still easily find the deployment 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.
Deployments:
After having at least one Form View and one Table View defined, the App Builder admin will need to deploy his App in order to make it accessible for the final users, be it as a standalone app, widget or in one of the DXP products menu. Once an Object can have more than one Form and/or Table view, sometimes the App Admin will need to make more than one deployment, one for each combination of Form and Table that he needs available for his App to work and address all possible requirements.
The Deployments Search:
In some cases, it's possible that a user may need to create lots of Deployments to attend his business needs and when that happens, it may become very hard to search for specifics Deployments 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 Deployments 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, Deployed As, Status, 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.
• An option to filter by the Deployment status (deployed or undeployed).

Acceptance Criteria:

• Given a object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to search and retrieve all Deployments that has a specific "term" defined by him;

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to order the list of "Deployments" by Name (Asc or Desc);

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to order the list of "Deployments" by Created Date (Asc or Desc);

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to order the list of "Deployments" by Modified Date (Asc or Desc);

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to order the list of "Deployments" by Status (Deployed Undeployed) (Asc or Desc);

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to order the list of "Deployments" by Deployment type (Widget, standalone, etc.) (Asc or Desc);

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to apply a filter to see only Deployments in a specific status (Deployed or Undeployed).

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to apply a filter to see only Deployments that were deployed in specific types (Standalone, Widget, etc.).
  • Obs: this filter must allow multiple selection (e.g. Filter deployments that were deployed as Widget and Standalone)

• Given an object with multiple "Deployments" defined, when a user accesses the "Deployment" listing screen of that object, then the user must be able to combine a search for Deployments by term, filter by status and also order by Name, Status, Deployment type, Created Date or Modified Date.

• Given that an user is searching for "Deployments" in the listing screen and that his search has retrieved one or more "Deployments", 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 Deployments that were retrieved by the search.

• Given that an user has submitted a search in the "Deployments" 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 "Deployments" 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 Deployments available for the object.

• Given that an user has submitted a search in the "Deployments" listing screen, when the user looks at the "Search results" banner, then the user must be able to identify how many "Deployments" 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)