[object Object]

A new portal project lands on your desk. Service Portal is mature, the team knows it, and the docs are everywhere. UI Builder is the strategic direction and the only thing ServiceNow is actively investing in. Choose carefully — migration after launch is a year-long project.

The honest state of each

Service Portal hit its functional ceiling around Vancouver. New investment is essentially zero. The Bootstrap 3 underpinnings are showing their age and AngularJS support is on borrowed time. UI Builder is component-based, uses the Now Components library, and is where every new portal-class feature ships first.

When Service Portal is still right

  • Heavy reliance on Bootstrap 3 widget marketplace add-ons
  • A team that has never touched modern web components
  • A go-live deadline inside 90 days and no UI Builder experience on staff
  • Customer-facing portal already on Service Portal with zero appetite for re-skin

When UI Builder is right

  • Greenfield employee or customer experience
  • Need for record pages with complex contextual layouts
  • Plans to integrate with Now Assist conversational UI in the next 18 months
  • Team comfortable with declarative data resources and event-driven components

The component story

UI Builder ships Now Components, a Web Components library that mirrors the platform forms. The crucial detail: data resources are declarative.

Data resource: GlideRecord
Table: incident
Query: assignment_group=javascript:gs.getUser().getMyGroups()
Limit: 25

You bind UI components to that resource and the platform handles caching and reactivity. No widget controller code, no $scope.

The migration trap

Do not attempt to lift-and-shift a Service Portal page into UI Builder. Re-architect from the data resources up. Anyone who has tried the lift-and-shift can tell you it costs more than rewriting.

Performance reality

UI Builder pages render slower on first load than Service Portal — the component framework cost is real. Cached navigation is faster. If first-paint time on slow networks is a hard SLA, prototype both before committing.

What to do this week

For your next portal project, write the decision in a one-page ADR with the criteria above. If the choice is still ambiguous, build the simplest page in both and time the team. The faster team wins, every time.

[object Object]
Share