GlideContentPage object is not exposed to scoped applicationsDescriptionThe current_page object is not available in Scoped Applications, causing the following exception: Evaluator: java.lang.SecurityException: GlideContentPage is not allowed in scoped applicationsCaused by error in <refname> at line 2 1: ==> 2: var current_page = new GlideContentPage(e92ead1f4f910200e5ec14ee0310c712); 3: gs.info(123); 4: gs.info(current_page.getURLSuffix());Steps to Reproduce 1. Observe the code below displayed in a dynamic content block contained in a Global scope UI Page: <tr> <td>URL Suffix</td> <td>${current_page.getURLSuffix()}</td> <td>$[current_page.getURLSuffix()]</td> </tr> <tr> <td>Page Title</td> <td>${current_page.getTitle()}</td> <td>$[current_page.getTitle()]</td> </tr> 2. Switch into a scoped context. Observe nothing displays. 3. When instantiating a GlideContentPage object and then referencing the objects, the following line causes the Java exception: var current_page = new GlideContentPage(e92ead1f4f910200e5ec14ee0310c712); 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 apologize for any inconvenience.Related Problem: PRB646957