[BUG] rules executed on batch result in error (Oops)

[oba-reliatec]

Description:
Rules executed on batch result in error (Oops) after new CRF versions with new items are introduced into the study.

Requirements:
A study with rules using items that occur not in all versions of a CRF.
I.e. you have CRF C version 1 with items IA, IB, and version 2 with items IA, IB, IC. A rule referencing item IC in CRF C.

Steps to follow:

1. In the Tasks menu select CRFs and click on the view icon (magnifier) that shows the CRF metadata (for CRF C following the above example).
2. Click "Run All Rules for this CRF" and submit.

Expected result:
The page Execute rules report (dry run) is displayed, allowing to executed the rules-initiated actions by clicking submit or to cancel.

Actual result:
Oops Error page

Related (optional):
#339

Screenshots (optional):

Server Setup (optional):

• OS Debian 10
• Application Server Tomcat9
• Java openjdk-14-jdk
• Postgresql 12

Additional context (optional):
If the rule is executed individually it works, the problem only occurs on batch.
When executing rules in batch mode, LibreClinica goes through all items of the CRF and looks for them in all versions of the CRF. When it comes to a version, that does not contain the items, it throws an exception. The problem can be circumvented by specifying the whole "path" of the item in the rule definition, including CRF version and item group, e. g. instead of

I_IC

try

F_C_V2.IG_UNGROUPED.I_IC

However, the first version is recommended in the OpenClinica manual. This recommendation makes sense, as it prevents you from updating your rules everytime you update CRFs.