Log full warnings related to 'glide.ui.polaris.follow.enabled' and BR 'Polaris follow event queue'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 08:05 AM - edited 03-11-2024 08:07 AM
Hi all,
We noticed our logs are full of below warning, over a 1000 a day. All related to a Business Rule 'Polaris follow event queue' and a system property 'glide.ui.polaris.follow.enabled'.
On checking this property, I noticed it does not exist in our Instance, so by default it is seen as 'true' in the Business Rule trigger. I can not find any documentation on what it does ....
However I would like to get rid of this warning. Is there any way to fix this without impacting current functionality?
Will it hurt just to set the property 'glide.ui.polaris.follow.enabled' to 'false'?
Or is there already something broken in my instance since most of the records in my live_group_profile table do not have the attribute 'table' filled in which is causing this Business Rule to generate a warning.
Anybody who can help out here?
Warning message
org.mozilla.javascript.EvaluatorException: GlideRecord.setTableName - empty table name (sys_script.02af2d1f77aa1110866ea2059f5a99c8.script ➚; line 😎
EvaluatorException(JavaScript evaluation error on:
(function executeRule(current, previous /*null when async*/ ) {
var gr = new GlideRecord('live_group_profile');
gr.setWorkflow(false);
gr.addQuery("sys_id", current.group);
gr.query();
gr.setWorkflow(true);
if (gr.next()) {
var updatedRecord = new GlideRecord(gr.table);
updatedRecord.addQuery("sys_id", gr.document);
updatedRecord.query();
if (updatedRecord.next())
gs.eventQueue("polaris.follow.update", updatedRecord, null, null);
}
})(current, previous);
)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2024 01:27 AM
Hi @Patrick Oudsho1
Did you find a solution for this?
We have recently moved from Utah to Xanadu and enabled Next Experience (activating this BR).
I am also seeing many records with no live_group_profile.table (or live_group_profile.document).
I followed the same log errors to the BR.
I have adjusted the query to exclude the records with no table or document, but I'm searching for the cause.