As an object creator, I want to define one-to-one relationships among custom objects

• Type: Story
• Status: Closed
• Priority: Major
• Resolution: Discarded
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Objects
• Labels:
  • 7.4-must
  • forms-board-out
  • good-to-go
  • low-code-initiative
  • now-dxp-latam
  • pt-app-security-review
  • pt-upgrade-review
  • qa_reviewed

Context:

Some relationships must be in a 1 to 1 relation, a classic example of this relationship would be a citizen and its ID document. The one-to-one relationship also helps the user to build their objects, lets say we have this CitizenInfo, IDdocument objects, and Adress. If we add all the information of the IDdocument and Adress inside of the CitizenInfo one, it would be a massive table with the same permissions and would be much harder for the user to delete their adress and create a new one, or relate the adress with another objects that might be necessary.

Acceptance Criteria

1 - Given an objects admin,
when adding object relationship,
then I must be able to add one-to-one relationships among objects

• For this story we are only considering amog custom objects

2 - Given an objects admin,
when managing objects relationships,
then I must be able to manage the existing one-to-one relationships

3 - Given an objects admin,
when having a one-to-one relationship,
then I must be able to identify in both objects that relationship

4 - Given an objects admin,
when having a one-to-one relationship,
then I must be able to add only as fields in object layouts

• One-to-one should not be a relationship tab in the layout

5 - Given an user,
when adding entries in a object,
then I must be able to relate the entries from both objects

6 - Given an user,
when adding entries in a object,
then I must not be able to relate the same entry with more than one entry in the related object

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)