"appointment_status": "mappingStatus(fields.SVMXC__Order_Status__c, null, [[\"StatusOne\":\"Closed\",\"StatusTwo\":null, \"MappedStatus\":\"Demo\"], [\"StatusOne\": \"Completed\",\"StatusTwo\":null, \"MappedStatus\":\"Finished\"]])"

{
"svmx_appointment" : {
"null,Pending" : "Open",
"Pending,Accept" : "Open",
"Pending,Canceled" : "Open",
"Pending,Rejected" : "Open",
"Accepted,En Route" : "Open",
"Accepted,Rejected" : "Open",
"Accepted,Canceled" : "Open",
"En Route,Onsite" : "Open",
"En Route,Incomplete" : "Closed",
"En Route,Canceled" : "Canceled",
"Onsite,Finished" : "Completed",
"Onsite,Incomplete" : "Closed",
"Onsite,Canceled" : "Canceled"
}, "svmx_job" : {
"null,Canceled" : "Canceled"
}
}

|
|
Typically, the Order Status field is updated based on status changes in Appointment records. For Jobs without scheduled Appointments, Service Board uses the default status mappings between Jobs and Order Status values defined in the svmx_job section. For example, when Jobs that are not yet dispatched are canceled, Service Board uses these mappings.
|