Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 karthigeyan ravichandran (karthigeyanr)
Common Wealth Bank of Australia

Common Wealth Bank of Australia
AU
karthigeyanr Member since 2017 13 posts
Common Wealth Bank of Australia
Posted: May 15, 2019
Last activity: Jul 15, 2019
Posted: 15 May 2019 10:22 EDT
Last activity: 15 Jul 2019 2:58 EDT
Closed

Unable to send Binary Data using connect-REST in Pega 722

We are currently using Pega 722 and we are integrating with JFROG artifactory for storing the Pega builds. Though native JFROG integration capability is available from Pega 73, there is no plan for upgrading our instances in near future. Hence we are using connect-REST to send zip files as binary data to artifactory repository. But with this approach connect-REST is failing with outbound mapping exception (unable to use java object property to send request data).

Moreover the fix given in the support article (https://community.pega.com/support/support-articles/rest-issue-when-sending-message-body-binary) to customise pyInvokeRESTConnector is not feasible in our case as the OOTB activity is changed in Pega 722

Any other recommendations to resolve the issue would be appreciated.

***Moderator Edit-Vidyaranjan: Updated SR details***

To see attachments, please log in.
Data Integration
DevOps
Support Case Exists

Posted: 5 years ago
Posted: 15 Jul 2019 2:58 EDT
Vidyaranjan AV (Vidyaranjan) Senior Online Community Moderator
Pegasystems Inc.
IN

Hi,

From the SR notes, I read that this issue needs deeper analysis and troubleshooting is active in the SR.

Once you arrive at the solution, please feel free to share it here for the benefit of the community users.

Thanks.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice