Resource Management Workspace navigation arrows

athavichith · 3 weeks ago

Hi everyone,

Has anyone experienced an issue in Resource Management Workspace where the navigation arrows on the resource cards disappear after moving to the next page?

The arrows show up on the first page as expected, but once I click to go to page 2 (or beyond), the arrows no longer appear, so users can’t navigate through the cards.

If anyone has seen this before or knows what might cause it, I’d appreciate any insights or suggestions.

Thanks!

Vikram Reddy · 3 weeks ago

Hey @athavichith,

Resource Management Workspace is built on the Now Experience UI Builder framework, so the My Resource Cards list and the pagination footer you circled (first, prev, next, last) is a client-rendered component, not something the server paints fresh on every page. Components like that keep their own local state for current page, total pages, and whether there's a next/previous page to go to. It's a known category of problem in UI Builder-driven workspaces for that local state to fall out of sync with the underlying data resource once you page past the first fetch, particularly when the list uses server-side paging under the hood rather than pulling everything client-side. When that happens the row data still renders fine, but the component decides there's nothing left to page through and the arrows just stop painting, even though more resource cards exist.

There's nothing in the current product docs pointing to a documented defect for this exact screen, so before you log a case, a few things worth isolating on your end:

Reproduce in a private/incognito window to rule out a stale client-side cache. Next Experience workspaces cache the UI Builder page definition in the browser, and a half-updated cache after an app or platform upgrade is a common reason a control silently disappears on some pages but not others.
Open the browser console (F12) right before you click to page 2 and watch for a JS error the instant you advance. If the pagination component throws on the second fetch, that error is exactly what you want captured for a support case.
Check the installed version of the Resource Management Workspace app under System Applications > All Available Applications > All against the current listing on the ServiceNow Store. This app ships incremental updates independent of platform upgrades, so a fix for exactly this kind of list/pagination bug may already exist in a newer version.
Confirm whether the My Resource Cards page has been customized in UI Builder. If it was cloned or extended from the out-of-box page, check the list component's pagination configuration and any visibility binding on the arrow controls tied to page index, since a custom binding is a very common way this kind of thing breaks in ways the OOB page never would.
Try a second browser to rule out a rendering quirk tied to one engine specifically.
Note whether the record count text next to the arrows still updates on page 2 or freezes along with the arrows. That tells you whether it's the whole pagination component losing state or just the arrow icons failing to render.

If it reproduces cleanly out of the box, on an unmodified page, in a fresh browser session, that's a legitimate defect worth logging with ServiceNow support rather than something to configure around. A console error plus a short screen recording of the transition from page 1 to page 2 will get it triaged far faster than a text description alone.

References

Thank you,
Vikram Karety
Octigo Solutions INC

athavichith · 3 weeks ago

I reproduced this error in incognito mode.

Vikram Reddy · 3 weeks ago

Hey @athavichith,

Good, that's actually a useful result, even though it's the annoying kind. Ruling out incognito means we can cross stale client cache off the list entirely, the UI Builder page definition and any half-updated browser state weren't the culprit. So the arrows disappearing on page 2 is either a real defect in the pagination component's logic, a version-specific bug in the app, or something in how that page was configured on your instance. I checked the ServiceNow Known Error portal and the current Resource Management Workspace product documentation for anything matching this specific symptom, arrows vanishing past page 1 while the cards themselves keep loading, and there's nothing published that matches it yet. So this hasn't been publicly documented as a known issue as of today.

Given that, here's where I'd focus next, in order of how much signal each one gives you:

Capture the console error. This is the single most useful thing you can hand to support. Open dev tools, go to the Console tab, clear it, then click to page 2 and watch the instant the arrows vanish. If the list/pagination component throws when it re-renders with the second page of data, you'll see it right there. Screenshot or copy the full stack trace, not just the message.
Confirm the exact app version. Go to System Applications, then All Available Applications, then All, and find Resource Management Workspace. Note the installed version and compare it against what's currently listed on the ServiceNow Store. This app gets incremental updates outside of platform upgrades, so if you're a version or two behind, a fix for this may already be sitting in a newer release.
Rule out customization on the My Resource Cards page. Open it in UI Builder and check whether it's the untouched out-of-box page or was cloned/extended. If it's customized, look specifically at the pagination configuration on the list component and any visibility binding tied to page index on the arrow controls. A binding that only accounts for page 1 is a very common way this exact symptom shows up.
Watch the record count text next to the arrows when you hit page 2. If it keeps updating correctly while only the arrow icons vanish, that points to a rendering/visibility issue isolated to the arrows. If the count also freezes, the whole pagination component is losing its state on that transition, which is a different kind of bug to chase.

If you run through 1 and 4 and it reproduces on an unmodified out-of-box page with a console error to show for it, that's enough to open a case with ServiceNow support rather than keep troubleshooting locally. Attach the console error plus a short screen recording of the page 1 to page 2 transition, that combination gets these triaged fast because support can usually match the stack trace to an existing PRB even if there's no public KB for it yet.

Let me know what the console shows, that'll tell us which of these four buckets we're actually in.

Thank you,
Vikram Karety
Octigo Solutions INC