Skip to content

KC-1469: Enterprise root-node isolation is not handled correctly - #2380

Merged
sk-keeper merged 1 commit into
releasefrom
fix/KC-1469
Sep 18, 2026
Merged

sk-keeper merged 1 commit into
releasefrom
fix/KC-1469

Conversation

@IliaTheKeeper

Copy link
Copy Markdown

Enterprise root-node isolation is not handled correctly. The root node’s visibility restriction is returned in GeneralDataEntity.restrictVisibility, rather than the root Node entity, but Commander only reads the node-level value. As a result, root isolation can display incorrectly and toggling root isolation sends the root node ID instead of the enterprise-level identifier (0), causing unreliable behavior.

This patch includes the following:

  • Load and map generalData.restrictVisibility onto the enterprise root node.
  • Preserve child-node isolation handling from node-level data.
  • Toggle root isolation using node ID 0; continue using actual node IDs for child nodes.
  • Force-refresh enterprise data after isolation changes and report the verified resulting state or a no-op warning.
  • Add unit coverage for root/child isolation loading, root toggle requests, and unchanged server responses.

@sk-keeper
sk-keeper merged commit 98d24ef into release Sep 18, 2026
4 checks passed
@sk-keeper
sk-keeper deleted the fix/KC-1469 branch September 18, 2026 18:05
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