All fields defined for Mobile Push Messages can now contain personalization. The following example might be personalization on a mobile push title, as well as on the expiration date set for the mobile push message: addweeks(sysdate(), 4)%]
Some enhancements were made to Pages support in Selligent Marketing Cloud within this release. Rendering pages (both regular and API response pages) are be default in the language of the user. The language in which the pages are rendered can now be overridden. This is typically convenient for API response pages, where pages are expected in a specific language. If the specified language page does not exist, the fallback language of the default for the user will still be displayed.
Enhancements were made to Content Blocks, so that now when they contain the sg:content tag they can contain language specific text, e.g. provide a content section with 2 different languages included. Only the text in the language for the message will be displayed. Below is an example where two languages are defined:
<sg:lang value=“NL“>Mijn content in het nederlands</sg:lang>
<sg:lang value=“EN“>My content in English</sg:lang>
This release includes enhancements related to users sharing lists within Selligent Marketing Cloud. When using a Data Component within a custom Journey which includes a shared list with a filter, it will list the fields that are used for the filter with the values automatically filled out. A filter icon indicates this in the drop-down list so the user understands why these filters cannot be changed. The user is also notified when trying to create records which do not comply with the filter.
This release now supports the operator “is one of”, whereby a list of values can be provided. The values need to be entered as pipe separated before it can be tested. This makes it easier for the user to specify business rules against a large number of values, such as a range of Zip Code or Postal Codes.
Within the Visibility Constrain Editor, the DataError System variable is now available. This enables different rules to be applied over what content is visible in the event that a specified error occurs.
The Web Custom component now also supports the POST method. With the POST method, the input parameters used for the component are not visible in the URL.
Within this release, enhancements were made to the Library within Selligent Marketing Cloud. Users can now sort files in the Library in either Ascending or Descending order, using one of the following fields: name, modification date, extension, size and dimensions.
Moreover, when new files are uploaded, conflict management is available where you can decide to rename the uploaded file, to keep the existing one or to overwrite the existing one.
Enhancements have been made to extend the assets which can be copied between folders, especially to other Organizations. Now support for template messages is included. The same features are provided, whereby the content will be adapted to the settings of the target Organization and validation will check that require assets exist in the target Organization, e.g. Images, Content Blocks, etc. If they do not exist, a warning is displayed, but the user can still force the copy of the asset in any case, regardless.
When users need to change their password, information can be provided on the format of the password that they need to adhere to, e.g. upper case, lower case, characters supported, etc. This provides them additional guidance with regard to policies around acceptable passwords.
Building upon the launch of Cadence Management in the Damson (v3.3) Release, this release adds enhancements to improve the usability of this capability.
A new feature has been added to the Plan Properties which suggests a plan recalculation time based of previous recalculation times, and the first journey included within the plan.
Furthermore, enhancements were made to selecting a journey within a cadence plan, presenting a dialog which enables a journey to be selected from a common folder structure. Also, now when you open a cadence plan you are automatically directed to the properties tab to define the journeys. Clicking on the journey name in the priorities tab now displays the details for the selected journey. Where less than 10 journeys are included, the details for all journeys are automatically expanded.
Some minor enhancements were made to the Top Component in order to improve general usability. Firstly, now the number of contacts to be targeted is presented on the journey canvas without the need to expand properties. The default number of contacts is set to blank.
The Top Component is now available to use in Single Batch and Recurring Batch Journeys. This can be defined in the Advanced Properties of the journey. It enables the user to limit the number of contacts targeted by the journey, but additionally, within Recurring Batch Journeys allows this limit to be applied to either an individual or all runs of the journey.
The Split Component previously supported changing the audience path on a journey based on a RequestValue, Constrain or TEXT field. This release expands the functionality to support use of an Expression.
Tracking on journeys provides a view on the volume of emails sent as well as interacts such as opens, views of clicks. For some journey types though, such as password reminders, this tracking information is not always valuable. Users now have the option to disable tracking on such journeys. Support is provided for Single Batch Journeys, AB Journeys, Recurring Batch and Custom Journeys via the Advanced Properties of the journey.
Enhancements were made to the deduplication function which now sets a limit of a maximum of 5 fields to be used for deduplication. Also, the following field types are not permitted: LONGTEXT, BOOLEAN, FLOAT and DATETIME. To improve usability, now when deduplication is being used an icon reflects this on the Message Component in a Custom Journey. This makes it easier for users to see where deduplication is in effect, at a glance.
Usage of Transactional Journeys in SQL Tasks and Import Tasks is now tracked. This means that when a user tries to delete a Transactional Journey from the Journey Start page, they receive a warning that the journey is in use.
Custom Journeys that are being edited are by default blocked for other users. Users can now explicitly unlock these journeys through the Action menu in the toolbar for improve user experience. Other additions to the Action menu include the ability to display the Component IDs and the Target Count for each Message Component on the canvas. Previously, the user had to perform this via an icon on the Validation Pane. Hovering over the target count provides a callout bubble containing additional information for an improved user experience.
Smart Content, which provides product recommendations through Selligent Cortex, our AI-powered engine include some additional enhancements in this release. Filters can now limit the products offered based on new timing options, such as “Newer than, “Older than”, “Between” and additional values such as 12 hours, 6 hours, 4 hours and 2 hours. This means users can now leverage these functions to only recommend products which are new and created in the last X hours.