Question
Lloyds Banking Group PLC
GB
Last activity: 7 Aug 2018 4:27 EDT
JSON attribute name translation in v715
There is a third party service - used by multiple consumers - that our PEGA application has consumed and one of the request attributes is named as "top". However, as we know, top is a keyword in PEGA and cannot be created as a property in pega.
I tried to implement a suggestion provided in the support community about creating a property of a different name and using a property qualifier to do this translation to map to the "top" attribute name, but this is not available on v715. I am writing this to understand if there is any other option for v715.
Pegasystems Inc.
IN
Property qualifiers should be used to address special symbols
Needs integration JSON data mapping for below reasons :
Special symbols in JSON key names - $, @, *
Standard keywords as JSON keys - Primary, Top, px/pz…
Not to represent pxObjClass or any other clipboard page specific property values in JSON
SingleValue-* class mapping
Heterogeneous arrays
Lloyds Banking Group PLC
GB
Would you be able to elaborate a bit more on what this statement means? "Needs integration JSON data mapping for below reasons"
Lloyds Banking Group PLC
GB
And probably should have mentioned my scenario - The service we consumed was already built and when we originally imported the sample request to build the integration classes, some fields were missed and now we have a need for these missed attributes. Hence we were trying to manually create these 2 or 3 attributes that we missed originally and system wouldn't let us create a property with name as "top".
I launched a new connect rest wizard and imported a sample request with "top" as an attribute in it to see how the system handles this and it creates the top property. Apparently, the system doesn't perform the same validations on property names while creating through a connector wizard to when it is created manually!!!