OpenAPI Profile UDR Generation Backwards Compatibility

Owned by Jenni Wallin
Apr 25, 2023
1 min read

Due to a bug fix on the OpenAPI profile for UDR generation, refer to MZ-39311 in the Bug Fix Appendix, using the OpenAPI profile with the bug fix will result in backwards compatibility where your APL statements, utilising the UDRs from the OpenAPI profile will require modifications.

The bug occurs when MZ encodes or decodes UDRs that contain special symbols in the field name or field names that begin with numbers.

Previously special characters are replaced by underscore, after the fix, special characters are replaced with a unique string of characters to allow MZ to revert the replaced symbols back to the original field name.

This will break backwards compatibility on UDRs that were previously generated by the OpenApi profile used within the APL agent in the workflow. This will only occur if the UDRs are regenerated.

Example

@ -> _40_
. -> _2E_
- -> _2D_
The field name test-name will now become test_2D_name instead of test_name after the fix