Fourth Quarter of 2020

Release Date: December 11, 2020

This topic provides a list of product changes released for this module on this date.

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now search the Asset and Tag instances with special characters in the attribute values. To enable this feature, the following changes have been made:
  • While creating or modifying the Tag instances from the UI Asset microapp, you can add UTF-8 special characters to the attribute values.
  • While creating or modifying the first class (Name, Source ID, and Description fields), reserved, and custom attributes for the Tags instances from the UI Asset microapp, you can add UTF-8 special characters.
  • While creating or modifying Asset and Tag instances through API or Asset Ingestion, you can add UTF-8 special characters to the attribute values.
  • While searching for a value that contains UTF-8 special characters through the user interface, you can search all the values with special characters except ,(comma), :(colon), and *(asterisk) characters.
  • While searching for a value that contains special characters through the GET API and Query Endpoints, you must add a \(backslash) before the special character to escape the ,(comma), :(colon), \(backslash), =(equals), ()(parenthesis), |(pipe), ‘(single quotes), and *(asterisk) characters.
    Note: If the value itself contains a backslash, you must escape it by adding another backslash.
F56575
Table 2. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, if you ingested a new patch JSON file to update reserved attributes of an existing tag instance, the fields were added or updated appropriately. However, after the ingestion, all the existing custom attributes were deleted. This issue has been resolved. Now, in this scenario, it only adds or updates the fields from the JSON file. DE140742