Release 5.9 - 2021 May

1. imicampaign’s New UI (‘Limited GA’ for Email, SMS & MMS)

Continuing to build on what we delivered previously, in this release we are introducing the MMS channel capability on the New UI as ‘Limited GA’ for specific clients. In addition, a few more enhancements and capabilities for Email Channel and for the TG-Splitter feature are introduced on the New UI. These are described later in this Release Note.

If you are interested in getting access to the New UI, then please contact your imimobile customer success team.

The New UI can be accessed using the ‘nextgen/’ context of your usual imicampaign URL; e.g. https://client-xyz.imicampaign.io/nextgen/.

Going forward, new product features will only be introduced on the New UI.
After the New UI is fully developed, we will decommission the Old UI sometime during Q3-2021.
Any Campaigns, Deployments, and Assets that you have previously created on the Old UI will be available to view and edit on the New UI.
Similarly, any Campaigns, Deployments, and Assets you create on the New UI will be available on the Old UI for the next few months (until the Old UI is decommissioned).

The following sections introduce the key features of the New UI:

1.1 Left Navigation Menu

The Left Navigation Menu can be expanded by clicking on the ‘three-lines / burger’ icon in the top-left corner of the screen. And it can be collapsed again by clicking on the arrow icon.

The top-level menu has been slightly reorganized relative to the menu options on the Old UI; e.g.

Dashboard & Reports are now separate top-level menu items.
Under the ‘Campaigns’ → ‘Target Data’ menu, the following features have been consolidated: Events, Seed Lists, Target Groups, Target Group Splitter, and Test Contacts.
Using the ‘Email Composer’ top-level menu, you can directly go to the ‘Email Message Templates’.

You can also navigate the menu by hovering the mouse over the menu options without expanding it fully.

1.2 Campaign Details & Deployment Listing

On the ‘Campaign List’ page (shown in the screenshot above), when you click on any specific Campaign Name, you can see the Deployments under that Campaign. This is similar to the ‘Campaign Flow’ screen on the Old UI.

On this screen, you can use the following features:

a) Create a New Deployment under this Campaign (see section 1.3)

b) View ‘Deployment Summary’ by clicking on the Deployment Name (see sections 1.4 & 1.5)

c) Activate / Delete an existing Deployment by clicking on the ‘three-dot’ Actions menu

d) Visualise the relationships between all the Deployments within this Campaign
(see section 1.7)

1.3 Create a New Deployment in ‘Draft’ status

The following series of screenshots shows the steps in creating a new deployment:

1.3.1 Create a skeleton deployment

A ‘Deployment Wizard’ guides you through the 3 steps to create a new skeleton deployment on the ‘Deployment Canvas’.

Now, you can drag-&-drop one of the ‘Target Group Source’ nodes on to the grey-colored ‘Add Target Group’ placeholder node. Then you can complete the TG Source configuration on the right-side panel by selecting this node. (This is similar to what you would have done on the ‘WHO’ tab on the Old UI).

Similarly, you can drag-&-drop one of the ‘Deployment Schedule’ nodes on to the blue-colored ‘Add Schedule’ placeholder node and complete the Schedule configuration on the right-side panel. (This is similar to what you would have done on the ‘WHEN’ tab on the Old UI).

Finally, when you select the ‘Email’ node, you will be able to specify the Email content (similar to how you would have configured it on the ‘WHAT’ tab on the Old UI).

The following subsections cover these steps.

1.3.2 Configure TG Source Nodes

In this example, the TG source is a ‘File’. After you drag the ‘File’ icon from the ‘Node Selector Panel’ on the left side onto the central canvas, you can select that node and specify the details about the File in the right panel a.k.a. ‘Node Properties Panel’.

The red triangular ‘attention’ icon will remain on a node until you have configured that node completely and clicked on the ‘Save Changes’ button.

1.3.3 Configure Schedule Nodes

In this example, the user has dragged and dropped the ‘Existing Calendar’ node onto the central Deployment Canvas.

