Lumpy Nguyen

Concern:

When dispatcher creates a booking in Daily view, if the resource already had a booking, the booking is split into 2 bookings which requires dispatcher to update the booking (by right click the booking > Edit > edit the time). Initially when dispatcher creates a booking in Daily view, there is no option to set the time of the booking and the booking will be created with start time = resource’s start time, which leads to the scenario.

The goal is to prevent multiple bookings from being created for a single work order when customer's scheduler drags and drops it on the schedule board. 

Issue Details:

 Duplicate booking records are generated for a Work Order, all having the same "Created On" date, whenever the Scheduler drags and drops the Work Order on the schedule board as per screenshot below.

Concern:

When dispatcher creates a booking in Daily view, if the resource already had a booking, the booking is split into 2 bookings which requires dispatcher to update the booking (by right click the booking > Edit > edit the time). Initially when dispatcher creates a booking in Daily view, there is no option to set the time of the booking and the booking will be created with start time = resource’s start time, which leads to the scenario.

The goal is to prevent multiple bookings from being created for a single work order when customer's scheduler drags and drops it on the schedule board. 

Issue Details:

Duplicate booking records are generated for a Work Order, all having the same "Created On" date, whenever the Scheduler drags and drops the Work Order on the schedule board.

In the macros action step "Open a new form to create a record", we want to know about the slug/ parameter to get the agent Id who is current user Id. We need the agentId or userId to run query to retrieve fields from SystemUser entity.

I have tried using the session context variable anchor.agentid or anchor.userId , unfortunately it does not work.

This script to create an Account during a Whatsapp conversation.

We have checked in the development tool (F12) with this command: Microsoft. Apm. getFocusedSession. getContext but no session variable agentid there.

Microsoft Product team confirmed anchor.agentid doesn’t exist and it’s not documented, so it won’t work.

They only have anchor. parameters for the parameters that exist in the entity (for entity sessions) or from the parameters created by the provider.

So, I am filing a feature request in Ideas portal as MS suggests.