As an App Adm, I want to add new upload fields on my object

• 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_manual
  • appbuilder_test_needed
  • appbuilder_test_poshi_sanity
  • appbuilder_test_spira
• Story Points: 1
• Epic Link: App Builder - Create Custom Objects
• Sprint: App_Builder_7.3_7

As an App Adm, I want to add new upload fields on my object, so that I can collect, store and show files in my object

Design Deliverables:

Mockups

The Upload Field Type:

Nowadays, digital files have become part of the daily actives of most of the business industries/market. That being said, the upload is a crucial field type to attend most of the use cases that customers may have for creating Forms based Apps and automating their business process. In this Story, we aim to allow users to drag, drop and include upload fields into their Form Views, and consequently, add digital files as a field of the data model of the custom object.

Acceptance Criteria:

• Given a user in the "Form View Builder" screen of an object, when the user drags and drop a "Upload" field type from the sidebar into the Form stage area, then the system must include and display an Upload type field into the current Form View.

• Given a user in the "Form View Builder" screen of an object, when the users includes a new "Upload" field type into the Form View , then the system must also automatically include a new "Upload" field type into the Data Model of the object.

• Given a user in the "Form View Builder" screen of an object, when the user is dragging and dropping a "Upload" field into the Form stage, then he should be able to choose the place where the upload field should be displayed in the Form View.

• Given that a user has included a "Upload" field into a Form View of an Object, when the user highlights/selects the field in the Form View stage area, then the system must provide the user with the same options and properties of the "Upload" field available in the Forms module.
  • Including: Change label, set a placeholder text, set a help text, required, change field name, change searchable options, show/hide label, make repeatable, etc.

• Given that a user has included a "Upload" field into a Form View of an Object, when a user clicks in the "Duplicate" option of the field kebab menu, then the system must automatically create a copy of the field into the Form View and in the Object model.
  • Obs: use the same behavior of the Forms module.

• Given that a user has included a "Upload" field into a Form View of an Object, when the user clicks in the "Remove From Object" option of the field kebab menu, then the system must remove the field form the Form View and also remove it from the data model of the Object.
  • Obs: When the field is being used by other Form Views, the system must warn the user and propagate the deletion to the other forms.

• Given that a user has included a "Upload" field into a Form View of an Object, when the user clicks in the "Remove from Form" option of the field kebab menu, then the system must remove the field from the Form View, but keep it as an attribute of the object;
  • Obs: When the field is being used by other Form Views, the system must delete the field from the Form View in question, but keep it in those other Form Views.

• Given that a user has included a "Upload" field into a Form View of an Object, when the user drag and drops an existing field in the stage area, then the system must allow the user to reorder the position of the field in the Form View.

• Given that a user has included a "Upload" field into a Form View of an Object, when the user highlights/selects the field in the Form View stage area, then the system must allow the user to see and change the properties of the field.

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)