Documentation

{{docApp.title}}

{{docApp.description}}

Connect an AI assistant

Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.

The catalog did not load. Refresh the page to try again.

Loading…

How can we help?

{{docApp.searchError}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

 {{docApp.currentResultsSearchText}}  in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown. Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
  • {{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}

    {{resultItem.url}}

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

Entity API / update

Operation Information

  • Application Reference: com.hornbill.servicemanager
  • Scope: Entity - Requests
  • Class: Entity
  • Required Privilege Level: guest
  • Required Rights: none

Description

Update the primary and extended fields of a request

Request Parameters

The update API takes the following input parameters.

Note

When sending a JSON request payload to the API, the order of parameters is not significant. However, for XML request payloads, parameters must be provided in the exact order specified in this documentation to comply with input validation requirements.

Name Type Required Description
requestId xs:string Yes ID of the request
h_summary xs:string No Summary of the request
h_description xs:string No Description of the request
h_category xs:string No Category of the request
h_category_id xs:int No Category ID
h_site xs:string No Name of the site
h_site_id xs:int No Site ID
h_external_ref_number xs:string No External reference number
customFields xs:string No A JSON representation of the custom fields for a request
resumeBpmProcess xs:boolean No This parameter determines whether the BPM process is resumed or not. By default, this option is disabled.

Response Parameters

Name Type Description
exceptionName xs:string This output parameter captures a code for errors that occured while updating the details section of a Request. The options are "exceededMaximumAllowableSize" and "failedToUpdateLockedDetails".
exceptionDescription xs:string This output parameter captures a description for errors that occured while updating the details section of a Request.

Request Parameters - Additional Information

customFields

The customFields input parameter enables the update of any of the custom fields against your request records.

The input is of type xs:string, but the API expects a string representation of a JSON object, with key-value pairs for each custom field needing updating, where they keys are the database field names and the values are in their native datatypes. The following example, when provided as a string to the customFields input parameter, would prompt the API to update the h_custom_a, h_custom_p, h_custom_21 and h_custom_26 fields angainst the target request:

{
  "h_custom_a": "A VARCHAR(255) string to be written into h_custom_a",
  "h_custom_p": "A LONGTEXT string to be written into h_custom_p",
  "h_custom_21": "2023-11-01 15:07:42",
  "h_custom_26": 42
}

Code Examples

In This Document