:warning: Please ensure you have read the upgrade notes from the PREVIOUS RELEASE, if upgrading from an earlier version
UID
or by a combination of Relationship Type
, from
field and to
field. From 2.39 Relationships are only identified by their UID
. This is causing a potential breaking change as earlier a payload with a Relationship without a specified UID
could be imported multiple times without errors (just a warning that updating the relationship was not possible), while now the import is throwing an error stating that a Relationship of the same type and linking the same entities already exists.Metadata attribute validation: Validation of metadata attributes will be executed when saving objects with attribute values in the maintenance app. Validation rules are now based on the Attribute.ValueType
. Most of those rules are straightforward. For instance value type “number” will only accept digits. On the other hand, “phone number” has a regular expression validation rule "^[0-9+\\(\\)#\\.\\s\\/ext-]{6,50}$"
. As a result of this new validation feature, you might get errors when editing metadata objects which now have invalid attribute values. In that case please update the values and save the object.
SYNC
. Deprecated API endpoints (except SYNC
) are:
```
These endpoints have been replaced with the new tracker endpoint:
Deprecated endpoints have been removed: (see deprecated-features )
XML support in metadata APIs as well as in metadata import and export has been removed.
The POST /api/dataAnalysis/stdDevOutlier
and POST /api/dataAnalysis/minMaxOutlier
API endpoints are removed. These endpoints are superseded by the /api/outlierDetection
API which offers higher performance and more sophisticated outlier detection.
The POST /api/dataAnalysis/followup
API endpoint for reading follow-up data values is removed. This endpoint is superseded by the GET /api/dataAnalysis/followup
API endpoint.
The type
field in the /api/analytcs
API endpoint metadata
> headers
response is removed. Instead use the valueType
field.