Repository navigation
feat(servicenow): add Test and Prod realm lifecycle to Connect - #509
Open
DapheneShao wants to merge 3 commits into
Open
DapheneShao wants to merge 3 commits into
DapheneShao wants to merge 3 commits into
Conversation
Discover the promoted Test or Prod sibling of the recorded Dev agent from natural language or an agent link, reuse the Dev tenant foundation, and check Connections, Runtime configuration and Maker validation per realm. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Remove the Dev-Ready and Test-Ready gates; Dev record is an optional reference. Per-item read-only connection, topic and portal checks per realm. Connection problems are blocked with no repair or handoff and never reuse the Dev connection. Admin-confirmed values are retained only when they still apply to the agent, tenant and instance. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Add the realm intro, Test-pane request, Done follow-up, completion scope, destination question, denied vs inconclusive access, and J/K/L/M recovery wording. Wording only; no state changes. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
DapheneShao
pushed a commit
that referenced
this pull request
Nov 18, 2026
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
4 of 8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds Test and Prod lifecycle support to ESS ServiceNow Connect (HRSD and ITSM), following the Workday Connect DEV/TEST/PROD journey. The maker says the agent was promoted to Test or Prod, or pastes the Test or Prod agent link, in the same
/connectServiceNow flow (no new slash commands). The controller proves the exact promoted sibling of the recorded Dev agent; a Dev link or a link outside the family is rejected.Test and Prod checks are independent of Dev, so a connection that is on in Dev but off or stale in Test or Prod is caught:
Maker-visible wording follows the ServiceNow Connect UX spec (S5): realm intro, Test-pane request, a "Done"-only reply is never recorded as pass or fail and gets the follow-up question, a "Which destination" question when the realm is unclear, denied vs. inconclusive access messages, a completion message that says what was and was not verified, and short recovery rules (wrong environment tested, expected empty result, identity mismatch, empty HR service areas). Wording only; no state changes.
Unchanged: Dev behavior and wording, Setup, Workday. Trial merge with #507 is clean, so this PR targets
main.Related issue
Refs #507
Type of change
Testing
ruff check .passed.pytest tests/scripts/test_connect_servicenow_da.py tests/scripts/test_connect_servicenow_realms.py tests/setup: 639 passed, 1 failed (the known baselinetest_workday_topic_activation_uses_complete_mapped_scope).Checklist