/mcp<ApiErrors> <ApiError> <ErrorType>Invalid Input</ErrorType> <ErrorMessage>layoutxml</ErrorMessage> </ApiError> </ApiErrors> Example Failure Response: LayoutConfig API Parameters Notes Possible Values Description Type Parameter — The URI to get a new copy of the LayoutConfig object. String uri Must be valid XML and must conform to the Finesse schema. — The XML data that determines the layout of the Finesse desktop. String layoutxml LayoutConfig API Errors Description Error Type Status The submitted XML is invalid or does not conform to the Finesse schema. Invalid Input 400 The layout XML file was not provided. Parameter Missing 400 Unauthorized (for example, the user is not yet authenticated in the Web Session). The user is not authorized to use the API (the user is not an administrator). Authorization Failure 401 The user attempted to run the API against the secondary Finesse server. Configuration APIs cannot be run against the secondary Finesse server. Forbidden 403 Any runtime exception is caught and responded with this error. Internal Server Error 500 ReasonCode The ReasonCode object represents a reason code that can be applied when an agent changes state. There are two categories of reason codes: not ready reason codes and sign out reason codes. Administrators can use either the ReasonCode APIs or the Finesse administration console to configure not ready and sign out reason codes. When using the APIs to configure reason codes, the administrator specifies the category of reason code in the request (NOT_READY or LOGOUT). Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 236 Cisco Finesse Configuration APIs LayoutConfig API Parameters