Manage applications

Applications are a replacement for the site definition feature in CMS 12. Go to Settings > Applications to configure the applications.

Create applications

CMS has a streamlined process for creating applications through a dedicated pop-up interface, initiated after selecting to create a channel. Users must provide an application name and start page, with an automatically generated (but editable) API ID.

Creating an application restricts the start page selection to the content tree and offers to create a content item if none exists. The system validates for duplicate application names and, upon successful creation, displays a Application created confirmation before redirecting to the applications list view, while a Cancel option lets you return to the previous state without creating the application.

Edit and delete applications

You can edit and delete existing applications within the CMS.

You can access an application's details and settings by clicking its name in the Application list view or by selecting Settings > Application.

• The Application name is editable and mandatory. If you use a name that is already in use, an error message, Application name here is already taken, displays, and the field is highlighted.
• The API ID is displayed but is not editable.
• You can change the start page with the current start page displayed by default.
• Delete Application displays in red with a warning message: This will permanently remove the application and cannot be undone.
• Save remains inactive until changes are made to the Application's settings.
• Clicking the back arrow (< Applications) closes Settings view . Any unsaved changes are lost.
• Revert is inactive until changes are made to the application name or start page. When active, selecting Revert restores the application name and start page to their initial values without saving.

Updated terminology for applications

Added updated terminology across the CMS user interface to align with the application management features.

• Renamed (Web)Site to Application throughout the CMS's UI.
• Renamed Channels to Applications throughout the CMS UI and APIs.

Simpler interface to create applications

Simplified the UI for creating applications. The Create Application dropdown menu was replaced with a single Create Application button, streamlining the application creation process.

Application-specific assets

Added functionality that lets content editors upload and select assets unique to each application.

• Application specific assets checkbox in Settings > Applications enables this feature.
• When enabled for a headless website application, unique URL segments are generated to distinguish its assets.
• For in-process website applications, asset URLs remain unchanged.
• Translations related to asset scope now use For this application.

Default application designation

Added the ability for administrators to designate a default application, replacing the previous wildcard behavior for site definitions.

• A field was added to the Application configuration to store its default status.
• Administrators can set an application as the default using a dedicated checkbox in the Application UI.
• Only one application can be designated as the default at any given time.
• A default application requires at least one hostname to be defined.

Expanded application host types and validation

Added expanded support for application host types and refined host validation rules to provide more granular control over application configurations.

• For Headless applications – The following host types are now supported – Primary, Preview, and Media.
• For In-Process applications – The following host types are now supported – Default, Primary, Media, Edit, RedirectPermanent, and RedirectTemporary.

Updated host validation rules

• Media, Edit, and Preview hosts do not require a language.
• Media, Edit, and Preview hosts are not unique, allowing their use across multiple applications.
• Each application is limited to one Edit host, one Preview host, and one Media host.
• Redirect host types can only be added if a Primary or Default host in the same language exists as a redirect target.
• All hostnames must be entered in lowercase.