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

Operation Information

  • Application Reference: com.hornbill.boardmanager
  • Scope: Entity - Card
  • Class: Entity
  • Required Privilege Level: none
  • Required Rights: Group A - canView

Description

Flowcode to write board timeline entries

Request Parameters

The timelineEntry 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
messageType xs:string Yes The id for the message to add to the timeline one of:* cardAdded* cardRemoved* cardMoved* cardUpdated* memberAdded* memberRemoved
cardId xs:integer Yes Card id (generate the link to replace in %C)
cardTitle xs:string No The title of the card (replaces %C in string)
boardId xs:integer No Id of the board (%B)
laneId xs:integer No Id of the lane (%L)
columnId xs:integer No Column Id
userId xs:string No userId (%U link)
userName xs:string No User name (%U)
position xs:string No Position of card
filename xs:string No attached filename
imageUrl xs:string No image to be attached to the post

Response Parameters

Name Type Description
boardId xs:integer Id of the board
activityUrn xs:string The URN of the activity

Code Examples

In This Document