Client and possibly other Scripts do not run as expected in Domains other than Global - Support and Troubleshooting

Client and possibly other Scripts do not run as expected in Domains other than Global Description  Symptoms Client and other possibly Scripts do not run as expected in Domains other than Global

Release All releases supporting Domain Separation

Cause System is following out of box Domain Separation's Process Separation rules and working as designed

Resolution All tables containing a 'sys_overrides' field follow Process Separation rules within Domain Separation In addition, when the 'glide.sys.domain.use_record_domain_for_processes' system property is set to True, the system uses the Record's domain to apply process separation rules As a result, for example when an onLoad Client Script runs, the system checks for a Script in the record's domain, and if it exists, it applies that version of the Client Script In case that client script (whose domain equals the current session's domain) is INACTIVE that Script will not run because of the Active=False setting and is expected behavior This is because the system evaluates this client script and since it is inactive it ignores the script Additional Information KB0684442 - Can Contain-Domain records be available for Process Separated data in Domain Separation KB0676353 - Application support for domain separation KB0662346 - Tips for Domain Separating 'NON Out of Box Domain separated' Tables