Reply posted on November 3, 2016 by raghu.raob
Hi All, I am facing the similar issue when using resume flow thru SLA, did you have any solution
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!
Kindly specify if the 'new final stage' that you added was a primary stage or an alternate stage ?
Hi Chris Koyl, We have used the below code for IAC gadget. <div id="EFormIACGadget" style="overflow: hidden;" pegagadget="EFormIACGadget" pegaresize="stretch" pegaa="OpenWorkByURL" pegaa_model="...
Whenever the flow action which is connected to the assignment shape in flow is successfully exicuted/submitted then Wor Item not be in the Current Assignment
I yet didn't see the way to avoid that message. I am also facing this issue now in my new app. Can anyone guide me how to stop that. I am using optimistic locking and don't have any SLA.
Wow, this stinks, because this would have been a half hour solution to the POC I was working on, instead I have to use columns or move the information elsewhere instead of providing the customer with an easy solution to get to the information they...
Sorry about that. From your initial post I was given to understand that you upgraded to 7.1.7 and thus I provided that link. With 7.1.8, there are no rule table triggers in the database. You should check what Kevin Zheng has suggested.
Please wait while we search for PDN content that suits your question.