current validation rules only for BT-131(d) and BT-132(d) allow inconsistencies in BT-131(t)/BT-132(t) about eforms-sdk HOT 6 OPEN

Hi,
This control is restricted by the current EFX language and shall get fixed with EFX 2.

from eforms-sdk.

Hi,
The rule for BT-132(d) in comparison with BT-131(d) is unclear.
We can see in the fields.json for the conditions regarding BT-132(d)-Lot that the error message for rule|text|BR-BT-00132-0151 is 'Opening date' (BT-132) must be later than 'Deadline for receipt of tenders' (BT-131). Still we can validate a notice successfully even though BT-131(d) and BT-132(d) have the exact same date and time. Should this be the case? If so, will you then remove the rule for BT-132(d)-Lot in an upcoming SDK?

from eforms-sdk.

This will be the case until EFX2 will be available

from eforms-sdk.

Just to get this crystal clear :) Does this mean that when EFX2 is available there will also be a time validation for BT-131(d) and BT-132(d). So they can still have the same date, but the time for BT-132(d) must be later than the time in BT-131(d)?

from eforms-sdk.

Yes, it will be possible to compare date-time values from the date and time ones.

from eforms-sdk.

And the timeline for EFX2 is pre-releases during 2024 as you progress and a final release Q1 2025, right?

from eforms-sdk.