Reply posted on July 1, 2019 by SureshS
The above solution works after adding below settings even though it is not recommended jsch.setConfig("StrictHostKeyChecking","no");
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!
Hi Ujjwal, I did a complete implementation of the Chase HPF payment service in Pega, which works even in Pega Mashup. I am currently working on an article with "how to", which I will post on Pega Community soon. We did this implementation...
Hi Sirisha, I hope that it did help, if your REST service that is creating the case is being called first, you may only want to call the activity to progress the case separately if you are expecting a user to manually input case information before the...
Hello Tamont! We are currently looking at the July/August timeframe to make 8.1.6 available. Please DM me the support request you are interested in and I will make sure to track it through our system. Thank you! Matt
Hi Venkat, Thank you for your questions. The configuration described in https://community1.pega.com/community/pega-support/question/configuring-pega-mobile-client-authenticate-against-okta will work for both web and mobile. The fact that we choose ...
I was try to delete all the customization but i didn't found the thing that making glith. I will try more harder to find that Have more suggetion to do that?
Please wait while we search for PDN content that suits your question.