current validation rules only for BT-131(d) and BT-132(d) allow inconsistencies in BT-131(t)/BT-132(t)

[gabrieledall]

The validation rules that make sure,any opening of tenders in open procedurese will take place after the end of the submission deadline is reached are currently inmplemented in a way that is not fully consitent:

Currently (at least from SDK 1.72 to 1.10.0) BT-132(d) ist validated according to BT-131(d) as follows:

"condition" : "{ND-PublicOpening} ${(BT-132(d)-Lot is present) and (BT-131(d)-Lot is present)}", "value" : "{ND-PublicOpening} ${BT-132(d)-Lot >= BT-131(d)-Lot}",

iIt is allowed to have open procedures to be opended on the same day, the submission deadline is reached - this is fine and please do not change this rule, but then:

Opening time and submission time are set separately in BT-131(t) and BT-132(t) and no validation check is implemented to the time-related fields. this makes it ist possible to hand in CNs like this:

BT-131(d) = 11.12.2023 UTC+1:00 BT- 132(d) = 11.12.2023 UTC +1:00

BT-131(t) = 18:00 UTC +1:00 BT-132(t) = 12:00 UTC +1:00

Which would make the opening date/time earlier than the submission deadline date/time.

Could you please correct this issue with a next patch-release of at least SDK-1.10?

Thank you in advance G.D.