1.71 – August 17th 2013
Table of Contents
- Overview of 1.71
- Resend Email Function
- Default Account
- Restrict Survey and Event Access
- Engage on SSL
- Tweaks and Bug Fixes
- Coming Up: App Messaging
- Coming Up: Transactions
1.71 is scheduled for release on 17th August 2013. A few small features and more performance improvements and bug fixes. Ubiquity are currently focusing on a couple of larger enhancements mentioned below under Coming Up.
2. Resend Email Function
People sometimes ask to have an email resent to them.
Prior to this release the only way to resend an email was to go through the send Mailout wizard again.
We’ve introduced a resend email function. You can send the email to the recipient or to any email address.
Find a database contact then go into contact history. View the email, click Resend and type the email address to send the email to.
An exact copy of the original email is sent.
The resend function is currently only available for Mailout and Automated Mailout emails.
When you log into Engage you often need to change accounts using the account chooser.
You can now choose which account you’re automatically logged in to.
Click My Settings and then choose your Home Account from the drop down.
If Engage can’t log you into that account for some reason then you will be logged into the parent account (if, for example, you no longer have permissions in the account).
Prior to this release anyone could click the link to a Survey or Event.
The responses/registrations are marked as Anonymous when you view and download them.
You may want to restrict access so the links can only be visited by contacts in your Engage Database.
For example, if you turn the setting on then personalised links clicked from an Engage Mailout will show the survey/event, however clicking an anonymous link from a website will show the inactive page.
Make this change on the Survey or Event Settings page. Clicking the link if restricted will show the inactive page.
Engage uses SSL on some pages (log in, add user and change password) but not others.
Using SSL on every page can cause browser popup warnings which makes using Engage impossible.
In this release we’ve made a change to get around the browser warnings. Now SSL can be on across all of the logged in area of Engage.
We’ll be turning on SSL across Engage over the next few weeks.
Please note that public pages will stay as they are (links to Surveys, Forms and Events). SSL is currently only for the logged in area.
For the technically minded we’re proxying insecure content so it loads as https. Images in CSS files won’t proxy correctly so there is a chance that some SSL warnings may still appear.
If you have questions or comments about SSL please contact us.
|Tweaks and Bug Fixes:|
|We’ve improved the import wizard so you can now cancel an import, added a wizard so you can easily jump back to a previous step, and also combined the first three pages into one, making the import process faster.|
|Engage is smarter when mapping fields during an import.|
|The Automated Mailout activation dialog could show incorrect number of emails to send if next run date was in the future. Solved.|
|Restyled the date pickers.|
|Fixed bug in copying an existing TXT Programme.|
|Improved performance for downloading database contacts.|
|Improved performance for loading the account tree.|
|File Upload would sometimes not work correctly on surveys if the progress bar was turned off. Fixed.|
|For some websites the Get Friendly Names feature for tracked links would pull in too much content. Fixed.|
|Friendly names in triggered emails now save correctly.|
|Updated share to social images to fit with the new Twitter brand guidelines.|
If your organisation has a mobile app then you’ll soon be able to use Engage to send push messages to your users.
Once the ability to receive push notifications has been developed into the app then you can take advantage of the Engage framework to send out push notifications.
Using Engage to send push notifications is like sending out a Mailout. You can segment on any Engage data, merge fields and personalise and include RSS.
Ubiquity will need to setup Engage first and then you simply need to register the user into Engage whenever they install/use the app. If you also capture email address as part of the app experience then you can store this in Engage.
You’ll soon be able to store purchase data in Engage.
Storing transactions in Engage will allow you to segment contacts based on what they purchased when and how much was spent. Use this for personalised messaging, automated marketing programmes and loyalty systems.
This enhancement will also allow any other relational data to be stored.