Overview

The Custom Field Input component streamlines the process of fetching and modifying custom field values by enabling direct updates through user input. It supports updating custom fields across three asset classes, Profile, Case, and User, thereby allowing users to specify and update fields based on the selected asset type. This component eliminates the need for separate configurations, reducing effort and enhancing efficiency. Additionally, it offers the option to set disability conditions, ensuring the component can be restricted in certain scenarios. By simplifying workflows and providing flexibility, this component enhances usability and accelerates data updates within forms.

​

Various Fields of the Custom Field Component

• Asset Class: This field helps define the asset class for the custom field, indicating where you want the entry field to be updated. There are three options available: Profile, Case, and Message Level. Based on your selection, the custom field options will populate accordingly. 

• Custom Field: After selecting the asset type, a dropdown menu will display the fields created for that asset type. For example, if you select the Profile asset type, the dropdown will show relevant custom fields, such as Phone Number. Once the user fills in the phone number, it will be displayed in the user-level properties and can also be used for reporting purposes. 

• Default Value: You can configure the pre-populated value for the component. You can choose a variable here or write custom code.

• Restricted Keyword Lists: It is a multi-select configuration field. It enables you to assign one or more predefined keyword lists. If your input contains any terms from the selected restricted keyword lists, an error message will be triggered. This message is configurable once you enable Configure Error Messages toggle. This feature helps you maintain better input quality control and enforce compliance or content guidelines dynamically within your workflow.

• Skip Updating Custom Field in the Asset: This is a checkbox field that, when selected, prevents updates to custom fields on the associated asset during workflow execution.

• Configure Error Message: This field allows you to create a warning message for users if:

  • They do not fill the field value.

  • The text entered has restricted keywords.

• Visibility Conditions: It is a rule or set of rules that determines whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

  • Example  

    • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High."

    • Implementation: Visibility Condition: Ticket_Priority == 'High' 

    • Result: The "Priority Escalation" section appears only for high-priority tickets. 

• Input Disability Condition: is a rule or set of criteria that determines whether a specific element, such as a field, button, or component, should be disabled (i.e., grayed out and non-interactive) in a user interface. It restricts user interaction based on certain conditions, ensuring that actions are contextually valid or preventing errors. 

  Example: 

  1. Based on Field Value: 

     1. Condition: Disable the "Submit" button if the "Terms and Conditions" checkbox is unchecked. 

     2. Result: The user cannot submit the form until they accept the terms. 

  2. Based on User Role: 

     1. Condition: Disable the "Delete Record" button for users without "Admin" permissions. 

     2. Result: Only admins can delete records, while other users see the button but cannot interact with it. 

  3. Based on Data Completeness: 

     1. Condition: Disable the "Next" button until all required fields are filled. 

     2. Result: Users are prevented from moving forward until they complete the required steps.

​