Loading...
Loading...
With the following domain configuration in mind: GLOBAL -> TOP -> ACME -> domain1 | | UserA Record1 If glide.sys.domain.use_record_domain_for_data is set to false and UserA modifies Record1 a flow triggered on Record1 will run in domain1 and it will not have visibility in to TOP or ACME like the user. Steps to Reproduce 1. install domain seperation plugin (com.glide.domain.domain_center and com.glide.domain.msp_extensions.installer) 2 . Import attached update set 3. Open any incident which is in TOP/ACME, if not modify any incident's domain 4. log instance using admin user which belongs to global. 5. modify incident which is in TOP/ACME domain, remember user is in domain "global". 6. inspect Problem table, it will create two record, EXPECTED: Both record should have same domain ACTUAL: record created via FD have different domain than record created by BR. Flow create a problem record and BR "DEF0252513" create a problem record Workaround 1. Create a BR (Business rule) on sys_flow_context as given below 2. In same BR under Advance option put below script (function executeRule(current, previous /*null when async*/) { if (String(gs.getProperty('glide.sys.domain.use_record_domain_for_data')) == 'false') { current.setValue('sys_domain', gs.getUser().getDomainID()); } })(current, previous); 3. Save the Business rule
PRB1534243
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.