Skip to content

docs(sage50): remove support-enablement steps from the restart page - #1886

Merged
pmckinney-codat merged 1 commit into
mainfrom
exp-321-sage50-restart-docs
Aug 17, 2026
Merged

docs(sage50): remove support-enablement steps from the restart page#1886
pmckinney-codat merged 1 commit into
mainfrom
exp-321-sage50-restart-docs

Conversation

@pmckinney-codat

@pmckinney-codat pmckinney-codat commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

What

Rewrites the Sage 50 restart page so it just explains how to restart the connector. The Enable the restart connector link section (get the connector ID from your user → raise a support ticket → Support enables it) is gone, along with the connector-ID screenshot.

Why

The page told customers the Restart connector link is "disabled by default" and has to be turned on per-connector by Codat Support. That's no longer true in the code:

  • The link lives in the shared connector SDK's About overlay — Codat.Connector.UI.WPF/Overlays.xaml binds the hyperlink straight to RestartConnectorCommand with no visibility or enablement condition, and AboutConnectorViewModel has no gate either.
  • connector-sage50 never reads the per-connector allowRestart setting; its only feature gating (IFeatureServiceStorage, fed by EnabledFeatures on the pending-actions poll) is used for an invoice push feature.
  • sage50-service still stores and serves the allowRestart setting (connectorSettings table, partition sage50), but nothing in it branches on the value. RestartRequested on pending-actions comes from the connectors-api remoteRestarts endpoint — that's the admin-triggered remote restart, not this toggle.

So the toggle only survived in the docs and some stale table rows. The original ask (Feb 2023) was that publicly documenting a support-enabled restart made the connector look unreliable.

Acceptance criteria

AC Status
1. Connector keeps its place in the About sections Already true — the restart link is in the About overlay for all connectors
2. Public docs updated or removed This PR
3. New connector can restart from the UI Already true — link is unconditional at HEAD
4. Connector without restart enabled gets it on update Already true — no gate to satisfy
5. Connector with restart enabled keeps it on update Already true — the setting is ignored either way

Checks

  • prettier --check on the changed file: clean
  • cspell on the changed file: clean

🤖 Generated with Claude Code

The Restart connector link is available to every Sage 50 Accounts
Connector user — nothing in connector-sage50, connector-sdk or
sage50-service gates it on the per-connector allowRestart setting any
more. Remove the "Enable the restart connector link" section and the
connector ID steps, and keep the instructions for using the link.

EXP-321

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Link check results:

[]

@github-actions

github-actions Bot commented Aug 17, 2026

Copy link
Copy Markdown
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-08-17 13:35 UTC

@pmckinney-codat
pmckinney-codat marked this pull request as ready for review August 17, 2026 13:15
@pmckinney-codat
pmckinney-codat merged commit 1558f9a into main Aug 17, 2026
7 checks passed
@pmckinney-codat
pmckinney-codat deleted the exp-321-sage50-restart-docs branch August 17, 2026 13:35
@pmckinney-codat pmckinney-codat changed the title docs(sage50): remove support-enablement steps from the restart page [EXP-321] docs(sage50): remove support-enablement steps from the restart page Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants