- Views (25)
- Replies (3)
- Login to like
- Reply
Reply posted on December 6, 2019 by RaviY230
Hi AnthonyTham, It's working perfectly as expecting. Thank you very much
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!
Hi AnthonyTham, It's working perfectly as expecting. Thank you very much
Hi, I am not able to pass values dynamically while running the test case. Not allowing me to pass parameter values. For example, there is an email field, I got otp to my inbox. Now I need to enter OTP in the enter OTP field. Please help me with this
Hi Abhinav In my very first post I included an extract from that log file. I'm attaching a copy of the latest log file. Regards, Johan
Hi Sundeep, The Activity Step was already set as Route, the Warning is coming because the activity have only property-set step the warning will come even if its acitivty type changed.
Can you try to call 'pxCreateAssociation'? That's what is being used to associate two cases. You can create a link association between two cases using the activity @baseclass.pxCreateAssociation, this activity creates a link association...
This link should work.
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.
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....
AccessGroup.pyPortal contains the name of a portal, not the name of access group. Accessgroup name is in AccessGroup.pyAccessGroup property.
Please wait while we search for PDN content that suits your question.