UPSERT when processing rule
User Story
As a SysAdmin, I want to have new products created if not found when trying to map.
Background Documents
Acceptance Criteria
-
The method of copy should be an UPSERT. -
A product inserted (not updated) in Family-B will need a unique identifier generated. This identifier should be a UUIDv4, generated by the system. -
in Process Tracker, there should be distinction between number of inserted and updated items to destination Family.
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 Joanna