MAINSYSTEMS 
verify a configuration change through appropriate retesting
1. Regulatory Concept & Core Standards
In this video we will consolidate a skill: verify a configuration change through appropriate retesting. Use the case to test what you would do in a similar situation. We will explain the proposed response step by step so that you can understand each choice and recognise when more information would be needed. Configuration examples describe general working methods. Verify features in the actual system. Changes must connect permissions, procedures and Estonian legal requirements. Use fictional test cases so that verification creates no new confidentiality risk.
An administrator seeing a setting does not establish correct operation. Test actual roles, permitted actions and blocked access. Changes may affect messages, logs and older cases. Document the test’s scope.
Apply the following rule: Section 10(3) prescribes three years and refers to feedback under section 11(4), while final-outcome feedback now appears in section 11(6). Do not conceal the cross-reference issue or automatically replace it with receipt. Document the legally confirmed starting event before automating deletion. Government Regulation 12 of 2 February 2026 covers the report, collected material and media, review of oral-report minutes and destruction under a procedure approved by the organisation’s head.
2. Practical Implementation & Procedure
Define expected results, use fictional cases and different roles, and test grants and removals. Record version, result and repair. Retest to show the correction works without a new problem. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.
3. Case Study & Compliance Action
A limited role can open one case but search exposes other reports’ titles. The team restricts search and checks lists, export and notifications. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.
The exercise is as follows: Does one successful opening test prove every permission correct? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.
No. Test prohibited access and other revealing views. Limit the conclusion to the actual test coverage.
One mistake to avoid is: extending one positive test to the whole system.
Now apply the national rule to a second decision. The system deletes every case five years after receipt. Is that correct for Estonia?
No. The three-year period in section 10(3) references feedback rather than automatically receipt. The current cross-reference issue needs a documented legal resolution. Apply Regulation 12 and privacy rules to related material and copies. Do not keep everything indefinitely without grounds.