Message Center Template
This feature allows you to add an RSS feed to a Solstice Pod's Welcome screen that scrolls across the top. You can also create and publish an emergency message that is broadcast to all Pods it is published to.
How To
Note
Configured Custom Message may fail to display in Solstice 5.5.2 and higher when the default Solstice Wireless Display RSS feed is disabled.
The following will work around this issue until Mersive puts a resolution in place: Add an RSS feed after the disabled default feed, enter the Source address http://mersive.com/blank.xml, and enable the blank feed. The enabled Custom Message following the blank feed should display.
To add a new RSS feed, click the Add an RSS Feed button. A new row appears.
Enter in the Name of the RSS feed.
Set the Duration the RSS feed appears before displaying the next feed or custom message.
Enter in the Source RSS URL. The URL must point to a valid XML file with a root element type of <rss>.
To have a custom message display in the top banner, toggle the slide switch to enabled (it is green when enabled), and enter your message in the Custom Message field.
Click Save.
To disable any of the RSS feeds or the custom message, toggle the Enabled option off. The toggle slides to the left and turn grey to indicate it is disabled.
To delete any of the RSS feeds, click the Delete
icon located to the right of the Source field.
Note
Solstice administrators should be aware that the Cloud settings for a Solstice Pod take precedence and overwrite any conflicting settings on the Pod itself.
In the case of a settings mismatch for a Pod between Solstice Cloud and the Pod's own settings, Cloud settings always "win." The only exception is when a settings change in a Cloud template causes Solstice Cloud to be unable to connect to the Pod. In this case, the settings in that template set are rolled back to the last working configuration for that Pod. Pod and template status indicators alert users when this case occurs.
In the left sidebar menu of Solstice Cloud, click Manage > Pods.
The Pod Template Assignments table displays. This table is used to apply templates across your deployment. You can apply a template to multiple Pods at once.
Tip
Filter Solstice Pods in your deployment by default categories or categories you have created to apply templates efficiently to similar Pods. Filters allow you to apply templates by criteria such as location or campus, depending on the categories you have created and assigned to Pods.
Select the Pods you want to apply the template to. You can select each Pod's checkbox individually, or select the checkbox in the header row of the table to select all Pods showing in the table.
For each template you want to apply, go to the corresponding template type column (e.g., Welcome Screen). You can view different groups of templates by selecting a template category in the upper right corner of the table.
Select the template with the desired configuration from the list in the appropriate column for one of the selected Pods. This applies the template to all the selected Pods in the table.
Click Confirm when to confirm applying the selected template to all selected Pods.
As changes are being applied, the pending changes
icon appears next to the template(s) being applied. After the changes are applied, the Pod's normal status resumes.If a Pod is offline, any changes made are applied when the Pod comes back online.
If a settings change in a Cloud template causes Solstice Cloud to be unable to connect to the Pod, the Pod's settings for that template is rolled back to their previous configuration. A failure icon
shows that the template could not be applied.
If a template you applied has any unique-to-Pod settings that need to be applied each Pod individually, a pop-up pane appears prompting you to enter the needed information for each affected Pod. After you complete all of the settings screens, click Save & Close.
Tip
Solstice checks the settings selected for a Pod in Solstice Cloud management against the settings on the Pod itself approximately once an hour, as well as upon Pod reboot.