Senior users with the required permissions would be able to edit the decision tree configuration details. Edit configuration can only be performed if the Preset Tree value is set to ‘No’ i.e., the decision tree selected is not a pre-configured template tree.
If the Preset Tree value is set to ‘Yes’, users can only view the configuration details as it is a pre-configured template tree.
Users with the required permissions can select the ‘Edit Configuration’ button on the bottom right of the ‘Decision Tree Configuration’ panel.
Upon selecting the ‘Edit Configuration’ button, the view within the "Decision Tree Configuration" section would transition to an editable state.
On the "Decision Tree Configuration" panel, the senior users will be able to perform the below actions:
- Change the decision tree name.
- Change the display name for the input field.
- Change the status of the decision tree (Published/Unpublished)
- Update any existing thresholds.
- Add new metrics not in the current decision tree.
- Set thresholds for any new metrics.
- Remove new or existing metrics from the decision tree configuration. This means that the metric will not be included when you run a decision for that decision tree.
- Add/Update the action if compare fails.
- Add/Update the action if data is unavailable.
Add and Remove Metric
User must be able to add a new metric to an existing decision tree by selecting the ‘+’ icon on the ‘Decision Tree Configuration’ panel.
- When user hovers over the ‘+’ icon, they must view a tooltip that states “Click Here to Add a New Metric!”
2. When user selects the ‘+’ icon, a new record is added.
3. User can select the metric from the ‘Business Data to Evaluate’ dropdown. Based on the metric selection, the evaluation logic will get prepopulated.
4. Now, user can enter the value to compare and select the statuses for the action if compare fails and if the data is unavailable from the respective dropdowns.
5. If user wants to remove any newly added metric or an existing metric from the configuration, then select the remove icon next to the metric record.
6. Upon confirming, the metric will be removed from the configuration.
7. If user wants to discard the changes made to the configuration, then select the ‘Cancel’ button on the ‘Decision Tree Configuration’ panel. Upon selecting the ‘Cancel’ button and confirming on the pop-up modal window, all the changes made to the tree configuration will be reverted.
8. Upon selecting ‘Yes’, user will be navigated to the view configuration page.
9. User can now go ahead and save the configuration. Select the ‘Save Configuration’ button. Upon selecting the ‘Save Configuration’ button, all the updates made to the tree configuration will be saved and user will be navigated to the view configuration page.
10. Upon saving, the user can view the updated details on the ‘Decision Tree Configuration’ panel on the view page.
Modify the Basic Tree Details
User can also update the basic tree information like the ‘Decision Tree Name’, display name for the input field i.e., ‘Input Name’ and ‘Status’ in the Edit mode.
- User can select the ‘Edit’ icon next to the field. Upon selecting the ‘Edit’ icon, the field transitions into an editable state.
2. User can make the necessary changes and click on the tick icon to update the details.
3. Similarly, user can also update the Input Name and the Status.
4. The Status field can be updated to either ‘Published’ or ‘Unpublished’. Published or unpublished status would decide whether this decision tree would be available for decision run or not.
Modify Threshold Values, Failed Status and Unavailable Status
User can update the threshold values, Failed statuses, or Data unavailable statuses for the existing metrics as well.
We are performing certain validation checks when a user is updating the data in the configuration table and saving the changes. We are going to display some visual cues to indicate the required fields explaining what went wrong and how to correct it.
User can view a placeholder text that indicates the defined range for a particular metric. For example, if a user wishes to add Risk Score metric to their existing configuration, they can see that the Min and Max value defined for ‘Risk Score’ in the ‘Value to Compare’ column.
If user enters a value that is beyond the defined range, then we indicate that to the user by highlighting the field and providing some visual information. For example, user has entered 1000 as the threshold value for ‘Risk Score’ metric but the defined range is 0 to 100. In this case, we highlight the cell and provide a visual cue to the user.
User will not be able to save the configuration unless they enter a valid value wherever applicable or leave a required field blank.