Jar to save criteria in Junk Notification Filter (Admin->Notification Rules)

Jar to save criteria in Junk Notification Filter (Admin->Notification Rules)

Problem:

      Unable to save criteria in Junk Notification Filter ( Admin -> Notification Rules )

Jar is For?

      The attached fix fjar is to save criteria in Junk Notification Filter.

Applicable SDP version :

      10502

                  New to ADSelfService Plus?

                    • Related Articles

                    • Unable to Save Junk Notification Filter

                      Issue: Unable to save the Junk Notification Filter due to the CSRF parameter being passed twice in the payload. A 400 error occurs when attempting to save the configuration. The issue will occur only from 14820. Issue ID : SD-123127 Screenshot: Error ...
                    • Technician notification based on the site

                      This KB will help you to get the notification about based on the site to a technician. Please follow the below instructions. Please navigate to Admin >> Request timer action >> Add new timer action. Please configure the below in the application. ...
                    • Restricting Account Specific Notifications for Certain Requesters

                      Steps are not application in latest builds due to behavior change. In some rare cases where you would like to be able to close a Request without notifying the customer, please follow the below mentioned: 1. Go to Admin > Notification Rules > Choose ...
                    • Notification script using Custom function in custom trigger

                      This is applicable from 10600 builds. From 10600 , Business rules dont have Email notification feature. The same use case be achieved through Custom triggers feature as mentioned below. Script to enable notification of request creation using custom ...
                    • #8888147 - Debug jar for the customer

                      Issue: Junk Notification Filter isn't loading in the product. On viewing from the logs, there is an issue with query construction in the backend. Debug: To analyse this further, we have prepared a debug jar to get additional prints in the serverout ...