Getting 'Data Policy Exception: The following fields are mandatory: Event' error while trying to add a plan to an 'Exercise' event recordIssue <!-- /*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: ; } } After upgrading to Australia, the 'Data Policy Exception: The following fields are mandatory: Event' error message is displayed while trying to add a plan to an 'Exercise' event record . The error is seen in mskdev and mskprod instances but not in the msktest instance and all these 3 instances are on the same Australia versions. I checked the business rules and it looks like msktest has more OOB business rules while mskdev and mskprod does not have the same as seen in msktest. Can you check and let me know the issue? 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: ; } } Australia Patch 2 Hot Fix 1 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: ; } } The error is raised by the out‑of‑the‑box Data Policy on the sn_recovery_activated_plan table which (correctly) requires the parent Event reference.In an OOB BCM flow that field is populated by one or more Before Insert Business Rules on sn_recovery_activated_plan that read the current Exercise event from the workspace context and copy it onto the new activated‑plan record before the Data Policy validates.Your own observation that msktest (where the flow works) has more OOB Business Rules than mskdev / mskprod confirms that one or more of those Before‑Insert BRs has been deactivated, deleted, or skipped during a prior upgrade in dev and prod — so the Event field is empty at insert time and the Data Policy blocks the row.The Australia family release introduced no functional changes to BCM vs. Xanadu/Washington DC, so the Australia upgrade did not cause the gap — it only re‑validated the OOB Data Policy that has always been there.Recommended solutionIn mskdev, navigate to System Definition → Business Rules, filter Table = sn_recovery_activated_plan (and the related sn_recovery_event, sn_recovery_event_asset tables).Compare this list with the same view in msktest. Identify the BRs that are active in test but inactive/missing in dev (focus on Before Insert rules that touch the event field or call the EventRecordAPI / EventUtilBase / EventTaskUtil script includes).For each customized record, open it → Versions → Revert to the Base System version (or simply set Active = true if the only difference is the Active flag). Capture the change in an Update Set.Validate by creating a new Functional exercise and adding a plan — the Data Policy exception should no longer occur and tasks should generate automatically.Interim workaroundUntil the BR is restored you can create the Activated Plan directly from the classic list view (sn_recovery_activated_plan.list → New) with the Event field populated manually with the Exercise record — the plan then attaches and tasks generate normally.