- Views (499)
- Replies (4)
- Login to like
- Reply
Reply posted on December 5, 2019 by MarissaRogersMod
This link should work.
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!
This week we recognize Cloe Walker as our Participant of the Week! Cloe is using the PSC in an effective manner by actively driving their discussions forward and acknowledging the community for the responses received; thus, building successful solutions. Hope to see you around and Congratulations!
This link should work.
That's correct, We can create our own code to handle emails, but it will be like recreating email listeners functionality
Hi Jagdish, On the latest version IPV can handle multiple request on the single e-mail. https://community.pega.com/knowledgebase/articles/whats-new-pega-platform/trigger-multiple-actions-during-email-intelligent Please check this one. Regards, Anandh
Hi Johan, Okay, It means something wrong with kafka itself.Can you please share error logs which got generated during kafka startup. Thanks, Abhinav
Question posted by SathishV1966 on December 5, 2019
Unfortunately there is no such capability.
Question posted by GodavariM5332 on December 5, 2019
At high level, REST is the industry standard at the moment and hence JSON payload, which is in general performing better than any XML based protocol (e.g., SOAP).
Question posted by Sree Evonsys on December 5, 2019
Hi, You can use below code it will switch to the tenant context From shared layer try{com.pega.pegarules.priv.context.PegaRequestor p=((com.pega.pegarules.priv.context.PegaRequestor)tools.getRequestor()); p.setTenantName(tenantId); LogContext.put("...
Hi, The below link might be helpful to understand the new feature in 8x. https://community1.pega.com/community/pega-support/question/new-application-rule-guardrail-warning Thanks, Geeda.
Aniket, I would recommend taking a look at the Pega Marketing User Guide and specifically at the Real-Time Containers chapter which will provide you the required details. You can find them here https://community.pega.com/knowledgebase/products...
Hi, There is no manual commit because this happen when User opened the work case from workbasket. If I use another flow action without ActionAutoSubmit, there is no error, but the work case stopped at the Perform Harness, this only happen in Pega 8.1....
Please wait while we search for PDN content that suits your question.