Release 6.4 - 2022 Aug

1.0 Enhancements spanning multiple modules

1.1 Webex-themed icons & typography

Building on the new Webex-branded look that we introduced in the previous release, we have changed most icons within Webex Campaign to align with the Webex UI design guidelines. Also, the color of all the headings has been changed from blue to black as per Webex UI design guidelines.

1.2 Enhancement in the ‘user profile’ setting pop-up (within the menu in the top right of the screen)

Users can now see a few more configuration information about their own profile e.g., their mobile number and the role that has been assigned to them. Users can also update their own mobile number. This enhancement is useful because the mobile number is used as part of the password of the Excel file that is sent by email in case of scheduled reports.

This feature is associated with Nolt enhancement idea # 236.

2.0 Campaign Manager module enhancements

2.1 Ability to create Target Groups from CSV files

You will now be able to use .CSV files as a source for Target Groups where the TG Source is ‘File’ or ‘SFTP’. The .CSV files must use ‘comma’ as the delimiter to separate header values within a record. If the file extension is .CSV, but it uses some other non-comma character as the field delimiter, then the file will be rejected (e.g., tab-separated files with .CSV as file extension are not supported).

This feature is associated with Nolt enhancement idea # 154.

The comma-separated .CSV file can be used in the following areas of the Webex Campaign:

• 1. Create a TG pop-up on the TG List screen
     a. TG from file upload
     b. TG from SFTP
• 2. Create Deployment (Deployment Canvas):
     a. when the user drags & drops the File / SFTP nodes from the left panel onto the grey ‘Add Target Group’ placeholder node in the central canvas area
     b. Additional options – Seed list
     c. Additional options – Exclusion list
     d. Additional options – Inclusion list
• 3. Event-triggered Instant deployments using the ‘file-drop’ method

Usage Notes:

1. Comma-separated .CSV files are supported for both types of target groups: Static TG & Dynamic TG.
2. After the comma-separated .CSV file is ingested within Webex Campaign, it will be internally converted into the system-native ‘pipe-delimited .txt’ format.
3. As per the existing behavior for all files ingested for TG creation, the uploaded CSV files will also be deleted immediately after Webex Campaign has ingested it and converted it into the system-native ‘pipe-delimited .txt’ format.
4. All the internal processing of the files will continue to be performed in this system-native format. Therefore, when you download files from Webex Campaign UI, they will be in pipe-delimited .txt format. e.g., downloading error records from the ‘Deployment summary’ page.
5. If the uploaded CSV file has any value with a ‘pipe’ character, then that whole record will be considered invalid and rejected.
6. When you select any TG from the ‘Existing TG list’, then it will be in the pipe-delimited .txt format.
7. If you request any TG file data from the L2 support team, then those files will also be in pipe-delimited txt format.
8. When a Segment is copied into a dynamic TG, the format of the TG will be in pipe-delimited txt format.
9. The only supported ‘enclosing character’ will be ‘double quotes’. i.e., if a header value itself contains a comma (e.g., a customer’s address may contain a comma) then it should be enclosed in double quotes.
10. The only supported ‘escape character’ will be ‘backslash’. It should be used if the header value itself contains double quotes.

2.2 Ability to create a new event from a previously created event template

You will now be able to save any event as an ‘event template’ and then use this template when creating a new event definition. As a reminder, the event creation functionality can be accessed from the following menu: Campaigns >> Target Data >> Events. Within the ‘Event information’ section, you can now save an event as a template.

Once an event is saved as a template, then you can use it as the basis to create a new event.

This feature can save you lots of time and effort if you need to create multiple events with many event parameters which are only slightly different from an existing event.

📘

To be able to see the list of available event templates, you will need to set the value of the ‘Created by’ filter to ‘All’ on the ‘Events list’ screen.

This feature is associated with Nolt enhancement idea # 201.

2.3 Events list screen improvements

We have added the following 3 additional columns on the ‘Events list’ screen:

• Event key type: This column will have one of the following 5 values: MSISDN, EMAIL, APPDEVICEID, CUSTOMKEY or the designated <'M Profile key'> for the specific tenant.
• Event params: This column shows the number of parameters within that event. If you hover the mouse over the number, you will see the list of parameters.
• Templated: This column will have a value of ‘T’ or blank. The value ‘T’ indicates that the event has been templated and another new event can be copied from this templated event.

2.4 TG Splitter: Sequence of headers in the output files will match that of the original file

When using the TG Splitter feature, the sequence of the headers in the output (children) files will match the sequence of headers in the original (parent) file.

This feature is associated with Nolt enhancement idea # 227.

2.5 SMS: Showing the last message template associated with a deployment

You will now see the name of the last message template that was associated with a deployment along with the date and time when it was selected by the user. This feature was introduced for Email & MMS channel message templates in the last release; now we are extending it to SMS message templates.

This feature is associated with Nolt enhancement idea # 89.

3.0 Profile Manager module enhancements

3.1 Profile Manager SFTP configuration: Ability to test connectivity

A new action item called ‘Test connectivity’ will help you in testing connectivity when setting up and using SFTP for file exchange. (Administration >> Profile manager file clients set up).

After you click on the ‘Test connectivity’ option within the 3-dot action menu, a pop-up screen will display more details about the SFTP connectivity.

📘

For this feature to work correctly, your SFTP account must have Read/Write permissions for its home path. Otherwise, you may be displayed a ‘file system exception’ error. In that case, you will need to contact your IT team to request appropriate SFTP permissions.

3.2 A new monitoring report: Data exchange report

This new report is available from the following menu location: ‘Administration >> Monitoring >> Data exchange report’. This will enable you to monitor and review the outcome of every instance of file transfer using a specific data exchange configuration.

You can view more details about any specific instance of data exchange by clicking on the ‘View details’ from the 3-dot action menu at the right.

4.0 Maintenance items in this release

The following table lists all the improvements and bug fixes in this release.

In addition, the following bug fixes & improvements will be deployed as part of a small patch release on top of release 6.4. The dates of deployment of this patch release are as follows:
• AWS-UK: Aug 29th, 2022
• AWS-Ireland: Sep 1st, 2022 (on the same day as the main release 6.4)
• AWS-USA: Sep 5th, 2022
• AWS-Canada: Sep 6th, 2022

There is no planned outage expected while this patch release is being deployed.

5.0 Need more information?

Please contact your Cisco / imimobile 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]