Skip to content

Conversation

@glenn-rodgers-sf
Copy link
Contributor

Writer's Quality Checklist

Before merging your PR, did you:

  • Run spell checker
  • Run link checker to check for broken xrefs
  • Check for orphan files
  • Perform a local build and do a final visual check of your content, including checking for:
    • Broken images
    • Dead links
    • Correct rendering of partials if they are used in your content
    • Formatting issues, such as:
      • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
      • Messed up tables
      • Proper indentation
      • Correct header levels
  • Receive final review and signoff from:
    • Technical SME
    • Product Manager
    • Editor or peer reviewer
    • Reporter, if this content is in response to a reported issue (internal or external feedback)
  • If applicable, verify that the software actually got released

@glenn-rodgers-sf glenn-rodgers-sf requested review from a team and marinasasso as code owners June 17, 2025 18:41
@glenn-rodgers-sf glenn-rodgers-sf changed the base branch from flex-1-10-release to pdk-1-4-release June 17, 2025 18:42

PDK provides functions to report a policy violation. Reported policy violations appear in Anypoint Monitoring.

A request can only have one active policy violation. If a previous policy reports a policy violation, generating a new policy violation overrides the previous violation. If multiple policies generate policy violations for a single request, only one policy violation appears in Anypoint Monitoring.
Copy link
Contributor

@Cristian-Venticinque Cristian-Venticinque Jun 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A request can only have one active policy violation. If a previous policy reports a policy violation, generating a new policy violation overrides the previous violation. If multiple policies generate policy violations for a single request, only one policy violation appears in Anypoint Monitoring.
Only one policy violation can be active for a request at a time. When a new violation occurs, it replaces any existing violation. If multiple policies generate violations, only the most recent one appears in Anypoint Monitoring.

This paragraph is a bit repetitive, I've suggested a rewording. Please check if it remains accurate.

Copy link
Contributor

@Cristian-Venticinque Cristian-Venticinque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with suggestions.

glenn-rodgers-sf and others added 2 commits June 18, 2025 10:22
Co-authored-by: Cristian-Venticinque <46459586+Cristian-Venticinque@users.noreply.github.com>
@glenn-rodgers-sf glenn-rodgers-sf merged commit ed467ba into pdk-1-4-release Jun 18, 2025
4 checks passed
@glenn-rodgers-sf glenn-rodgers-sf deleted the W-18359572-policy-violations-gr branch June 18, 2025 14:28
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.

3 participants