Access to Insight > Segment > and click on Create a Segment button.
Choose the filter definition in the precondition and insert the param name like: test 01.
Expected result: Returns only the profiles with name test 01.
Actual result: Returns many profiles which names do not have test 01.
With the same filter definition, insert param name with value in double quotes like "test 01" - it returns the correct profile.
If you click Save segment in step 2, this segment will have many profiles without test 01 in the name (exactly the number of profiles that are returned in step 2). Note: The same bug occurs if you insert parameter with value: test 00, but not for parameters test 02, test 03, test 04.
Marketers can now set the time or/and count metrics when creating a segment based on event filter definitions, and reuse the same filter definition in combination with the time period and the number of event occurrences.
Form field dependencies are not imported correctly
Steps to reproduce:
Create a form with 2 elements and make the second element show if the condition is met on the first element.
Export the page with the form to a file.
Change the name of the first element in the form.
Import the form without updating existing content.
Go to the dependencies tab in the second element of the imported form.
The dependency has a crisscrossed background and the name of the dependent form element is the name of the changed element from the first form.
Form field dependencies should work.
Dependencies for form elements do not get imported correctly and do not work. In the Dependencies tab in the imported form, the second text element's dependency points to the first text element in the original form.
A default set of filter definitions are now included out of the box in Visitor Intelligence. Marketers can create segments based on Commerce events and profiles without asking developers to create their own filter definitions.
The Info property should display consistent information.
Mar 30, 2021
Episerver Campaign 8.53
Overview of scheduled jobs If you have scheduled jobs configured in your client, such as automatic recipient imports, you can now view them in the Episerver Campaign front end. This is helpful, for example, if you want to configure new jobs and check which jobs already exist and when they are running. See also: Scheduled jobs in the Episerver User Guide.
Optimizely Full Stack
Per-environment A/B test configuration and experimentation results reports.
Simplified, flag-centric data model. A/B tests and rollouts are now both types of "flag rules", and "rollouts" are now "flag deliveries".
New, consolidated configuration pane for flags and flag rules.
New REST API for configuring flags and flag rules.
New SDK methods (Decide) which offers the same functionality as Is Feature Enabled and more. Allows for future expansion of the new flag-centric data model to all experiment types.