TEDEFO 5001 dependency graph

[rousso]

No description provided.

[bertrand-lorentz]

I do not see any unit test for global variables, for example with en EFX rule like:

LET text* : $global-org-ids = OPT-200-Organization-Company:rawValue;

WITH OPT-300-Contract-Signatory
  ASSERT OPT-300-Contract-Signatory in $global-org-ids
    AS ERROR R-4ZU-5UE
    FOR OPT-300-Contract-Signatory
    IN *

From this rule, OPT-300-Contract-Signatory effectively depends on OPT-200-Organization-Company.
But I'm not sure if it is supposed to be handled by the dependency extraction.

[rousso]

I do not see any unit test for global variables, for example with en EFX rule like:

LET text* : $global-org-ids = OPT-200-Organization-Company:rawValue;

WITH OPT-300-Contract-Signatory
  ASSERT OPT-300-Contract-Signatory in $global-org-ids
    AS ERROR R-4ZU-5UE
    FOR OPT-300-Contract-Signatory
    IN *

From this rule, OPT-300-Contract-Signatory effectively depends on OPT-200-Organization-Company. But I'm not sure if it is supposed to be handled by the dependency extraction.

Indeed, indirect dependencies through variable references are not currently being detected.
In general, this feature is meant for client-side validation so it should actually exclude the post-validation rules.
This type of implementation is currently encountered in in rules meant to be for post-validation (on the xml).
Nevertheless, I should consider this in a future iteration and I will create a ticket for it.
For this iteration i think this should be left out of scope.

[bertrand-lorentz]

OK to have indirect dependencies through variable references out of scope for now.
Just want to ensure it was not an oversight.