The Business Rule "Prevent creating duplicate vault" does not exclude the current record during updates, causing it to falsely detect a duplicate<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue:When updating the FQCN field in the Vault Configuration table, the system returns the following error: "Vault with name = [Vault Name] or fqcn = [FQCN] already exist. Provide a unique name and fqcn for new vault." The update fails even though there is no actual duplicate record.Steps to Reproduce:1. Navigate to the Vault Configuration table.2. Select an existing vault record.3. Attempt to update the FQCN field.4. Observe that the update is blocked and the above error message is displayed.Cause:The issue is caused by the “Prevent creating duplicate vault” business rule. The business rule checks for existing records with the same name or FQCN but incorrectly includes the current record being updated in its check.Works correctly when creating a new record.Prevents updates because it treats the same record as a duplicate. /sys_script.do?sys_id=d621de7a87ea0e102c47fcc4dabb3525&sysparm_record_target=sys_script&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=nameCONTAINSPrevent+creating+duplicate+vault%5EORDERBYname 33 var vault = new GlideRecord('vault_configuration');34 vault.addQuery('name', current.name).addOrCondition('fqcn', current.fqcn);35 vault.query();36 if (vault.hasNext()) {37 gs.addErrorMessage(gs.getMessage('Vault with name = {0} or fqcn = {1} already exist. Provide an unique name and fqcn for new vault.', [current.name, current.fqcn]));38 current.setAbortAction(true); //This prevents records from getting saved into database.Resolution/Workaround:Temporary Workaround: Deactivate the Prevent creating duplicate vault business rule, update the FQCN value, and then reactivate the business rule.Permanent Fix: The defect is tracked under PRB1904023, which updates the business rule logic to exclude the current record during duplicate checks. This fix will be applied in the Australia version.