CIS-ITSM · Question #66
Your customer wants incidents to close automatically 7 days after the incident is resolved. How do you meet this requirement? (Choose two.)
The correct answer is A. Modify the Incident Lifecycle flow to trigger from the Resolved date instead of the Updated date D. Modify the Incident Lifecycle flow to expire after 7 days. ServiceNow's out-of-box Incident auto-closure is handled by the Incident Lifecycle flow. To close incidents 7 days after resolution: (A) the flow's trigger must reference the Resolved date field rather than the Updated date, so the 7-day countdown starts at the moment of…
Question
Your customer wants incidents to close automatically 7 days after the incident is resolved. How do you meet this requirement? (Choose two.)
Options
- AModify the Incident Lifecycle flow to trigger from the Resolved date instead of the Updated date
- BUpdate the incident_close UI action script
- CFrom the Incident Properties application, set Enable auto closure of incidents based on Resolution
- DModify the Incident Lifecycle flow to expire after 7 days
How the community answered
(33 responses)- A79% (26)
- B15% (5)
- C6% (2)
Explanation
ServiceNow's out-of-box Incident auto-closure is handled by the Incident Lifecycle flow. To close incidents 7 days after resolution: (A) the flow's trigger must reference the Resolved date field rather than the Updated date, so the 7-day countdown starts at the moment of resolution; and (D) the flow's wait/expiration must be set to 7 days, causing it to transition the incident to Closed after that period. Option B (UI action script) handles manual closure logic, not scheduled auto-closure. Option C describes a property that does not exist in standard ServiceNow ITSM. The correct answers are A and D.
Topics
Community Discussion
No community discussion yet for this question.