Application Container

Where to find it: Manage → Application Containers

An application container is a named bundle of everything a device needs to run: the content it serves (playlists, tables, and individual items), the software it runs, and any supporting files that software needs. Packaging these together means a device can be set up (or updated) from a single, reusable definition.

Containers exist independently of devices. One container can be assigned to many devices, and each device uses one container at a time. A device’s container is chosen on its own settings page, under the Canvas / Application Container tab.

Note The software and startup parts of a container are usually set up for you during installation. Day to day, the part you’re most likely to work with is the Content: the playlists, tables, and items the device serves.

Before You Begin

Before working with application containers:

• Make sure you have permission to manage application containers.

• Know which company the container belongs to.

• Have ready any content (playlists, tables, items) you want the container to serve.

The Containers List

The Application Containers page lists your containers by name and owning company, and you can search by name. Each container has a menu of actions:

Removed containers remain in the list with a struck-out style until they’re permanently deleted.

Creating a Container

To Create a Container

1. On the Application Containers page, choose to create a new container.

2. Enter a name.

3. Choose the owning company.

4. Save.

The container is created with its own storage area for resource files, ready for you to configure.

Configuring a Container

Opening a container shows a form with several sections in a sidebar. Your changes save as you go when you move between sections or click Save. The sections are described below.

Information

The basics of the container: its name, its owning company, and who can access it. Access is granted through User Exceptions: a list of specific users who should have access. Administrators of the owning company already have access and don’t need to be added here.

Content

This is the heart of the container for most people: the content it serves to the device. Content is organised into Object Groups (folders), and each group can hold:

Within the content browser you can:

• Click a folder to open it.

• Open any object’s own edit or manage page in a new tab.

• Use an object’s menu to rename it, move it to another folder, edit it, manage a playlist or table, or preview a playlist.

• Select several objects to move or delete them together.

• Search across everything in the container. When searching, each result shows where it lives.

You can also create new playlists, tables, and items directly from the bottom of this section.

Resource Files

A file area for any supporting files the container needs, organised in folders. It works just like the file browser elsewhere in the dashboard: open folders, upload files, create folders, and rename, move, or delete items. The whole set of resource files can be downloaded as a ZIP using the Export action on the list.

Installer & Dependencies

This advanced section lists the software packages the device installs, in order from top to bottom (drag to reorder). Each package has a name, an uploaded installer file, and any installation options it needs. This is usually configured during setup rather than changed day to day.

Startup Command

A single field holding the command the device uses to launch its application. Like the installer section, this is normally set up for you and rarely needs changing.

Note The Installer & Dependencies and Startup Command sections are advanced setup, typically handled by Omnially when a device is deployed. If you think one needs changing, it’s worth checking with support first.

Copying a Container

Copy creates a new container with the same content: its object groups and all the objects inside them. The copy is named after the original with a timestamp added.

Important: A copy carries over the content only: the installer packages and resource files are not copied. If the new container needs those, they’ll have to be set up separately.

Deleting and Recovering

Deleting a container sets it aside rather than removing it immediately: it stays in the list with a struck-out style and can be brought back with Recover. Deleting an already-removed container a second time destroys it permanently.

Important: Recover a removed container rather than deleting it again: the second deletion is permanent and can’t be undone.

Exporting

The Export action downloads a list of everything the container serves: each object’s name, its type, and where it’s served on the device. Playlists are broken out file by file, and tables cell by cell, so the export is a complete inventory of the container’s content.

Best Practices

• Focus on Content: For most updates, the Content section — your playlists, tables, and items — is the part you’ll work with.

• Reuse with Copy: Duplicate a container to reuse its content setup, remembering that installers and resource files don’t carry over.

• Leave advanced sections to setup: The installer and startup sections are normally configured during deployment: check with support before changing them.

• Recover rather than re-delete: A removed container can be restored; deleting it again is permanent.