Reply posted on December 12, 2019 by HasnaaBimezzagh
Hello, I have the same issue. Did you find a solution?? Best regards; Hasnaa
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 Anthony Tham for achieving the title of Participant of the Week! Anthony proactively assisted several users with their queries, which helped them progress with the troubleshooting and arrive at successful solutions. We appreciate your efforts to share knowledge in the community. Hope to see you around and keep up the great work!
Hello, I would recommend you to change your locking mechanism for optimistic locking. What Pega version are you running?
Hi @AnthonyTham, Thanks for sharing the details. I could see all the values are empty (0 days) for pyEffortEstimate & pyEffortActual properties. Could you please guide me to find where/how exactly those property values are getting updated.
When you click on the previous button, try tracing the events. Check whether is there any errors in the tracer or in the logs. Also, if you are using custom harness, try using OOTB TabbedScreenFlow7 harness to verify the behaviour.
Hello Arvind, Can you confirm if you implemented all the steps of the upgrade guide which are under the section named: " Upgrading from Pega 7.1.6 and earlier:Configuring the default search nodes and storagedirectory " (Page 73)? Here's...
The above message gets triggered for edit validate rules. The message being displayed comes from a message rule 'PropertyInfo-EditValidate'. You can override this one in application ruleset and modify the message by removing the second part. ...
Please wait while we search for PDN content that suits your question.