AdobeDocs / AdobeDocs/experience-platform.en

Impact of computed attributes on the Policy Enforcement Service (PES) execution.

Open Beginner friendly
#515 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
11
Forks
148
PR merge metrics
No merged PRs in 30d

Description

A recent case highlighted how Computed Attributes fields, derived from labelled fields, are added in the PES node process.
Contribution of computed attributes is mentioned in this CA article, but is missing any reference in the main Automatic Enforcement article.

I warmly suggest to include an explicit reference to the CA contribution to the PES process in this article as well.
For reference:

- [CA FAQ](https://experienceleague.adobe.com/en/docs/experience-platform/profile/computed-attributes/faq#how-are-data-usage-labels-applied-on-computed-attributes).
- Case: E-002117040, PLATIR-62114

Issue in ./help/data-governance/enforcement/auto-enforcement.md

Contributor guide

Open the contributing guide

Research direction

Start with ./help/data-governance/enforcement/auto-enforcement.md and compare its treatment of the PES process with the linked CA FAQ. Add an explicit reference explaining the contribution of Computed Attributes to PES execution, then verify that the Automatic Enforcement article contains the intended cross-reference and renders correctly.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
82/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.