The system will automatically add an extra node for ‘Days / Times Exclusion’ where you can confirm whether you want to stick to your company’s default exclusion-days and exclusion times or you can choose to apply different values for your specific deployment.

Again, the configuration for the ‘Existing Calendar’ node will need to be completed on the ‘Node Properties Panel’ on the right side.

1.3.4 Configure Email Content Node

By selecting the ‘Email’ channel node, you will need to configure the Email content on the ‘Node Properties Panel’ on the right side.

Here, you will be able to choose previously created Email Templates, Partials etc.

1.3.5 Save Deployment in ‘Draft’ status

The drop-down within the ‘Deployment Canvas’ will keep track of which nodes are fully configured and which still need to be configured by the user.

By using the drop-down at the top of the Canvas screen, you will then save this deployment as a ‘draft’. You can save a deployment in the ‘draft’ status without necessarily completing all the node configurations. (You may choose to come back and fill in the missing details later by editing this already drafted deployment).

1.3.6 Configure Additional Optional Target Group Nodes

Depending on your requirements for a specific deployment, you will be able to add additional optional nodes related to the ‘Target Group’ definition e.g. Seed Lists, Control Group, Additional TGs, Exclusion List etc.

If you want to delete any of these optional nodes, then you can select the node and use the ‘Delete’ icon at the bottom of the Canvas. You can also use the ‘zoom’ and ‘pan’ options.

1.4 After drafting: Preview & Test, Edit, Activate, Save-as-Template, Prepare TG

After a deployment is drafted, it will appear on the ‘Campaign Details and Deployment listing’ screen (as shown in the previous section 1.2 ). When you click on a deployment in the ‘Draft’ status, the ‘Deployment Summary’ screen will open up.

Here, you can use the following features for this deployment :

Preview & Test,
Edit,
Activate,
Save As Template and
Prepare TG (This is a new tenant-specific feature only available on the New UI)

For a deployment in ‘Draft’ status, the ‘Deployment Summary’ screen will show the basic info, Targeting Options, Schedule Options, and the Deployment Snapshot.

1.5 View the Deployment Summary of a Completed / Activated Deployment

In case of a ‘Completed’ deployment, you will only have the option to ‘View’, rather than ‘Edit’ the deployment. For a deployment in ‘Completed’ status, the ‘Deployment Counts’ panel is also available.

1.6 View a Completed Deployment using the ‘Deployment Canvas’

The ‘Deployment Canvas’ will open up when clicked on the ‘View’ button on the above screen.

1.7 Visualize all Deployments within a Campaign

From the Campaign Details / Deployment Listing screen, you can click on the ‘Visualize’ button to view the relationships between all the Deployments within a Campaign. This is especially useful in case of follow-up deployments.

By selecting one of these deployments, you can see a few more details about it on the right-side panel.

The grey icons convey the type of TG Source ( File / FTP / Profile Segment) and how the blue icons convey the type of schedule (Onetime, Recurring, or Instant).

1.8 ‘Prepare TG’ for Onetime Parent & Follow-Up deployments

This tenant-specific feature is only available on the New UI. Please contact your imimobile account manager if you would like to access this feature.

On the Deployment Summary screen, you will see a new option called ‘Prepare TG’ in case of Onetime Deployments. This option will ‘prepare the target group’ by processing options such as control groups, exclusion list, DND, etc.

If the ‘Prepare TG’ option is selected multiple times, then if there is any previously 'Prepared’ TG already present, it will be discarded, and the TG Prep process will start again for that deployment.

After the TG is prepared, the deployment creator will receive an email as shown below. This email will include all the relevant counts for the TG. This feature is especially useful to assess the count of customers eligible to receive a follow-up communication ahead of the follow-up being sent out.

In case of Onetime Parent Promotions, if the ‘Prepare TG’ option has been used before activation, then the TG will not be prepared again at the time of activation – thus saving time.

This feature is useful in situations where you know the Target Group ahead of time but may want to make last-minute changes to the email content just before activation (especially when using the ‘Immediately’ schedule option). You can get the ‘Prepare TG’ step completed ahead of time; and thus, get the email communication out of the door more quickly after activation.

