Are there any OOTB Notifications for FSM that work. For some reason, in my instance it does not.
I can see there are 3 OOTB Notifications, an dI am interested in the First and the third.
Both of them are configured to send when: Event is fired.
But I do not see any entries for these events in my event log, although I have tried making changes to the WOTask and WO itself, like state changes, Work Notes changes etc.
I need to know what are the OOTB notifications that work for FSM.
 
 
 
 
oh sorry - i misunderstood your requirement, i thought you wanted the OOTB notifications for external customers and not internal.
//
to config notifications, yo go field service > admin > configuration, in the process tab
//
for wm_agent, you can config push otifications mobile - dont think they are any forthe browser.
go to system mobile > mobile push notifications
Push notifications on Mobile Agent,
//for dispatchers, it come from a lot of things,
- notifications such as flagged task, job started late, etc. are in the intraday flows
Intra-day schedule automation flows and subflows
- others pop up messages are configured in scripts, in some BR or script include
Code | Error Message | Conditions |
NO_GROUPS | No dispatch group or assignment group is defined | If both assignment_group and dispatch_group are not provided (i.e., they are nil), the method generates an error response with the message "No dispatch group or assignment group is defined". |
NO_ASSIGNMENT_GROUPS_COVERED
| The selected dispatch group does not cover any assignment groups | This message is used when the selected dispatch group does not cover any assignment groups |
NO_AGENT_AVAILABLE: | No Agent is available at specified time(s) | No agents in the selected group(s) have availability during the required time window. The agents' schedules do not match the task's required time frame. |
TOO_MANY_AGENTS: | There are too many agents covered by this dispatch group to dispatch the task. | when retrieving agents from a dispatch group or assignment group, the system will perform a query to fetch the relevant agents. If the number of agents exceeds the maximum allowed (100 by default work.management.max.agents.processed), this error message is triggered. |
UPSTREAM_DEPENDENCY | Cannot auto-dispatch because of upstream dependency. | This error message is used when a task cannot be automatically dispatched due to a dependency on another task or operation that hasn't been completed yet. |
INVALID_GOOGLE_KEY | Invalid Google Key. Please update the Google Key or turn off the functionality | when the Google API key, required for geolocation functionality, is missing or invalid. |
WINDOW_TOO_SMALL | The usable work window is too small for the task. | is generated when the available time window for a task is not large enough for its work duration. |
CONFLICTING_DEPENDENCIES | There are conflicting task dependencies for the specified time(s). | when the system detects that there are conflicting dependencies between tasks during the scheduling process. The start time for the task is earlier than the end time of any upstream task. The end time for the task is later than the start time of any downstream task. |
WINDOW_END_PAST | Window End is in the past | when the end time of a task’s scheduled window is in the past. |
NO_MATCHING_RULE | No task filter configured for this task | indicates that there is no matching rule configured in any scheduling method for the task. |
a
