- 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
06-18-2015 09:05 AM
Hi Ryan,
This is not expected behavior. I just tried to replicate it and it was not how it behaved for me. Requires verification was still false on the CI created from my new asset. Sounds like something for which you may need to open an issue on HI. What version/patch are you on (put stats.do in the Application Navigator's filter field if you are not sure).
Thanks,
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2015 09:11 AM
Thanks for the quick response Ben! We are on fuji patch2 hotfix1. I will open a ticket on Hi.
- 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
06-18-2015 12:33 PM
Glad you got it worked out, Ryan!