Skip to main content
Skip table of contents

Release 1.3

Release Version

 v1.3.x

Release Date

Previous Version

v1.2.0

Verison 1.3 of Amplify includes bug fixes, improvements and new features to the system.

What’s new in 1.3

Export Review PDF Document

We’re excited to share, that with the new update of Amplify it is possible to export a Review Document in form of a PDF file for all amps. The document shows all details of the amp needed for MLR reviews or any other type of content reviews, such as conversation overview, all details about each conversation: Slide thumbnail preview, conversation triggers, and a full conversation graph view.

The Review Document can be exported from the “Export” button located on the amp builder page.

Example of a Conversation Overview page in the Review Document

New plugin type: Embed

For plugin developers we’ve defined a new type of plugin: the embed plugin type. This type can be used for embedding any external website inside the conversation flow. It will open as a full overlay on the chat and pause the conversation flow in the background. Once the user finishes using the embedded content, they can close the embedded overlay and continue the conversation.

Use the Amplify CLI to create new plugins of this type.

Calendly Plugin

Using the new embed plugin type, we’ve created a system-wide plugin (enabled for all organisations in Amplify) that renders a Calendly meeting booking overlay.

Simply add the Calendly plugin (using the plugin option in the left toolbar on the builder page) into the conversation to make it possible for users to book meetings directly with your sales representatives.

Example of how the Calendly plugin is rendered

Improved visuals of usage limitations based on selected plan

As an improved user experience the editors are now shown if the organisation has reached the usage limitations according to their selected pricing plan.

That means, if they try to publish new amps or invite members past the organisation limits, a warning message will let them know that it isn’t possible due to the selected plan of the organisation.

Importing eDetailers now supports a presentation.json file

We have improved the import processes of eDetailer zip, that was generated by Activator.

Previously, each imported slide from an Activator zip was named after the slide folder in the zip, which is the document number and version. This was causing issues when re-importing an eDetailer with updated slides, as the version number was different and the slide name therefore didn't match up with an existing slide in the amp.

Now, the slide conversations are correctly named, and therefore support re-importing of updated slides in eDetailers. With this update, the re-import process even support if the slide document in the eDetailer was renamed after the initial import.

This feature is possible due to the presence of a "presentation.json" file, which is present in the eDetailer zips generated by Activator.

Other notable improvements

  • When creating plugins for Amplify it is now possible to define a label and a hint text for each field, whereas before the label was rendered based on the field ID. This will improve the editor experience of using plugins.

  • While the data for plugins are being computed it will show a loading animation, so the user are aware that a new message is incoming.

  • Snackbar notifications has gotten a design update to better align with the rest of the Amplify visuals.

  • As an improved experience on laptop sized screens, the publish dialog and other similar overlays on the amp builder page now renders on top of the preview overlay instead of beneath it.

  • When attaching a storage to a node in the amp builder, the storage label is now shown in the builder, so the editor doesn’t have to open the storage dropdown on the node to see which storage was attached.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.