Skip to content

W-23907611 docs: draft Policy Write documentation - #548

Open
luanamulesoft wants to merge 5 commits into
latestfrom
W-23907611-document-policy-write
Open

W-23907611 docs: draft Policy Write documentation#548
luanamulesoft wants to merge 5 commits into
latestfrom
W-23907611-document-policy-write

Conversation

@luanamulesoft

Copy link
Copy Markdown
Contributor

Summary

Drafts documentation for the Policy Write initiative (MS2026-08-R2 / Dreamforce), covering all 8 in-scope user stories. Single PR for both affected exp- topics.

  • exp-governance-policy-library-apply.adoc — rewritten from a fully commented-out draft into an active topic: apply a universal policy template (F1), edit native policies with the two-tier schema/read-only fallback (F2), delete with confirmation (F3), enable/disable (F4), permissions (F5), the in-progress workflow lock (F7), and the read-only out-of-scope state (F6).
  • exp-services-view-details.adoc — Policies-tab section now notes native-policy management actions and read-only out-of-scope policies, cross-linked to the apply/manage topic.

Grounding

Content is grounded in the mulesoft-omni-app UI code. This is a draft — details that could not be verified in code are flagged inline with TODO(W-23907611) comments and must be confirmed with the PM before the DRAFT banner is removed and the topic is published:

  1. The universal template list + per-gateway native mappings (APIM-owned, not in Omni code).
  2. Which feature flags are ON for GA, per gateway.
  3. The enable/disable gateway support matrix.
  4. Human-readable required permission/role names.
  5. Whether applying policies from the API Instance page is in scope for this release.

AWS write is out of scope for this release.

References

🤖 Generated with Claude Code

Rewrite exp-governance-policy-library-apply.adoc from a fully commented-out
draft into an active topic covering the Policy Write scope (MS2026-08-R2):
apply a universal policy template, and edit/delete/enable-disable native
policies, plus the in-progress workflow lock and read-only out-of-scope state.

Update the Policies-tab section of exp-services-view-details.adoc to note the
new native-policy management actions and read-only out-of-scope policies, and
cross-link to the apply/manage topic.

Content is grounded in the mulesoft-omni-app UI code. Details that could not be
verified in code (universal template list + per-gateway native mappings, GA
feature flags, enable/disable support matrix, permission role names, and the
API Instance page apply entry point) are marked with TODO(W-23907611) comments
for PM confirmation before publishing. Gap analysis: Policy Write —
Documentation Gap Report (2026-08-18).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@luanamulesoft
luanamulesoft requested a review from a team as a code owner August 18, 2026 13:24
luanamulesoft and others added 4 commits August 18, 2026 16:53
…-policy-write

# Conflicts:
#	modules/ROOT/pages/exp-governance-policy-library-apply.adoc
Add coverage for the Activity log tab surfaced by the two additional scope
PRDs (Policy Write / Unified Policy Catalog) and verified in code
(ActivitiesTab.tsx, activitiesTab i18n). Applies are asynchronous and tracked
(Apply/Update/Toggle/Remove; Running/Completed/Failed). Cross-linked from the
apply flow and the instance Policies tab. Left as DRAFT with a TODO on the
feature-flag/external-provider gating and no actor field (not a full audit trail).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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