The "current" object is not available in Advanced View Rule scripts although selectable in the script editorDescriptionThe "current" object is not available in Advanced View Rule scripts, even though it is selectable in the script editor.Steps to Reproduce 1. Navigate to System UI > View Rules.2. Create a new View Rule.3. Check the Advanced checkbox to make the script field available.4. Set the table to "incident".5. Toggle on the tree picker in the script editor.6. Expand the field group.7. Select "Activity due". When the tree picker in the script editor is toggled on, the fields group is available. When the user selects "Activity due", "current.activity_due" is inserted into the script. This is confusing as the tree picker should provide functions and fields that are actual available to use in the script.WorkaroundAfter carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience. If needed to access the current record being viewed by the user in order to determine which view to use, first try using the condition builder without scripting. If more complex business logic is required, for example to check the role of the user and check certain values in the current glide record, then use a script without the "current" object. The following example sets the view based on the user's role and the urgency of the incident record: (function overrideView(view, is_list) { var url = gs.action.getGlideURI().getMap(); var sysId = url.get('sys_id'); //access the GlideRecord of the currently viewed record var gr = new GlideRecord('incident'); gr.get(sysId); //if the incident is urgent change the view to major incidents if(gs.hasRole('itil') && gr.urgency == 1){ answer = "Major Incidents"; } else { answer = "ess"; } })(view, is_list); Related Problem: PRB1236269