- 24 Nov 2023
- 3 Minutes to read
- Print
- PDF
Set Values
- Updated on 24 Nov 2023
- 3 Minutes to read
- Print
- PDF
The primary purpose of the Set Values tab is to set the values of those source fields that need to be updated after the successful mapping of a source form and a target form.
Consider the previous example of conversation of an incident to a service request. From operational perspective, an incident is getting closed whereas a service request is being opened up. In this case, values of the source fields should be updated in such a way that system is consistent.
User Persona: Application Designer
Configure Set Values
This section provides the details of the third stepper configuration of Form Relation.
To configure the Set Values tab, perform the following steps:
- Click ID hyperlink to open any existing form relation or click New to create a new form relation from scratch.
- After configuring the General and Map Fields steppers, the Set Values stepper gets enabled for a new form. You can directly navigate to the Set Values stepper for an existing form. A sample screenshot is shown below:
Figure: Form Relation - Set Values
The following table contains a brief description on Set Values screen fields.
Source
The following table contains a brief description on Source tab screen fields.
Field Name | Description |
---|---|
Source | Select the Source tab to configure the source field values. By default, the Source tab is selected. If a field (with dependent fields) is selected under the Source tab then all dependent fields get automatically added and displayed under the Source tab. The displayed dependent fields are non-deletable. For Example: If the Field is selected as Status and Value as Closed then the dependent fields such as Closure Code and Closure Category gets automatically added and displayed under the Source tab. Note The mapping takes precedence over setting values. If the mapped source field is empty then the value set here is displayed. |
Field | Displays all the fields available in the source form. |
Value | Displays the current field value. Select the new value as per the requirement. For Example: In the Form Relation (Incident to Service Request), the incident is getting closed and getting converted to an SR. So, in this case, the Status field of the Source Form (Incident Form) displays the current value as In-Progress. Now, the requirement is to change the value of the Status field (Incident Form) to Closed. |
Target
The following table contains a brief description on Target tab screen fields.
Field Name | Description | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Target | Select the Target tab to configure the target field values. Note The mapping takes precedence over set values for Target field. The following are a few scenarios for target field.
| ||||||||||||||||||||
Field | Displays all the fields available in the target form. | ||||||||||||||||||||
Value | Select the required current field value for the Target Form. For Example: In the Form Relation (Incident to Service Request), the incident is getting closed and getting converted to an SR. So, in this case, the Status field of the Target Form (Incident Form) current field value has to be selected as In-Progress as we are changing it as an SR. | ||||||||||||||||||||
Select it to override the source field value with new selected value. Let us understand the functionality of Override button with the following example. Scenario - Changing Priority field value from P1 (Source Field Value) to P2(Target Field Value)
| |||||||||||||||||||||
Click + icon to add multiple rows. A new row is added with each click on the + icon. The system displays the following validation message if you attempt to add a row without mentioning values to it. A sample screenshot is shown below: Figure: Add rows - Validation Message | |||||||||||||||||||||
Click this icon to delete rows. The selected row is deleted with each click on the icon. |
System displays the following error message if the Next button is clicked when minimum one mandatory Target field is either unmapped or does not have any set value.
Figure: Error Message
For Example: If the Field is selected as Status and Value is blank, as it is a mapped field but without a value, hence the system displays the above validation message.
A list of errors is displayed when there are more than one errors. A sample screenshot is shown below:
The Application Designer can save the changes and proceed further only when all the errors are resolved.