Release-20230228 Release Notes

Symend's current focus is still system performance, so if operations such as sending outreaches appear to be processing faster, that's because they are! With that understood, our releases will continue to be less feature intensive. Our February 28th 2023 release includes: detailed views of Events in Customer Trail; information tool tips on those Events and Event Properties; and Data Workspaces being hidden as a Data Source if you don't have them enabled when creating a Data Source Mapping. We have also resolved some bugs in Customer Trail, Data Source Mappings, Exports, File Transfer Settings, and Email Settings.

You can find the details in the Bug Fixes section.


Customer Trail

Learn more - Customer Trail

The Customer Trail can show you the various Events that have occurred for your individual customers but prior to this release, it wouldn't show you the full details. Now you are able to click the chevron to the right of that Event and it will display the full details. In addition, for each Event or Property, there is now a tool tip available next to them explaining exactly what they are.

Customer Trail

Description

Customer Trail

Description

What’s New

  • Accordion menu to the right of a Customer Trail Event to view Event Properties

  • Expand the menu by clicking the chevron

  • Information tool tips on Events and their Properties

What's Changed

  • N/A

What’s Removed

  • N/A


Data Source Mappings

Learn more - Data Source Mappings

There were some smaller changes surrounding error handling, which you can view in the change table. However, the biggest change you may notice is when selecting a Data Source in your mappings. If Data Workspaces have not been enabled, then you will not see the option to utilize it as a Data Source.

Data Source

Description

Data Source

Description

What’s New

  • When clicking the Manage Data Source and navigating to the Data Sources screen, if a Data Workspace was missing, only the first missing Data Workspace would display an error message. Now all missing Workspaces will display an error

  • When clicking on a Data Workspace and navigating to the Data Source Fields screen, and a Source Field is missing, then an error will be displayed on the appropriate field

  • If for some reason the underlying services encounter an issue when viewing the list of your mappings, an individual mapping page, or the data sources page, then an error would be displayed and you would be blocked from being able to access these pages. Now instead, you can still access these pages

What’s Changed

  • Data Workspaces will not appear as a source if they have not been enabled for your Organization

What’s Removed

  • N/A


Bug Fixes

Platform Area

Description

Platform Area

Description

Customer Trail

  • Filtering an individual Customer Trail by a specific Campaign would return no results because of an incorrect handling of the Campaign's ID, which now references the correct ID and filters the information as expected

Data Source Mappings

  • The error message when missing the Account Key using a Data Workspace used to read Data Source not found, which has been corrected to Source Field not found Visual corrections when selecting a Data Source Type, specifically around spacing with the elements When adding a new Data Source:

    • If the Update Frequency field is not populated, then Update frequency and Time of day will no longer be visible When selecting a Data Source Type, clicking outside of the creation menu would close it, now Cancel must be clicked or the escape key must be pressed to close the menu Not selecting a Data Source would not say the field is required, you would simply not be allowed to save, now a Required error message will appear if this is attempted

    • Using a Data Workspace table in one mapping will no longer allow you to select it in another mapping

Exports

  • When cloning an Export, if the name was more than 123 characters, when copy was added to the end of the duplicated Export, it would be more than 128 characters, causing an error. Now, any additional characters that causes this to occur from the original Export name will be truncated

File Transfer Settings

  • When two Import files had overlapping names, such as File_10012 023.txt and File_Two_1 0012023.txt, then the ingest of the second file would fail. This will no longer occur

Email Settings

  • The example text for an email domain would read www.payments.company.com, which was misleading, as www should not be included. It now reads payments.company.com