Create Problem based on incident volume - pull 1 (#2557)

* script.js

Automatically create a problem record from incident volume
Use case: Automatically create a problem record if a specific Configuration Item (CI) is associated with more than a certain number of incidents within a defined timeframe. 
Code snippet
This code can be placed in a Scheduled Script Execution or an After Insert Business Rule to check new incidents

* README.md

* Script.js

Identify the oldest active incident for each assignment group. This helps managers focus on long-running tickets that may require special attention.

* README.md

* script.js

This example searches a JSON document for all developers listed under the specified path.

* README.md

* Update README.md

* script.js

Identify inactive users who still have unresolved incidents. This helps with offboarding processes and ensures incidents aren't left unattended.

* README.md

* Update script.js

* Delete Core ServiceNow APIs/GlideAggregate/Count Inactive Users with Active incidents/README.md

* Delete Core ServiceNow APIs/GlideAggregate/Count Inactive Users with Active incidents/script.js

* Delete Core ServiceNow APIs/GlideAggregate/Find oldest Incident based Assignment Groups/README.md

* Delete Core ServiceNow APIs/GlideAggregate/Find oldest Incident based Assignment Groups/script.js

* Delete Core ServiceNow APIs/GlideJsonPath/GlideJsonPath Reader Example/README.md

* Delete Core ServiceNow APIs/GlideJsonPath/GlideJsonPath Reader Example/script.js

Author: trimbakeshmadhan-109

Core ServiceNow APIs/GlideAggregate/Create Problem based on incident volume/README.md

@@ -0,0 +1,37 @@
+Key features
+Automatic problem creation: The script uses a GlideAggregate query to count the number of incidents opened for a specific CI.
+Time-based threshold: Problems are only created if more than five incidents are opened within a 60-minute window.
+Targeted incidents: The script focuses on incidents related to the same CI, making it effective for identifying recurring infrastructure issues.
+Customizable conditions: The number of incidents and the time frame are easily configurable within the script.
+Efficient performance: The use of GlideAggregate ensures the database is queried efficiently, minimizing performance impact. 
+
+How it works
+The script is designed to be executed as a server-side script, typically within a Business Rule. When an incident is inserted or updated, the script performs the following actions:
+Queries incidents: It executes a GlideAggregate query on the incident table.
+Sets conditions: The query is filtered to count all incidents that meet the following conditions:
+Same CI: The incident's cmdb_ci matches the cmdb_ci of the current record.
+Within the last hour: The opened_at time is within the last 60 minutes.
+Evaluates count: After the query is run, the script checks if the count of matching incidents exceeds the threshold (in this case, 5).
+Creates problem: If the threshold is exceeded, a new problem record is initialized.
+The short_description is automatically populated with a descriptive message.
+The cmdb_ci is linked to the new problem record.
+The new record is then inserted into the database. 
+Implementation steps
+Create a Business Rule:
+Navigate to System Definition > Business Rules.
+Click New.
+Configure the Business Rule:
+Name: Auto Create Problem from Multiple Incidents
+Table: Incident [incident]
+Advanced: true
+When to run: Select after and check the Insert and Update checkboxes. This ensures the script runs after an incident has been saved.
+Filter conditions: Optionally, you can add conditions to limit when the script runs (e.g., cmdb_ci is not empty).
+Add the script:
+Navigate to the Advanced tab.
+Copy and paste the script into the Script field.
+Customize (optional):
+Number of incidents: Change the > 5 value to adjust the threshold.
+Time frame: Adjust the gs.minutesAgoStart(60) value to change the time window.
+Other conditions: If you need to check for specific incident statuses or categories, add more addQuery lines to the GlideAggregate call.
+Save the Business Rule. 
+Customization examples

Core ServiceNow APIs/GlideAggregate/Create Problem based on incident volume/script.js

@@ -0,0 +1,13 @@
+var incidentCheck = new GlideAggregate('incident');
+  incidentCheck.addQuery('cmdb_ci', current.cmdb_ci); // Or any specific CI
+  incidentCheck.addQuery('opened_at', '>', 'javascript:gs.minutesAgoStart(60)');
+  incidentCheck.addAggregate('COUNT');
+  incidentCheck.query();
+  
+  if (incidentCheck.next() && parseInt(incidentCheck.getAggregate('COUNT')) > 5) {
+      var problem = new GlideRecord('problem');
+      problem.initialize();
+      problem.short_description = 'Multiple incidents reported for CI: ' + current.cmdb_ci.getDisplayValue();
+      problem.cmdb_ci = current.cmdb_ci;
+      problem.insert();
+  }