ease of use
Ease of use
Configure, prototype, test and deploy Experience Cloud solutions with the bare ‘minimum of custom code.
designed to be modern
Designed to be modern

UltraFlow forms can be styled with infinate customization. Form styles can also be used across multe forms.

documentation for everything
Documentation for everything

We’ve written extensive documentation for components and tools.

Frequently asked questions

Let us help answer the most common questions you might have.
What is the difference between Data Points and data fields?

Data Points define the data needed for your business process.
This is not necessarily the same data that you need to store in Salesforce.
At runtime, the data entered by the citizen is stored within a custom object in UltraFlow.
It is visible only to the citizen and is encrypted at rest.
You control which data is committed to Salesforce, and when.
This design allows you to collect and protect personally identifiable information, and also to discard
(for example) data for an application that has not reached a point where it is considered valid; you
can choose to create records in Salesforce only when it is complete.

Can I view Forms across multiple channels (Salesforce portals, website, mobile app etc.)

Yes.
UltraFlow Forms are simply metadata that is rendered at runtime by a Lightning Web Component
in the Runtime Engine

Can I view the Designer tools in languages other than English?

Yes.
UltraFlow Designer uses Salesforce custom labels to present all text visible in the Designer. These
labels have been translated into many languages for your convenience; more will be added in
future releases.

Can I render my Forms in languages other than English?

Yes – any language or dialect that your citizens use.
You first configure the list of languages that you need to use, including a default language – which
need not be English.
Then you configure all text that will be visible to the citizen – Data Point labels, help text, validation
error messages, Form headings.
Translated text becomes part of the Form metadata – it is not stored in custom labels.
You do not need to create multiple versions of a Form to support multiple languages.

I have a complex business process - do I need to build a complex Flow?

No – in fact we strongly recommend breaking processes down into smaller units.
Flows can be joined together, so if you need to (for example) validate a citizen’s identity, create a Flow that only does that.
You can then re-use this Flow whenever a process requires this action.

Is UltraFlow native to Salesforce?

Yes, UltraFlow is 100% native Salesforce.
A connector is needed to link the Designer app (installed once in a dedicated sandbox) to the Runtime Engine app (installed in all orgs where a client wishes to run their processes).
This is handled by the Publisher tool.

How do I apply styling to my Forms?

Use the Style Designer’s wysiwyg interface to configure the font, size, and colour you wish to apply to your text.
There are three types of Header and Footer text.
These Styles are applied to a Flow, not a Form – so all Forms displayed during a Flow will have the same Style. Therefore, one Form can be made to render differently depending on the Flow that uses it.
When processing passes to another Flow, the Style of the initial Flow is still used.

How was the cost of a license determined?

Using UltraFlow you can quickly create Experience Cloud solutions without having to build custom Lightning Web Components.
Setting the license at the usual cost of a single front-end developer means that you will save
money on your very first project.
UltraFlow’s primary purpose is to enable the public sector to create citizen portals while staying within their budget.
This is why the Designer license is per org, not per seat.
The separate Runtime Engine app is free.