Common use of Optional attributes and relations Clause in Contracts

Optional attributes and relations. For all attributes and relations that are modelled as optional (i.o.w. not mandatory, or zero to 1, or zero to many) the following applies. In case the reporting company has this data available, it is required for delivery. The optionality only implies that the reporting company is not required to have this data available yet. For functional attributes that are required, the presence of a value is validated by a validation rule. (See Appendix A for signaling validation rules) Also, for required child records (cardinalities 1-to-1 or 1-to-1..n), the existence of the child record is validated by validation rules. (See Appendix A for b signaling validation rules (not exhaustive!))

Optional attributes and relations. For all attributes and relations that are modelled as optional (i.o.w. not mandatory, or zero to 1, or zero to many) the following applies. In case the reporting company bank has this data available, it is required for delivery. The optionality only implies that the reporting company bank is not required to have this data available yetdata. For functional attributes that are required, the presence existence of a value is validated by a validation rule. (See Appendix A B for signaling signalling validation rules) Also, for required child records (cardinalities 1-to-1 or 1-to-1..n), the existence of the child record is validated by validation rules. (See Appendix A & B for b signaling both blocking and signalling validation rules (not exhaustive!rules))