The SHACL shape validation of the transformed notices that contain epo:ReviewRequest instances (such as in case of can_24_maximal example notice from the SDK) will result in a Minimum cardinality violation, as none of the epo:ReviewRequest instances will have a value on the property epo:hasNumberOfReviewRequests, as defined by ePO model:
This is due to the fact that according to the CM, which was reviewed by OP, none of the mapped eForms SDK fields provides this information. This should be confirmed by the eForms team.
If, indeed, there exists no field in the SDK to provide this information, there is no way to resolve this violation generated by the ePO 4.0.0 SHACL shapes, and therefore it should be ignored for now.
The SHACL shape validation of the transformed notices that contain
epo:ReviewRequestinstances (such as in case ofcan_24_maximalexample notice from the SDK) will result in a Minimum cardinality violation, as none of theepo:ReviewRequestinstances will have a value on the propertyepo:hasNumberOfReviewRequests, as defined by ePO model:This is due to the fact that according to the CM, which was reviewed by OP, none of the mapped eForms SDK fields provides this information. This should be confirmed by the eForms team.
If, indeed, there exists no field in the SDK to provide this information, there is no way to resolve this violation generated by the ePO 4.0.0 SHACL shapes, and therefore it should be ignored for now.