eForms Preview environment

In this version, the application is expected to allow users to create the 40 eForms notice types plus the 5 other notice types which include the 2 transport regulation notices, the European economic interest grouping and European company/cooperative registration forms, and the call for expression of interest. The fields which are available, along with their behaviour, are consistent with SDK versions 1.3, 1.4, 1.5 and 1.6. SDK version 1.6 is supported both in Preview and Production environments as of 15 March 2023.

In the codelist fields, prefilling of values is supported.

Users can see the validation returned from CVS and have their notices rendered in HTML and PDF.

Before you can create a Change notice or continue a procedure on a published notice, bear in mind that submitted notices go through another workflow in TED Monitor before they can be published, which takes place every working day.

The application also allows users to act upon notices and procedures, archiving, renaming and transferring them to other users or other procedures as well as export notices in XML.

There is also a search feature which allows users to sort through long lists of procedures.

Users can create workgroups between themselves and test the definitions of roles and permissions within these workgroups. They can also work and submit notices worked upon collectively.

Users can define personalised settings for the legal basis and notice types that they want to use, as well as default languages in the notice, and tailoring of some fields is available:

In the notice sections a search feature has been added and pagination for up to 2000 lots is supported.

As of SDK version 1.6, the lot distribution for lot groups has changed; there is a new section for that in the procedure.

At this point, the application is incomplete and many use cases are not fully implemented.

All validation errors are currently displayed as a pop-up window, without pointing to the error location. Please set a default currency to avoid validation errors in the notices created in the user interface that can lead to a message that the: “notice is probably incomplete”.

All the error messages and labels in the user interface (UI), notices and fields are subject to change – translation of labels is still work in progress.

Notices go through CVS validation when they are submitted, or when the user clicks on "validate" in the user interface, however, the feature may be unstable. Notices created in the user interface of eNotices2 that trigger a lawfulness warning cannot be submitted.

For the moment, CVS validation does not work dynamically, i.e. there is no check between notices. This has implications, e.g. for checking notices of the same procedure or the same UUID v4 and different version ID; currently, it is possible to submit and publish two notices that carry the same notice ID and different version IDs. See in contrast: https://docs.ted.europa.eu/eforms/latest/schema/notice-information.html#noticeIDSection.

For the moment, it is not possible to link a TED-Schema notice to an eForms notice via the Previous Notice (OPP-090) as described in the documentation: https://docs.ted.europa.eu/eforms/latest/schema/procedure-lot-part-information.html#previousNoticeSection.

eNotices2 uses the codelists from the SDK, which have not been completely tailored.

In Change notices, section "Information about the change" should not be repeated.

As of 19 December 2022, status “published” may not have been shown in Preview for notices that were submitted successfully; this issue is now fixed.

On 10 and 11 January 2023, notices submitted may have acquired status “not published”; this issue is now fixed.

Due to an error in the processing of notices at export time some notices remain in "submitted" status; we are working on fixing this issue.

Notices created before 15 March 2023 in Preview or Production environments and updated to SDK 1.6 may have issues. If editing a notice leads to an error (server error) or 'Notice Locked', the workaround is to export (download) the xml and reimport it somewhere else in eNotices2, even if it is in the same procedure.

The eNotices2 API URLs and parameters will change in later releases. The Swagger UI provides basic documentation of the four functions.

Currently, "stop publication" on a submitted notice will return error 500 in certain cases, i.e when the notice is being processed and ready to be published. The process will be simplified in the future with the introduction of status “PUBLISHING”, which will forbid stopping publication of a notice of this status. For more information on notice statuses, please see the eForms FAQ.

Currently, when submitting an XML to eNotices2 API that is invalid against XSD, error code 500 will be returned. To see if this the case, i.e. the XML is not compliant against XSD, please check the notice for now through CVS API.

The 'validationReportUrl' property present in the response body for submit notice is currently not fully correct; /api/v2/ is missing in the URL. Until this bug is fixed, eSenders should use instead URL pattern: 'https://enotices2.preview.ted.europa.eu/esenders/api/v2/notice/notices/{businessId}/validation-report' where the {businessId} is replaced with value taken from the submitted notice ('noticeId-versionId') or with {businessId} from validationReportUrl.

We are currently in the process of providing more guidance for users of the eNotices2 web interface. In recent weeks we have loosened many rules that required fields to be mandatory under certain conditions, which makes it easier to fill in the forms. However, as certain co-constraints and conditional rules have been removed, the same is not true for CVS validation upon validating a notice or trying to submit it via the user interface of eNotices2. Until we can provide some more guidance and until known issues are fixed and more rules are re-enforced, we have provisionally gathered here some tips to help users with avoiding validation errors:

This version of the application is focused on improvements to the UI experience and the correction of bugs.

We are working on resolving the following limitations and known issues: