Reply posted on July 15, 2016 by AndrewWebster
Many thanks for the reply, Rajiv
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!
yes. ideally when application extended for implementation app express/DCO will create implementation specific work table.
Resolved the issue by putting below change on host webserver.--- > Header set X-Frame-Options "DENY" < Header set X-Frame-Options "SAMEORIGIN"
Not sure what caused this issues. But this was happening sporadically when repeating gird was used inside a repeating. After trying a lot we made use of custom fragment code for the nested grid. Don't know if this is the ideal solution. But it...
It turns out that the work object doesn't have pyResolvedTimeStamp value from the beginning due to the application bug. However, the exposed column pyResolvedTimeStamp was updated manually before running PurgeArchive tool, so the work object...
Please wait while we search for PDN content that suits your question.