Before submitting this PR:

• Jira ticket is present in the title or in the description
• All items marked FILL IN are filled
• Any required labels are applied (Bug bash, exclude release notes, backport, etc.)
• Testing/reviewer instructions are filled out

About this change:

Jira Ticket: https://pagerduty.atlassian.net/browse/RPL-27

Purpose of the Changes:

Improve the ServiceNow plugin to prevent excessive delays when loading the list of groups from ServiceNow. Avoid unnecessary API calls to Snow when the information is not required.

Customer Impact:
Significantly reduces the time it takes to load the list of groups from ServiceNow, enhancing productivity and eliminating unnecessary delays.

Improves user satisfaction by providing a smoother and faster integration between Rundeck and ServiceNow.

Release Notes:

Kind of Change

• Bug Fix
• Enhancement/New Feature/Behavior
• Maintenance
• Backport (Other sections can be skipped)
• Other... (FILL IN)

Development Checklist

• Unit Tests added for modified/added code
• Documentation PR:
• Documentation Not needed

Specific Considerations:

• Feature Flag required (New behavior), name:
  • The new behavior is OFF by default (flag is false by default)
• API Functional Tests added (API Changes)
• API Version Increment needed (implies Documentation needed)

GUI Changes:

• No GUI Changes, OR
• Selenium UI Tests added

Testing:

Start a Rundeck instance.
Configure the ServiceNow plugin at the project level.
Create a job.
Add a notification to create an incident in ServiceNow.
Previously, loading the groups took 6–8 seconds. This time should now be significantly reduced.

ServiceNow Instance:
https://pagerduty.atlassian.net/browse/RPL-27?focusedCommentId=795301

Acceptance Criteria:

The ServiceNow plugin should function correctly when:

• Creating Snow notifications
• Modifying Snow incidents
• Snow plugin should be able to create notification
• Snow plugin should be able to execute workflow step

QA/Bug Bash Needed?

• manual-qa/bug-bash Label is applied, OR
  • Not needed

Manual QA Notes:

Reviewer Checklist

Functionality (choose one):

• I built and tested locally and code behaves as expected: OR
  • I tested via via Docker image, OR
  • It was not necessary, reason:

Code:

• Meets quality and style guidelines
  • Has complete Unit tests
  • Has complete Functional Tests