Encoding Behavior in Transformations

This alert applies to JST Designer in Itential Platform for the 2023.1 release.

Release Alert (2023.1)

Prior to Itential Platform version 2023.1, special characters (e.g., / and ?) were encoded in the schema keys to allow their use in transformations. This is because JSON schemas have a strict uri-reference match for schema keys, so users would encounter schema validation errors when saving transformations.

Going forward, special characters are no longer supported in this capacity and all JSON schemas must be compliant with JSON Schema validation rules. Previously encoded transformations will still work as expected, and both encoded and decoded versions of the affected schema keys will be accepted in transformation input.

What should I do?

As a best practice, please confirm all custom applications and adapters are unaffected by this code enhancement. If you need additional support or require more information, please contact our Product Support Team.