New filter types for 'in' and 'not in' scenarios
To handle cases where a filter needs to match incoming data based on one of many given values being present/not present, two new filter types have been implemented: Contains one of many and Does not contain one of many.
Using contains one of many or does not contain one of many for string filters
In shapes where source instance/endpoint options are available (e.g. connector, flow control, route), the endpoint selector has been enhanced to include a search field, so you can quickly search for the required endpoint by name.
Run process flow shape
When selecting a process flow to be initialised from a run process flow shape, ALL defined process flows and associated versions are available for selection (by default, the latest is prompted). This removes the restriction of only being able to call deployed & enabled process flows.
Filters: enforced validation for data types
Additional validation has been added for filters, which means that input values must be of the expected data type. For example, consider the payload below:
{"name": "Jane Smith", "ref": "14"},
{"name": "Bob Smith", "ref": 14},
Notice that both records include a ref field, but one (Jane) is a string type value and the other (Bob) is a number type value. Now suppose we define a filter to examine the ref field, and to expect the value of this field to be a number .
Previously, the data type was not validated, so both records (Jane and Bob) would have been matched. Now, the data type defined in filters is validated and a record will only be matched if the filter value is of the expected type. This is a phased change.
Phase 1 (this release)
In this release, any data type validation issues will be reported as warnings in run logs but this will not cause filter behaviour to change. So taking our example above, both records (Jane and Bob) would continue to be matched.
Phase 2 (next release)
In our next release, data type validation for filters will be enforced - i.e. filter behaviour will change so a record will only be matched if the required value is of the expected type. Taking our example above, only Bob will be matched - Jane would not be matched because the ref field is provided as a string.
For more information please see the Breaking changes section.
Company insights - usage stats
Fixed issue where usage figures shown in the left-hand navigation bar may not match the main customer insights page.
Company insights - graph display
Fixed issue where the graph display could be lost when switching between process flows/connectors/shapes tabs multiple times in quick succession. Now, switching between tabs is not possible until the current graph is fully loaded. In a related issue, graph zoom has been disabled.
CPT-3098
Static date selector for variables
Fixed issue where no time selector was available when choosing to add a static date/time in a flow variable or in the set variables shape.
Route shape settings
Fixed issue where creating a new route for a route shape did not go on to display settings for that route. Now, associated settings are shown when a new route is created.
