how filter is set as unsubscribe in cmn_notif_message table

[tiasha1231]

need to know how filter is set as unsubscribe in cmn_notif_message table that's causing notifications to NOT go out for end users. I have pasted the screenshot. I want to understand how its happening ? 

[k_lutz]

Hi @tiasha1231 

In our system there is only one business rule that sets it on create and that looks to be an OOTB one "Default to Unsubscribe". It does not look like it would apply to your table. The only two other ways I can think of is if someone had changed the default value to unsubscribe or the user did it. I am not seeing something in ours that does it. If you manually create an entry from the list what is the value when you save it?

[tiasha1231]

Hi @k_lutz ,

When manually created , the value is empty. There are two choices to select the value while manually creating (Critical issues and Unsubscribe), if I don't select any value then its empty upon creation.

Also, the OOTB Business rule: "Default to Unsubscribe" is not present in our system.

[k_lutz]

The place I am finding logic triggered that can set that is from an inbound action called "Unsubscribe from Notification". That can set it to unsubscibe unless there is custom logic somewhere in your system that is doing it.

[tiasha1231]

Hi @k_lutz ,

Thank you for your response!

The inbound action is present for our system as well. Additionally, one new observation is when activating/deactivating the notification from notification preferences from user profile, the record is getting created/removed respectively in the cmn_notif_message table. So, the issue is reproducible.