Reply posted on October 27, 2009 by JonnyGar
see this thread.
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 Al Wells from Monster Pixel on being this week's Participant of the Week! Last week Al posted a few questions and not only did he find the answers, he updated the thread as such to help others in the PSC! Congrats again!
Above link is obsolete now. The V55 version of this document (covers ALL versions) is at: http://pdn.pega.com/DevNet/PRPCv4/TechnologyPapers/documents/ConfigSettingsReference0505_lck.pdf
This is not a weird thing, this is expected behavior, if you are using Harness in your flow, all your entry (input) sections should be referenced inside your Flow Action, anything outside Flow Action will be in read-only mode and will be editable only...
hi, This link will be useful to you for solving the issue http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=DB520&uid=swg21249897&loc=en_US&cs=UTF-8&lang=en&rss=ct180websphere the Java class files will get...
I am also facing problem few fields (pxRefObjectInsName and pyTimeLimitUrgency) are not sorting because of pega overriding default sort function.Can any body know how to resolve issue?
Please wait while we search for PDN content that suits your question.