Loading...
Loading...
A condition script on a List Control record for Related Lists can evaluate differently under certain criteria: Related list is between tables in different scopes The script uses the the variable name answer, and accesses the parent object at some point Only happens when clicking on a UI Action within the related list Steps to Reproduce 1. Create two tables in different scopes (i.e. 'table_1' and 'table_2'). 2. Create a sys_relationship record: Name: Test Relationship Applies to table: table_1 Queries from table: table_2 3. Go to the form of table_1, Configure > Related Lists, and add a related list for table_2. 4. On table_1 form, in the newly added related list, go to Configure > List Control. 5. On the new form that is loaded, add the Omit new condition field. 6. Add the following script to Omit new condition field: var answer = true; gs.error("ERROR1"+parent.sys_id); answer=false; answer; 7. Back on the form for table_1, on the related list, click New. You will be redirected back to table_1.do and with an error message "Action not authorized".
This problem is under review and targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form. The workaround is to wrap the condition in an IIFE (Immediately Invoked Function Expression): (function () { var answer = true; gs.error("ERROR1"+parent.sys_id); answer=false; answer; })();
PRB1581607
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.