eForms SDK 1.5.2

SDK 1.5.2 Release Notes

This release includes only updated translations and updated notice visualisation templates.

A comprehensive list of changes between SDK 1.5.1 and SDK 1.5.2 can be seen at 1.5.1...1.5.2

eForms SDK 1.4.2

SDK 1.4.2 Release Notes

This release includes only updated translations and updated notice visualisation templates.

A comprehensive list of changes between SDK 1.4.1 and SDK 1.4.2 can be seen at 1.4.1...1.4.2

eForms SDK 1.3.3

SDK 1.3.3 Release Notes

This release includes only updated translations and updated notice visualisation templates.

A comprehensive list of changes between SDK 1.3.2 and SDK 1.3.3 can be seen at 1.3.2...1.3.3

eForms SDK 1.6.0

SDK 1.6.0 Release Notes

This release of the SDK does not contain any backwards incompatible changes: software that was able to use version 1.5.0 should also be able to use this version.

Additional information

Several new properties were added in fields.json:

• "presetValue" for fields that have a default or constant value, which can simplify the filling of forms
• "schemeName" for fields of type "id", to support to indicate the expected value of the "schemeName" attribute in the XML
• "captionFieldId" for nodes that have a "identifierFieldId", to indicate the field that can be used to show a more meaningful text for the user (like the organisation name), in addition to the technical identifier (like "ORG-0001")

The files "notice-types.json" now also contains information on all XML namespaces and prefixes that are used in XML notices.

Schematron rules now indicate the identifier of the field or node to which each rule applies, and this information is present in validation reports. This can allow front-end applications to help the end user to link error messages with the relevant field on the screen.

The SDK package now contains in the root folder a file named VERSION that contains the complete version number of the SDK. This makes it easier to identify the version after unpacking the SDK.

Updated metadata content

This version brings various changes in the metadata content that were needed for corrections, enhancements and consistency. The following is an overview of the main changes:

• The content of codelists was updated.
  • Aligned with the latest official codelists with EU Vocabularies.
  • Corrected Estonian translation for clos-nw in the "winner-selection-status" codelist.
