[SPIKE] Save and retrieve matching records server-side

Description

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:

  1. The records are stored for limited time. The time should be configurable on the tenant level with the default value set to 14 days

  2. The records should be stored either in the module local database or S3 (storage costs should be considered)

  3. Data purging mechanism has to be provided so that records that passed configured limit time can be removed

  4. 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?

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Illia DaliekNovember 17, 2021 at 2:52 PM

Illia DaliekNovember 11, 2021 at 1:35 PM

, a question regarding errors in a file. It says that in case of errors the changes will need to be reversed.
What are these errors actually? Does it involve just typos?

As I understood in the case of a wrongly edited file the user need to have a possibility to download the same file again in a non-edited state. Correct me if I am wrong.
And regarding reversed changes - does it mean changes done by the user in a file or it implies the changes done to some storage while processing the file?
Actually, on the backend side, we'd like to verify the correctness of a file before submitting the changes to the storage because it is a challenge to roll back the submitted changes to storage.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

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
TestRail: Cases
TestRail: Runs