Skip to content

Releases: OP-TED/eforms-sdk-playground

eForms SDK 1.14.13

16 Jun 10:10

Choose a tag to compare

SDK 1.14.12 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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tai...
Read more

eForms SDK 1.14.12

02 Jun 12:48

Choose a tag to compare

SDK 1.14.12 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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tai...
Read more

eForms SDK 1.13.3

31 May 10:09

Choose a tag to compare

SDK 1.13.3 Release Notes 8

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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 ta...
Read more

eForms SDK 1.14.11

29 May 21:40

Choose a tag to compare

SDK 1.14.11 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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tai...
Read more

eForms SDK 1.14.10

29 May 21:05

Choose a tag to compare

SDK 1.14.10 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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tai...
Read more

eForms SDK 1.14.9

29 May 13:43

Choose a tag to compare

SDK 1.14.7 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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tail...
Read more

eForms SDK 1.14.8

29 May 01:55

Choose a tag to compare

SDK 1.14.7 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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tail...
Read more

eForms SDK 1.14.7

28 May 23:03

Choose a tag to compare

SDK 1.14.7 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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tail...
Read more

eForms SDK 1.14.6

28 May 18:22

Choose a tag to compare

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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tail...
Read more

eForms SDK 1.14.5

28 May 08:02

Choose a tag to compare

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 OP-TED/eForms-SDK@1.14.1...1.14.2

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 OP-TED/eForms-SDK@1.14.0...1.14.1

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 tail...
Read more