The CreatorCon Call for Content is officially open! Get started here.

Notification not firing if Active flag of user is inactive

matthew_hughes
Kilo Sage

I'm trying to create a notification when the active flag of the Architecture Lead (owner) is set to False

find_real_file.png

 

However, if I set the active flag of the Architecture Lead (owner) to inactive, the notification doesn't get triggered. I was just wondering if somebody could explain why the notification is not getting triggered and what I need to do.

1 ACCEPTED SOLUTION

matthew_hughes
Kilo Sage

I've now managed to fix this by created a Scheduled Script Execution and two events.

View solution in original post

4 REPLIES 4

Community Alums
Not applicable

Hi,

You can use a Scheduled job to trigger a Event which in turns triggers a Notification.

Refer to this Approach for your respective table :https://community.servicenow.com/community?id=community_question&sys_id=80c64768db3e2b009a64e15b8a96...

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

Aman Kumar S
Kilo Patron

I believe notification condition will be evaluated, once there is any insert or update on the table for which the notification is setup.

So lets say the user is set inactive and essentially a sys_user table record, and we expect the notification for other table will be triggered, I don't it works like that.

You can take the approach of creating a script on the user table rather, and check against if the user is owner, then create an event and trigger the event when it fulfils your use case

Best Regards
Aman Kumar

Ankur Bawiskar
Tera Patron
Tera Patron

Hi,

you have advanced condition as well.

Are you sure the advanced condition is evaluating to True?

To whom the email is sent?

Check for the details of the recipient

1) is that user active and not locked out

2) is that user having email populated

3) Is that user having notification preference enabled

Regards
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

matthew_hughes
Kilo Sage

I've now managed to fix this by created a Scheduled Script Execution and two events.