Processing a rule
User Story
As a SysAdmin I want to be able to process a rule.
Background Documents
(Insert links to any relevant documents)
Acceptance Criteria
-
all attributes that exist in both families would be copied directly so that I may see a basic copy from family to family. -
Processing should be batched so as not to cause an out of memory error. -
Batch run may take quite some time, during which new Products might be added or removed from the source family, added products should be ignored, removed products should generate a quiet warning in the logs. -
Products created/updated in Family B should bypass the Draft system. -
Scoped (aka Channel) and Locale specific values are copied as-is. -
As a SysAdmin I want to be able to see the status of my rule running so that I can see how many products in Family A were read, how many have been written to Family B, and any read/write errors involved.
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