- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I am trying to track down the "Save" button shown in the attach image.
Issue: When an Agent clicks "Save", the incident is being assigned to the agent automatically, even though the Agent is not part of the assigment group. Due to the assignment, the notifications are not going to the assignemnt group.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Nevermind, I found the UI Action. However, the issue is with BR: Set assignment from Interaction. The business rule is assigning the incident to the current user (aka the Agent).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
are only noticing this issue in workspace or classic UI have same behavior ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
You can check whether there's a Business Rule or Flow (in the Flow Designer) that's automatically assigning the incident to a specific user upon saving.
It's also worth checking that the "Save" button's UI Action doesn't have any custom logic (script) forcing the Assigned to field to be assigned.
This type of behavior usually stems from one of these customizations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Nevermind, I found the UI Action. However, the issue is with BR: Set assignment from Interaction. The business rule is assigning the incident to the current user (aka the Agent).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Ok, if you need support we are here for that, if my answer was in any way helpful I just ask that you rate it, thank you!
