...
Returns a JSON object representing the new order. This will match the structure returned by Fetch a Single Order, though some fields will be empty until the order undergoes further processing. The HTTP status is 202 (Accepted) as the order will not be available in Rx-Universe until the Remote Order Processor has processed the request. The string array creationRemarks
will also be returned which may include any additional (non-error) information messages.
Error
If one or more parameters have invalid values based on their max/min/character count descriptions, an HTTP 400 code will be returned with an error body describing the issues
...
At least one of rtLensStyle/ltLensStyle and rtLensMaterial/ltLensMaterial must be provided, or else an HTTP 400 code will be returned with an error
Code Block language json { "error": "Incorrect arguments provided", "details": [ "rtLensStyle, ltLensStyle are missing, at least one parameter must be provided", "rtLensMaterial, ltLensMaterial are missing, at least one parameter must be provided" ] }
If a crib has been set and the job is not an uncut job (jobType = U) an HTTP 400 code will be returned with an error
Code Block language json { "error": "crib is only valid on uncut jobs", "details": [ "Job Type: F", "Frame SW:" ] }
If ellh has been set and the job is not an uncut job (jobType = U) an HTTP 400 code will be returned with an error
Code Block language json { "error": "ellh is only valid on uncut jobs", "details": [ "Job Type: F", "Frame SW:" ] }
If the customer number does not exist in Rx-Universe an HTTP 400 code will be returned with an error
Code Block language json { "error": "Customer does not exist", "details": [ "Provided: 9999" ] }
If the Frame Inventory module is in use, required for the order (the order is set to supply frame), and offline an HTTP 500 code will be returned with an error
Code Block language json { "error": "Frame Inventory Module is offline", "details": [] }
If the job type is addon and no addons are entered an HTTP 400 code will be returned with an error
Code Block language json { "error": "No addons entered", "details": [] }
If the job fails calculation validation an HTTP 400 code will be returned with an error
Code Block language json { "error": "Validation Failed", "details": [ "ERROR 112: SPHERE MUST BE BETWEEN -39.0 AND +49.0" ] }
If the entered PO is already in use for another order for the same customer an HTTP 400 code will be returned with an error
Code Block { "error": "Duplicate order", "details": [ "Duplicate of 10071993", "PO Number: dup is already in use for customer 1" ] }
If the job has trace data attached (one or more of the following are set to a value) then an array of validation failures may be raised
Trace parameters:
rtTraceFmt
ltTraceFmt
rtTraceZFmt
ltTraceZFmt
rtTracePoints
ltTracePoints
rtTraceZPoints
ltTraceZPoints
Trace points are submitted without a valid format declaration (e.g.
"rtTracePoints": [1,2,3,...], "rtTraceFmt: ""
)Code Block language json { "error": "Cannot process order - trace error", "details": [ "Received rtTracePoints without rtTraceFmt", "Received ltTracePoints without ltTraceFmt", "Received rtTraceZPoints without rtTraceZFmt", "Received ltTraceZPoints without ltTraceZFmt" ] }
The number of trace points does not match the number declared in the format declaration (e.g.
"rtTracePoints": [1,2,3], "rtTraceFmt: "1;4;E;R")
Code Block language json { "error": "Cannot process order - trace error", "details": [ "Number of RADII points sent does not match the TRCFMT entry for the right eye", "Number of RADII points sent does not match the TRCFMT entry for the left eye", "Number of Z points sent does not match the ZFMT entry for the right eye", "Number of Z points sent does not match the ZFMT entry for the left eye" ] }
Z points are submitted without the corresponding radii points
Code Block language json { "error": "Cannot process order - trace error", "details": [ "Right Z points with no right RADII points", "Left Z points with no left RADII points" ] }