Editing Optima - API

'''HoursAssimentShort'''

https call with periode and assignment number (tjenestenummer):
https://ais.allocate-cloud.de/api/workforce/1.51/HoursAssignmentShort?$filter=CancelFlag+eq+%27No%27and+ValidDate+ge+DateTime%272024-03-07T00:00%27+and+ValidDate+lt+DateTime%272024-03-11T00:00%27+and+(AssignmentNumber+eq+%2701303%27)

Old AWS endpoint: https://ais.allocate-cloud.de/api/workforce/1.4/HoursAssignmentShort

New AWS endpoint: [Https://ais.allocate-cloud.de/api/workforce/1.51/HoursAssignmentShort https://ais.allocate-cloud.de/api/workforce/1.51/HoursAssignmentShort]

Redcentric endpoint: https://pas.allocate-cloud.com/AIS/PROD/api/workforce/1.4/HoursAssignmentShort

If I use the HoursAssignmentShort API with a filter to only show recent duties for that assignment number eg
https://ais.allocate-cloud.de/api/workforce/1.51/HoursAssignmentShort?$filter=ValidDate ge datetime'2024-03-18' and ValidDate le datetime'2024-03-22' and AssignmentNumber eq '46991' 
 
then the duties on 18th, 21st and 22nd are returned by that API filter (see attached JSON results from the API),. You should also be able to verify this with your AIS.SD.ESBJERGLIVE login
 
When the API is invoked without filters, it will return all bookings going forward from the date 12 months back from the start of the current month. As these 3 duties were all booked by the auto-roster functions on 06-Oct-2023, they will have been showing in the API since then

The CancelFlag "No" Lines are duties that are booked to be worked.

The CancelFlag "Yes" Lines are duties that were booked to be worked but were then subsequently cancelled.

ShiftType: Responsibility with Shift Name: