As a power user, I want to add new fields in System Objects and reflect in its APIs

• Type: Story
• Status: Closed
• Priority: Critical
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Objects
• Labels:
  • 7.4-must
  • bpm_q3
  • fc_22_08
  • now-dxp-latam
  • partial-dependency
  • pt-app-security-review
  • pt-upgrade-review
  • qa_reviewed
  • qa_test_mapped
  • retro_bravo_done
  • squad-bravo
  • team-bravo
  • ticketing-milestone
  • timeline_bpm_q3_q4
• Epic Link: Low Code Data - System Objects Extensions 2/2

Context:

This story aims to allow power users to do the following actions on System Object:

• Create new custom fields to extend the data structure of a system object
• Update previoysly created custom fields in the system object structure
• Remove existing custom fields that are no longer relevant to the business
• Extend the System Objects APIs

Mockups:

Acceptance Criteria

1 - Given a power user,
when managing a System Objects
then I must be able to add a new custom field

• This field can be created using all data field types and has the same rules.
• This field needs to exist on the API, and follow all the existing rules

2 - Given a power user,
when managing a System Objects
then I must be able to use a custom field as Title Field

3 - Given a power user,
when managing a System Objects
then I must be able to edit a custom field

4 - Given a power user,
when managing a System Objects
then I must be able to delete a custom field

5 - Given a power user,
when managing a System Objects
then I must be able to use the custom field on Actions

6 - Given a power user,
when managing a System Objects
then I must be able to use the custom field on Validations

5 - Given a power user,
when managing a System Objects
then I must be able to import/export the object with the custom fields

Definition of Done (DoD):

• All Acceptance Criteria were passed;
• Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
• Validated by QA and Product Manager;
• No critical bug related to Story scope (FP5);
• Make sure that all system documentation were updated (if necessary)