Release 6.9 - 2024 June
7 months ago by Kamalakar Bayya (kamalb)
This release is mainly a maintenance release focused on delivering many behind-the-scenes ‘non-functional’ improvements in security, engineering, supportability, scalability, resilience, database performance, response-times, operational monitoring, accessibility and test-automation. There are no functional features being introduced in this release; however, some bug-fixes are being delivered.
1.0 Maintenance items in this release
The table below lists some of the notable smaller functional improvements, engineering improvements, bug fixes, and fixes for production incidents/problem tickets are included in this release.
| # | Module | Change Type | Description |
|---|---|---|---|
| 1 | Campaign Manager | Deprecated | Facebook Custom Audiences: We will be stopping support for the ‘Facebook Custom Audiences’ channel with immediate effect when release 6.9 goes live. Currently, no client is using this channel. The channel may still be visible on the UI after release 6.9 goes live; however, it will be removed from the UI over the next few weeks. |
| 2 | Campaign Manager | Improved | Further enhanced the accessibility by ensuring input elements are properly labeled, provide clear instructions and are visible, link buttons are descriptive, and ensure error messages are announced by screen readers.[CMPN-19976] |
| 3 | Campaign Manager | Improved | Improved the performance and reliability with regards to our file handling processes to prevent occasional ‘Out of Memory’ issues with large files by creating temporary files, securely decrypting data, and streaming it in manageable chunks.[CMPN-19904] |
| 4 | Campaign Manager | Improved | Further improved the reliability and enhanced the user experience by ensuring that if there are any issues or updates, the user requests will automatically be redirected, preventing disruptions and keeping the user flow running smoothly.[CMPN-19762] |
| 5 | Campaign Manager | Improved | Further enhanced our system's reliability and user experience by implementing a robust failover and retry strategy to ensure continuous data flow, minimized downtime, and optimized resource usage.[CMPN-18605] |
| 6 | Campaign Manager | Improved | Improved our logging systems to make our applications more reliable and to fix issues faster, ensuring a smoother and better experience for all users.[CMPN-19159] |
| 7 | Campaign Manager | Improved | Enhanced our code quality by implementing thorough testing, and ensuring new code meets high coverage standards. This will result in more stable and reliable application, reduce bugs, and improve overall performance.[CMPN-19160] |
| 8 | Campaign Manager | Improved | To make deployments smoother and more reliable, we will now ensure that each tenant's deployment only checks exclusion times relevant to their specific timezone, avoiding unnecessary delays and errors.[CMPN-20157] |
| 9 | Dashboard / Reports | Improved | To improve clarity, we have added an important note in the Report Wizard regarding system timezones and SMS content. The note explains that reports use the system timezone and how to find the actual SMS content sent to recipients.[CMPN-18113] |
| 10 | Dashboard / Reports | Improved | Pre-configured Reports: Going forward, Transactional Pre-configured reports will not be available in Excel format i.e. they will only be available in CSV format. This change has been implemented because typically the transactional reports have a lot of data and many times Excel is unable to cope with this amount of data and crashes. [PRB0010075 / CMPN-18637] |
| 11 | Profile Manager | Improved | We have improved the design of the step indicators in the Segment Builder Wizard to make it clearer which step you're on thereby reducing any confusion.[CMPN-18077] |
| 12 | Profile Manager | Improved | Improved how the dates are shown in the filter tooltips while creating segments to reduce confusion and provide a clearer and more accurate experience for all users.[CMPN-19943] |
| 13 | Campaign Manager | Fixed | Fixed a bug, which under a specific scenario was preventing the users from adding an advanced calendar to multiple email deployments. [INC0125715,INC0125710 / CMPN-18568] |
| 14 | Campaign Manager | Fixed | Resolved an issue where duplicating a deployment was resulting in the incorrect transfer of some metadata from the original deployment. [PRB0010865 / CMPN-19422] |
| 15 | Dashboard / Reports | Fixed | ‘Campaign Deployment Summary - By Dynamic Reporting Headers’ report: Addressed the scenario where the users were unable to run the report due to a malfunction in the campaign name filter which was happening because the backend system responsible for preparing the data was not updating correctly due to a technical misconfiguration. [PRB0010522 / CMPN-18923] |
| 16 | Profile Manager | Fixed | Add SFTP configuration screen: Resolved an issue that occurred under a specific scenario when attempting to add a new SFTP configuration. The restriction on the site name field was preventing the creation of SFTP configurations for sites with longer names. [PRB0011222 / CMPN-19964] |
| 17 | Profile Manager | Fixed | Datastore update screen: Resolved an issue that occurred under intermittent scenario while attempting to update a Datastore. The overutilization of the resources in the backend was preventing the Datastore from being updated. [PRB0050022 / CMPN-18723] |
| 18 | Campaign Manager | Fixed | Email Partials: Fixed a bug, which under certain conditions, was causing email partials not to be shown correctly while previewing on the UI for event-triggered instant deployments [PRB0010980 / CMPN-19406] |
| 19 | Campaign Manager | Fixed | Customer Care screen: Fixed a bug, which under certain conditions, was causing content personalization parameters ($TG or $EV values) to not be properly replaced with actual parameter values while showing the communication on the Customer Care screen. [PRB0011253 / CMPN-20083] |
| 20 | Email Composer / LP Composer | Fixed | Customer Care Preview screen: Resolved an issue wherein, if the parameter values were empty in the target file, the parameter names were being incorrectly displayed instead of being replaced with an empty value or being omitted. The limitation on the preview screen was leading to the personalization header not being replaced for the preview only. [PRB0011148 / CMPN-20075] |
2.0 Need more information?
Please contact your Cisco Webex client representative 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]