As an App Adm, I want to search for a specific object field, so that I can easily find the fields that I need to insert in my Form View.
Once an object can have more than one form view, it will be a common use case to have users creating new Form View for objects that are already define with fields (attributes), that can even have dozens or even hundreds of fields in a single object. That being said, just listing for the user all the fields available when creating a new form view won't be enough, users may take a lot of time to create a Form View if they have to "eye-scroll-search" for fields every time they need a field that isn't already visible for him.
To solve that problem, this Story aims to create a search tool to let users quickly and easily find fields of the object that he needs to insert in the Form View.
- 1-Given an object with one or more fields/attributes, when the user is creating a new Form View for that object, then the system must allow the user to search for a specific field in the available fields list of the object in the Form View Builder.
- The search must be a approximate match (A.K.A "LIKE search type" or "character by character comparison");
- The search result must still show if the field is available to be added or already inserted in the form view.
- 2-Given that a user is searching for an object's field in the Form View builder, when the search result finds no match with the available fields, then the system must show a “No fields found” message.
- 3-Given that a user is applying a search of fields in the Object sidebar of the Form View Builder, when there are results for the search, then the user must be able to drag and drop a field from the search result to the Form View canvas.
- 4-Given that a user has successfully applied a search for the fields in the Object sidebar in the Form 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 fields of that object.
- 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)