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}}

Keep typing  - a search needs at least two characters

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

Operation Information

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

Description

Returns the boards the calling user can see that already hold a card matching the given type and key, or a given card id. Used to tell whether something has already been added to a board. An operation rather than a direct stored-query call so a client can ask for it over the JSON API, where data::queryExec is not available.

Request Parameters

The getBoardsContainingCard 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
type xs:string No The type of card to look for, e.g. core.email.
key xs:string No The key of the card to look for - typically the URN or id of the subject it was created from.
boardId xs:integer No Only look on this board.
cardId xs:integer No Look for this specific card by id, instead of by type and key.

Response Parameters

Name Type Description
boards JSONDataType One row per matching card placement, exactly as the stored query returns it. Each row identifies the board (h_id, h_name, h_description), the lane it sits in (h_lane_id, h_lane_name, h_lane_limit, h_lane_width, h_lane_style, h_lane_config, h_lane_order) and the card itself (h_card_id, h_card_title, h_card_icon, h_card_type, h_order, h_column, h_value, h_progress, h_key, h_card_lane, h_archived), together with the caller's combined permission bitmask on the board (h_permissions). Always an array, including when a single row matches, and empty when the card is on no board the caller can see.

Code Examples

In This Document