Visibility issue reference field in Agent Workspace on a domain separated instanceSummaryWhen we use the 'current' object in a reference qualifier for a reference field, it works fine on the native UI 16. However, the 'current' object fails on the Agent Workspace.ReleaseSeen in Paris & Quebec. Fixed in Rome.InstructionsLet's take the interaction table for example, on a domain-separated instance. User A creates a new interaction, who belongs to domain A. While creating a new incident, we have to fill the Assigned To field. In the dictionary entry for Assigned To add the reference qualifier as - javascript:"sys_domain="+ current.sys_domainAs user A when we click on the Assigned To field from native UI, it shows us all the users from domain A. (working as expected)Now navigate to Workspace, and try creating a new interaction.Click on the Assigned To field.You will see users from the global domain, but not from domain A.If you type the names, it will not show the results from domain A.Related LinksInstead of using a current object in the reference qualifier, use a before query business rule on the sys_user table as below. Condition - !gs.hasRole('admin')Script -(function executeRule(current, previous /*null when async*/) {current.addQuery('sys_domain', gs.getUser().getDomainID());})(current, previous);