Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue Mapping incoming Array from HTTP POST into Pega

SA-37475

Summary



Third party application is posting content to PRPC to run a specific activity using a form level input element array.

User sees that the post data is coming into Pega and mapped to the "Parameter Page" but the issues is that the third party application sends the data as "Arrays" and only the first element in that array is mapped to the "Parameter Page".

NOTE: User created this SR, based on the recommendation received to create an SR on the community:
https://pdn.pega.com/community/product-support/question/mapping-incoming-array-http-post-pega


Error Messages



Not Applicable


Steps to Reproduce



HTML form post using input element array. (Input name attribute repeated).


Root Cause



A third-party product issue.

Using form level input element arrays is not supported when calling an activity this way.

Pega does support form level input element arrays for mapping to the clipboard but that is handled in a specific way to map data to ListValue properties and so on.

Resolution



Make the following change in the operations environment:
  1. The third party application should post a XML or JSON structure.
  2. This can then be parsed in the activity and mapped to the clipboard properly.

Published May 16, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us