When you activate the deployment, you will be shown an alert informing you that the TG has already been prepared and the same already-prepared TG will be used. Of course, if you have made any changes to the Target Group since the TG was last prepared, you will be able to select the ‘Prepare TG’ option again before activation.

In case of Onetime Follow-Up deployments, even if the ‘Prepare TG’ option has been used one or more times before the activation, the TG will still be prepared again at the time of activating the deployment. This is essential to account for any potential updates to delivery and engagement metrics of the parent deployment ( e.g. Opens, Clicks) since the ‘Prepare TG’ option was last used for that Follow-up deployment.

1.9 New UI: Auto-Generate Conditional Email Content Tests for Follow-Ups

This tenant-specific feature is only available on the New UI. Please contact your imimobile account manager if you would like to access this feature.

This feature was previously available only for Parent promotion deployments. After you use the above- mentioned ‘Prepare TG’ feature for a Follow-up deployment on the New UI, you can now also auto-generate the conditional content tests.

1.10 New in Release 5.9: MMS Channel

Now, in addition to Email & SMS channels, you can use the New UI to configure MMS channel campaign deployments.

1.11 New in Release 5.9: Customer Care screens

With this release, the Customer Care screens are available on the New UI.

1.12 New in Release 5.9: Recurring TG-Splitter & other improvements

In the previous release, the TG-Splitter feature only supported the ‘One-time’ option on the New UI. In this release, we have introduced the ‘Recurring’ option to the TG-Splitter feature. We have also introduced a few other UX improvements and changes to this feature.

On the Old UI, this feature was also acting as a ‘File Splitter’ whereby you could upload a file to be split.
On the New UI, the ‘TG Splitter’ will function as a ‘Target Group Splitter’ as its name suggests. This means that you will first need to create a Target Group from your file and then use this TG as a starting point to use the TG Splitter feature.

Here’s how the ‘TG Splitter’ feature works on the New UI :

Step 1: Provide a name for your ‘TG Splitter’. On the Old UI, there was an option to ‘Use the existing file name’ in this step. That option has been removed from the New UI.

Step 2: Select the TG you wish to split on the pop-up. The only supported TG-sources are ‘File Upload’ and ‘SFTP’.

To configure a Recurring TG-Splitter : Select a Dynamic TG
To configure a Onetime TG-Splitter : Select a Static TG

Step 3: Choose whether the TG should be split randomly or based on the values of specific headers.

Step 4: Choose whether the TG-Splitter should be run Onetime or on a Recurring-basis.

Step 5: Specify what should be done with the split child TGs. The options available are different depending on whether you chose a Onetime or Recurring schedule for the TG-Splitter.

After a TG-Splitter task is configured, it can be viewed on the ‘Target Group Splitter’ screen.

For Onetime TG Splitters, you can view the configured set up.
For Recurring TG Splitters, you can view the history and stop the recurring schedule.

1.13 New in Release 5.9: Email Channel – Improved Automatic Link Tracking

We have made the following changes and improvements to the Email Automatic Link Tracking feature on the New UI:

The original HTML code created by the user will no longer be updated by imicampaign with its tracked-link URLs on the UI. The tracked-link format will be applied behind the scenes after the deployment is activated. This enhancement will save a lot of time for clients who go through multiple reviews and updates of their email content before a deployment is activated.

This enhancement is only applicable to the New UI. After you have pasted your email content on the New UI Email channel node, please do not open this deployment on the Old UI WHAT tab. This may cause problems in automatic link tracking.
On the Deployment Canvas within the Email content node, the Link Tracking section will now have checkboxes where you can indicate your choice whether a particular link should be tracked by imicampaign or not. On the Old UI, you will need to manually enter the keyword ‘notrack’ within the HTML code if you wanted a particular link to be not tracked by imicampaign.

On the Email Preview screen, the links are now clickable so that you can easily verify before activation that links within your email will indeed redirect to the correct destination. From the Preview screen. please use the Ctrl + Click command to open the destination URL webpage for any link on a new browser tab.

1.14 New in Release 5.9: Email Channel – Google Analytics UTM tags

