Release 1.5
Release Version | v1.5.x |
Release Date | |
Previous Version | v1.4.0 |
Version 1.5 of Amplify includes bug fixes, improvements and new features to the system.
What’s new in 1.5
Deploy changes to specific domains
With this new release, it’s possible to deploy amp changes to a specific domain of the amp, instead of simply deploying to all configured domains on the amp. This allows the editor to have two (or more) domains configured for an amp, where one domain is a test domain and another is the production / live domain. The test domain can then be used to test amp changes and then only deploy the changes to the production / live domain once everything has been approved.
The editor can now deploy only to the selected domains in the publish popover.
Setup custom domains for self-detailers
Up until now, all self-detailers has only had one domain: the automatically configured test domain generated and provided by Amplify. With this release, however, it will now be possible to configure a custom domain on the self-detailer to get a branded and correctly named URL of the self-detailer, so it’s associated with your organisation when sharing links to the self-detailer.
To configure a custom domain on a self-detailer, you will need a subdomain (i.e. https://self-detailer.anthillagency.com) controlled by you (or your IT department) to use for the self-detailer, and then a DNS CNAME record configured to make the setup work (the requirements of that DNS CNAME record will be provided in the custom domain configuration steps).
Configuring a custom domain for a self-detailer, which provides the required DNS CNAME record information.
Amp session tracking
We’re happy to announce, that with this release we’re gathering tracking data regarding the user’s progress through the conversation tree. That way it will be possible to get insights into, which answers the users has given, whenever conversations changes, their time spend with amp, and much more.
The tracking data is anonymous and will not include any personal details.
Add custom scripts in self-detailers
Self-detailers are hosted in a separate environment, which is unaccessible for editors, and it’s therefore not possible to include any custom consent or tracking scripts into it. But with this update, it is now possible.
In the settings of a self-detailer, we’ve included a JavaScript field where custom scripts can be injected into the self-detailer experience.
The new custom script field is located in the settings of a self-detailer.
Other notable improvements
Lists (ordered and unordered lists) in messages nodes has gotten some styling updates to better fit the size and contents of the message output.
It’s now possible to remove notifications individually under the notification bell in the top right corner of the dashboard.
Buttons in the conversation history, where an answer wasn’t selected before a new conversation started, is now shown as inactive / disabled, to avoid potential conversation conflicts.
We’re added an option to embedded nodes (only usable via Plugins) to automatically close the embedded overlay once the “success event” of the iframe has been emitted.