CIS-ITSM · Question #101
Your customer complains that when their users click on the Configuration Item magnifier from the Incident form, that they are overwhelmed by the volume of CIs to choose from. They want to exclude…
The correct answer is A. Use the Principal CI class checkbox to identify the CI classes that they want visible on the Incident. Once any class is set as a principal class, the principal class filter is automatically applied to the CI field on change, incident and problem records. This means that only CI's within a principal class can be selected on the CI field. If there are no CI Classes marked as…
Question
Your customer complains that when their users click on the Configuration Item magnifier from the Incident form, that they are overwhelmed by the volume of CIs to choose from. They want to exclude certain types of CIs from the CI lists on the Incident, Problem and Change forms. What do you recommend to your customer?
Options
- AUse the Principal CI class checkbox to identify the CI classes that they want visible on the Incident
- BMake a show/hide Ul action to show only the desired CIs to the itil users
- CAdd a Show field to the base cmdb table: Check the Show box on those CI records they want to
- DCreate an Access control to hide the unnecessary Cls from the itil users
How the community answered
(44 responses)- A70% (31)
- B5% (2)
- C7% (3)
- D18% (8)
Explanation
Once any class is set as a principal class, the principal class filter is automatically applied to the CI field on change, incident and problem records. This means that only CI's within a principal class can be selected on the CI field. If there are no CI Classes marked as Principal Class, then all CIs on all forms will be selectable on the CI field.
Topics
Community Discussion
No community discussion yet for this question.