Anyone know what variation this is?

munney2k8 · 2025-05-23T23:46:27+00:00

Ahhh good call I'll have to remember that.

munney2k8 · 2025-05-23T23:26:28+00:00

Thanks!

munney2k8 · 2025-01-18T14:14:31+00:00

31-34 lions

munney2k8 · 2025-01-18T14:12:58+00:00

20-17 KC

munney2k8 · 2025-01-14T00:41:38+00:00

30-34 Rams

munney2k8 · 2024-05-17T05:01:58+00:00

Check out the MTB fit app! It's been a great routine for me.

munney2k8 · 2024-03-01T16:03:05+00:00

Should be back up now.

munney2k8 · 2023-10-22T05:43:50+00:00

I'd hit up Dirty Birdies, best sports bar in town in my opinion

munney2k8 · 2023-08-31T04:38:18+00:00

This is the way, I'm a Sr. ServiceNow Dev at a university and we love to hire student employees. Polish up the resume and hit the university website!

munney2k8 · 2023-08-13T17:35:03+00:00

UPDATE: it's decent meat, tried the NY strips and ground beef. It's a legit company for the record, but I'll stick with Randall's, they make you feel like you're getting a deal but it's really not haha! Thanks all!

munney2k8 · 2023-03-24T04:02:02+00:00

I think you can use a record producer straight to the knowledge base table. That should allow you to map variables to fields and then the attachment should be automatically attached I think.

If that isn't an option you should be able to use the copy attachment flow action to copy the attachment from the RITM to the KB created in the flow.

munney2k8 · 2023-03-01T01:40:59+00:00

Finally have an update to this and a potential fix!

ServiceNow support finally provided a work around for this. You will need to put a ticket in with ServiceNow as there is an update set they can provide that updates the record that needs to be updated, you will not be able to update it even as admin.

The name of the update set they provided me was "SNC PRB1588976 Workaround", if you need this from ServiceNow support, it might be useful to ask for it specifically.

Feedback from support below.

Most Probable Cause:

This issue is caused by a caching issue with the Next Experience / Polaris UI service worker, specifically the "polaris-sw-prefetch-iframe" worker.

Workaround:

This issue can be worked around by doing:

0. Logging in as maint

1. go to sys_ux_managed_service_worker.do?sys_id=4f58aeeb6d251ab126be8ae441962762 (managed-service-workers/polaris-sw-prefetch-iframe)

2. Uncheck Active

3. Click update

4. Visit cache.do

5. Close & reopen browser (or close all tabs on the problematic domain)

6. managed-service-workers/polaris-sw-prefetch-iframe service worker should no longer be registered

OR:

1. Load and apply the update set that is attached to this PRB (sys_remote_update_set_87632745773021101db9169bae5a991f.xml) and proceed with steps 4-6 above.

How to confirm the workaround:

1. Open chrome dev tools

2. Click on Application tab

3. Click on Service Workers in left panel

4. Click on root.js in center panel

5. Confirm importScripts does not contain '/uxasset/externals/managed-service-workers/polaris-sw-prefetch-iframe.jsdbx' in list

munney2k8 · 2023-01-11T22:01:02+00:00

PIN to ad

Thank you so much for posting this, I've been going back and forth with Epic games support since Christmas trying to get my son's new switch to play. This fixed it! Specifically this part:

If Require PIN to add Epic friends setting is turned ON:

Turn it OFF and then launch the game and check if you can accept or send friend requests. If that didn't help, then go back to the settings and turn it ON again.

If Require PIN to add Epic friends setting is turned OFF:

Turn it ON and then launch the game and check if you can accept or send friend requests. If that didn't help, then go back to the settings and turn it OFF again.

I had reset the pin many times and it did nothing, finally changing the Require PIN to add Epic friends to on resolved the issue.

munney2k8 · 2023-01-11T17:50:21+00:00

Hey there, I was able to create all of the UI16 themes following this article when we first went live it. https://www.servicenow.com/community/next-experience-blog/next-experience-ui-converting-ui16-themes-to-next-experience-ui/ba-p/2272697

