Display data from multiple sources - both internal data from Salesforce and external data from a website or a third-party legacy system.Unlike screen flows, OmniScripts are responsive. Use them on any device via any channel, without having to change the configuration.Some additional behind-the-scenes differences between screen flows and OmniScripts are worth noting.Īs explained in this Trailhead unit, with OmniScripts you can: I added similar constraints to the ABN, Date of Birth, Postcode, Email and Landline fields. This is the screen flow version of the form (the red numbers relate to the above list items): Conditionally show or hide the ABN field - as that field is not relevant for an individual applicant.Contain similar input controls across both screens.
Display informational text on the first screen - to provide further guidance on the meaning of accreditation versus registration.Include a bus image on their first screen - to visually communicate what the application relates to.So, what does a screen flow-based version of this application process look like? And what does an OmniScript version look like?īoth tools make it easy to create clean-looking forms, without requiring any custom styling or coding. In Victoria, bus operators must complete a Word-based application to be accredited or registered by the government. I chose a process I had learned about, earlier in my career - applying to operate a bus service in my home state (Victoria, Australia). To understand the differences in detail, I rebuilt an existing paper-based government form using both tools.