Question
Scotia
US
Last activity: 24 May 2024 15:11 EDT
application/x-www-form-urlencoded not working after Pega upgrade to Pega 23
The application was built in the Pega 7.2.2 version, and due to some issues, the team has developed the Rest-Connector for "application/x-www-form-urlencoded" parameters implemented with pyRequestAttachmentPage page parameters after encryption.
Now that we are upgrading from Pega 7.2.2 to the Pega 23 version, the URL-encoded parameters are not getting passed to other systems, and because of that, the source system is sending a validation error back.
PFA word document with screenshots.
Note: I checked multiple discussions before posting this, but it did not work.
link1: https://support.pega.com/question/connect-rest-applicationx-www-form-urlencoded
Please let me know any inputs on this.
***Edited by Moderator Marije to add INC-B17707 tags***
Accepted Solution
Scotia
US
@MarijeSchillern Hi, We got the solution, it's because the pyRequestAttachmentpage has the parameters that are used for authentications. Maybe URL encoded params are getting overridden from this page while sending the request. after removing the page and following the above link links logic it worked.
Pegasystems Inc.
GB
@AnilkumarV8313 please log this as a support issue via the MSP. and provide the INC id here in a reply.
Updated: 24 May 2024 15:07 EDT
Pegasystems Inc.
GB
@AnilkumarV8313 I see that you logged INC-B17707 (application/x-www-form-urlencoded not working after Pega upgrade) on 1 May but did not respond to our support team when they requested the client validation error message you received, along with the tracer and snapshots of the error message. The ticket was closed.
You can log a new support issue in the future when you can work with our GCS team.
Accepted Solution
Scotia
US
@MarijeSchillern Hi, We got the solution, it's because the pyRequestAttachmentpage has the parameters that are used for authentications. Maybe URL encoded params are getting overridden from this page while sending the request. after removing the page and following the above link links logic it worked.