Release notes 3.22Release Content Summary The following table provides a list of the customer facing / relevant changes in this release. Not all platform backend changes are included in this list. Domains Type Notes Support Ticket Backend refactoring Improved the pagination process for dynamic data model Backend refactoring While performing LDAP integration in Sweagle, SAML URL should be defined in the tenant preference to prevent null pointer exceptions. Backend bug Fixed the GUI error where moveNode API returns a successful 200 response but doesn't move the node in the GUI CS5478563 Backend bug For wrong identified words (order not respected) in GUI and API, use “identifierWords” parameter in the API calls. The behavior of “find.identity_attributes_discovery.word_list” tenant preference cannot be changed as it will cause performance issues. CS5390042 Backend bug While copying a node, no more “Bad Input Exception” is thrown if the destination node refers to a node type with only ONE allowed child type. UI bug Fixed the issue while duplicating nodes where the nodes are created as dimensions after losing the parent node data after the first attempt. UI refactoring Improved the pagination process for dynamic data model Details - Wrong identified words (order not respected) in GUI and API Issue Description: If a value "description" is added to tenant preference setting "find.identity_attributes_discovery.word_list"(Example: find.identity_attributes_discovery.word_list=id,Id,name,Name,description), The order of the identifier words is not respected while uploading data. With some json files, the node name is taking the value “description” instead of taking the correct value “name”. Workaround: The order of the keys inside the sent json is important, not the order in the tenant preference. Json sorts the fields by name. As a result, data is handled on Sweagle side by the same order that it gets from the json file. If “name” and “description” are identifiers in the list, “description” will be picked naturally since “d” comes before “n” in the alphabets. To solve this sorting, either use identifierWords param with bulk upload call or delete “description” from the tenant preference. Details – Copy a node While copying a node, if the destination node refers to a node type with only ONE allowed child types, api call returns the below error. The Rest call: https://endpoint/api/v1/data/node/178107/copychangeset=569695&to=61690&name=mTeAuthTacacs2©Metadata=true returns the message:{"error": "BadInputException","error_description": "You should select a type from the list"} This error is fixed while copying a node in this version. The documentation mentioning the list of parameters are corrected, the type of “to” parameter is changed from ‘Long’ to ‘Text’.