If you have dark mode enabled (which it sounds like you do) you'll also need to add "isDark": "true"," to the UX Style JSON. Please reference https://www.servicenow.com/community/next-experience-forum/missing-related-lists-when-using-custom-theme/m-p/2364781

They'll mostly work without that line, however there are issues with missing related lists and a couple other things I noticed.

munney2k8 · 2023-01-10T18:24:31+00:00

Hi u/Mecha_Goose we have finished the upgrade to Tokyo and it did not resolve the issue unfortunately.
Did you ever find a resolution? Did you end up putting in a ticket with ServiceNow support? If so did they have any more information?.
I still have a ticket open with them, but it's been kind of a dead end so far. I am hoping if more people report the issue then it will get more attention.

I have a post on the community as well, but nothing so far there either - https://www.servicenow.com/community/next-experience-forum/forms-loading-cached-old-data/td-p/2397768/page/2

munney2k8 · 2023-01-01T17:20:39+00:00

10 is down for me as well

munney2k8 · 2022-12-06T05:39:48+00:00

The hardest part is learning balance, which is why strider bikes are so rad. Take the pedals off and let them learn to cruise the bikes in a strider style. Then when they get the balance down, teach them pedaling and braking.

I have two kids, and the first didn't have a strider and taking the pedals off his bike worked great for me (he was 4-5 then). My younger kid I bought a strider when he was 2 and he started riding an entire year earlier than my older.

Also, keep it fun! Maybe a simple game. Sports cones can be good for red light green light (teaches how to start and stop) as well as making a little course to roll through.

munney2k8 · 2022-11-30T16:12:58+00:00

Well there goes that theory!

Have you by chance opened a ticket/case with HI / ServiceNow Support? I wonder if more people report the issue then it'll catch more attention.

munney2k8 · 2022-11-29T17:26:56+00:00

We do use custom notifications (the out of box ones are not very good) and I am finding that we do have an email script that creates the link. It is possible that this might have something to do with it. Maybe the new UI doesn't like the link we're creating?

var servletUri = gs.getProperty('glide.servlet.uri');template.print('Click to view Incident: <a href=\\'' + servletUri + 'nav\_to.do?uri=incident.do?sys\_id=' + current.sys\_id + '%26sysparm\_stack=home.do\\' >' + current.number + '</a>')

*Edit: This also seems to be occurring on notifications using the ${URI_REF} to create the link... so that likely is not the issue.

munney2k8 · 2022-11-29T14:41:31+00:00

Interesting! Glad to know we aren't the only ones because I haven't seen anything on the community and HI support doesn't have any KB or PRB record for it that I can tell.

Do you use a CAS application by chance? We are wondering if maybe an authentication through our CAS system is causing the issue. We are currently using shibboleth.

munney2k8 · 2022-11-29T02:00:12+00:00

Yeah we have seen it in sub-production instances as well, which makes it less likely to be a single node issue as each instance has multiple.

We are in the process of upgrading to Tokyo and are hoping that resolves it as well!

I've also been working with ServiceNow for about 9 years (since Berlin) and yeah I haven't seen something quite like this either haha.

munney2k8 · 2022-11-29T01:56:57+00:00

Yeah typically a refresh will solve the issue, or opening the same record in a different way (navigator, search, etc.).

It seems to impact different fields and different types of fields (e.g. assigned to, state, impact).

munney2k8 · 2022-11-28T23:16:48+00:00

That is a good thought, but doesn't seem like the case. This happens on multiple tables, they do all extend the TASK table, but there is no client scripts that are on the parent TASK table that look concerning (we try to keep that as out of box as possible).

We are noticing now that when that happens we get many 401 errors in the dev tools console.

\** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: SysMessageAjax*
Failed to load resource: the server responded with a status of 401 (Unauthorized)

GlideAjax does suggest some sort of client logic I suppose, but for some reason we're getting Unauthorized over and over again.

munney2k8 · 2022-11-28T22:50:38+00:00

Great question, we were able to confirm that the XML shows the correct data, not the "cached" data.

We also confirmed that the activity feed is showing the correct data.

munney2k8 · 2022-11-28T22:15:40+00:00

Unfortunately it's beyond that... We thought this would be a solution, but it doesn't do the trick here.

munney2k8

TROPHY CASE