• Schematron rules were added and updated.
  • Harmonised rules for Unpublished Access Date (BT-198): it must be between 2 days and 10 years after the Notice Dispatch Date (BT-05).
  • Removed rules for form-type="change" and notice-type="corr". Change notices should use the same form-type and notice-type as their original notice; "change" and "corr" will be deprecated and removed from their codelists (planned for June).
  • Corrected rule: Deadline Receipt Requests (BT-1311) value must be earlier than Dispatch Invitation Tender (BT-130) value.
  • Removed rules that required EU Funds (BT-60) to be true if legal basis (BT-01) is Regulation 2018/1046 or Decision 2016/245, which triggered errors for notice subtypes 1-6, T01, and T02.
  • Corrected rule: BT-531-Part is only mandatory for subtypes 4/5/6 and forbidden for others (from #257)
  • Corrected rule: for notice subtypes 4 and 5, Mediator should not be mandatory but only specified when it exists.
  • Corrected rule: prohibit the repetition of a single language for "text-multilingual" for BT-500-Organization-Company.
• Examples were updated accordingly, along with their validation reports. A new invalid example was added.
• The node structure was corrected, along with the definitions of corresponding fields. The definitions of several fields were corrected.
  • Corrected repeatable property of ND-LateTendererInformation, ND-LotEmploymentLegislation, ND-LotEnvironmentalLegislation, ND-LotFiscalLegislation.
  • Updated parent node of BT-106-Procedure and OPT-090-Lot.
• All notice type definitions were updated and corrected.
  • Corrected nodes referenced by 2 groups in the same notice type.
  • "Main nature" displayed as combobox instead of radio buttons (from #286).
  • Corrections for T01 and T02.
• View templates were corrected and updated, in particular for unpublished fields, and missing colons were added.
• Translations were added and corrected for various asset types.
  • rule_*.xml added for all languages (but note that the translated messages are not yet available).

As new rules were added, a notice that was valid with SDK 1.5.x might not be valid with this version.

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.

A comprehensive list of changes between SDK 1.5.1 and SDK 1.6.0 can be seen at 1.5.1...1.6.0

eForms SDK 1.5.1

SDK 1.5.1 Release Notes

This release includes several corrections:

• Correct notice type definition for subtype 14, add and correct a few groups for other subtypes.
• Add missing English texts for 2 codes in the "innovative-acquisition" codelist.

A comprehensive list of changes between SDK 1.5.0 and SDK 1.5.1 can seen at 1.5.0...1.5.1

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.

eForms SDK 1.5.0

SDK 1.5.0 Release Notes

This release of the SDK does not contain any backwards incompatible changes: software that was able to use version 1.4.0 should also be able to use this version.

This version brings various changes in the metadata content that were needed for corrections, enhancements and consistency:

• Several elements in the eForms schema were updated, to remove incorrect restrictions.
• Schematron rules were added and updated.
• Examples were updated accordingly, along with their validation reports.
• The node structure was corrected, along with the definition of corresponding fields. The definitions of several fields were corrected.
• All notice type definitions were updated and corrected.
• View templates were corrected and updated.
• Translations were added and corrected for various asset types.

As new rules were added, a notice that was valid with SDK 1.4.x might not be valid with this version.

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.

A comprehensive list of changes between SDK 1.4.1 and SDK 1.5.0 can seen at 1.4.1...1.5.0

The following non-exhaustive list can help to provide an overview of the changes:

• Changed some rules for Contract modification fields.
• OPT-301-Part-AddInfo is no longer mandatory for notice subtypes 4 and 5 (PIN only).
• Aligned forbidden rules for BT-133-Lot Public Opening Place and BT-134-Lot Public Opening Description.
• BT-196(BT-xxx) Unpublished Justification Description is no longer always mandatory (schema change).
• Form T02: OPP-021-Contract is made multilingual and can now have more than one occurrence (schema change).
• Added fields to allow Group Framework Re-estimated Value BT-1561-NoticeResult to be unpublished.
• Place of performance fields for lots are now aligned with parts and procedures.
• BT-738-notice preferred publication date was added to forms X01 and X02.
• Accessibility code and justification BT-754 and BT-755 accessibility now share the same repeatable parent node.
• Renewal description BT-57-Lot, a multilingual field, now has its direct parent as parent node.
• Framework Maximum value BT-271 was added to the notice type definitions.
• Non-disclosure agreement fields BT-801 and BT-802 were added to the notice type definitions and the same parent node
• Strategic procurement code and description BT-06 and BT-777 Strategic procurement now share the same parent node.
• Removed BT-630 from notice subtype 8 in the notice type definitions.

eForms SDK 1.4.1

SDK 1.4.1 Release Notes

This release include several corrections:

• Add missing codes in the "non-publication-identifier" codelist.
• Add missing codelist constraints for 2 fields, along with the corresponding Schematron rules.

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.

eForms SDK 1.4.0

SDK 1.4.0 Release Notes

This release of the SDK does not contain any backwards incompatible changes: software that was able to use version 1.3.0 should also be able to use this version.

This version brings various changes in the metadata content that were needed for corrections, enhancements and consistency:

• Two tailored codelists specific to eForms were added, and codes were added in one codelist.
• Schematron rules were added and updated.
• Examples were updated accordingly, along with their validation reports.
• The node structure was corrected, along with the definition of corresponding fields. This allowed to set back to "multilingual" the fields that were temporarily changed in version 1.3.2.
• All notice type definitions were updated and corrected.
• View templates were corrected and updated.
• Translations were added and corrected for various asset types.

As new rules were added, a notice that was valid with SDK 1.3.x might not be valid with this version.

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.

eForms SDK 1.3.2

SDK 1.3.2 Release Notes

This release includes several corrections and small updates:

• The type of field BT-802-Lot was corrected.
• Several fields were changed to not be multilingual, to avoid creating invalid XML notices. This will be fully addressed in a future version, and those fields with be changed back to being multilingual.
• Some incorrect "_repeatable" properties were removed in notice type definitions.
• View templates were corrected and updated.
• Translations were added and updated for various asset types.

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.

eForms SDK 1.3.1

SDK 1.3.1 Release Notes

This release includes several corrections and small updates:

• Add back missing fields "BT-762-notice" and "BT-803(t)-notice" in fields.json.
• Correct EFX expressions to use "in" when the right-hand side is a sequence.
• Various corrections in notice type definitions.
• Add and update translations for "group" and "notice" asset types.

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.