ForceFixJob RESTified API
Pass Through Call to Scheduling's "DVForceFixJobRequest" API
This RESTified API will perform a pass-through call to the Scheduling sub-system's "DVForceFixJobRequest" API (when configured).
URL
PUT /up/v5/rest/scheduling/ForceFixJob
HTTP Request Body
This request requires a JSON object supplied in the HTTP request body, which defines the parameters that will be passed through to the Scheduling "DVForceFixJobRequest" API.
ForceFixJob Object Format
ForceFixJob Object Properties (Bold property names indicate the field is required)
Property | Type | Length | Description | Req? | Field Mapping: | |||||
---|---|---|---|---|---|---|---|---|---|---|
Id | string SS: JobID | SS: 50 | The caller’s identifier of the job to be booked. The error | Yes | jobID | |||||
Tech | string SS: EmpID | SS: 25 | Is the caller’s identifier of the employee who is to do the job. The function will error (returning SP_EMPID_INVALID (5)) if EmpID does not exist in the ServicePower database. | Yes | empID | |||||
SchdStart | string SS: spDateTime (string) | SS: 16 | Is the time at which the employee will start travelling to the job. The function will error if StartDateTime breaks any of the hard constraints required by JobID, unless appropriate ForceOptions are used. Various soft constraints may also cause error – again appropriate ForceOptions can overcome these. Example: "2023-03-30T14:15" | Yes | expectedStart | |||||
Options | object | A set of options which specify which constraints normally applied when moving jobs should be ignored for this fn. | No |
HTTP Response
Success
On success, a JSON-formatted version of the Scheduling "DVForceFixJobRequest" API response will be returned.
{ "Success": true, "Code": 0, "Message": "OK", "Payload": { "result": { "type": "OK", "code": "0" } } }
Error
On error, a JSON-formatted version of the Scheduling "DVForceFixJobRequest" API response will be returned.
{ "Success": false, "Code": 9, "Payload": { "returnCode": { "type": "Error", "code": "SCH Error Code" } } }
Return Codes
In addition to the Standard Return Codes, and the Scheduling API return codes, the possible Return Codes from this API are: