Not all data is retrieved in certain situation when Extend to Database option is used with EDC

In the example rulesheet below, a Regeling has to be retrieved from the database based on a name (‘ViiV’).
User is interested in the AfpraakParameterItems under AfspraakParameter that are defined by transactieregelParameter with waardebereik=’ITEM’.



If the RuleStatements are enabled in the rulesheet above, the test results are different and afspraakParameter and afspraakParameterItem are retrieved



If in the rulesheet below , all rule statements are disabled.



The effect is that only Regeling and transactieregelParameter are retrieved as shown in below example:




If ‘Extend to Database’ is applied to part of the scope, the expectation is that all relevant data is retrieved. The purpose of this rulesheet is not to fire rules but to retrieve all relevant data here.User must not be forced to create a rule statement for each child leaf level in order to retrieve all the data.
For e.g. if there are 1000 records; it would produce 1000 rule messages and this is not desired.

 

This is expected behavior and Corticon EDC is functioning as designed .
The code is optimized to not load anything from the scope, if it is really not used in the rules.
Since no rules/rule statements apply to the child leaves (afspraakParameter and afspraakParameterItem) ,Corticon will not retrieve the data for these entities/attributes even if they are in the scope

Extend to Database’ is designed to enable retrieval of root-level entities.The feature you are requesting represents an enhancement.

• You may request to have a parameter or property added to control the EDC "Extended To Database" feature with optimization or without optimization.
• When no optimization property is used (Extend to Database (no optimization)), Corticon will retrieve all the relevant data from the database defined in the Scope.
• When optimization property is used (Extend to Database (optimization)), Corticon will use default behavior (as it is today ) and not retrieve all the data although it is present in the scope, since it is not used in the rules/rulestatment.
• This will not force the user to use rule messages for child level entities in order to avoid the code optimization and give the user flexibility.

You may request this enhancement through the Progress Community via an Ideas submission. Your feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the [Readme.txt file/Release Notes document] that accompanies each release. Once you have submitted your Idea the Progress Software Community will have the opportunity to comment on and vote for your Idea.

For detailed information on how to submit an Idea please visit our knowledgebase at  How to submit an idea for a Progress product enhancement
You can refer to your Idea at any time for updates on the status of your request. If this is a critical feature and you require that this particular functionality be added to the product, please contact your Customer Sales Account Manager