The server encountered an unexpected condition

Hi 

First time using openVpms.

Im trying to implement this API for a customer: 
https://openvpms.org/developers-handbook/online-booking-api/v1

 

I can get locations, appointment types and schedules with no issue. 

But I cant submit a booking:

Heres the body I send (the start/end times are free): 

{
  "location": 35,
  "schedule": 53,
  "appointmentType": 55,
  "start": "2020-09-28T13:00:00.000+02:00",
  "end": "2020-09-28T14:00:00.000+02:00",
  "firstName": "Judith",
  "lastName": "Bourke"
}

 

I know I can hit the endpoint - because if I change the location or remove firstName I get the following response: 

"Schedule is not available at location 352", "'firstName' is a required field" ect..

 

If I however send the body like the one listed above I get the following error:

HTTP Status 500 – Internal Server Error

Type Status Report

Message Request failed.

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Apache Tomcat/7.0.92

 

Has anyone else had this issue? 

Could it be because the user I have dont have premission to submit booking ?

I assume the locations, appointment types, free/busy times is set up right since I can get data in my requests.

"for an appointment type to be returned, its Online Booking flag must be ticked."

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: The server encountered an unexpected condition

Do you see any stack traces in the server logs?

Re: The server encountered an unexpected condition

Thansk for the reply

I currently dont have access to the server.

Im contacting the customer for access and will return when I have more

Re: The server encountered an unexpected condition

The error is unlikely to be in the OpenVPMS logs, but you might be lucky.
They are accessible via the UI under Administration - System. Click the Diagnostics button and go to the Logs tab.

If you can't see the error here, you'll need to look in the various log files that Tomcat produces. These are located in the Tomcat installation, in the logs directory.

Syndicate content