Introduce "Identity for lookup"
User Story
As a SysAdmin, I want to be able to identify an attribute that should be used as as the "Identity for lookup".
This attribute must exist in both family's and is used to determine in the UPSERT if the action is to update or insert.
Background Documents
Acceptance Criteria
-
in create form -
edit form -
on rules list -
drop-down should display only those attributes that are in both chosen families - new endpoint needed -
backend validation if the attribute really is in chosen families
Definition of Ready
-
User Story can be broken down no further -
Acceptance Criteria and Story Points are agreed upon by development team and PO
Definition of Done
-
If required, UI Mockups are created and reviewed -
Code is written with automated unit tests, reviewed, merged to master branch, all tests pass -
All UI texts are multilingual -
Manual tests in test environment are successfully performed -
Test Plan is updated -
Documentation is updated -
Changelog is updated
Edited by Piotr Borek