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

Operation Information

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

Description

This flowcode is used to update the Status of a request and optionally update the Sub-status. You can choose whether to update the timeline, set the visibility of the timeline post and choose to set an indefinite or fixed off-hold time if updating the request status to 'On Hold'

Request Parameters

The smUpdateStatus 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 The h_pk_reference value of the h_itsm_requests record.
status xs:string Yes The status that the request is to be updated to (New, Open, On Hold, Resolved, Closed, Cancelled).
subStatus xs:string No The sub-status that the request is to be updated to
updateTimeline xs:string No Indicates whether or not a system update is made to the request timeline. Default is No. This param is superseded by the input param manualUpdateTimeline.
manualUpdateTimeline xs:string No Freetext update to the request timeline. This supersedes the input param updateTimeline.
visibility xs:string No The request timeline post visibility. If not specified, the application option value will be used.
onHoldUntilDate xs:dateTime No If placing on hold, you can provide the date and time that the request is to be placed On Hold until.
statusActionReason xs:string No This parameter is now deprecated.
isEmailCustomerChecked xs:boolean No This parameter checks if Email Customer checkbox is checked so we can send an email to customer when placing the request on-hold.

Response Parameters

Name Type Description
activityId xs:string The ID of the entry created in the activity stream
exceptionName xs:string Name of the returned exception
exceptionDescription xs:string Description of the returned exception

Code Examples

In This Document