Documentation

{{docApp.title}}

{{docApp.description}}

INDEX

Documentation Library

Search for information on Hornbill Documentation.

{{docApp.searchError}}

{{docApp.searchResultFilteredItems.length}} results for "{{docApp.currentResultsSearchText}}" in {{docApp.searchFilterBySpecificBookTitle}}

Have questions about this site?


What is this site?

  • This website is Hornbill's new product documentation website and is currently under development.
  • It is intended that all existing and future public-facing documentation we produce will be available to search, browse and share.
  • Hornbill's current documentation is available at Hornbill Wiki but over time this content will be migrated to this documentation site.
  • Please feel free to have a look around at any time.

Why has Hornbill created this site?

  • Hornbill's products have moved on considerably since we introduced it almost 10 years ago. At the time, the MediaWiki tool was sufficient, but we have outgrown it.
  • Our customers are more enterprise focused and more self-sufficient than ever before, so for 2023 and beyond we have established a new documentation platform and team to drive our documentation initiative forwards.
  • We are aiming to deprecate the use of Hornbill Wiki for most Hornbill related documentation.
  • We want to enable our growing partner network with product resources and information, documentation beyond our Wiki approach is required.
  • We could definitely do with some help, and may even pay for some! If you have domain knowledge and would like to help, please check out our Hornbill Docs Contributor Guide and contact the Hornbill docs team at docs@hornbill.com.

What will this site be good for?

  • Community contribution will be facilitated, encouraged, and most welcome.
  • High quality documentation, will be kept up to date as rapidly as our products evolve.
  • Real-time content search and discovery.
  • Articles organized into books, books into libraries, creating a more natural and logical structure to our documentation.
  • Legacy API documentation and various other documentation sources will all be consolidated into a single unified documentation system.
  • Documentation available in browser as well as printable/viewable as PDF on demand.
  • Personalized documentation experience, allowing dark/light mode, article subscriptions, social media sharing and other useful features.
  • Almost all publicly available documentation on docs.hornbill.com will be open-source and available to fork on GitHub, allowing customers to derive their own custom documentation around Hornbill products should they wish to.

What is the timeline for this site?

  • We have taken the decision to publish and make available early, there is very little content at this time.
  • As and when we have completed/usable documentation, it will be published here.
  • We have a host of additional features we wish to add over time, so please watch this space.
  • We expect most of our existing documentation should be reviewed/migrated to docs.hornbill.com over the coming months.
  • The documentation project will be ongoing, will continue to expand, evolve and improve day-by-day.

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

Entity API / addCard

Operation Information

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

Description

Add a card to the board

Request Parameters

The addCard API takes the following input parameters. It is important to note that the parameters must satisfy the requirement of the input validation checks.

Name Type Required Description
h_board_id xs:integer Yes The board Id
h_lane_id xs:integer No The Lane Id
h_title xs:string No Card Title
h_content xs:string No Display contents of card
h_order xs:integer No order card appears in lane
h_column xs:string No Which column within the lane a card will appear (if the lane has multiple columns)
h_type xs:string Yes Card Type that define what properties a card can have (eg card, note, seperator). Not different applications can define different types
h_value xs:decimal No A value for the card (eg scrum points, cost etc)
h_progress xs:integer No Progress of card from 0-100
h_key xs:string No The key if the card is related to another object
h_link xs:string No link to open from card
h_members xs:string No List of member URN to add
h_status_name xs:string No Status for Card
h_status_icon xs:string No Icon for status
h_status_info xs:string No Status info of the card
h_checklist xs:string No A checklist to add to the card
h_style xs:string No Custom style of card
tag_ids xs:integer No Tags data to add to card
h_activitystream_id xs:string No The activitystream to post updates too
fromBoard xs:boolean No Is this created from the board
h_custom_1 xs:string No The first custom field in board manager
h_custom_2 xs:string No The second custom field in board manager
h_custom_3 xs:string No The third custom field in board manager
h_custom_4 xs:string No The fourth custom field in board manager

Response Parameters

Name Type Description
h_card_id xs:integer Id of the newly created card
h_entered_on xs:dateTime Time set for when card entered
log xs:string Log message alerting any possible problems

Code Examples

In This Document