VRM Classification rules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
We have a requirement to allow more than one way of classification of VITs whereas ootb functionality picks the rule whichever matches first and ignores the rest.
Currently, there is no OOTB Classification Type in sn_vul_vulnerable_item. We have created a custom field to categorize the VITs. The same VIT qualifies for multiple types of classifications that we want to use it in our business rules for further logic adoption.
Is it a good practice to have a comma separated values in our custom field for categorization and have a script in the classification rule, keep building the conditions in the script to amend the custom field (u_category).
The concerning factor is if ServiceNow improves classification rules in future or introduces ootb classification type in VIT, it will be difficult for us to maintain the tech debt created.
Any thoughts?
Regards,
Viji