Reply posted on November 10, 2016 by AkshaySinhaPega
Hello, Please click on View additional configuration options:
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 Basil Pozdeev for achieving the title of Participant of the Week! Basil proactively assisted several users with their queries, which helped them progress with the troubleshooting and build successful solutions. We appreciate your efforts to share knowledge in the community. Hope to see you around and keep up the great work!
Hello Ajit, Thanks fo the info. Recently we are also facing the same exception for Connector. Where can we exactly find the XML Stream Tag to delete it?
Hi, I'm facing the same issue at this moment. can you advise how do I set pxcontexturi and what value should it contain to point to desired node before making a call to connect-File method. Please Note: Current Pega platform is running in one node...
we also have the ACTIVITY Work- • pxForceCaseClose which closes all related work objects, i.e. removes assignments and updates the status.
You should use OOTB API activities pxAdjustSLA OR pxAdjustSLATimes which takes care of updating the SLA and the SLA event queue also.
see in the call pysocialnetwork int that it will ask for a parameter and u need to mention the oauthclient name not "twitter"
You can find more information at https://pdn.pega.com/sites/pdn.pega.com/files/help_v72/procomhelpmain.htm#concepts/casemanagement/con_conceptsgetnextwork.htm#kanchor1455 and that article refers to https://pdn.pega.com/sites/pdn.pega.com/files/help_v72...
while routing please make sure the respective operator has a respective work group and make sure he will be haivng enough roles. kindly provide some more details of the issue so i can share my knowledge on same
Please wait while we search for PDN content that suits your question.