Skip to main content

Player update (firmware)

Player update (firmware)

Users can update the player of a selected screen directly through a menu option in the screen list. The update option is only visible when a new firmware version is available and when the user has permission to upgrade players. Before starting an update, a confirmation dialog shows the firmware name and version. Once the update is initiated, a snackbar notification confirms that the request has been sent. The actual player updates are identical too Publisher 10, there are no difference in firmware versions et.c.

A optional column, "Firmware version," is available in the screen list. If an update is available, an ( i ) appears next to the version number with a tooltip indicating "update available." If the player already has the latest version, the tooltip shows "latest version."

Customizable group names in Template Creator

Customizable group names in Template Creator

We've added the ability to rename groups in Template Creator to make organizing and managing templates more intuitive.

  • Users can now assign custom names instead of the default Group 1, Group 2, etc.
  • Group names are edited in the right most property panel, like other item names.

This improvement makes group organization clearer and more flexible, especially when working with complex templates. The feature is available now for all Template Creator users and requires no additional configuration.

New POST option for JSON datasources

New POST option for JSON datasources

To give users more flexibility when connecting to APIs, JSON datasources now support both GET and POST methods. This makes it possible to fetch data from APIs that require request bodies or POST parameters.

  • A new dropdown is available before the JSON link field with options: GET (default) and POST.
  • When GET is selected, the Body field is hidden and the request is sent as a standard GET request.
  • When POST is selected, a Body (raw) text area appears for entering JSON or text content.
  • Custom request headers continue to work for both methods.
  • If a POST request is sent with an empty body, it remains valid.

This enhancement expands integration possibilities for templates using JSON datasources, as more and more APIs are using POST.

Tag renaming improvement

Tag renaming improvement

We've improved how tag renaming works to ensure tag consistency throughout the system. When a tag name is updated, the change will now automatically apply everywhere the tag is used.

  • On tag save, all instances of the old tag name are replaced with the new one.
  • No manual updates are needed-changes take effect across all linked items.

This update reduces manual work, and minimizes the risk of outdated or mismatched tags when using tags for publishing. The feature is available for all users with tagging permissions and requires no additional setup.

Reports

Reports

We've introduced the report export feature in Smartsign 11, allowing you to export reports for tasks such as analyzing media usage.

  • Accessible under Management › System › Reports
  • Exports data in Excel format
  • User permissions aligned with existing profile settings from the previous Publisher
  • Full functionality replicated from Smartsign 10 for a familiar experience

The report export feature provides a straightforward way to review data. By exporting reports to Excel, avid users can perform deeper analysis and create visualizations using Excel's diagram features. This feature is available to all users with the appropriate permissions.

“Changed By” column in booking list view

Changed By column in booking list view

We've added an optional "Changed By" column to the booking list view to provide better insight into content updates. This makes it easier to see which user last modified a media item. The column can be added directly from the booking list's column settings.