Description

Imagine two users (UserA - right, UserB-left)
UserA has created a TEI on the system and has synchronized it. It contains the UNIQUE attribute 0011.

UserB decides to create a new TEI (the same 0011) as they are not aware that the TEI might have already been created so they perform the search

They ignore the results and decide to create the TEI with 0011 by clickin on the button

The UserB will never be able to send the TEI 0011 (which is correct) as it already exists on the server. However, the App should have blocked the insertion as a search was performed even though the TEI was not downloaded.

Requirements

• Do not copy unique attributes from search to enrollment form when creating a new TEI

• In the enrollment form, when a unique attribute is changed, perform an online search (if connection available) to check if the value is in used in the server and the uniqueness in the system/orgunit is fullfill.

Acceptance Criteria

GIVEN a search by unique attribute
WHEN the user decides to create a new TEI
THEN do not copy searched unique attribute value to the form

GIVEN an enrollment form with unique attributes and an internet connection
WHEN the user changes the attribute value
THEN uniqueness will be checked using an online search (org unit included for unique in org unit, not needed for unique in system)

GIVEN an enrollment form with unique attributes and no internet connection
WHEN the user changes the attribute value
THEN uniqueness will be checked locally (org unit included for unique in org unit, not needed for unique in system)

Develop

Test

Tests cases :

Possible side effects to take into account: