Reply posted on November 22, 2015 by sahup1Pega
Thank you Harish!
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Gouri Shankar for achieving the title of Participant of the Week! Gouri Shankar believes in sharing knowledge. He proved to be an amazing participant by writing a knowledge share article on a topic that will be informative to the diverse audience in the community. Read his article here. Keep up the great work!
Just want to clarify the resolution of this issue. This looks like a bug in the ojdbc7.jar version 126.96.36.199.0. I do not think it is related to whether this is part of a global transaction or not. Caused by: java.sql.SQLException: Could not commit with...
Hi Harish, You can check the AES version using the PegaAES ruleset version. 3.5- 03-05-xx 7.1- 07-10-xx 7.1.7- 07-13-xx-Rajiv
I don't think Pega put any constraint on the ejb types, but Java RMI requires the types to be serializable. So short answer, you cannot directly receive InputStream as it is not serializable. You can write a wrapper class implementing Serializable...
"Unable to synchronize on requestor H4733C449EBB0C1825910F4CF3805427F within 120 seconds"- 1) Where is this "120 Seconds" value set and what's the parameter name? 2) What if there's a genuine requirement where the...
Hi Mandar, It would be helpful to others if we can start a new thread on this new question about securing SMA on Websphere.-Adi
Hi Marc, This can work. It is more like work around. The original question was more about field value rule not interpreting special characters.
Bob, follow this article: https://pdn.pega.com/support-articles/updating-prmbeansproperties-in-pega-717
Please wait while we search for PDN content that suits your question.