Reply posted on December 5, 2019 by GiovaniPega
Hi Jaikumar, Were you able to fix this issue? I'm facing the same problem.
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!
Why don't you want to skim your ruleset? Generally, it's a safe operation and not very time consuming. Anyway, in case of oooold legacy system, I can imagine that something may go wrong with skimmed ruleset. So you can try to skim it and if...
Hi Rett, The issue got resolved with local changes mentioned below though Pega Engineer created a FDBK request(FDBK-64336) for this. An email was sent to you on this as well. Current application behavior: TabbedScreenFlow7 (Harness) => Header ...
Thank you for sharing the solution. It helps fellow community users who would come across the same query.
Hi All, After raising SR we came to know that it is the 'Pega Express App' (downloaded from play store) issue. The app has limited functionality support and it was recommended to build our own custom app for iOS and Andriod.
Hello, the dropdown is populated using the report definition pxGetRulesByRecordTypeAndClassName with Declare_CAApplicationSettings.PreChatClass as the class name. This basically gets all the Flow rules that are in the class defined by the property...
While you don't need to worry about the Apple ID login requirement you still need to upgrade to Pega Infinity. Otherwise you'll not be able to publish any update to your app store application after March 2020.
Please wait while we search for PDN content that suits your question.