Tabella dei contenuti
Operations and lifecycle
Creation and version management
A template e-service behaves similarly to an e-service. While it is in draft, it is visible only to its creator. Upon publishing the first version, the template becomes available in the template catalog, allowing parties to instantiate their own e-services from it.
When structural modifications are needed (e.g., updating the API interface file), a new version of the template must be published.
The main difference from an e-service lies in the types of fields to be filled in, divided into:
- Fixed fields (defined by the template creator and not editable by those who instantiate it):
- E-service: name, description, technology, producing or receiving mode, purposes (only in case of data receiving);
- E-service version: description, attributes, API interface, voucher duration, technical documentation.
- Suggested fields (operational parameters, editable by the producer):
- E-service: Signal Hub availability;
- E-service version: API call thresholds/day, automatic or manual approval of service requests.
- To be completed (information specific to the party):
- E-service: acceptance of delegations;
- E-service version: audience, API interface completion fields (server URL, contact info, terms and conditions URL).
For more details on the e-service structure, see the dedicated section.
Publishing a new template version
When a new version of the template is published, the previous version is automatically retired:
- no new instances can be created from the retired version;
- existing instances cannot be updated to the retired version.
Suspension and reactivation
When a template is suspended, the ability to create new instances from it ceases. Suspension does not affect existing instances (including those in draft). A suspended template can be reactivated at any time.
Using one’s own template
The party that created a template may also instantiate it for itself. However, only one instance may be created from the same template, to prevent duplication of name and purpose. An exception applies to delegated e-services, as described in the dedicated section.
States
| State | Description | Allowed actions |
|---|---|---|
| Draft | The template is being prepared and is visible only to the creator; it is not available in the template catalog. | By publishing the first version, it becomes active and can be instantiated. |
| Active | The template is published in the template catalog and can be instantiated by producers. | Publishing a new version automatically marks the previous one as retired (no longer instantiable or updatable). It can also be suspended and later reactivated. |
| Suspended | The template remains in the catalog but is not instantiable; existing instances (even drafts) are unaffected. | It can be reactivated at any time to return to the active state. |
Hai bisogno di aiuto?
Apri un ticket utilizzando l’apposita funzione all’interno della tua Area Riservata