For Email channel deployments, we have introduced a new optional node for the Google Analytics UTM tags. This will allow you to (optionally) specify whether links within your email should be automatically suffixed with UTM tags and specify the format of the 3 most commonly used UTM tags, viz. UTM Source, UTM Medium & UTM Campaign.

1.15 New in Release 5.9: Upload a file into a Datastore from your workstation

We have made it easier to upload a file from your local PC to populate a Datastore. Previously, you could only use SFTP, AWS S3, or Remote Databases to ingest data into a Datastore.

With this enhancement, you will be able to quickly create a Datastore and upload data into it if you have the data available on your local workstation (PC / Mac). You can then use that Datastore for building Customer Audience Segments without any need to configure SFTP locations or Remote Databases.

While adding a new Datastore, you will now see a new option to add “From File”.

Here’s how this feature will work in short :

You will need to load a sample file while adding a new Datastore. This sample file will be used to identify and define the Datastore columns and their datatypes. You can edit these imputed values and define further configurations such as Encryption for the Datastore columns, as needed.
After adding the Datastore, you can use “Import File” option from the 3-dot menu to upload data using file, one or more time, into the Datastore.
Optionally, you can click on “View Report” option from the 3-dot menu. This will open the “Datastore Load Report” where you will be able to see the status of data loads into the specific Datastore. Only data for the last 7 days is shown by default in the Datastore Load Report.

1.16 What’s not yet available on the New UI in this 5.9 release

In the upcoming releases 6.0 and 6.1 during 2021 Q2/Q3, we will introduce most of the remaining features of imicampaign on the New UI. e.g.

Campaign Manager module:

Email Channel: AMP Interactive Emails
App Push channel deployments
Ext Action API channel deployments
File channel deployments
Facebook Custom Audience channel deployments
Voice (Outbound Dialler) channel deployments
Deployment Approvals by Individuals
Deployment Approvals by Teams

Profile Manager module :

Profile definition
Datastore definition
Segment Builder
Data Management, Data Ingestion, ETL (extract-transform-load)
Data Management Administration screens

Offer Fulfilment Engine module:

SMS 2-way offer fulfillment deployments

2. Dashboard & Reports enhancements

2.1 Email Deployments: Email Clicks Charts – Toggle between Unique / Total metrics

For Email deployments, you will now be able to toggle between Unique / Total clicks.
This enhancement is based on user-suggested Nolt idea #145.

2.2 Email Heatmaps: Ability to download as a PDF

We have improved the PDF Export feature so that you can now specifically export just the Email Heatmaps. (PRB0042025)

2.3 New Pre-Configured Report: Email Opt-Out Transactions Report

We have introduced a new pre-configured report called ‘Email Opt-Out Transactions Report’.

2.4 New Pre-Configured Report: Instant Deployments Transactions Report

We have introduced a new pre-configured report called ‘Instant Deployment Transactions’.

2.5 Email Summary Report: A new column for ‘Email Subject Line’ has been added

In the ‘Email Summary Report’, we have added a new column to display the ‘Email Subject Line’.

2.6 Promotion Transactions Report: UX Improvements

We have made a few UX improvements and applied a few bug fixes in this pre-configured report.
( INC10890770 / PRB0043989 )

2.7 AB+ Summary Report : UX Improvements

We have made a few UX improvements and applied a few bug fixes in this pre-configured report.

2.8 Reports available for 90 days to be downloaded

To improve the overall response times and general performance optimizations, previously generated reports will be now available to be downloaded for 90 days and will be deleted afterward.

3. Drag-&-Drop Email Composer enhancements

3.1 Text block: Improved (upgraded) floating black text toolbar

For the Text block, we have improved the floating black text toolbar within the Email Composer. Some of the improvements are as follows

A new ‘Custom Colour’ setting for text color and text background color. You can now specify the colors in both formats: RGB & Hex.

Custom color added by you will be added in the text color/text background color selection palette

3.2 Text block : Ability to specify mobile-specific padding

