Undocumented choice Reference Cascade Rule for initiated_from field in sm_order and sm_task tablesDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms There is an undocumented choice Reference Cascade Rule for initiated_from field in sm_order and sm_task tables. The documentation did not have an explanation for it. Release All available releases Cause It is an invalid Reference Cascade rule. Reference Cascade rule for initiated_from field is not suppose to have any restriction when the referencing record is deleted. Resolution The value "restrain" actually is not a valid value in the DB, therefore the behavior defaults to none - not having any cascade effect (expected behavior). If this value is set to "restrict", the behavior will start restricting cascade deletion when the referencing record is deleted, which we is not intended. So no action is required to resolve the issue. Additional Information https://docs.servicenow.com/csh?topicname=t_CascadeDeleteRules.html&version=latest