Servicenow Real Time Scenarios, Mock Interviews & Guidance

The lecture titled "Real Time scenarios session 1" focuses on various real-time use cases in incident management, particularly for new employees in organizations. It addresses the common confusion surrounding the distinction between incidents and requests.

Key highlights include:

1. Incident vs. Request: Emphasizes the need for clarity for new employees when determining whether to create an incident or a request.

2. Use Case 1: Demonstrates a scenario where an employee incorrectly creates an incident instead of a request for a laptop. The speaker shows how to use the UI action "Create Requested Item" to convert the incident into a request while managing database operations to carry over any attachments.

3. Use Case 2: Explains managing multiple incidents for the same issue by designating one as a parent and others as child incidents. It covers creating a business rule that automatically closes all child incidents when the parent incident is closed, emphasizing the use of asynchronous business rules.

4. Use Case 3: Focuses on updating comments by creating a business rule to copy comments from the parent incident to all child incidents whenever there is an update.

Overall, the lecture provides practical insights and technical implementation strategies for incident management, making it particularly beneficial for newcomers in understanding their roles and responsibilities effectively.

n this lecture, the main focus is on handling state changes in incidents and the implications of using synchronous versus asynchronous business rules in a system. Here are the key points:

1. State Changes in Incidents: The speaker discusses a use case where changing the state of a parent incident requires updating the comments of all associated child incidents, ensuring that both the current and previous state values are captured.

2. Synchronous vs. Asynchronous Business Rules: The importance of using an 'after business rule' for these updates is emphasized, as it allows access to the required state values synchronously. However, processing numerous child incidents synchronously can lead to performance issues.

3. Implementation of Glide Record: The lecture demonstrates how to create a Glide Record to query child incidents and update their comments based on the parent's state change. Methods like 'getDisplayValue' are used to retrieve appropriate labels for state values.

4. Script Actions for Performance Improvement: To tackle the performance challenges, the speaker introduces script actions, enabling asynchronous execution. By firing an event that triggers a script action, child incident comments can be updated without waiting for all records to finish processing.

5. Scheduled Event Use Case: The lecture also outlines a second use case where a problem record must be created five minutes after an incident is created. This is done using a scheduled event, employing the 'gs.eventQueueScheduled' method to ensure the problem record is created and linked to the incident after the specified duration.

In this lecture, the focus is on real-time scenarios related to problem management in IT service management. Here are the key points covered:

1. Problem and Task Relationship: The instructor explains that every problem has associated tasks and emphasizes that all these tasks must be closed before marking a problem as resolved.

2. Closing a Problem: A demonstration is given on how to create a problem and its related tasks, assigning them to different teams. A 'before business rule' is introduced that checks the status of these tasks when trying to close the problem. If any task remains open, an error message prevents the problem from being closed.

3. Technical Implementation: Using GlideRecord, the lecturer outlines how to implement the logic that checks for active tasks. The script queries the problem task table and ensures that the problem cannot be closed if any associated tasks are still open.

4. Email Notifications: The lecture transitions to how to configure email notifications to be sent once a problem is closed. Members of the problem task assignment groups are included in the CC list. An email script is demonstrated, which retrieves task assignment group members and adds them to the notification.

5. Conclusion: The session concludes with a practical demonstration of both the business rules applied and the email notification process, reinforcing the importance of understanding these components in managing problems effectively within IT service management.