Looking at getting Appointment Bookings during some other testing and noticed that a slot was offered when I wasn’t expecting it.

I have then gone to test in isolation and noticed the following.

Resource 127 will be the only person able to do this job. There is a private activity ending at 15:30 on 5th June.

I have 2 tasks being sent to ABE with an activity group as follows

  <Activity_Group>
    <activity_id1>5961328</activity_id1>
    <activity_id2>5961327</activity_id2>
    <pre_co_req>PRE</pre_co_req>
    <min_delay>PT0S</min_delay>
    <same_resource>true</same_resource>
    <split_allowed>false</split_allowed>
    <all_or_nothing>true</all_or_nothing>
  </Activity_Group>

The time left at the end of the shift is 90 mins.

Activity Id 2 is 80 mins and 1 is 45 mins.

ABE gave the following on the Appointment Output.

    <prospective_resource_id>127</prospective_resource_id>
    <prospective_allocation_start>2023-06-05T15:30:01+01:00</prospective_allocation_start>

Once DSE looks to allocate, it can’t.

Therefore just wondering if this is either expected behaviour, a known bug and now fixed, or something that is occurring due to the inputs we’re passing to ABE.

Regards

Ady

Hi,

I don’t think this is a known bug so it would be best to raise a case for this.

Thanks,

Sam

@sarugb Hi, thanks for the reply.

Not sure why, but remember raising this topic and having issues posting it. There should be some screenshots to accompany the description above.

However, i’m currently speaking to a PSO Consultant reference this as part of the project we have in place.

But thanks again for the comment.

Ady