To stop email notification for "Requested for" field when offboarding catalog form is submitted

[Adetunji Olayem]

How can I prevent email notifications from being sent to the Requested For field when the catalog item is the offboarding form? I want this change to apply only to the offboarding catalog item and not affect any other catalog items.

The notification in question is the “Request Was Opened” notification, which is currently used for all requests. I’ve already tried adding an advanced condition using the sys_id, but after checking the email logs, notifications are still being sent to both the Requested For and Opened By users.

Could someone help me figure out how to meet this requirement? Thanks.

[MaryG]

The reason the advanced condition isn't fully solving this: it controls whether the notification fires at all, not which recipients receive it when it does. So if the condition passes, both Requested For and Opened By still get the email.

To suppress a specific recipient for a specific catalog item, you need to work at the recipient level, not the condition level. Two clean options:

**Option 1: Recipient Script (recommended)**
In the "Request Was Opened" notification, go to the Who Will Receive tab and add a Recipient Script alongside the existing recipients. The script can check whether the triggering request includes the offboarding catalog item and conditionally return the Requested For user only when it's not offboarding:

var items = current.items();
while (items.next()) {
if (items.cat_item == 'YOUR_OFFBOARDING_CATITEM_SYSID') {
return; // suppress Requested For for offboarding
}
}
answer = current.requested_for;

Then remove the standard Requested For recipient entry and replace it with this script. Everything else continues working as before.

**Option 2: Clone the notification**
Duplicate "Request Was Opened" into two versions:
- Original: add advanced condition excluding the offboarding item sys_id, keep all recipients
- Clone: advanced condition matching only the offboarding item, remove Requested For from recipients

This is more transparent and easier to hand off to someone else, but means two notifications to maintain going forward.

Option 1 is cleaner if you're comfortable with recipient scripts. Option 2 is easier to troubleshoot if your team is less familiar with scripted notifications.

What does your current advanced condition look like? That'll help confirm whether the notification is even scoped to the RITM level or the request level.

[Adetunji Olayem]

Thanks, I have one question, under who will received, opened by and requested for is selected. Should I keep the same way and just update the script.

[MaryG]

Yes, but with one adjustment. Keep Opened By as-is. For Requested For, remove the standard entry and replace it with the recipient script instead — otherwise both the standard recipient and the script will run and Requested For will still get the email.

So your Who Will Receive tab should end up with:
- Opened By (standard, unchanged)
- Your recipient script (replacing the standard Requested For entry)

The script handles the logic of whether to include Requested For based on the catalog item, so you only need it in one place.