For the Text block, we have introduced a new setting called ‘Apply different padding on mobile’ for the Text block. If you do not select this setting, then by default, both mobile and desktop email clients will have the same padding.
This feature enhancement builds on many other enhancements we have added over the last few months to give you more control over how your email looks on mobile device email clients.

3.3 Text block: Ability to add custom colors from the Style Palette

We have added the ability to use some of the custom colors for applying background color, border color, etc. from the Style Palette.

3.4 Background images on Outlook email clients

We will now support the rendering of background images for Outlook email clients (both Outlook desktop and Outlook mobile clients). Previously, instead of a background image, background color had to be rendered on Outlook email clients.

4. API & Integration Capability enhancements New API : Get Last N Customer Transactions API

With this release, we have upgraded this API from ‘Beta’ to ‘GA’ status.

This is a tenant-specific API that is available to specific clients and will incur additional charges. Please contact your imimobile account manager if you are interested in using this API. The charges will depend on the volume of communications and the duration for which you want those data to be available with this API (e.g. for 15 days after the outbound communication is sent).

The expected use case for this API is when your customer service contact center application needs to query as to what messages have been sent to a specific customer from imicampaign and how that customer engaged with those messages (e.g. whether the recipient opened the message / clicked on any links within the message etc.).

Only customer communications sent via Deployments associated with specific pre-defined P&Ls will be available via this API.

More information about this API can be found in our online documentation at https://docs.imicampaign.com/reference#get-last-n-customer-transactions-api

5. Maintenance items in this release

