Automatic removal of notifications when situation solved

[azappi]

Hi

I have a question regarding the automatic closing of a notification. From what I understand, you can get the system to automatically delete the notification when the situation is resolved.

My scenario is that I have created my own Situation type, where I check whether the purchase order has been updated with the relevant confirmations. However, I have not yet managed to get the system to remove the notification that was created in the first place, even though I have updated my purchase order.
This means that my selection is: if the confirmation control category is blank, I need to send a notification, and when the field is filled in, the notification should be removed.
But unfortunately, nothing happens, and I think it is because the selection criteria are no longer met.

Or?

[axel_spriestersbach]

Hi, 
this not correct: (Fiori) Notifications are never removed when a Situation Instance gets delete or resolved. 
They are much like an eMail where the user controls the lifecycle not the system. 

Situation Instances can be removed, but their lifecycle is decoupled from the Notification lifecycle for 
the reason above.

 - Axel 

[azappi]

Hi Alex

Thanks for your feedback, maybe I should have been a little bit more precise 

E.g. in the standard scenario proc_pendingsupplierconf_v2, I can set the status as obsolete, when the situation has been solved 

I want to do the exact same, eg. with status Resolved

I have set it up with my situation object and event changed, then I added the Remove (Trigger data available) and Remove (Trigger data not available)to my Situation Scenario I tried both. 

Then I used the supplier confirmation category as selection, however the status are not set to resolved 

maybe you have any idea why?