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 / resolveRequest

Operation Information

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

Description

This operation resolves a Request.

Request Parameters

The resolveRequest 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 This parameter must contain Id of a Request.
resolutionText xs:string Yes This parameter must contain the resolution text for a Request.
resolutionLanguage xs:string No This parameter contains the resolution language of a Request.
closureCategoryId xs:string No This parameter can contain Id of a Closure Category.
closureCategoryName xs:string No This parameter can contain the display name of a Closure Category. You no longer need to supply this param.
updateTimelineInputs xs:string No This parameter can contain the options that will be used to post an update in the Timeline. This must be supplied as a JSON Object in form of a String. Properties includeactivityType, updateText, source, postType and visibility.

Response Parameters

Name Type Description
activityId xs:string This parameter captures activity Id for the post to the Timeline.
exceptionName xs:string This parameter returns validation error code. The options are "notAllowedToResolveRequest", "requestAlreadyResolved", "failedToGetTask", "requestHasTasks" and "failedToGetTask".
exceptionDescription xs:string This parameter returns validation error description.

Code Examples

In This Document