EFORMS Workshop on Business Issues and Technical Solutions

EFORMS BUSINESS ISSUES 4th eForms Technical Workshop 28 March 2023 Karl Ferrand TED unit -Publications Office of the EU

Feedback and actions on eForms business issues Labels and translations Fields and rules Conditional rules Exclusion, selection and award criteria Linking and changing notices Organisation and roles SDK releases Image by Gregor Ritter from Pixabay

eForms labels and translations /translations folder in SDK one file per asset type per language, e.g. field_et.xml Each asset type may have one or more label types, e.g. name, description, text Translations are carried out by EC translators but many labels still using EC machine eTranslation OP checking ways to collect input or feedback get in touch if you have capacity or needs in your MS Translation planning: - Close gaps in translations for all labels (except rules) for SDK 1.7 (in April) - Complete all translations (including rules) no later than June - Previous SDK versions will be patched with translations Image by CCXpistiavos from Pixabay

Translations by asset type (1) business-term: has name (user-friendly), description (if in regulation) and some hints (for tooltips) field: labels are the same as for business-term except for a handful of cases, e.g. BT-01 legal basis group: name labels are groups of screen fields in notice type definitions, many eTranslations auxiliary: text labels are display headings or other texts in view templates, many eTransations code: name labels exist for each value in a codelist - Official codelists come from EU Vocabularies - Technical codelists provided by OP, eTranslated for now - Tailored codelists use the labels of their parent codelist codelist: name label for the title of each codelist, eTranslated for now

Translations by asset type (2) rule: text label for each rule ID, thousands generated from template, about 450 texts are not generated expression: name label for each condition, used by templates, e.g. - Conditionally mandatory: field X is mandatory in notice subtpe Y when condition expression Z Need clearer English texts and not easy to translate well but internal target is end of May notice: name label for each notice type definition view: name label for each view template indicator, node, pattern, internal: no labels used yet for these asset types More details at https://docs.ted.europa.eu/eforms/latest/translations/index.html (to be updated)

Field and rules Field metadata and rules are available in fields.json Web view of BTs, rules and codelists available in metadata reference on docs.ted.europa.eu eSender demand for lists to support systems that are not driven by SDK metadata OP looking at ways to generate CSV lists of field metadata and business rules and include in docs.ted.europa.eu NB: lists will use SDK versions same info, different format Extended annex Excel or implementation handbook do not have the necessary detail

Conditional rules SDK 1.2 in October 2022 had many rules for conditionally mandatory and conditionally forbidden - Too many rules for end user to satisfy to fill in a form (in eNotices2) - But rules are too loose and some eSenders need more rules to help users via front-end validation Conditional rules will be progressively re-introduced - In SDK 1.7: rules for deadline dates BT-131, BT-130, BT-1311 - Review and add significant majority of conditional rules by end of May

Exclusion, selection and award criteria Exclusion: currently need at least 1 criterion Selection: currently need all 3 criteria (apart from other ) > loosen this rule Award: currently need at least 1 criterion Future: have options for buyer to indicate the equivalent of see procurement documents

Linking notices eForms notices are linked via procedure ID But explicit linking to previous notices can be done through: - BT-758-notice change notice - BT-125(i)-Lot and BT-125(i)-Part previous planning - BT-1501(n)-Contract contract modification - OPP-090-Procedure previous notice (in particular if linking to TED-XML non-eForms notice) Previous notice must be in Published status, i.e. on TED Notice reference can be: - eForms business ID: notice ID (UUID) + version number - TED publication number: nnnnnnnn-yyyy, up to 8 digits with or without leading zeros

Change and cancel - again form-type change and notice-type corr will be deprecated no later than June Change notice should have the same form-type and notice-type as the original notice - A changed notice can be identified by the existence of a change section - SDK 1.6 removed the rules to enforce change and corr for Change notice - SDK 1.8 will remove change and corr from the codelists Rules for Change notice not implemented yet: will include at least the same as current F14 so cannot change legal basis, procedure type, nature, number of lots Change reason cancel notice not recommended except in specific cases - Future rules will forbid changing or linking to a cancelled notice To cancel a lot or procedure: publish contract award notice with no winner

Reminder of notice lifecycle 9:00 CET Deleted Publishing Published daily export eNotices2 web UI Draft by OP Not Published Submitted CVS ok Stopped by buyer eNotices2 API CVS nok Validation Failed If a notice is Submitted, Publishing or Published, the notice ID cannot be used again If a notice is Stopped, Validation-failed or Not-Published, the notice ID can be used again with an increased version ID, i.e. a different business ID (notice ID+version ID) Publishing status not yet available externally

SDK releases SDKs 1.0, 1.1 and 1.2 will be deprecated on 14 April - Versions not used and not aligned with 2022 amendment to eForms regulation - Still available for testing in Preview SDK 1.6 in March: various components updated (schema unchanged) see release note - Translations and view-templates patched to 1.3.3, 1.4.2 and 1.5.2 SDK 1.7 in April SDK 1.8 in May or June (including translations and conditional rules) SDK 2: see the next presentation no technical impact unless you use EFX Reminder: all active releases are supported in parallel and for at least for 1 year Image by PIRO from Pixabay

THANK YOU FOR YOUR ATTENTION Links https://docs.ted.europa.eu - Developer guide, APIs, Preview, FAQ, every SDK version https://github.com/OP-TED/ - Components and code for developers, SDK, discussions https://op.europa.eu/en/web/ted-eforms - OP eForms events Any questions? Business: ted@publications.europa.eu Technical: https://github.com/OP-TED/eForms-SDK/discussions/