Make it Yours: Using Process Skins

April 9, 2026
Get advanced tips with our free guide
Book a Free Consultation
Get advanced tips:
Get advanced tips

If you’ve ever built a process in Solvexia and then watched someone else try to use it in Subscriber View, you’ve probably noticed the disconnect. The logic and the outputs are exactly right, but the interface still says things like “Run Process” and “Process Inputs” — labels that made perfect sense when you were building it in Designer View, but feel generic and unfamiliar to the person running it every morning. That gap between how a process works and how it feels to use it, is what process skins are designed to close.

With process skins, you can rename labels, relabel buttons, and show or hide entire sections of Subscriber View, shaping the experience around the language and workflows your end users already know. There’s no code to write and no underlying logic to change — it’s a presentation layer that takes about five minutes to configure and makes a noticeable difference the moment someone opens the process.

Your team already has a language for this work — now the interface can match it

Every finance team develops its own vocabulary over time. What Solvexia calls “process inputs” might be “submission parameters” at one organisation and “upload configuration” at another. The run button might make more sense as “Generate report” or “Start reconciliation” depending on the context. These aren’t cosmetic differences — they’re the difference between an interface that feels like it was built for your team and one that feels like it was built for everyone

Process skins let you rename every visible element in Subscriber View: the process tab label, the run tab, section headings, the button that kicks off a run, and the button that appears afterward to start another one. Each change takes a single field edit in the Process Skin panel, and you can preview it instantly by selecting View in Subscriber — so you’re never guessing about what the end result looks like.

Sometimes less is better

Not every process benefits from displaying a progress section while it runs, and not every workflow needs a results summary on screen after it completes. For some processes, those extra sections just add visual noise that makes users scan the page looking for the part that’s actually relevant to them.

Process skins include show/hide toggles for both the results and progress sections, which means you can strip Subscriber View down to only the pieces your users need to see. If a process runs in a few seconds and the output lands in a spreadsheet, there’s no reason to show a progress bar at all. If users never need to review results on screen because they get an email notification, you can hide that section entirely. The goal is a focused experience where everything on the page has a reason to be there.

Setting it up

Getting started is straightforward. Open your process in Designer View, navigate to Settings in the left-hand panel, and select Process Skin to open the customisation panel. From there, you’ll find nine configurable options you can explore today:

  1. Process Tab Label
  2. Run Tab
  3. Process inputs section: Section label
  4. Run process button
  5. Process run tab
  6. Process results section: Section label
  7. Process progress section: Section label
  8. Process inputs section: Section label
  9. Create another run button name

Configuring each option

Each option is covered in detail below.

Process tab label

This setting controls the label displayed under the process description in Subscriber View.

To test it, enter a new value, then select View in Subscriber to preview the change.

Run tab

Renames the tab that users select to initiate a run.

Process inputs section: section label

Renames the heading of the inputs section displayed before a run is started.

Run process button

Renames the button users select to trigger the process.

Process run tab

Renames the tab displayed while the process is actively running.

Process results section: section label

Renames the heading of the results section shown after a run completes.

This section also includes a show/hide toggle, which removes the entire results section from Subscriber View when hidden.

Process progress section: section label

Renames the heading of the progress section displayed during a run.

Like the results section, this includes a show/hide toggle to hide the section entirely from Subscriber View.

Process inputs section: section label

This second inputs section label applies to a separate inputs area in the Subscriber View layout.

Create another run button name

Renames the button that appears after a run completes, allowing users to start a new run.

Why this matters more than it looks

It's tempting to think of process skins as a cosmetic feature, but the impact goes further than appearances. When Subscriber View speaks the same language as the people using it, there's less confusion, fewer questions about what to press or where to look, and a stronger sense that the tool was built for the task at hand.

For process designers, it also changes the dynamic around handoff. Instead of writing documentation that says "the button labelled Run Process actually means Generate Monthly Report," you can just make the button say what it does. The interface becomes self-documenting — less overhead and a cleaner experience.

The best tools are the ones that get out of the way and let people focus on the work that matters. Process skins are a small step in that direction.

Need help? Email us on support@solvexia.com.

FAQ

Intelligent reconciliation solution

Intelligent rebate management solution

Intelligent financial automation solution

Intelligent Financial Automation Solution

Intelligent financial automation solution

Intelligent financial automation solution

Intelligent financial automation solution

Intelligent financial automation solution

Intelligent regulatory reporting solution

Free up time and reduce errors