Site Manager Update 4.2.0

Created by Faye for Freshworks, Modified on Fri, 30 Jan at 11:06 AM by Faye for Freshworks

In this article:

Update Rollout

This update was made in late April 2023.

 

Update Summary

As well as various behind-the-scenes improvements, the two main features added are:

API for Auto-Creation of Chime Go Sites

An API that works with some middleware we have built allows Chime Go Sites to be created from an Encore Support Centre Form, which will be available in the Knowledge Center. This is now ready for when Chime Go is officially launched.

The first trial is in the US and will be restricted to specific venues.

 

Automatic Off-Lining of Sites

When the scheduler runs overnight in each Region, it will trigger the “Backup & Delete” option for sites - based on the Off-Line Date set on the Settings page in the CMS (found below the Show Dates in 6.15 Sites and above):

Offline

This is the same process as if you are using the manual “Backup & Delete” option. The newly created ZIP file of the Site will then live in the ZIP-Backups folder. The Zip is stored on the AppBuild server, which is also the server that has Site Manager running on it. So both AppBuild and Pre-Post un-cleaned backups are there.

Automated

Since this is now active in Site Manager 4.2.0, you should have this in mind for any testing/trialing of Chime 6.15 sites you are currently doing.

If at any time, a site does get taken down due to a wrong setting here, you can easily use the “Restore from Server” option to get it back up and running.

 

Chime 6.14 and below do not have this Off-Line Date Option within the CMS, so the automated process will not trigger for Chime Live versions 6.14 and below.

Once 6.15 does become the default for new sites – each region will be supplied with an Excel list of sites on the server. If you choose, you can add Offline dates to those 6.14 and below sites and the team will import them directly to the Database that drives this function.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article