- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 07:25 AM
We have a simple notification on a custom case table (caste type) to send to the consumer user when a new case record is inserted. It works correctly when the case is created by an agent, but not when the consumer user themselves submits the case (via a record producer in the customer service portal). We want them to be able to receive the email for their own cases no matter who created it.
Is this an ACL issue or is something else at play? If ACL, what do you recommend?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2025 02:05 PM
Turns out @Hemant Ch was in the correct zone.
First, we were operating under incorrect information -- the notification wasn't sending to the submitter for either internal or external users. We were focused on external and additionally the ACLs turned out to not be the problem.
What we needed to do is check the box for "Send to Event Creator" in "Who will Receive".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2025 07:00 AM
I believe this ACL which was already in place should provide read access to that field (and the rest) on dining cases:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2025 07:11 AM
try with that and see if it works
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2025 07:31 AM
I don't understand your last post. Try with what? The ACL was already there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2025 02:05 PM
Turns out @Hemant Ch was in the correct zone.
First, we were operating under incorrect information -- the notification wasn't sending to the submitter for either internal or external users. We were focused on external and additionally the ACLs turned out to not be the problem.
What we needed to do is check the box for "Send to Event Creator" in "Who will Receive".