* Add UI knowledge: client-expression in-list and Role Center AccessByPermission
Two ui articles with compiled good/bad samples:
- page-client-expression-must-not-use-in-list: an `in [...]` list in
Enabled/Visible/Editable/StyleExpr is rejected (AL0573 on actions,
groups and parts; AL0322 on fields); remediate with an or-chain or a
global Boolean, not a procedure call. Plain comparisons stay valid.
- rolecenter-permission-gating-must-use-accessbypermission: Role Center
pages and pageextensions of them cannot host triggers/procedures
(AL0378/AL0569); gate parts by permission with AccessByPermission,
with the UI Elements Removal and non-security-boundary caveats.
Wired into al-ui-review worklist tokens and high-signal mappings, and
registered both pairs in the ui review-fixtures override.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Address review: OnAfterGetCurrRecord for action state, RC gating nits
- page-client-expression-must-not-use-in-list: recompute action/group/part
state in OnAfterGetCurrRecord (OnAfterGetRecord runs per row), cite
EDocumentLogs and concrete or-chain examples, note HideValue and that
the property list is not exhaustive; good sample uses OnAfterGetCurrRecord.
- rolecenter-permission-gating-must-use-accessbypermission: clarify
LicenseFile vs LicenseFileAndUserPermissions removal, cite Business
Manager RC Control96, samples gate a part the RC does not already have.
- al-ui-review: add ReadPermission/WritePermission tokens.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
