As an App Adm, I want to delete a field from an object

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.3.0 CE GA1, 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
• Story Points: 5
• Epic Link: App Builder - Create Custom Objects
• Sprint: App_Builder_7.3_8, App_Builder_7.3_7, App_Builder_7.3_9, App_Builder_7.3_10, App_Builder_7.3_11

As an App Adm, I want to delete a field from an object, so that I can avoid misconceptions and remove obsolete or faulty fields from my object model

Design Deliverable:

Mockups

Delete Field from a Object

There are several reasons that can make a user need to delete a field from an object, including:

• Mistakes during the creation of an update;
• Removing obsolete information that doesn't add value anymore;
• Removing faulty fields;
• Etc.

To solve those problems, this Story aims to let the user delete a field from an object, including the consequences of propagating the deletion.

Differently from deleting from a Form View, the field deleted from an object cannot be used anymore by any View (Form or Table), making necessary to create it again if the user finds out the he needs the deleted field again (that's why warns and confirmations will be very important during this actions).

Acceptance Criteria

• 1.Given an object with existing fields, when the user clicks on the "x" button of a field in the left panel or in the "Delete from Object" option in the kebab menu of a field inside a Form View of that object, then the user must be prompted for a confirmation before deleting the field form the object.

• 2.Given an object with a same existing field being used in more than one View (Form and/or Table) , when the user clicks on the "x" button of a field in the left panel or in the "Delete from Object" option in the kebab menu of a field inside the Form View, then the user must be warned that the field is being used by others Views and prompted for a confirmation before deleting the field form the object.
  • The warn must also inform which views are also using the field.
  • If confirmed, the field deletion should be propagated to the other views (Forms and/or Table) that has that same field.

• 3.Given an object with an existing field that has data (entries) stored in it, when the user clicks on the "x" button of a field in the left panel or in the "Delete from Object" option in the kebab menu of a field inside the Form View, then the user must be warned that the field has already data (entries) stored and prompted for a confirmation before deleting the field form the object.

• 4.Given that a user requested to delete a field from an object and that he was prompted for a confirmation, when the user confirms the deletion of the field from the object, then the field should be deleted from any view containing this field and also from the object data model.

• 5.Given that a user requested to delete a field from an object and that he was prompted for a confirmation, when the user doesn't confirm the deletion of the field from the object, then the delete action must be cancelled and no data or configurations should be lost.

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)