If a case is waiting on a Validator queue, and the case is subsequently resent from the Online Information System, the case on the Validator queue will be overwritten by the new case.
There are however two exceptions to this behaviour if the original case is on an ordinary validation queue (i.e. not a copy queue):
- The resent case is queued to a different queue to the original case, or
- The resent case is autovalidated.
The resent case is queued to a different queue to the original case
If the resent case is queued to a different queue to the original case, the original case is deleted.
If the original case was being reviewed in the Validator at the time the resent case is processed, then the original case will be deleted once the user has finished reviewing that queue.
In fact, any actions on the original case will be ignored if done after the resent case is processed. In particular, if the original case was approved (with or without change), then the approved report will not be sent back to the Online Information System.
This is to prevent two approved reports being sent back to the Online Information System. The approved report sent back to the Online Information System will be the one for the resent case on the different queue.
Similarly, if the report was approved with change, then the case will not be sent to the Knowledge Builder’s rejected case list.
The resent case is autovalidated
If the resent case is autovalidated, the report for the resent case will be immediately sent back to the Online Information System. The original case will be deleted for the Validator queue.
As above, if the original case was being reviewed in the Validator at the time the resent case is processed, then the original case will be deleted once the user has finished reviewing that queue.
Note:If the original case is on a copy queue, and the resent case is queued to a different queue or is autovalidated, then the original case is not deleted.