Version 2 of the Decision API was released. User experience should be unaffected by this change.

When creating a new rule based on an existing filter, Experience Builder didn’t display a confirmation notification for the new rule.

When users clicked the Settings tab for configured rule cards in the sidebar interface, Experience Builder didn’t respond.

Deleting rules from a slot caused Experience Builder to stop displaying the slot on a webpage in isolation mode.

When attempting to filter content based on dates, Experience Builder either didn’t display all the content associated with selected dates, or returned errors in the browser console.

Users didn’t receive notifications when configuring multiple rules that used the same filter.

The Content card for slots now defaults to a list view.

Goals with the same name on multiple websites caused an error.

Goals failed to identify site_ids properly, causing an error.

Click-through goal rule names default to the format [Rule name] Click-Through. If a goal exists with that name, the format is [Rule name] Click-Through [uuid].

Decision API contains changes which won’t affect users’ experience with the product.

The same goal name may be used on different websites.

In the Content tab, content is presented as a list instead of cards.

The filter card scrolls, which prevents the card from being cut off in lower resolution screens.

In the rules screen, the Number of content items maximum has been increased to 10.

The URL field in View Modes doesn’t contain meaningful data and has been removed from Experience Builder and the Decision API.

The Slot Isolation Panel opens properly when multiple segments are active and all have higher priority than the current segment.

When modifying an existing slot to be visible by all segments, Experience Builder didn’t preview content in the slot.

When users created a rule from a filter that returned no results, Experience Builder displayed a console error message.

Creating a filter with the date range set to last 30 days caused browser crashes.

When users replaced content in an A/B testing rule, the new content didn’t retain the distribution value assigned to the previous content.

Attempting to highlight a slot not included on the current page caused Experience Builder to display error messages in the JavaScript console.

By default, Experience Builder now displays reports that contain one month of data, instead of two.

When users attempted to view a report filtered by a date range, Experience Builder displayed incorrect data.

When attempting to create recommendation rules, the content preview failed to display, displaying instead a JavaScript console error.