Documentation

This is taking longer than usual. If nothing appears, refresh the page.

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

Operation Information

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

Description

This operation posts an update to a Request's Timeline.

Request Parameters

The updateReqTimeline 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 be set with the Id of a Request.
action xs:string No This parameter is deprecated.
source xs:string No This parameter is deprecated.
content xs:string Yes This parameter must be set with the content of the Timeline entry.
extra xs:string No A JSON structure representing additional content for the Timeline entry.
visibility xs:string No This parameter must be set with the visibility of the Timeline entry. The options are public, trustedGuest, colleague, manager and owner.
imageUrl xs:string No This parameter can be set with the URL of an image that is associated to the Timeline entry.
activityType xs:string No This parameter can be set with activity type that is associated to the Timeline entry. For example, "System" is used for generic updates.
skipBpm xs:boolean No This parameter determines whether the Request's process is resumed following the Timeline update. By default, this parameter is set to "false".

Response Parameters

Name Type Description
outcome xs:string This parameter is set with the outcome of the operation. The options are "success" and "failure".
activityId xs:string This parameter is set with the activity Id that is generated after posting a new Timeline entry.
exceptionName xs:string This parameter captures any validation errors. The options are "failedTimelinePost" and "failedTimelineImagePost".
exceptionDescription xs:string This parameter will be set with an exception's description, thrown by an API.

Code Examples

In This Document