Service Exchange consumer revision is missing a catalog UI policy when Impact Scan Engine real-time validation is enforcedIssue After a remote record producer is checked out and published on the Service Exchange provider, the new revision on the consumer lists one fewer catalog UI policy than the provider. Republishing does not restore the missing policy. Symptoms The consumer remote record producer revision shows one fewer catalog UI policy than the same revision on the provider.The missing UI policy exists on the consumer with the provider's sys_id, but catalog_item is empty, run_scripts is false and the short description is empty. It was created by system at the time of the consumer build.The transport queue entry for the revision is processed with no error.No error appears in the system log for the build.Every new revision drops the same UI policy. A revision can look complete only when an administrator created the record on the consumer before the build. Facts Which UI policies are affected? Catalog UI policies whose scripts contain a pattern that an active Impact Scan Engine definition flags at the Error or Warning level. Other UI policies on the same item build normally. Which instances are affected? Consumer instances with the Impact Scan Engine installed and Enforce real time validation turned on. Did the UI policy change? Not necessarily. A policy that built before can start dropping after new Scan Engine definitions are added or the Scan Engine properties change. Release Observed on the Australia release with Impact Scan Engine 6.0.3 and Service Exchange consumer 2.3.29. Not limited to these versions. Cause The consumer builds a revision by inserting each catalog UI policy delivered from the provider. With Enforce real time validation turned on, the Impact Scan Engine business rule Scan Engine - Exception Reason runs before every insert on sys_metadata, including inserts made by a system process. It checks the record's scripts against the active scan definitions for that table, and it blocks the insert when an unresolved Error or Warning finding is present. For example, definition sn_SE10058 ("g_form.setVisible should be replaced with g_form.setDisplay", level Error) applies to catalog_ui_policy. A UI policy whose script calls g_form.setVisible() is blocked. The build then continues without reporting the blocked insert, which leaves the policy without its catalog item, so it is not attached to the revision. Resolution Identify the finding. Compare the missing UI policy's script on the provider (script_true and script_false) with the active Scan Engine definitions that apply to catalog_ui_policy (sn_se_applicable_table), and note any Error or Warning definition that matches.Have the Scan Engine administrator choose one of the documented controls: Resolve the finding in the UI policy's script on the provider, following the definition's Steps to resolve issue guidance.Add the table to Excluded tables on the Scan Engine Properties page. This removes real-time scanning for every record on that table, and scheduled scans still include it.Turn off Enforce real time validation on the Scan Engine Properties page. Check out and publish the remote record producer on the provider, then confirm the new consumer revision lists the same number of catalog UI policies as the provider and the policy's catalog_item is populated. Related Links Configure real-time scanning propertiesPrevent technical debt with real-time code fixesCreate configuration revisions