Appointments PUT Confirm (add value)
Posted: Tue Nov 14, 2023 1:31 pm
Request: Please add "Reschedule" as a value for "confirmVal" as we would pr3fer to utilize "confirmVal" instead of defnum
Please let us know if approved and timeline.
thanks
Appointments PUT Confirm
Version Added: 21.1
Only one field is allowed in the JSON object, either confirmVal or defNum. A confirmVal of "None" corresponds to the default status for all new appointments, which is based on the first item listed in Definitions, Appt Confirmed. The other four confirmVal options are managed by the office in eServices Setup, Automated Messaging. Use the defNum field to set the status to any ApptConfirmed type.
confirmVal: Either "None", "Sent", "Confirmed", "Not Accepted", or "Failed".
defNum: (Added in version 21.2) Definition.DefNum where definition.Category=2.
Example Requests:
PUT /appointments/34/Confirm
{
"confirmVal":"Confirmed"
}
{
"defNum":209
}
Please let us know if approved and timeline.
thanks
Appointments PUT Confirm
Version Added: 21.1
Only one field is allowed in the JSON object, either confirmVal or defNum. A confirmVal of "None" corresponds to the default status for all new appointments, which is based on the first item listed in Definitions, Appt Confirmed. The other four confirmVal options are managed by the office in eServices Setup, Automated Messaging. Use the defNum field to set the status to any ApptConfirmed type.
confirmVal: Either "None", "Sent", "Confirmed", "Not Accepted", or "Failed".
defNum: (Added in version 21.2) Definition.DefNum where definition.Category=2.
Example Requests:
PUT /appointments/34/Confirm
{
"confirmVal":"Confirmed"
}
{
"defNum":209
}