Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

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

{{book.title}}
More...

Complex Types - buzzCommentType

  • Article
  • 1 minutes to read

Description

This type is used to represent a comment.

Properties

Name Type Occurrence Description
activityOwnerLikes xs:boolean Required Indicates that the owner of the activity that this comment belongs to likes this comment.
actor xs:anyURI Optional Person or object that posted this activity. This is DEPRECATED and should not be used, USE actorInfo INSTEAD
actorInfo accountBasicDetailsType Required Person or object that posted this activity.
comment xs:string Required The comments text body.
extra xs:string Optional Used to store a JSON structure that represents a referenced resource or application-specific additional content.
fileAttachment serverFileAttachmentType Optional
Array (0/∞)		 Information about the file attachment.
icon xs:anyURI Optional Icon that should be displayed against the comment.
id xs:anyURI Required The unique resource name identifier for this activity.
language xs:language Required The language the comment is written in.
likes xs:unsignedInt Required Indicates the number of people that like this comment.
published xs:dateTime Required The date/time the comment was published.
read xs:boolean Required
Default=true		 Indicates that the person querying the activity stream has read this comment.
replyToActorInfo accountBasicDetailsType Optional Actor information of the comment being replied to.
replyToExtra xs:string Optional Extra information relating to reply to comment
replyToID xs:anyURI Optional ID of the comment being replied to.
thumbnailAccessToken xs:string Optional If the activity included embedded content, this access token will provide time-limited access to the thumbnail image for the content via WebDAV cafs_raw.
visibility activityVisibilityType Optional The visibility the method invoker has on this comment.
youLike xs:boolean Required Indicates that the person querying the activity stream likes this comment.
  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document