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…
{{server.name}}
{{server.summary}}
{{server.documentCount.toLocaleString()}} pages Not published to this site
- Name
-
{{server.name}} - URL
-
{{mcpServerUrl(server.path)}}
| Tool | What it does |
|---|---|
{{tool.name}} |
{{part.text}}{{part.text}} |
How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
Searching for:
{{docApp.searchResultFilteredItems.length}} results for:
{{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}}
{{group.title || group.id}}
{{group.description}}
Details
Table ID: h_itsm_request_types
Contains a list of supported Request types
Table Attributes
| Name | Value |
|---|---|
| Primary Key | h_pk_id |
Columns
| Name & ID | Description | Column Attributes | Relationships | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Description
h_description |
The purpose of the request type |
|
|
||||||||
|
ID
h_pk_id |
System generated ID as we use composite key as well |
|
|
||||||||
|
Is Custom
h_custom_type |
0 = a fixed system request type like incident, 1 = custom type created by administrator |
|
|
||||||||
|
Request Class
h_requesttype_class |
The request class custom type is based on. A custom type can be based on a non-custom request type i.e Major Incident could have request class Incident meaning the request record is stored in incidents extended table |
|
|
||||||||
|
Request Type
h_requesttype |
The request type, current hardcoded values would be Incident, Problem, Change, Known Error, Release and Service Rquest, this would be the FK reference to the h_requesttype column in the h_itsm_requests table |
|
|
||||||||
|
Request Type Configuration
h_config |
A JSON string containing the request type configuration information. |
|
|
||||||||
|
Request Type Feature Color
h_color |
The feature color that is used as a visual cue for this request type |
|
|
||||||||
|
Request Type Icon
h_icon_ref |
The icon to associate with this request type |
|
|
||||||||
|
Service Desk ID
h_desk_id |
Service Desk ID, for upcoming change to introduce service desk partitioning. |
|
|
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}