Add/update job_dispatch_log
Request Information
URI Parameters :
None.
Body Parameters :
job_dispatch_log| Name | Description | Type | Additional information |
|---|---|---|---|
| id |
Primary Key |
globally unique identifier | |
| jobs_id |
Job Id |
globally unique identifier | |
| user_id |
User Id |
globally unique identifier | |
| date_create |
Date+Time in UTC when the row has been created |
date | |
| date_proceeded |
Date+Time in UTC when the Dispatch goes to PLanned or Rejected |
date | |
| is_accepted |
Case the technician accept it. |
boolean | |
| is_rejected |
Case the technician reject it |
boolean | |
| rejected_reason |
In case the technician reject it, what is the reason |
string | |
| sys_logical_delete |
Boolean used to logically delete the record. This is to optimize the synchronization. sys_logical_delete doesn't need to be proceeded offline (record can be physically deleted offline) |
boolean | |
| is_workshop |
Using to distinguish between dispatch and workshop |
boolean | |
| modified_dateutc |
Readonly system field managed by database, filled with GetUtcDate when adding,updating |
date | |
| sequence |
sequence |
integer | |
| assigned_user_ids |
The list of user_id that assigned to the job, separate by commas. It's not a real column |
string |
Request Formats :
application/json, text/json
{
"id": "567c1c0c-91e3-4ca3-ac31-eb151e427f59",
"jobs_id": "5f1e9a72-a0e8-4276-9cd5-3b00416d5f59",
"user_id": "ab53b170-9ede-42f6-85e5-eac282e3ac0a",
"date_create": "2026-01-11T21:02:31.7932294+00:00",
"date_proceeded": "2026-01-11T21:02:31.7932294+00:00",
"is_accepted": true,
"is_rejected": true,
"rejected_reason": "sample string 8",
"sys_logical_delete": true,
"is_workshop": true,
"modified_dateutc": "2026-01-11T21:02:31.7932294+00:00",
"sequence": 12,
"assigned_user_ids": "sample string 13"
}
application/xml, text/xml
<job_dispatch_log xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <assigned_user_ids>sample string 13</assigned_user_ids> <date_create>2026-01-11T21:02:31.793Z</date_create> <date_proceeded>2026-01-11T21:02:31.793Z</date_proceeded> <id>567c1c0c-91e3-4ca3-ac31-eb151e427f59</id> <is_accepted>true</is_accepted> <is_rejected>true</is_rejected> <is_workshop>true</is_workshop> <jobs_id>5f1e9a72-a0e8-4276-9cd5-3b00416d5f59</jobs_id> <modified_dateutc>2026-01-11T21:02:31.793Z</modified_dateutc> <rejected_reason>sample string 8</rejected_reason> <sequence>12</sequence> <sys_logical_delete>true</sys_logical_delete> <user_id>ab53b170-9ede-42f6-85e5-eac282e3ac0a</user_id> </job_dispatch_log>
Response Information
Resource Description :
job_dispatch_log| Name | Description | Type | Additional information |
|---|---|---|---|
| id |
Primary Key |
globally unique identifier | |
| jobs_id |
Job Id |
globally unique identifier | |
| user_id |
User Id |
globally unique identifier | |
| date_create |
Date+Time in UTC when the row has been created |
date | |
| date_proceeded |
Date+Time in UTC when the Dispatch goes to PLanned or Rejected |
date | |
| is_accepted |
Case the technician accept it. |
boolean | |
| is_rejected |
Case the technician reject it |
boolean | |
| rejected_reason |
In case the technician reject it, what is the reason |
string | |
| sys_logical_delete |
Boolean used to logically delete the record. This is to optimize the synchronization. sys_logical_delete doesn't need to be proceeded offline (record can be physically deleted offline) |
boolean | |
| is_workshop |
Using to distinguish between dispatch and workshop |
boolean | |
| modified_dateutc |
Readonly system field managed by database, filled with GetUtcDate when adding,updating |
date | |
| sequence |
sequence |
integer | |
| assigned_user_ids |
The list of user_id that assigned to the job, separate by commas. It's not a real column |
string |
Response Formats
application/json, text/json
{
"id": "9c9a9df6-6e4d-4ec1-801f-f04847d76f21",
"jobs_id": "3a3f6f8a-a84d-4ed8-ab7f-560bbe4362b6",
"user_id": "4b5fa680-7b78-4ca4-b71a-1be31b3e65d1",
"date_create": "2026-01-11T21:02:31.7932294+00:00",
"date_proceeded": "2026-01-11T21:02:31.7932294+00:00",
"is_accepted": true,
"is_rejected": true,
"rejected_reason": "sample string 8",
"sys_logical_delete": true,
"is_workshop": true,
"modified_dateutc": "2026-01-11T21:02:31.7932294+00:00",
"sequence": 12,
"assigned_user_ids": "sample string 13"
}
application/xml, text/xml
<job_dispatch_log xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <assigned_user_ids>sample string 13</assigned_user_ids> <date_create>2026-01-11T21:02:31.793Z</date_create> <date_proceeded>2026-01-11T21:02:31.793Z</date_proceeded> <id>9c9a9df6-6e4d-4ec1-801f-f04847d76f21</id> <is_accepted>true</is_accepted> <is_rejected>true</is_rejected> <is_workshop>true</is_workshop> <jobs_id>3a3f6f8a-a84d-4ed8-ab7f-560bbe4362b6</jobs_id> <modified_dateutc>2026-01-11T21:02:31.793Z</modified_dateutc> <rejected_reason>sample string 8</rejected_reason> <sequence>12</sequence> <sys_logical_delete>true</sys_logical_delete> <user_id>4b5fa680-7b78-4ca4-b71a-1be31b3e65d1</user_id> </job_dispatch_log>