Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Assinging Work Order Tasks "Across Schedule Entries"

mcconnellsj
Mega Sage

Hi

I am looking for experience of assigning field agents across multiple days.  We have enabled this plugin for FSM and having difficulty working out why we are getting the following error.

find_real_file.png

Note that the error DOES NOT appear if I uncheck "Assign Across Schedule Entries".

Taking this literally, this must mean that the agent's schedule does not cover this day and time.

However even if apply the 24/7 schedule to this agent, the error still appears, and even if the duration is only an hour or a minute (so not spanning any schedule entries anyway).

I have the following entry for the user in the "Work Schedule" table (agent_work_schedule).

find_real_file.png

Surely if the work schedule is 24/7 this error would not appear?

Obviously something else is causing the error and a review of the relevant script includes reveals a sphagetti of functions that is tricky to follow.

(Conversely on my developer instance, I have the opposite issue: I do not get the error if I assign something at 2am to a user with a 8-5 monday schedule, so I am missing something that isn't to do with the schedule itself I think)

Thanks in advance.

1 ACCEPTED SOLUTION

mcconnellsj
Mega Sage

This was a defect where if the system date format was set to anything other than default, the spanning failed.  It is fixed in Tokyo.

View solution in original post

9 REPLIES 9

Hi

Timezone for agent and schedule are both Europe/London.

It is okay to share instance details here?

Vasanth12
ServiceNow Employee
ServiceNow Employee

This is a defect. Please log a case.

For now fixed the issue in your instance. Please check.

Thanks can detail what the fix is?

Hi

I get the same error if an Assignee is selected for a work order task that is qualified.

Please have another look.

mcconnellsj
Mega Sage

This was a defect where if the system date format was set to anything other than default, the spanning failed.  It is fixed in Tokyo.