Done
Details
Assignee
Illia DaliekIllia DaliekReporter
Magda ZacharskaMagda ZacharskaPriority
P3Story Points
5Sprint
NoneDevelopment Team
FirebirdTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Illia Daliek
Illia DaliekReporter
Magda Zacharska
Magda ZacharskaPriority
Story Points
5
Sprint
None
Development Team
Firebird
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 23, 2021 at 6:36 PM
Updated November 18, 2021 at 10:08 PM
Resolved November 18, 2021 at 10:08 PM
Purpose/Overview:
Once the user saves the matching files locally, the file can be modified and used later for the bulk edit. It may happened that the file that is later uploaded contains errors and the changes will need to be reversed. For this purpose, the copy of the data will need to be stored on the server side so that it can be used to restore the changes
Requirements/Scope:
The records are stored for limited time. The time should be configurable on the tenant level with the default value set to 14 days
The records should be stored either in the module local database or S3 (storage costs should be considered)
Data purging mechanism has to be provided so that records that passed configured limit time can be removed
The data can be retrieved on demand
Approach:
Acceptance criteria:
The proposed approach is documented and reviewed with the team
Technical stories are created
Question: Should the errors be stored servers side as well?