Oracle ECP provides system templates. A system template represents the base configuration for a supported make, model, and platform version. System templates are read-only. You can use a system template as the source when you create a user-defined template.

A system template is the default template for its hardware and platform combination. It remains at version 1, shows System as the creator, and cannot be edited or deleted. Oracle ECP maintains one system template for each supported make, model, and platform version combination.

You create a user-defined template from an existing template version. User-defined templates let you maintain your own configuration versions for a specific use case.

The Edge Configuration Templates page also includes standard Oracle ECP table controls, such as search, filter chips, and the Columns button.

Edge configuration templates are tied to the platform version that runs on the edge node.

Oracle ECP provides a system template for each supported make, model, and platform version combination. When Oracle ECP introduces a new platform release, Oracle ECP can provide a new system template for that release. Continue to use the template that matches the platform version on the edge node.

If an edge node runs an older image that does not support the newer configuration provisioning approach, continue to use the existing edge management workflow for that edge node until you move it to a supported newer image.

An edge configuration template can contain more than one version.

When you create a user-defined template, Oracle ECP creates version 1 in the Draft state. Draft versions are editable. You can save changes to one or more configuration blocks while the version remains in draft.

A template can have only one draft version at a time. If a draft version already exists for a template, Oracle ECP does not let you create another draft version for that template.

If a template has multiple published versions, Oracle ECP lets you create a new draft only from the latest published version. Oracle ECP creates the next sequential version from that latest published version.

When you publish a draft version, Oracle ECP makes that version read-only. A published version is immutable. To continue making changes, create a new draft version from the published version.

This workflow gives you revision control for your configuration. You can prepare changes in draft, publish a stable version, and apply that version later when the timing works for your edge nodes.

Only published versions can be applied to edge nodes.