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

Operation Information

  • Application Reference: com.hornbill.servicemanager
  • Scope: Entity - SupplierContacts
  • Class: Entity
  • Required Privilege Level: user
  • Required Rights: none

Description

This flowcode operation updates the specified supplier contact.

Request Parameters

The updateSupplierContact 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
id 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

No response parameters are returned.

Code Examples

In This Document