As an App Adm, I want to use an existing fieldset

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Data Engine
• Labels:
  • 7.3-app_builder_must_have
  • 7.3-ce-ga3
  • 7.3_form_builder_replacement_must_have
  • appbuilder_test_manual
  • qa_reviewed
• Epic/Theme:
  • Data_Engine
  • Old_Form_Builder_Renderer_Replacement
• Epic Link: WEM & D&M requirements
• Sprint: App_Builder_7.3_18, App_Builder_7.3_19, App_Builder_7.3_20, App_Builder_7.3_21, App_Builder_7.3_22, App_Builder_7.3_23, App_Builder_7.3_24, App_Builder_7.3_25, App_Builder_7.3_26, Data_Engine_7.3_29, App_Builder_7.3_27, Data_Engine_7.3_28

As an App Adm, I want to use an existing fieldset

Design Deliverable:

Mockups

Context

It is very common for users to find themselves in need of using the same group of fields in different objects and forms views (e.g. address). Without fieldsets, the users would have to create those same fields over and over for each object, even when all the parameters and configurations are exactly the same for all objects, there is no way to reuse. To solve that, we need to implement the fieldsets, which will offer them a way to save, update and reuse those groups of fields that are commonly used by many of their objects.

This Story aims to allow users to check the list of saved fieldsets and place them in their Objects and Form Views.

Users should be able to:

• Check the list of saved/available fieldsets
  • Saved fieldsets should be shared across objects
    • A fieldset created in an object X should also be available for object Y.
• Reuse/insert an existing fieldset into the Form View/Object
  • When this happens, the fieldset should be linked to the object/form and the fields of the fieldset shall now be also in the object/form
  • If there is already a field in the Form/Object with the same "Field name" that one of the fieldset's field, the new field that will be inserted along with the fieldset should be automatically renamed to avoid field name conflicts.

When is use, fieldset should:

• Act as a group in the Form, allowing users to move (drag and drop) the group of fields as a whole in the view;
  • Users should be able to change the size and position of the field within the fieldset.

Acceptance Criteria

• 1- Given that a user is creating a Form View for an Object, when he clicks on the "Fieldset" tab of the right sidebar, then the system should list for the user the saved fieldsets that are available for him.
  • Fieldsets should not be object scoped, users should be able to share fieldsets across objects.

• 2- Given that a user is creating a Form View for an Object and clicked on the "Fieldset" tab of the right sidebar, when a user double clicks or drag and drop an existing fieldset into the Form View canvas, then the fields of the fieldset should now be in the Object and the Form View
  • The Object and Form View should now be linked to the fieldset, in a way that any update on the fieldset should impact also the Form/Object.
  • If there is already a field in the Form/Object with the same "Field name" as one of the fieldset's field, the new field that will be inserted (along with the fieldset) should be automatically renamed to avoid field name conflicts.

• 3- Given that a user is creating a Form View for an Object and the Form View has a fieldset in it, when a user clicks to drag inside the area of the fieldset, then the user should be able to move/drag and change the position of the fields as a group in the Form View.

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)
• Make sure that it has the extensions points needed to allow GS and customers to customize the feature