Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Custom defaulted Pega Pulse filter is not running on screen load

SA-27992

Summary



User built a new custom Pega Pulse Filter as per the steps in this article : https://pdn.pega.com/configure-and-customize-pega-pulse

The first entry in the data transform appears as the default value in the user interface, but if user sets their custom filter as the default, it does not load pulse messages when the screen is loaded.

After changing the filter to standard and then to custom filter in that case custom filters are displayed.


Error Messages



Not applicable


Steps to Reproduce



1. Specialize @baseclass.pyFilterOptions on the Work level. This will ensure new custom filters will only show up in Case Context.
2. Add a new filter "Realted Cases" as the first entry of the Data transform.
3. Write logic in PegaSocial-Message.pyCustomFilterHandler to support the new filter.
4. Create a case and add some Pega pulse messages.
5. Close case and reopen, no messages is displayed (Note the default filter is the custom "Realted Cases" fitler).
6. Change filter to one of the standard filters, example, "All Posts". Note that data is being displayed.
7. Change filter to the custom filter "Realted Cases". Note that data is now being displayed.


Root Cause



Customizing the pyCustomFilterHandler caused issues due to pyWorkPage being referenced in the custom logic is missing when the activity runs.

Resolution


 

Perform the local change in the pyCustomFilterHandler, and also include the pyWorkPage in the Pages & Classes tab:




 

Published September 21, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us