Reply posted on August 12, 2019 by PANP0001
Thank you it worked!
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!
This feature is not supported. For more details please refer to https://community.pega.com/knowledgebase/apache-cassandra-database-support
We are facing a similar situation. Can anyone please chime in if they disabled the compression and the resulting performance impact. Thanks in advance.
Hello Kevin, Thank to your response it's now working. For people that want to know how to get those information, there are two way: 1/ go to the change stage view with Live UI and find the fields used. 2/ use API to get the fields: Method: PUT...
Thank you for you really complete answer. Now I understand why a property should be optimized or not.
Thank you, that is exactly what I was looking for. I have implemented this as described with a single Committed-Save and Commited-Delete at the Parent level, and it is triggering for it's children. I was able to place the logic in these triggers...
So this is how it's done easily. I've used two when rules already attached with the comment. it compares the two pages by the parameter count(where count is incremented by 1 every time) for comparing side by side and then for the last when...
I can see the class there in prpublic.jar (you can extract it from pegadbinstall-classes.zip).
Please wait while we search for PDN content that suits your question.