Help/Advise Assignment Rules with modified User Group Field values

[Joe Kline]

We added a couple "Remediation Group" fields to the CMDB CI records.  Attempting to utilize them, we added Assignment Rules (to both CC and VR) to set CTR and VIT assignments to the User Group Field values of cmdb:u_remediation_group_infrastructure or cmdb:u_remediation_group_software (the names of the two new user columns added) based on proper conditions of the field "is not empty".  When I list the rules, my new rules are showing the conditino, assign using fields but the "Assignment value" field is blank for all of them.  The resulting CTR/VIT records are showing the correct Assignment Rule, but the Assignment Group is "(empty)".  I had to customize the form listings to change which groups are available for selecting in the rule.

Anybody out there performed a similar customization to explain what I missed or did incorrectly such that the rule is not picking up the actual value stored in the CI?

Thanks in advance for your time and feedback/comments.

[andy_ojha]

Hey Joe,

Great question - there is a quirk with adding a new Assignment (User Group Field) 'Choice' ...

The resulting outcome should still work (consuming the custom field on the CMDB_CI) - even though the 'Assignment Value' does not get set on the Rule record, the custom Choice pointing to your custom field on the CMDB_CI table will still win.

1) Open up the Assignment Rule (perhaps start with VR first) in the Vulnerability Response App Scope
2) Set 'Assign using' to [User Group field]
3) Right-click the [User Group field], and select "Show Choice List"
4) You should see the native values (3 records) here 
5) Add a new record here (you can also pick an existing record and do an 'Insert and Stay')
6) They key part is ensuring the 'Value' points to your custom reference field (sys_user_group) on the CMDB Table (e.g. u_my_custom_field_name)
7) Update your Assignment Rule to pick your new Choice that you added 

NOTE: the Assignment Value will show up as empty (there is some hardcoded settings that latch onto the three native values) - but the Assignment Rule should still work as expected and leverage the custom field on the CMDB_CI you picked

Let me know if you get a win with this or still have issues (along with the version of VR you have installed).

Reference:

[Joe Kline]

./andy-b2poYQ==,

While I did not add the choice list quite as easily found as you advice, I do in fact have them added, and they appear in the list when I right clicked and showed choice list.  I double checked the name of the field and on what hierarchy of the CMDB they were actually placed.  I've tried gathering some screen captures to show the values:

CMDB table/dictionary listing:

Rule Choice List:

One of the new rules - showing the group field and the selected value from the modified choice list drop menu:

Vulnerable Items showing which rule "won", that the type is Rule, and the "empty" setting chosen for the Assignment Group:

And from the CI record of the top VIT from above, you can see that the Remediation Group fields have a non-empty value in them, which is the expected Assignment Group value instead of "empty":

[Joe Kline]

Well!  I sure failed miserably on the images/attachments (first time trying to do that).

[Joe Kline]

Trying the attachments again - a picture of the CMDB dictionary to confirm the new field labels and names, the choice list of the rules, the rule to show how it was set up, and a short list of the CC test results showing the "empty" assignment next to the remediation rule ...

Thanks, for your time,

Joe