Releases: OP-TED/eForms-SDK
eForms SDK 1.13.3
SDK 1.13.3 Release Notes
This release brings updates to the business rules, labels and translations. These changes are back-ported from SDK 1.14.
Updates on business rules:
- Re-introduction of 3 rules making ‘Tender Value’ (BT-720-Tender) conditionally mandatory for subtypes 38, 39 and E6
- Update of rules to remove reference to ‘Winner Chosen’ (BT-142-LotResult) for VEAT and Contract Modification notice subtypes
- Removal of conditionally forbidden rule for 'Performing Staff Qualification' (BT-79-Lot) in subtype E3
- Removal of rule making ‘Lots Max Awarded’ (BT-33-Procedure) mandatory for subtype 16 when the notice is divided into Lots
- Removal of the rule requiring ‘Additional Nature’ (BT-531-Lot/Part) to be different from ‘Supplies’ for procedures under the Concessions Directive (Directive 2014/23/EU)
Updates on labels and translations:
- Updates to rule-, field name-, field description- and code labels and their translations
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.
This release note does not cover the details of all changes.
A comprehensive list of changes between SDK 1.13.2 and SDK 1.13.3 can be seen at 1.13.2...1.13.3
SDK 1.13.2 Release Notes
This release adds the recently adopted first "International Procurement Instrument" measure regarding medical devices from China (Regulation 2025/1197).
In addition, the Defence Directive (2009/81) is now allowed as a legal basis for notice subtype 38 (contract modification).
The lawfulness warning rule BR-BT-00500-0309 has been removed to no longer check for "test" in organisation names.
This release also contains corrections to the view templates:
- Ensure exclusion grounds and selection criteria are shown in the correct conditions.
- Display the sections for EED, IPI and CVD correctly in the section "Statistics about strategic procurement".
A comprehensive list of changes between SDK 1.13.1 and SDK 1.13.2 can be seen at 1.13.1...1.13.2
SDK 1.13.1 Release Notes
This release adds the Regulation 2024/2509 on the financial rules applicable to the general budget of the Union: new code in the codelist for legal basis, adjustments in a few rules to take this code into account, and new corresponding translations.
This change has no impact for notices for which the buyer is not an EU institution or body.
This release also contains corrections to the Czech translations for rules.
A comprehensive list of changes between SDK 1.13.0 and SDK 1.13.1 can be seen at 1.13.0...1.13.1
SDK 1.13.0 Release Notes
This release of the SDK does not contain any backwards incompatible changes: software that was able to use version 1.12.0 should also be able to use this version.
Updated metadata content
eForms regulation second amendment
This SDK release completes the implementation of Commission Implementing Regulation (EU) 2023/2884 of 20 December 2023
The implementation can be seen in changes in almost all SDK components: schemas, fields, codelists, schematrons, notice-types, view-templates, translations and examples.
The following fields and forms have been added:
- International Procurement Instrument (IPI) in Result notices
- Energy Efficiency Directive (EED) in Competition and Result notices
- E1 Pre-Market Consultation, with new consultation form type and pmc notice-type
- E2 voluntary Planning
- E3 voluntary Competition
- E4 voluntary Result
- E5 Contract Completion, new completion form type and compl notice-type, including new Review section, also added to all Result notices (subtypes 29-37, E4, E5)
- E6 Contract Modification for defence directive 2009/81/EC
The European Commission has published policy guides for IPI, EED and Review
All new components are optional so a notice in SDK 1.12 format will validate against the schema of SDK 1.13 (but the notice will be subject to other rule changes as listed in this release note).
EFX grammar
A small change was made to the EFX grammar, to remove an unneeded alternative in a parser rule. This improves the performance of parsers generated from the grammar by reducing the time spent looking ahead and backtracking.
This does not change the EFX language, or the output of the parser or translator.
A new version of the EFX toolkit will be released to take advantage of this improvement. If you have your own ANTLR parser generated from the EFX grammar, you will need to re-generate it to benefit from this change.
Schema, nodes and fields
- Finalisation of the nodes & fields definitions for the "Review" section.
- Add fields for IPI and EED.
Rules
In order to reduce the time required to validate notices with a high number of entities (organisations, lots, tenders, etc.), some Schematron rules have been modified to make better use of variables. Those rules have also moved to new files (validation-stage-4m.sch and validation-stage-5m.sch), to facilitate their maintenance.
Based on tests with the Central Validation Service, the validation can be 3 times faster. So if you plan to submit large notices, we strongly encourage you to use SDK 1.13.
If you execute the Schematron rules yourself and use the "ph-schematron-pure" library, you will need to use version 8.0.3 or later, due to limitations and bugs in previous versions of the library. For other Schematron implementations, no change should be required to benefit from this improvement.
Business rules
- Improve controls for existence of Deadlines with added dependency on Procedure Type.
- Add Deadline Receipt Requests (BT-1311) as optional for qualification systems (notice subtype 15).
- Allow Tender Validity Deadline (BT-98) for single stage procedures only.
- Extend the use of Dispatch Invitation Tender (BT-130-Lot) to all single stage procedures and "Direct Award Without a Prior Call for Competititon".
- Update existence rules for fields related to Procedure Type (BT-105).
- Improve rules to ensure the presence of the place of performance (BT-5141, BT-727).
- Add rules to check that the organisation size (BT-165-Organization-Company) is indicated when the organisation is a winner.
- Remove the rule that required the Organisation Business ID to be unique in the notice (some countries use the same ID for multiple organisations).
- Remove the constraint that forbids Buyer and Tenderer from being Service Provider or eSender.
- Improve information on framework agreement reporting in Contract Modification notices (adding missing fields to align with other forms).
- Update lawfulness warning rules:
- Add a check for the exact string "test" in all organisation names (BT-500) in any language
- Adapt the rules that check that buyer country is in a lawful-country to apply regardless of EU funding (BT-60) and subtype
- Remove checks for string "sale" in descriptions in English.
- Update the rule context so the rules get effectively fired for:
- Foreign Subsidy Regulation indicator (BT-681)
- Reserved Participation (BT-71) and Late Tenderer Information Description (BT-772)
- Revenues Allocation of tickets sales code (OPP-035) in T02 form.
- Forbid FSR (BT-682) for T01 and CEI.
Codelists
- NUTS 2021 replaced by NUTS 2024: removed UK, added Kosovo, changes in DE, IT, LV, NL, PT, FI, NO; more details on Eurostat's NUTS page.
- Define tailored lists for Procedure Type per subtype.
- Remove unused codes from non-publication-identifier codelist: not-dis-dat, not-pub-dat.
- Incremental updates and translations from EU Vocabularies; changes to corporate-body.
Notice type definitions
- The Strategic procurement group with BT-06 and BT-777 was moved above the groups with the different types of strategic procurement; the Type of Procurement Group has been adapted to have Strategic Procurement as the first choice in all notices where this groups exists (based on this proposal).
- The fields related to the existence of a framework agreement (BT-765-Lot and BT-768-Contract) were added to the lot and contract sections in subtypes 38/39/E6 to allow contract modifications in the scope of framework contracts.
- The Tender Validity field (BT-98-Lot) and its related group were removed from subtypes 9 to 15, following the review of procedure types per form and the absence of single stage procedures.
- The correct node ND-ProcedurePlacePerformanceAdditionalInformation is now associated to GR-Procedure-PlaceOfPerformance.
- Deadline Receipt Requests (BT-1311) was added to Qualification System (subtype 15).
View templates
- OPT-100-Contract "Framework Notice Identifier" is now included within "Contract information" for winning tenders.
- OPP-124-Business "Gazette Issue Identifier" is now included within "Publication in the official gazette" for Business Registration notices (subtypes X01 and X02)
- BT-726 Suitable For SMEs (Part, Lot and LotsGroup) is now displayed when the value is "false"
- BT-726 "Suitable For SMEs" (Part) will now be displayed under section "4.1.2 General information"
- "Procurement Service Provider" has been removed from the list of organisations under Section "5.1.16 Further information, mediation and review".
- As the role "eSender" applies to the Notice as a whole, the line "TED eSender" has been removed from section "5.1.16 Further information, mediation and review" for all eForms subtypes.
- Lines for the following fields will no l...
eForms SDK 2.0.0-alpha.2
eForms SDK 2.0.0-alpha.2 Release Notes
SDK 2.0.0-alpha.2 is the second in a series of pre-releases of the upcoming eForms SDK 2.0.0, building on the foundation established in alpha.1.
Caution: Pre-release
Please be aware that this is a pre-release version intended to give you a chance to preview and follow the development of the next major version of the SDK.
Objective
The goal of SDK 2 is to introduce a new version of EFX (the eForms Expression Language) that:
- enhances the template definition vocabulary to allow more accurate and user-friendly notice visualisation that is easier to maintain and share,
- improves the ability of the language to express business rules with completeness and simplicity, enabling porting of validation rules to engines other than Schematron and supporting live validation on different target platforms,
- enhances the language in ways that improve its expressiveness and readability, making it easier to write, read, maintain and interpret.
Contents
SDK 2.0.0-alpha.2 contains significant enhancements to the EFX-2 grammar introduced in alpha.1, as well as changes to the SDK metadata contents.
EFX Grammar Changes
EFX-2 has two distinct language flavors — EFX Templates and EFX Rules — both built on the shared EFX Expressions syntax which they extend for their specific applications.
EFX Expressions
The shared expression syntax has been enhanced with:
WITH ... COMPUTEsyntax: Expressions can now be written asWITH context COMPUTE expression, improving readability over the EFX-1{context} ${expression}syntax. The EFX-1 syntax is retained for backward compatibility but will likely be removed by beta.1.- Improved type safety: The grammar has been reorganised to enforce a stricter distinction between scalar and sequence types. Ambiguities in late-binding have been removed, and variables and parameters can now be declared with sequence types (
type*:$var,type*:$param). - Working with sequences: Sequence literal syntax now uses
[...]instead of(...)to remove ambiguity with parenthesised expressions. The codelist expansion operator has been changed to[...codelistName]for consistency (#codelistis still supported but will be removed by beta.1). New conditions allow testing sequences directly:sequence is [not] empty,sequence has [no] duplicates, andexpression is [not] unique in sequencefor all scalar types. Iterations now support aDISTINCTmodifier (FOR ... RETURN DISTINCT expression) and can return sequences (FOR ... RETURN sequence) to concatenate results. - Node presence testing: Presence conditions (
is present/is not present) can now be applied to node references in addition to field references. - Field context indexing: Field contexts now support indexers, expanding how field references can be used in expressions.
- Field properties:
- Privacy controls: Access to privacy-related properties of fields withheld from publication —
field:privacyCode,field:publicationDate,field:justificationCode,field:justificationDescription,field:wasWithheld,field:isWithheld,field:isWithholdable,field:isDisclosed,field:isMasked. - Linked field properties: Field references can carry a
:propertysuffix to access values of linked fields without explicitly referencing them by name, improving readability. - Raw value access:
field:rawValue.
- Privacy controls: Access to privacy-related properties of fields withheld from publication —
- New built-in functions:
- Working with numbers:
min,max,average,absolute,round,round-down,round-up. - Working with strings:
substring-before,substring-after,normalize-space,trim,trim-left,trim-right,pad-left,pad-right,repeat,replace,replace-regex,split,url-encode,capitalize-first,index-of-substring,empty. - Working with dates, times and durations:
year,month,day,hours,minutes,seconds,years,months,days,current-date,current-time. - Working with sequences:
sort,reverse,subsequence,index-of,get-duplicates,count-duplicates. - Type conversions:
text(boolean),text(date),text(time),text(duration),number(boolean),indicator(number).
- Working with numbers:
measurerenamed toduration: Themeasuretype in EFX-1 was only used for durations, which are a special case because they carry the unit in their value (e.g.P10D) to allow calculations. Renaming todurationfrees themeasurekeyword for other types of measure that can be treated as simple numbers. Related function names have also been updated (add-measure/subtract-measure→add-duration/subtract-duration).- XPath axes removed: Axis specifiers (
preceding,following,ancestor,descendant, etc.) were hard to translate to non-XPath target languages and did not add real value to the expressivity of EFX.
EFX Templates
The template language has been enhanced in three areas: more expressive template logic, better reuse and maintainability, and richer output capabilities.
Template syntax and logic
- EFX-2 template syntax: Template lines now use
WITH context DISPLAY template;instead of the EFX-1{context} templatesyntax. Template lines are now semicolon-terminated, and the context declaration is optional — allowing template lines that display content without iterating over a context. The EFX-1 syntax is still supported for backward compatibility but will likely be removed by beta.1. - Conditional templates:
WHEN condition DISPLAY template/OTHERWISE DISPLAY templatefor conditional rendering within a template line. - Navigation and Summary sections:
---- NAVIGATION ----and---- SUMMARY ----section headers for structuring view templates.
Reuse and maintainability
- Callable templates:
LET template: name(params) DISPLAY ...for defining reusable templates, invoked withINVOKE templateName(args). - User-defined functions:
LET type: ?name(params) = expressionfor declaring reusable typed functions (scalar and sequence return types), invoked with?name(args)syntax. - Dictionaries:
LET $name INDEX field BY keywith bracket-access$name[key]for key-value lookups, improving performance by avoiding repeated traversals.
Richer output
- Hyperlink blocks:
text @{url}syntax for linking template content to URLs. - Character references and escape sequences:
&entity;,&#digits;,&#xHEX;and\escape sequences are now supported in template text. - Formatting functions:
format-short,format-medium,format-longfor locale-aware date/time formatting.
EFX Rules
EFX-2 introduces a complete rules language, allowing business rules to be authored directly in EFX.
Rules file structure
- Validation stages: Rules are organised into stages (
---- STAGE stage-id ----), each containing one or more rule-sets. - Stage-level variables:
LETdeclarations scoped to a validation stage, evaluated once and reusable across all rule-sets in the stage.
Dynamic rules
Dynamic rules allow validation to consider information retrieved from other notices through a specialised API. This replaces the EFX-1 cross-notice reference syntax (notice(...)) which was impractical and never used.
- API endpoint declarations:
ENDPOINT "name" AT "url"for named API endpoints, overridable at runtime. - Dynamic/API functions:
LET dynamic: ?name(params) CALL API "endpoint"withON ERROR WARN|REJECTclauses for declaring external API-backed validation functions.
Rule syntax
- Rule-sets: Multiple rules can share the same context via a single
WITHclause, avoiding repetition. - ASSERT and REPORT: Two rule types with distinct semantics —
ASSERTdefines a condition that must be true for the rule to pass (fires when false),REPORTdefines a condition that triggers a report when true. - Conditional rules:
WHEN condition ASSERT|REPORT .../OTHERWISE ASSERT|REPORT ...for branching logic within a rule-set. - Severity and rule ID:
AS ERROR|WARNING|INFO rule-id— each rule has a severity level and an identifier following theR-XXX-XXXpattern, used for error message translation lookup. - FOR clause:
FOR field|nodespecifies which field or node the rule validates, used to organise validators by target. - Notice type targeting:
IN 1-3, E1-E3, X01with range expansion, andIN */IN ANYwildcards. - Scope annotations:
SCOPE @PRE/@POSTfor pre/post submission applicability, plus#flagfor categorisation.
Shared between EFX Templates and EFX Rules
- Include directives:
#include "path/to/file.efx"for composing template or rules files from fragments. - Variable declarations:
LET type:$var = expressionfor declaring typed variables (both scalar and sequence types), available as global declarations in templates and as global or stage-level declarations in rules. - Context declaration with inline variables: The context declaration block (
WITH) now supports local variable declarations before and/or after the context, allowing variables to be computed and reused within the scope of a template-block or rule-set. - Comments:
//comments are now supported everywhere (expressions, templates, rules).
SDK Metadata
SDK 2 focuses its breaking changes exclusively on the EFX language. The metadata file formats and directory layout remain the same as SDK 1, so that applications can migrate to SDK 2 without having to rewrite their metadata import logic. All EFX expressions embedded in SDK metadata (constraints, view templates, validation rules) use EFX-2 syntax.
SDK 2.0 will be released in alignment with SDK 1.15. With the exception of fields withheld from publication ("unpublished" fields) and dynamic rules, SDK 1.15 will have business equivalence wi...
eForms SDK 1.14.2
SDK 1.14.2 Release Notes
Update of pattern-matching rules for amount fields inter alia to allow for negative amounts.
A comprehensive list of changes between SDK 1.14.1 and SDK 1.14.2 can be seen at 1.14.1...1.14.2
eForms SDK 1.14.1
SDK 1.14.1 Release Notes
This release corrects label identifiers in the snippets under the ".ted" folder.
This change has no impact for applications other than eNotices2.
A comprehensive list of changes between SDK 1.14.0 and SDK 1.14.1 can be seen at 1.14.0...1.14.1
eForms SDK 1.14.0
SDK 1.14.0 Release Notes
This release of the SDK does not contain any backwards incompatible changes: software that was able to use version 1.13.2 should also be able to use this version.
Updated metadata content
The schema has not changed in this release compared to SDK 1.13.
Updates on Business Rules
- Introduction of rules to check that the 'Notice Dispatch Date' (BT-05(a)-notice) and the 'Notice Preferred Publication Date' (BT-738-notice) are earlier than 'Deadline Receipt Tenders' (BT-131(d)-Lot), 'Deadline Receipt Requests' (BT-1311(d)-Lot) and 'Deadline Receipt Expressions' (BT-630(d)-Lot) (unless it is relating to a change notice); and later than 'Winner Decision Date' (BT-1451-Contract)
- Introduction of a rule controlling that when 'other' is selected as a 'Procedure Legal Basis' (BT-01-notice), the other legal basis must be specified in 'Procedure Legal Basis (ID)' (BT-01(c)-Procedure) or 'Procedure Legal Basis (NoID Description)' (BT-01(f)-Procedure)
- Introduction of several rules to enhance the data quality of statistical information given in fields 'Number of tenders or requests to participate received' (BT-759-LotResult) and 'Type of received submissions' (BT-760-LotResult) following the publication on the Guide on Statistical Information by DG GROW
- Removal of several rules regarding the fields 'Number of tenders or requests to participate received' (BT-759-LotResult) and 'Type of received submissions' (BT-760-LotResult) following the publication of the Guide on Statistical Information by DG GROW
- Introduction of co-constraint rules to check the consistency between the NUTS Code and Country Code when both are provided
- Introduction of rules controlling that the data put into certain fields is actually of type integer
- Introduction of rules limiting the length of the input for certain fields to 4 digits
- Introduction of rules checking that content of amount (currency value) fields have 0 or 2 decimal points
- Introduction of rule to ensure that '32025R1197' can only be selected in the field 'Specific IPI Measure' (BT-685-LotResult) if the CPV code is in a certain range
- Update of rules to exclusively refer to the new Financial Regulation "Regulation (EU, Euratom) 2024/2509"
- Update of a rule to forbid 'Not Awarded Reason' (BT-144-LotResult) for subtype T02
- Introduction of a rule to ensure that for subtype T02 only 'selec-w' ("At least one winner was chosen") can be selected from the 'winner-selection-status' code list in the field 'Winner Chosen' (BT-142-LotResult)
- Update of rules to forbid 'Procurement Relaunch' (BT-634-Procedure and BT-634-Lot) in all competition notices
- Update of co-constraint rules for the 'Procurement Relaunch' fields (BT-634-Procedure/Lot) to check that the procedure/lot can only be relaunched if 'Winner Chosen' (BT-142-LotResult) is 'No winner was chosen and the competition is closed' or if 'Change Reason Code' (BT-140-notice) is 'Cancellation intention' (no longer 'Notice cancelled')
- Update of rules to conditionally allow 'Organisation Natural Person' (BT-633-Organization) in subtypes 38-40 and E6
- Removal of rules making 'Framework Maximum Participants Number' (BT-113-Lot) mandatory for subtypes 16 and 18
- Removal of rule making 'Lots Max Awarded' (BT-33-Procedure) mandatory for subtype 16 when the notice is divided into Lots
- Update of rules to (conditionally) allow the fields regarding procurement documents for subtype T01
- Update of rules so that the fields related to the Clean Vehicles Directive are (conditionally) allowed for subtypes T01 and T02
- Update of conditionally forbidden and mandatory rules on prizes and rewards regarding the fields 'Prize Value' (BT-644-Lot), 'Rewards Other' (BT-45-Lot) and 'Prize Rank' (BT-44-Lot)
- Introduction of one conditionally forbidden and one mandatory rule for the field 'Selection Criteria Second Stage Invite' (BT-40-Lot) in subtype 22
- Introduction of rules making 'Participant Name' (BT-47-Lot) forbidden unless 'Procedure Type' (BT-105-Procedure) is 'Restricted' in subtypes 23 and 24
- Introduction of rules making 'Award Criterion Description' (BT-540-Lot and BT-540-LotsGroup) mandatory for subtypes 7 to 16
- Introduction of conditionally forbidden and mandatory rules for the fields 'Used asset' (OPP-021-Contract), 'Significance (%)' (OPP-022-Contract) and 'Predominance (%)' (OPP-023-Contract) in subtype T02
- Update of rules to ensure that there are no minimum candidates restrictions for procedures under the Financial Regulation
- Removal of the rule requiring 'Additional Nature' (BT-531-Lot/Part) to be different from 'Supplies' for procedures under the Concessions Directive (Directive 2014/23/EU)
- Removal of the "warning" rule checking that the string "test" is not used for organisations (BR-BT-00500-0309)
- Update of rules following the removal of 'group of public authorities' from the "buyer-legal-type" code list
- Introduction of rules making 'Award Criterion Name' (BT-734-Lot, BT-734-LotsGroup) forbidden if 'Award Criterion Description' (BT-540-Lot, BT-540-LotsGroup) is not present
- Update to the rules regarding the fields on 'Award Criteria Order Justification' (BT-733-Lot, BT-733-LotsGroup) by removing all mandatory rules and by introducing rules to only allow these fields when 'Award Criterion Number Weight' (BT-5421-Lot, BT-5421-LotsGroup) is 'Order of importance'
- Introduction of rules to enforce the content of fields 'Award Criterion Weight Number' (BT-541-Lot-WeightNumber, BT-541-LotsGroup-WeightNumber) to be integers when the associated 'Award Criterion Number Weight' (BT-5421-Lot, BT-5421-LotsGroup) is 'Order of importance'
- Update of rules to align time-date dependencies for the fields regarding the 'Additional Information Deadline' (BT-13(d)-Lot/Part, BT-13(t)-Lot/Part) and the 'Public Opening Date' (BT-132(d)-Lot, BT-132(t)-Lot)
- Update of rules to allow 'Performing Staff Qualification' (BT-79-Lot) in subtype E3 and make it mandatory in subtype 17 when the contract involves works or services
- Correction of expression used in multiple co-constraint rules on 'Group Lot Identifier' (BT-1375-Procedure)
- Update of rules to remove references to 'Winner Chosen' (BT-142-LotResult) for VEAT and Contract Modification subtypes
- Update of rules on 'Tendering Party Leader' (OPT-170-Tenderer) to forbid this field also when no Tenderer is defined (previously it was only forbidden when one Tenderer was defined)
- Update of rules on 'Direct Award Justification Text' (BT-135-Procedure) to ensure that in subtypes 25-35 the field is only allowed when 'Direct Award Justification Code' (BT-136-Procedure) is present and is mandatory if it is allowed
- Introduction of rules that make 'Buyers Group Lead Indicator' (OPP-050-Organization) mandatory when multiple buyers exist
- Update of rules on 'Numeric value of the tender validity deadline' (OPA-98-Lot-Number) and 'Numeric value of the duration period' (OPA-36-Lot-Number, OPA-36-Part-Number) to align them with the rules on 'Tender Validity Deadline' (BT-98-Lot) and 'Duration Period' (BT-36-Lot/BT-36-Part)
- Introduction of 3 previously missing rules making 'Tender Value' (BT-720-Tender) conditionally mandatory for subtypes 38, 39 and E6
- Removal of 2 previously duplicated rules for 'Subcontracting Value' (BT-553-Tender) in subtypes 29 and 31
- Removal of rules that made the Fiscal-, Environmental- and Employment Legislation Document ID fields (OPT-111-Part-FiscalLegis, OPT-111-Lot-FiscalLegis, OPT-112-Part-EnvironLegis, OPT-112-Lot-EnvironLegis, OPT-113-Part-EmployLegis, OPT-113-Lot-EmployLegis) mandatory for the subtypes 6 and 9
- Update of a rule that conditionally forbids 'Selection Criteria Second Stage Invite' (BT-40-Lot) in subtype 14 to align this rule with the corresponding rules in the other subtypes
- Update of the whitespace controls to limit the check to leading and trailing white spaces and allow for extra spaces within strings
- Update of the Regular Expression used for email patterns to allow for non-ASCII characters
- Update of the contexts for several rules to apply
- Optimisation of rules on 'Tender Variant' (BT-193-Tender)
- Introduction of rules that forbid 'Procedure Legal Basis (Description)' (BT-01(d)-Procedure) unless 'Procedure Legal Basis (ID)' (BT-01(c)-Procedure) is filled in
Updates on Codelists
- Synchronization of the code lists with their latest version on EU vocabularies
- Notable updates after synchronisation:
- Update of "legal-basis" code list to replace the old Financial Regulation with its latest version (Regulation (EU, Euratom) 2024/2509)
- Removal of the code 'group of public authorities' from the code list 'buyer-legal-type'
- Update of the 'document-used-in-public-procurement' code list: addition of new code 'epo-acc-espd-request' and removal of code 'epo-sub-espd'
- Notable updates of technical code lists:
- CPV code hierarchy fixes
- Addition of translations of the codes in the "metric-type" code list
- New label for code '32025R1197' in code list 'international-procurement-instrument-measure' (Once this is also updated on EU vocabularies, this will be synced in the future)
- Updates to the following GA labels in the code list 'permission': 'required" and 'not-allowed' (Once this is also updated on EU vocabularies, this will be synced in the future)
- Addition of Bosnia and Georgia to the tailored code list 'lawful-country'
Updates on Notice type definitions
- Change of all group label identifiers that have the asset identifier "group|name|ND-XXXX" ("node" labels) to group label identifiers having the asset identifier "group|name|GR-XXXX..."
- Removal of the 'Procurement Relaunch' fields BT-634-Lot and BT-634-Procedure from competition notices
- Addition of 'Organisation Natural Person' (BT-633-Organization) for contract modification subtypes 38, 39, 40 and E6
- Addition of "procurement ...
eForms SDK 1.13.2
SDK 1.13.2 Release Notes
This release adds the recently adopted first "International Procurement Instrument" measure regarding medical devices from China (Regulation 2025/1197).
In addition, the Defence Directive (2009/81) is now allowed as a legal basis for notice subtype 38 (contract modification).
The lawfulness warning rule BR-BT-00500-0309 has been removed to no longer check for "test" in organisation names.
This release also contains corrections to the view templates:
- Ensure exclusion grounds and selection criteria are shown in the correct conditions.
- Display the sections for EED, IPI and CVD correctly in the section "Statistics about strategic procurement".
A comprehensive list of changes between SDK 1.13.1 and SDK 1.13.2 can be seen at 1.13.1...1.13.2
eForms SDK 1.13.1
SDK 1.13.1 Release Notes
This release adds the Regulation 2024/2509 on the financial rules applicable to the general budget of the Union: new code in the codelist for legal basis, adjustments in a few rules to take this code into account, and new corresponding translations.
This change has no impact for notices for which the buyer is not an EU institution or body.
This release also contains corrections to the Czech translations for rules.
A comprehensive list of changes between SDK 1.13.0 and SDK 1.13.1 can be seen at 1.13.0...1.13.1
eForms SDK 1.12.1
SDK 1.12.1 Release Notes
This release brings the following corrections in the validation rules, making them more permissive:
- Do not require the organisation identifier (BT-501-Organization-Company) to be unique in the notice.
- Allow the buyer and tenderer organisations to also be a service provider.
This release also includes updated translations and updated notice visualisation templates.
A comprehensive list of changes between SDK 1.12.0 and SDK 1.12.1 can be seen at 1.12.0...1.12.1
You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?base=1.12.0&version=1.12.1
eForms SDK 1.11.2
SDK 1.11.2 Release Notes
This release brings the following corrections in the validation rules, making them more permissive:
- Do not require the organisation identifier (BT-501-Organization-Company) to be unique in the notice.
- Allow the buyer and tenderer organisations to also be a service provider.
This release brings the following corrections in the notice visualisation templates:
- Add back the display of BT-748-Lot for all relevant notice subtypes. It was incorrectly removed in the previous version.
This release also includes updated translations and updated notice visualisation templates.
A comprehensive list of changes between SDK 1.11.1 and SDK 1.11.2 can be seen at 1.11.1...1.11.2
You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?base=1.11.1&version=1.11.2
eForms SDK 1.10.5
SDK 1.10.5 Release Notes
This release brings the following corrections in the validation rules, making them more permissive:
- Do not require the organisation identifier (BT-501-Organization-Company) to be unique in the notice.
- Allow the buyer and tenderer organisations to also be a service provider.
This release brings the following corrections in the notice visualisation templates:
- Add back the display of BT-748-Lot for all relevant notice subtypes. It was incorrectly removed in the previous version.
This release also includes updated translations and updated notice visualisation templates.
A comprehensive list of changes between SDK 1.10.4 and SDK 1.10.5 can be seen at 1.10.4...1.10.5
You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?base=1.10.4&version=1.10.5