- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2016 07:42 AM
We just turned on Discovery. Enforce CI Verification has also been turned on for the model categories. We do not wish to create assets for virtual servers. So I have set the VMware models to "Don't create assets". However, we already have over 1,000 virtual server CIs created with "Requires Verification" = true. Do we just need to update "Requires Verification" to false for the CIs that have already been created? I don't seem to have the permission to make changes to this attribute. Is this a Sys Admin function only?
Teresa
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2016 08:47 AM
Hi Teresa,
The value for Requires Verification is meant to be adjusted when you create an asset for those items or merge with another CI and not something that is changed manually.
I just tested this scenario, and the Asset tracking strategy still prevents the Asset from being created, even if you choose to Create Assets (which you can do from a list), so you will not end up with Assets for these items.
That does not, however, make the flag go away, which is what you want. For that, you will want to enlist your Sys Admin so you have something set up that you can use without assistance in the future.
I made a quick UI Action (I made it a link under Related links to avoid button sprawl and also made it available on the list) that will allow you to change the verification flag without creating an asset. I called it Verify CI and in the help text I indicated that it verifies the CI without creating an Asset. Here is the code:
current.unverified = false;
current.update();
action.setRedirectURL(current);
You will want to set the condition to:
current.unverified == true
so it only displays for unverified CIs. Just be careful when you use this. I could see potentially making a corresponding one that reverses this in case you accidentally verify a CI you didn't mean to. This could be done easily by reversing the true and false in the script and condition.
Hope this helps.
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2016 08:47 AM
Hi Teresa,
The value for Requires Verification is meant to be adjusted when you create an asset for those items or merge with another CI and not something that is changed manually.
I just tested this scenario, and the Asset tracking strategy still prevents the Asset from being created, even if you choose to Create Assets (which you can do from a list), so you will not end up with Assets for these items.
That does not, however, make the flag go away, which is what you want. For that, you will want to enlist your Sys Admin so you have something set up that you can use without assistance in the future.
I made a quick UI Action (I made it a link under Related links to avoid button sprawl and also made it available on the list) that will allow you to change the verification flag without creating an asset. I called it Verify CI and in the help text I indicated that it verifies the CI without creating an Asset. Here is the code:
current.unverified = false;
current.update();
action.setRedirectURL(current);
You will want to set the condition to:
current.unverified == true
so it only displays for unverified CIs. Just be careful when you use this. I could see potentially making a corresponding one that reverses this in case you accidentally verify a CI you didn't mean to. This could be done easily by reversing the true and false in the script and condition.
Hope this helps.
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2016 09:07 AM
Thank you, Ben. This is very helpful.
Teresa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-23-2019 11:10 AM
Hello, which is the role can I need to access the model categories? only admin?