You might have custom fields defined for Mid Tier, that you would like to display in the BMC Helix ITSM user interface. You might also want to display out-of-the-box Mid Tier fields that are not shown by default in BMC Helix ITSM. You can also define a custom field in Mid Tier and then make the fields available for selection in BMC Helix ITSM.
Developer Studio: You can add custom fields to the views in Progressive Web Application screens using Developer Studio.
Screen Configuration: If you have not enabled the Enable-Progressive-Views parameter as described in Setting configuration parameters in BMC Helix ITSM, you can use Screen Configuration to add custom fields views in classic Smart IT.
Create custom fields or select the out-of-the-box fields that are not visible by default in Mid Tier. To add custom fields to a progressive web application screen, you must perform the following high-level tasks:
Open the Developer Studioin Best Practice Customization mode (the default).
Depending on the ticket type, open the relevant backend form and add custom fields to SV_Create, SV_Edit, or SV_View views. For example, add custom fields to the HPD:Help Desk form for incidents.
Operation
Form name
Read
SV_View of HPD:Help Desk
Edit
SV_EditofHPD:Help Desk
Create
SV_Create of HPD:Help Desk
Sync the Mid Tier cache and validate that you can view the newly added custom field.
Log on to BMC Helix ITSM.
Open the corresponding record to verify that the field was added to the ticket view.
Videos about Remedy Progressive Views
Watch the following webinar (01:03:00) to learn about progressive views:
Types of fields that can be added to classic Smart IT views
Fields that can be added
Fields that cannot be displayed
Character
Large Character
Date/Time
Selection fields, such as drop-down, check box, and radio button fields
Integer
Real
Decimal
Static menus
Dynamic menus
Currency fields
Table fields
Trim fields
Display only fields
Attachment fields
Diary fields
Best practice We recommend not adding fields with auto-generated values, such as Incident ID, to classic Smart IT views. For example, Incident ID is a required field that must be populated to save the ticket, but the user cannot enter a proper value for this field because it is auto-generated by the system.
To add custom fields to views
If you have not enabled the Enable-Progressive-Views parameter as described in Setting configuration parameters in BMC Helix ITSM, you can use Screen Configuration to add custom fields in classic Smart IT.
Find the backend forms to which you want to add custom fields. For example, the following AR System forms need to be modified to add custom fields to the Incident view:
Operation
Form name
Read
HPD:Help Desk
Edit
HPD:IncidentInterface
Create
HPD:IncidentInterface_Create
SLM Join
INT:HPDSLM:HelpDesk_SLM_Join_Outer
Open the Developer Studioin Best Practice Customization mode (the default).
Add new fields to the form as required. Depending on the view and the forms that it contains, you may have to copy the field to other related forms.
Navigate to the Mid Tier Configuration Tool and use the Sync Cache option.
Clear the browser cache.
In classic Smart IT, use the Screen configuration to add the fields to applicable views.
You can specify the area in which the field should appear. For example, you can add a custom field to the Assignment area of the Incident View. The custom field then appears in incident ticket details, with the assignment information. If you add custom fields to the Person Profile, those fields also appear in the customer information displayed in the Smart Recorder. You can also specify whether the field is read-only. You can add any number of fields to a section, with the exception of the header section, where you can add up to 5 fields.
In classic Smart IT, the visibility of custom fields when creating and editing tickets depend on the field access given to custom fields in Mid Tier. You may set one of the following field access:
Read/Write - Custom fields with Read/Write field access are displayed when creating or editing a ticket. You can input values when creating and editing the ticket.
Read Only - Custom fields with Read Only field access are not displayed when creating a ticket. Though they are displayed when editing the ticket, they remain disabled. You cannot edit them.
Out-of-the-box Mid Tier fields are displayed in view mode even if the fields are blank. Custom fields are displayed only when values are present and are hidden in view mode if the fields are blank.
Dynamic expressions for configuration
In BMC Helix ITSM, administrators can build dynamic expressions to configure on-screen fields and provider actions. This topic provides details and examples of the dynamic expressions. For more details, see Dynamic expressions for configuration.
Procedures for adding fields to specific classic Smart IT views
The following topics provide procedures with additional details:
Videos about configuring fields in classic Smart IT screens
View the following videos for additional information and procedures. The screens of the following videos refer to the earlier versions of BMC Helix ITSM.