What Motivates You to Participate Here in the PSC?
Reply posted on October 21, 2019 by PatriceS
This has been resolved. We were able to connect and successfully extract by upgrading our JDBC drivers. However, SQL 2016 is not supported by Pega unless we upgrade to 7.3, which is not possible for us at this time.
Reply posted on October 21, 2019 by LaurenceB_GCSPega
prpcServiceUtils does have an option to rollback. But this relies on talking to the application server. So if you can't start the server then I don't think this will be of use to you. We do have the standalone prpcUtils script through (which...
Reply posted on October 21, 2019 by vysypPega
Hi Manoj, Thank you for posting your query in PSC. Our engineering team is working on this issue and it may be addressed in a later release. In case of any updates, please reach out to your account executive to get the latest update on the feedback item.
Reply posted on October 21, 2019 by br001Pega
Hi Dalbir, Kindly validate the Environment configuration details such as JVM & DB details and connection pool size in Context.xml of the server.
Reply posted on October 21, 2019 by Vikash KarnPega
When the new application wizard is run to extend the FW layer, it creates equivalent case types by "direct-inheriting" from case types in the FW layer. The new application wizard used to clone the tables that are mapped to the FW layer case...
Reply posted on October 20, 2019 by leung.cheung
If we have 8.2.2 right now, if we go to 8.3 or 8.4, these fixes are not in the newer versions? Do you mean we should go to 8.2.4 before we can upgrade to higher version?