As an App Adm, I want to search for a specific field to add as a column to my table view

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.2.X, Master
• Component/s: App Builder
• Labels:
  • 7.3-app_builder_must_have
  • 7.3-ce-ga1
  • appbuilder_test_manual
  • appbuilder_test_poshi_sanity
  • appbuilder_test_spira
• Branch Version/s:
  7.2.x
• Backported to Branch:
  Committed
• Story Points: 2
• Epic Link: App Builder - Create Custom Objects
• Sprint: App_Builder_7.3_5, App_Builder_7.3_6, App_Builder_7.3_8
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/77628

Design Deliverable:

Mockups

As an App Adm, I want to search for a specific field to add as a column to my table view , So that when I have a huge list of available fields in my object, I can still easily find the field that I need to add.

Acceptance Criteria (In Progress)

• 1-Given an object with one or more fields/attributes, when the user is creating a new table view for that object, then the system must allow the user to search for a specific column(field) in the available columns list of the object in the Table View Builder.
  • The search must be a approximate match (aka "LIKE search type" or "character by character comparison");
  • The search result must still show if the column is available to be added or already inserted in the table view.

• 2-Given that a user is searching for a column in the table view builder, when the search result finds no match with the available columns/fields, then the system must show a “No columns/fields found” message.

• 3-Given that a user is applying a search and/or filter of columns in the sidebar of the Table View Builder, when there are results for the search and/or filter, then the user must be able to drag and drop a field from the search/filter result.

• 4-Given a user in the table view builder of an object, when the user clicks on the "Filter" box and selects one or more field types, then the system must filter the columns of the sidebar to show only the columns that matches the field types selected in the filter.

• 5-Given that a user has successfully applied a search for the columns of the Table View Builder, when the users clicks on the "x" (Clean) button of the Search box, then the system must clean the search box and go back to showing all available columns of that object.

• 6-Given that a user has successfully applied a filter per field types for the columns of the Table View Builder, when the users clicks on the Filter box and selects the "Clear Filter" option, then the system must clean the filter and go back to showing all available columns of that object.

• 7-Given a user in the Table View Builder of an object, when the user applies a Search for column name and a filter per field type, then the system must filter the columns to show only the columns that attends both criteria (the search and the filter).

Definitions of Done

• Related tests created and passed successfully;
• All Acceptance Criteria were passed;
• Make sure that all system documentation were updated (if necessary);
• Validated by QA, Product Designer and/or PM;
• No critical issue related to Story scope (ex.: similar of a FP4, FP5 bug);
• Code with peer review completed.