Continuing to build upon our marketer-managed data approach, now when creating a list and defining the fields, users can now set a field as computed field and define the function to be used for that field. This makes it much easier to manipulate data to make it fit for purpose for use within Selligent Marketing Cloud. Validation also provides the user with feedback on where that computed field is used, for example in personalization, if they attempt to delete a field created using this method. In addition, within a List, users can define a Content type of 'Data Selection Filter Set'. This enables fields to be used as a lookup field in content. This type of field contains a list of IDs (usually numerical) that are separated by a comma, semi colon or pipe. The field is used to filter items in a data source when used in content / messages. Only fields of this type can be used to filter the items. (See Custom Events within this release to see how this is used in messages).
Within this release, support has been added to use lookup data in Single Batch Messages. Users can now display items that are retrieved from your catalog data through a lookup, e.g. product preferences on your audience table, stored typically as numerical IDs. Previously this functionality was provided for Transactional Messages, and now has been extended to support marketing messages.
Support is now provided for duplicating Single Batch Journeys. In addition, a new validation component was added which allows for validating data before the next step in the journey is launched. One or more conditions can be configured to set the validation and all of these need to be TRUE for the step to be classed as successful. Error messages can also be defined, and these will be displayed when a corresponding condition in the validation fails.
User Interface (UI) Changes
A broad range of improvements were made to the user experience within Selligent Marketing Cloud within this release. Now, when adding items manually to a repeater in a message, you can do this through the buttons in the
repeater itself or via new buttons available from the top toolbar. A slight change has also been made to where the layout options are displayed in the properties of an item, which now appear at the top of the properties window so you can first select the layout to apply to the item.
When working with content, there are two new changes to not. The notification with the lock-info has moved from a separate toolbar into the regular toolbar as one usability enhancement. You are now also able to RELEASE your lock manually by clicking the option in the actions-button-dropdown.
Another change was made when working on content. By default, the content is locked for other users. To unlock the content and allow others to work on it, you have now an option available in the Actions drop-down menu that allows other users to edit. Also, an additional navigation level has been added to easily switch between text, design and source mode for your content. The buttons that were previously available in the Design panel of the content have been removed.
Finally, when designing a dynamic segment, the filter is now defined in a dedicated step of the wizard and can afterwards easily be viewed directly within the Segment details.
Segment Builder Enhancements
This release includes an enhancement to building a constraint whereby campaigns are used within the criteria. Previously users had to search through a tree view of campaigns, but now, they can enter search criteria at the top and select a journey from the list of results that are returned.
API Explorer Enhancements
New capabilities have been added to the API Explorer, including:
- You can trigger the execution of a journey with a JSON data-set.
- Calculated fields are now also supported
- The fields of type “data selection as an identifier set”: are now supported via the API (see “Lists” and “Custom Events” within this release)
You can now add text-based option lists through the Create List API
In the last release support was provided for using waves for Email, Push and SMS Channels. This enables users to avoid bottlenecks and performance issues, where volumes of communications are high, and you don’t want to drive too much traffic to the website / landing page, or to put resource challenges on the Call Center, where a communication may have a strong call to action (e.g. a competition, etc.). Within this release, support is extended to support Custom Channels (such as Twitter and Facebook for example) as we continue to enhance this capability in Selligent Marketing Cloud.