Standard Change Templates values are not being set on change request when change is created from specific userIssue When a user (A) from one of customer domains tries to use a standard change template that is part of their domain, they can see the standard change record producer, but not the standard change template (i.e the actual fields being set by the standard change).CauseBusiness rule - "Apply standard change template" - https://<instance_details>.service-now.com/sys_script.do?sys_id=54a5d058eb2312002a7a666cd206fe9c is getting skipped because condition which check for template version fails.This business rule fail because user "A" do not have access to record associated to standard change template from table "std_change_producer_version" ResolutionConfigure Standard Change Template in accessible domain to resolve this Issue.