Question
GFT
BR
Last activity: 26 Jun 2019 17:00 EDT
Issue with REST connector and JSON-LD mapping
I have a requirement to send files through a REST API to an external storage. The external storages uses internal schemas for metadata stored with the file and those schemas are mapped in the rest request to prefixes (from JSON-LD specification) for the properties in the JSON body, as below:
{
"fileContent":"xaiox7x3tr08ahxad3rasDSAGUEW...", //64bit encoded string
"md:filename":"filename.txt",
"md:author":"Name Surname",
"md:dateOfCreation":"2018-11-27"
}
Where md is the schema prefix.
In Pega 7.3.1, I have been unable to make Pega map this correctly (and I'm not looking into doing this in Java).
Is this supported by this version of Pega? If not, does a newer version support this? If yes, how should I proceed in doing this?
Accepted Solution
GFT
BR
I found a solution to this problem. There is the option for using pzExternalName as a qualifier for properties in the integration, so Pega will map correctly when building the JSON request/response.
Pegasystems Inc.
GB
Pega uses multi-part messages for sending attachments to external world.
Pega uses multi-part messages for sending attachments to external world.
- Create a REST Connector.
- In an activity, set the pyRequestAttachmentPage Step page with the values for pyAttachNames, pyAttachValues and pyAttachTypes. Set the pyAttachValues property to binary content, pyAttachNames property to a filename and pyAttachTypes property to text/plain.
- Invoke the Connect-REST from the activity using POST method.
The eaziest way to see the actual payload is to specify URL to be your TcpMon IP:port.
If that is you external system doesn't understand then you have to raise Enhancement request to add this feature to the Product.
Accepted Solution
GFT
BR
I found a solution to this problem. There is the option for using pzExternalName as a qualifier for properties in the integration, so Pega will map correctly when building the JSON request/response.