This guide explains how to move an existing profile from the legacy aspect styling (UI 2.0) to the new theme styling so your users get the redesigned 2.1 UI.
Why switch
The theme model gives you what aspect can't:
-
The redesigned 2.1 UI (
theme.base = DEFAULT_V2_1). -
Dark mode (
theme.palette.dark+functionality.colorMode). -
Per-variant typography and component-level styling (buttons, inputs, links, icons, shape, shadows).
🟨 Beta.
themeandDEFAULT_V2_1are currently beta.
The catch: you recreate the profile
aspect and theme are mutually exclusive in a profile and there is no in-place conversion. You do not edit a profile to switch - you create a new theme-based profile and point your web forms at it.
Steps
-
Read your current
aspectprofile (GET /api/profiles/{id}) and note its colors, font, and base theme. -
Create a new profile (
POST /api/profiles) with athemesection,theme.base = DEFAULT_V2_1, mapping eachaspectvalue to itsthemeequivalent (table below). Carry overbrandandfunctionalityas-is. -
Test by creating a web form with the new
profileId. -
Cut over - pass the new
profileIdwhen creating web forms, or mark the new profile asdefault. -
Delete the old profile once nothing references it.
Field mapping (aspect → theme)
⚠ Verify against the authoritative table on the source page before publishing.
|
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
What 2.1 adds vs ignores
-
Adds: dark palette, full typography scale, component styling, plus the 2.1-only functionality flags (
cancelButton,messageForm,featuredBankGroups,finapiFooterBranding). -
Ignores/leaves behind: anything
aspect-only that has nothemeequivalent - list these explicitly from the source table so customers know what won't carry over.