Difference between revisions of "Mapping Fields from Customised Forms"
Jump to navigation
Jump to search
m (Added a note (based on Support Incidents) about not using Integer fields for phone numbers.) |
|||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-config/customize/mapping-fields-from-customized-forms/ Hornbill Document Library]. | ||
+ | |||
+ | [[file:hornbill-document-library.png|Mapping Fields from Customized Forms|link=https://docs.hornbill.com/servicemanager-config/customize/mapping-fields-from-customized-forms/]] | ||
+ | <!-- | ||
+ | |||
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | ||
__NOTOC__[[Main Page|Home]] > [[Administration]] > [[Intelligent Capture Designer]] > Mapping Fields from Customised Forms | __NOTOC__[[Main Page|Home]] > [[Administration]] > [[Intelligent Capture Designer]] > Mapping Fields from Customised Forms | ||
Line 47: | Line 52: | ||
|- | |- | ||
− | | align = "left" | | + | | align = "left" |h_summary |
− | | | + | | VARCHAR/255 characters |
− | | | + | | The Summary field of a request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_description |
− | | | + | | TEXT/unlimited* |
− | | | + | | The description field of a request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" |h_site |
− | | | + | | VARCHAR/64 characters |
− | | | + | | The site field for a request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_custom_a - h_custom_o |
− | | | + | | Data Type/Capacity VARCHAR/255 characters |
− | | | + | | Description ''VARCHAR'' custom fields a - o each suitable for holding up to 255 characters of any type. |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_custom_p - h_custom_t |
− | | | + | | TEXT/unlimited* |
− | | | + | | ''TEXT'' custom fields p - t each suitable for holding large amounts of text characters of any type. |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_custom_21 - h_custom_25 |
− | | | + | | DATETIME/a single date-time stamp |
− | | | + | | ''DATETIME'' custom fields 21 - 25 each suitable for holding a single date-time stamp (YYYY-MM-dd HH:mm:ss). These columns should ONLY be used in conjunction with a date-time picker. |
|- | |- | ||
− | | align = "left" | | + | | align = "left" |h_custom_26 - h_custom_30 |
− | | | + | | INTEGER/any whole number |
− | | | + | | ''INTEGER'' custom fields 26 - 30 each suitable for holding whole numbers. When mapping to these columns, ensure the following RegEx is specified in your Custom field settings: ''[0-9]'' |
'''Note:''' Phone numbers are ''not'' Integers, do '''not''' use these fields to store phone numbers. | '''Note:''' Phone numbers are ''not'' Integers, do '''not''' use these fields to store phone numbers. | ||
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_custom_31 - h_custom_40 |
− | | | + | | TEXT/unlimited* |
− | | | + | | ''TEXT'' custom fields 31 - 40 each suitable for holding large amounts of text characters of any type. |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_backout_plan |
− | | | + | | Text/Unlimited* |
− | | | + | | The Back Out Plan of a Change or Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_support_plan |
− | | | + | | Text/Unlimited* |
− | | | + | | The Support Plan of a Change or Relase Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_communication_plan |
− | | | + | | Text/Unlimited* |
− | | | + | | The Communication Plan of a Change or Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_test_plan |
− | | | + | | Text/Unlimited* |
− | | | + | | The Test Plan of a Change or Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_implementation_plan |
− | | | + | | Text/Unlimited* |
− | | | + | | The Implementation Plan of a Change or Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_security_implication |
− | | | + | | Text/Unlimited* |
− | | | + | | The Security Implications of a Change or Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_change_justification |
− | | | + | | Text/Unlimited* |
− | | | + | | The Change Justification a Change Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_release_justification |
− | | | + | | Text/Unlimited* |
− | | | + | | The Change Justification a Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_release_plan |
− | | | + | | Text/Unlimited* |
− | | | + | | The Release Plan for a Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_disruption_level |
− | | | + | | VarChar/255 Characters |
− | | | + | | The Disruption Level of a Change or Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_change_category |
− | | | + | | VarChar/100 Characters |
− | | | + | | The Category of a Change Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_release_category |
− | | | + | | VarChar/100 Characters |
− | | | + | | The Category of a Release Request |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_proposed_start_time |
− | | | + | | DATETIME/a single date-time stamp |
− | | | + | | The Proposed Start date/time of the a Change or Release Request - (YYYY-MM-dd HH:mm:ss). These columns should ONLY be used in conjunction with a date-time picker |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_proposed_end_time |
− | | | + | | DATETIME/a single date-time stamp |
− | | | + | | The Proposed End date / time of the a Change or Release Request - (YYYY-MM-dd HH:mm:ss). These columns should ONLY be used in conjunction with a date-time picker |
|- | |- | ||
− | | align = "left" | | + | | align = "left" | h_workaround |
− | | | + | | Text/Unlimited* |
− | | | + | | The Workaround for a Problem or Known Error record |
|} | |} | ||
Line 176: | Line 181: | ||
* Once you have configured field mapping in your progressive capture custom forms, you may need to expose the mapped field on the request. See the [[Request_Details_Form_Designer|'''Request Details Form Designer''']] for more information. | * Once you have configured field mapping in your progressive capture custom forms, you may need to expose the mapped field on the request. See the [[Request_Details_Form_Designer|'''Request Details Form Designer''']] for more information. | ||
* When creating your email template, simply look for the '''custom''' options available from the variables drop-down pick list. Selecting the required variable in your email template, will pass through the answer from your custom question which has been mapped to the corresponding custom field. | * When creating your email template, simply look for the '''custom''' options available from the variables drop-down pick list. Selecting the required variable in your email template, will pass through the answer from your custom question which has been mapped to the corresponding custom field. | ||
− | + | --> | |
− | [[Category: | + | [[Category:HDOC]] |
Latest revision as of 21:34, 13 February 2024
This document can now be found at its new location in the Hornbill Document Library.