Business rule "SRM team member added notification" condition evaluates to null when main SRM application is not installed<!-- /*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: ; } } .kb-wrapper { font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; max-width: 100%; color: #000; } .kb-wrapper h2 { font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 4px; margin-top: 24px; margin-bottom: 8px; } .kb-wrapper p, .kb-wrapper li { font-size: 12pt; } .kb-wrapper ul { padding-left: 24px; } .kb-wrapper .steps-list { list-style: none; padding-left: 0; counter-reset: step-counter; margin: 10px 0 16px 0; } .kb-wrapper .steps-list li { counter-increment: step-counter; display: flex; align-items: flex-start; margin-bottom: 8px; } .kb-wrapper .steps-list li::before { content: counter(step-counter); display: inline-flex; align-items: center; justify-content: center; min-width: 24px; height: 24px; border-radius: 50%; background-color: #032D42; color: #63DF4E; font-weight: 700; font-size: 11pt; margin-right: 10px; flex-shrink: 0; margin-top: 3px; } .kb-wrapper .callout-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 14px; margin: 12px 0; border-radius: 0 4px 4px 0; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 5px; border-radius: 3px; font-size: 11pt; font-family: monospace; } .kb-wrapper .error-block { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 10px 14px; border-radius: 4px; font-family: monospace; font-size: 11pt; line-height: 1.5; word-break: break-word; margin: 10px 0; } .kb-wrapper a { color: #032D42; } .kb-wrapper .link-disclaimer { font-size: 10pt; font-style: italic; color: #555; display: block; margin-top: 2px; } Issue When saving a record that writes to the sys_user_grmember table — for example, when manually adding a user to an approval group — the following error is logged and the save may not complete correctly: Condition 'Condition: new sn_sow_srm.SRMTeamUtil().isSRMTeam(current.group.getRefRecord())' in business rule 'SRM team member added notification' on sys_user_grmember: evaluated to null; skipping business rule Symptoms The error message above appears when a sys_user_grmember record is savedActions such as manually adding an approver or group member may not save correctlyThe behavior affects all users regardless of role Facts The business rule SRM team member added notification is part of the Service Operations Workspace Service Reliability Management (SRM) Common application (sn_sow_srm_common)The business rule's condition makes a cross-scope call to SRMTeamUtil.isSRMTeam(), which is defined in the main Service Reliability Management (SRM) application (sn_sow_srm)When the main SRM application is not installed, the cross-scope reference cannot be resolved, causing the condition to return nullThe SRM Common application may be installed automatically as a dependency of other applications — such as Discovery Admin Workspace (sn_disco_workspace) — without the main SRM application being present Release Zurich Cause The Service Operations Workspace Service Reliability Management (SRM) Common application (sn_sow_srm_common) was installed as a dependency of another application — most commonly Discovery Admin Workspace — without the main Service Reliability Management application (sn_sow_srm). The SRM Common application contains a business rule whose condition makes a cross-scope call into the main SRM scope. When the main SRM application is absent, this call cannot resolve, the condition evaluates to null, and the business rule is skipped — interrupting the sys_user_grmember save operation. Resolution Choose the applicable option based on whether the Service Reliability Management application is required on the instance. Option 1 — Install SRM (if SRM functionality is required) Navigate to System Applications > All Available Applications.Search for Service Reliability Management (plugin ID: sn_sow_srm).Install the application. This provides the SRMTeamUtil script include and permanently resolves the cross-scope dependency. Option 2 — Uninstall SRM Common (if SRM functionality is not required) Warning: Before uninstalling, verify that no other installed applications depend on SRM Common. Removing it from an instance where another application — such as Discovery Admin Workspace — depends on it may affect that application's functionality. Navigate to System Applications > All Available Applications.Search for Service Operations Workspace Service Reliability Management (SRM) Common.Uninstall the application. This removes the business rule entirely, permanently stopping the error. Related Links Service Reliability Management overviewManage applications in the App Manager