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

Operation Information

  • Application Reference: com.hornbill.suppliermanager
  • Scope: Entity - SupplierContacts
  • Class: Entity
  • Required Privilege Level: user
  • Required Rights: Group B - canUpdateSupplierContacts

Description

This flowcode operation updates the specified supplier contact.

Request Parameters

The updateSupplierContact 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
supplierContactId xs:integer Yes The supplier contact id.
firstName xs:string No The first name of the existing supplier contact.
lastName xs:string No The last name of the existing supplier contact.
jobTitle xs:string No The job title of the existing supplier contact.
status xs:string No The status of the existing supplier contact. Accepted values are (status.active, status.archived).
phoneNumber xs:string No This is the primary phone number of the existing supplier contact.
phoneNumber2 xs:string No This is the secondary phone number of the existing supplier contact.
phoneNumber3 xs:string No This is the tertiary phone number of the existing supplier contact.
emailAddress xs:string No The primary email address of the existing supplier contact.
emailAddress2 xs:string No The secondary email address of the existing supplier contact.
emailAddress3 xs:string No The tertiary email address of the existing supplier contact.
notes xs:string No Any additional notes for the existing supplier contact.
country xs:string No The country of the existing supplier contact.
language xs:string No The language of the existing supplier contact.
custom0 xs:string No Custom data held against the existing supplier contact.
custom1 xs:string No Custom data held against the existing supplier contact.
custom2 xs:string No Custom data held against the existing supplier contact.
custom3 xs:string No Custom data held against the existing supplier contact.
custom4 xs:string No Custom data held against the existing supplier contact.
custom5 xs:string No Custom data held against the existing supplier contact.

Response Parameters

Name Type Description
outcome xs:string The outcome of the flowcode operation.
supplierContactId xs:string The supplier contact id.

Code Examples

In This Document