- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2015 08:55 AM
We are using 'Enforce Verification' which updates the 'Requires verification' flag from true to false when using the 'Create Asset' button from the CI. However, we received new assets (no pre-existing CI), and the flag on the new associated CI record is 'Requires verification' = 'true', which shows the 'Create Asset' button on the CI. Is this normal? I was expecting that when the CI is created from the asset, that the 'Requires verification' flag would automatically be set to 'false'.
Solved! Go to Solution.
- Labels:
-
Enterprise Asset Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2015 11:48 AM
Supports sean hamilton (NOW) found the issue! Back when we first implemented Asset Management, Enforce CI Verification was new, and as a temporary fix, we had set the default value to true for field 'Requires verification', but then never reverted this update. We will manually fix the flag for around 100 assets whose associated CIs have 'Requires verification' = true, and then revert the default value to the OOB version. Thanks again!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2021 11:07 AM
I hope this helps.
Provided the "Enforce CI Verification" checkbox is true in the model-category setting:
- If an asset is created a CI is created but the "Requires Verification" flag is false.
- If a CI is created (by Discovery for example) an asset is also created, and the "Requires Verification" flag is set to true, allowing either to Merge CI or to Create Asset (buttons).
M