#	Module	Change Type	Description
1	Campaign Manager	To be deprecated in Rel 6.0 : A/B Instant Deployments	In the next Release 6.0 (pencilled in to go live by July / Aug 2021), we will be removing the capability to configure A/B Instant Deployments. The reason to deprecate this feature is that it’s not being used by any client and it is adding unnecessary effort to the ongoing QA activities as well as making it harder to introduce other new features on the product roadmap.
2	Profile Manager + Campaign Manager	Deprecated in Rel 5.9 : Non-SFTP File Transfer	As previously communicated in the Release Notes of Release 5.8 in Feb 2021, after Release 5.9 , only ‘SFTP’ (Secure FTP) will be supported as a method of file exchange to / from imicampaign. i.e. (non-secure) ‘FTP’ will be removed as an option from the following 2 areas : Data Management >> Data Administration >> Add File Connection and Data Management >> Data Ingestion >> Add File Client
3	Campaign Manager	Improved	[Email channel TG Processing ] : We have improved how imicampaign manages the schedule for email deployments so that the possibility of any ‘abandoned TG records’ is now significantly reduced. Most email deployments will now be ‘completed-by-base’ , rather than ‘completed-by-time’. This improvement is most relevant in scenarios where the deployment schedule goes past midnight into the next calendar day, e.g. for North-America based clients who use imicampaign hosted in AWS-Ireland. ( INC10989113 / INC10992171 / CMPN-11719 ) Previously, some of the TG contacts in the email deployment were being ‘abandoned’ when the deployment schedule end time is reached. After this enhancement goes live in Release 5.9, all the records in the email deployment TG will be pushed to their destination emails even if the deployment schedule end time has reached. How many emails will be sent after the scheduled end time will depend on the available email TPS for the tenant and the combined TG sizes of all the deployments running in parallel at that time. Note : This enhancement is only applicable to the email channel because email is inherently ‘asynchronous’ in nature unlike the more ‘real-time’ nature of other messaging channels like SMS and Push Notifications. Schedule management for other channels remains unchanged, e.g. at the scheduled end time , imicampaign will stop pushing SMS messages ; the deployment status will be ‘completed-by-time’ and any remaining records in the TG will be recorded as ‘abandoned’.
4	Campaign Manager	Improved	[ Facebook Custom Audience channel ] : Upgraded the support for Facebook Marketing API to version 10.
5	Profile Manager	Improved	[ File Upload to a Datastore (Old UI) ] : You can now upload a file of up to 50,000 KB size from your PC to a Datastore. Previously, this size was limited to 1,000KB. (Note :50,000 KB is approximately 49.7 MB).
6	Campaign Manager	Fixed	[All channels : Target Group Processing ] : Fixed a bug, whereby under certain conditions, part of the target group for some follow-up deployments were not being processed correctly when the batch-size was specified as a percentage value, rather than as absolute value. ( PRB0044631 / INC10560058 / CMPN-10514).
7	Campaign Manager	Fixed	[ Multiple channels : A/B Deployments ]: Fixed a bug, whereby under certain conditions, when a Control Group was configured with an A/B deployment, the Target Group Prep was incorrectly being processed in the background. ( PRB0045247 / INC11018495 / CMPN-11786 )
8	Campaign Manager	Fixed	[ All channels : Pause / Resume ] : Fixed a bug, whereby under certain conditions, when recurring deployments are paused, the dashboard & reports were showing incorrect dates for ‘abandoned sends’.( PRB0045059 / INC10841034 / CMPN-11575)
9	Campaign Manager	Fixed	[ Forgot Password ] : Fixed a bug, whereby under certain conditions, after the user has changed their password on the ‘Forgot Password’ , sometimes a security warning was being shown incorrectly. (PRB0045202 / INC10981653 / CMPN-11553)
10	Campaign Manager	Fixed	[ Email channel : Link Redirection ] : Fixed a bug, whereby under certain conditions, links within emails were not redirecting correctly if there were certain special symbols within the link (PRB0045009 / CMPN-11557).
11	Campaign Manager	Fixed	[ Email channel : Partials ] : Fixed a bug, whereby under certain conditions, for personalized links contained within an email partial, the $(TG_) personalisation parameters were not correctly coming through in the emails delivered (PRB0045127 / INC10906525 / CMPN-11646)
12	Campaign Manager	Fixed	[ Email channel : Preview & Testing ] : Fixed a bug, whereby under certain conditions, for large TG sizes and/or if there are lots of conditional content blocks in an email template, there were performance issues in the ‘Auto-generation of test cases for email conditional content’ feature. ( PRB0045336 / INC11100500 / CMPN-12172 )
13	Campaign Manager	Fixed	[ Email channel : Preview & Testing ] : Fixed a bug, whereby under certain conditions, when multiple TGs are associated with a deployment, the ‘Auto-generation of test cases for email conditional content’ feature was not working correctly. ( INC10882844 / CMPN-11783 )
14	Campaign Manager	Fixed	[ Email channel : Preview & Testing ] : On the ‘Assets >> Email Message Templates >> Email Template Preview >> Send Test’ screen, if the user has not specified a subject line for the email template, then the system will provide a dummy subject line in order to complete the test-send process. The dummy subject line in this case will be “Note : Subject line not yet configured”. Previously, the send-test used to fail unless the user had specified a subject line.
15	Campaign Manager	Fixed	[ Email channel : RTE data ] : Fixed a bug, whereby under certain conditions, the ‘CMTRANSID’ header value was missing from RTE-sourced campaign history data-feeds for record-type 413. (INC11001166 / CMPN-11678 )
16	Campaign Manager	Fixed	[ Assets → Landing Pages ] : Fixed a bug, whereby under certain conditions, the ‘Landing Page’ asset was not able to be updated by a user if another user had originally created that Landing Page. (PRB0045315 / INC10984190 / CMPN-12081 )
17	Campaign Manager	Fixed	[ SMS & Push channels : Delivery Receipts from imiconnect ] : Fixed a bug, whereby under certain conditions, the timestamp of the delivery receipts received from imiconnect / imiaccess was not interpreted correctly by I imicampaign (applicable for SMS & Push Notifications deployments). ( PRB0045114 / INC10888478 / CMPN-11947 )
18	Campaign Manager	Fixed	[ Facebook Custom Audiences channel ] : Fixed a bug, whereby under certain conditions, the Facebook Custom Audiences were not being created correctly if the MSISDN (mobile number) values were empty in the Target Group. (PRB0044886 / INC10721942 / CMPN-11396 )
19	Campaign Manager	Fixed	[ API Ext Action channel ] : Fixed a bug, whereby under certain conditions, the deployment was not being processed correctly when the API Ext Action is configured to use ‘Action level’ parameters (instead of ‘Deployment level’ parameters). ( PRB0045318 / INC11078905 / CMPN-12127 ).
20	Campaign Manager	Fixed	[ USSD channel ] : Fixed a bug, whereby under certain conditions, the USSD channel deployment calendar schedules were not working correctly. (PRB0045022 / INC10822003 / CMPN-11556)
21	Dashboard / Reports	Improved	[ Dashboard : Date Filters ] : Improved the UX such that the calendar grids for date filters will now show the values of already selected ‘From’ and ‘To’ values.
22	Dashboard / Reports	Improved	[ Pre-Configured Reports ] : Many UX improvements in the ‘ESP Report’ e.g. better naming of column headers in the Excel report and removal of unnecessary columns.
23	Dashboard / Reports	Improved	[ Pre-Configured Reports ] : Many UX improvements in the ‘Action Transactions Report’ configuration.
24	Dashboard / Reports	Fixed	[ TG Deliverability Metrics ]: Fixed a bug, whereby under certain conditions, when the deployment schedule goes past midnight into the next calendar day,( e.g. for North-America based clients who use imicampaign hosted in AWS-Ireland ), the Dashboard / Reports were showing some TG records as in ‘Processing’ status, even though they were actually in ‘Sent’ status. ( PRB0045233 / CMPN-11796 )
25	Dashboard / Reports	Fixed	[ Dashboard Filters ] : Fixed a bug, whereby under certain conditions, on the Dashboard , when a specific campaign name was selected in the filter, some AB deployments were being displayed as options even though these AB deployments were not part of the campaign selected by the user. (PRB0045134 / INC10883004 / CMPN-11443)
26	Dashboard / Reports	Fixed	[ Dashboard : Email Deployment Details ] : Fixed a bug, whereby under certain conditions, on the Dashboard Email Deployment Details page, within the ‘Email Clicks by Devices’ chart, the counts were not being displayed correctly for devices with long names. (PRB0044493 / CMPN-11705)
27	Dashboard / Reports	Fixed	[ Dashboard : Email Deployment Heat Maps ] : Fixed a bug, whereby, on the Email Heat Maps, 2 duplicate click-counts were being incorrectly shown for each link. After this fix, only the click-count and CTR% metrics for that specific link will be shown over each link within the Heat Map; so the metrics shown on the Heat Map will now match with the metrics shown in the ‘Email Link Click Stats’ table shown above the Heat Map. (PRB0045278 / INC11020625 / CMPN-11801 )
28	Dashboard / Reports	Fixed	[ Pre-Configured Reports ] : Fixed a bug, whereby under certain conditions, on the Report Scheduler screen the ‘Purpose’ filter was not being applied correctly (Even though the user has selected a specific ‘Purpose’ value as a filter, the report was pulling deployments associated with all ‘Purpose’ meta-tag values). (PRB0045275 / INC11011316 / CMPN-11850 )
29	Dashboard / Reports	Fixed	[ Pre-Configured Reports ] : Fixed a bug, whereby under certain conditions, when a report generates lots of data (1000s of records), the user’s browser used to crash with ‘Out of Memory’ error message. (PRB0045230 / PRB0045273 / INC11017281 / INC11062779 / CMPN-12088 )
30	Email Composer	Deprecated in Rel 5.9 : Product-Compare block	As previously communicated in the Release Notes of Release 5.8 in Feb 2021, the ‘Product Compare block’ within the Email Composer will be deprecated when Rel 5.9 goes live. The ‘Product Compare’ block was a legacy ‘fixed’ block which is not used by most clients any more as clients now prefer to use the more flexible designs afforded by the ‘Structures’ and ‘Containers’.

6. Need more information?

Please contact your Cisco/imimobile account manager if you have questions or would like access to a new feature.

Cisco Webex technical support team can be contacted at any time by phone or email:

Europe / Middle East / Africa:
- Phone: +44 (0) 1494 750 600
- Email: [email protected]
North America:
- Phone: +1-855-324-0970
- Email: [email protected]