Properly link comments, verifications and approvals to batches

When Unit Procedure level criteria are used to link a report template to batches, it is possible to select any Unit Procedure, Operation, Phase or step to generate the report.

Whatever the selected Unit Procedure, Operation, Phase or step, the generated report will always be for the entire batch.

There is therefore a large number of possible selections which will all create the same report (same report template applied to the same batch, showing the same content).

The problem is that Comments, Verifications and Approvals are linked to the original selection, not the batch itself.

This creates a situation where user1 can generate a report and add a comment stating there is an issue. Then user2 generates the same report (using a different UP, operation or phase), not see the comment and approve the report.

In some cases, there will be hundreds of different instances of the same report. Each of them with its own set of Comments, Verifications and Approvals.

This does not match with Electronic Records/Electronic Signatures (ER/ES) standards and should be considered a design flaw.