Saving the same Content to two different CONREQITM records displays error: 'Each content can only have one associated content request item.' Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } As part of the 'Content Governance' application, Content Requests (CR) and Content Requested Items (CRI) records can be created using the out-of-box 'Content Request' record producer. The CRI has a 'Content' Field. Selecting a Content already associated to another CRI and saving will fail with error: "Each content can only have one associated content request item." Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This is working as expected and enforced by out-of-box business rule: 'Allow one CONREQITM to one Content only'. The 1:1 relationship between Content Request Item (CRI) and Content is a design assumption baked into the permission utilities, governance state transitions, and ACLs across both the sn_cg (Content Governance) and sn_cd (Content Delivery) scopes. Deactivating the BR removes the validation but leaves the rest of the platform unable to behave deterministically when multiple CRIs reference the same Content. The result is user-visible failures — denied approvers, stalled review transitions, and cascading edit locks — rather than a clean "multi-request" workflow. Data Model The dictionary definition of sn_cg_content_request_item carries the hint "Single content item to be worked on and delivered for content requests", indicating that the 1:1 model is the platform's intentional design — the Business Rule enforces it rather than defining it. Direct Code Impact 1. cg_PermissionUtils Script Include (sn_cg scope) File: sys_script_include_efac89cc77370110df94ebeaae5a990e.xml Two methods perform Content → CRI lookups that assume a single result: isRequestor(contentId, userId) — determines if a user is a requestor for a content isApprover(contentId, userId) — determines if a user is an approver for a content Both use setLimit(1) when querying by content. With multiple CRIs sharing the same Content, they return an arbitrary CRI, leading to incorrect permission determinations (the right approver can be denied; the wrong approver can be granted). 2. cd_ContentGovernanceUtils Script Include (sn_cd scope) The same 1:1 assumption exists in _getContentRequestItemInOpenOrWIPStateByContent, which drives: meetsSendForReviewCriteria setContentRequestItemStateToInReview getContentRequestItemByContentId Impact: Send-for-Review eligibility and the In-Review transition will only act on the first matched CRI; sibling CRIs silently stay behind in Open/WIP. 3. ACL Breadth Both cg_PermissionUtils and cd_ContentGovernanceUtils are referenced from ACLs in both the sn_cg and sn_cd scopes. Permission failures from non-deterministic lookups will surface in both the Governance UI and the Content Delivery UI. Functional Impacts Reverse lookup ambiguity: Any "given this Content, find its CRI" lookup becomes non-deterministic, affecting form widgets, governance state queries, and approver routing. Cascading edit locks: Once any one CRI on a shared Content enters In Review / Ready to Publish / Published, the Content record locks for non-admins — and every sibling CRI pointing at that Content becomes effectively un-editable as well. Form display: Ambiguity in determining which CRI to display for a given Content. Governance state: State transitions assume a single active CRI per Content; siblings will drift out of sync with no UI surface tying them together.