Request to add operation 'required_expected_variables' as the combination of required_variables and expected_variables

[mhungria]

Requesting to add operation 'required_expected_variables' as the combination of required_variables and expected_variables, to retrieve the Library IG variables with Core = 'Req' and Core = 'Exp' in only 1 list of variables, ordered by the variable's Ordinal.

It would allow us to improve checks: data against the Library and, when available, Define-XML against the Library.
Note: the variables that are to be present in a dataset (or its Define-XML document) include both Core ‘Req’ and ‘Exp’ and combined in the relative order indicated in the IG

[gerrycampion]

@mhungria can you provide a sample rule and the standard / rule id's this would apply to?

[mhungria]

@nickdedonder, @gerrycampion, @SFJohnson24:

Thanks for reviewing the backlog. @ Gerry, sorry I didn't respond to your question before. I thought we had discussed at some point in one of the meetings.

1. A combined operation 'required_expected_variables' would help the usability of checks and visualization of results with sponsor software tools by consolidating the Variable Metadata Check for rule CG0014 Part A (CORE-000355) and CG0016 (CORE-000334).
   Note the relative order of variables is relevant for visualization and one could provide only the variables that are missing in the dataset so that it is straight forward for the user to take action on.

2. In addition, CG0014 Part B Record Data check (CORE-000356) could be improved once the consolidation in Transfer engine logic from azure #1 is provided.

One could implement #1 and #2 as two separate custom rules while the team evaluates if changes to any published rules are convenient or not and any future timing. Each sponsor would have the ability to include custom rules and exclude published rules that may have been enhanced with custom rules.