The Dynamic Evidence Editor supports the definition of Mandatory and Optional Parents in the Modeling section. As such, Relationships are defined in one of the Dynamic Evidence Type Versions of the Child Evidence Type. As soon as the metadata of the Child Evidence Type Version is saved, a Rule Attribute will be generated. This Rule Attribute can be used to navigate to the Parent Evidence records for a given Child Evidence Record. The name of this Rule Attribute will be the same as that of the Parent Relationship and the type will be java.util.List<Parent Rule Class> . In the case where a Dynamic Evidence Type has multiple Parent Types, an Attribute will be generated for each Parent Type.
The Rule Set of the Parent Evidence Type will be updated to contain a Rule Attribute to navigate to the Child Records for a given Parent Record. One such Attribute will be generated for each Child Evidence Type. The Attribute for a particular Child Evidence Type will be generated only when the Child Evidence Type Version containing the Parent definition is activated.
When parent and child relationship is established and both parent and child Evidence Type Versions are activated the system generates a relationship attribute in the parent processing rule class. This attribute is named 'related_<child Evidence Type logical name>' and may be used in customized rulesets (e.g. eligibility and entitlement ruleset) to navigate from a parent evidence record to its children. This attribute should not be referenced in customized rulesets before both parent and child Evidence Type Versions are activated. If used earlier it will cause a CER validation error when activating the parent or child version. This is not a defect but a recommended approach to developing rulesets for parent child Dynamic Evidence Types.