When designing OmniScripts, the best practices that should be followed to optimize performance and user experience are:
Use a single DataRaptor to save the information: Instead of using multiple DataRaptors to update the account information after each step, it is better to use a single DataRaptor at the end of the OmniScript to save all the information at once. This reduces the number of database operations and improves performance.
Combine the three steps into one step: Instead of having three separate steps to capture the required information, it is better to combine them into one step with a simple layout. This reduces the number of page transitions and improves user experience.
The suggestions that are not best practices are:
Create a reusable OmniScript for this process: This may not be necessary if the process is specific to creating new billing accounts and not used by other OmniScripts. Creating a reusable OmniScript may add complexity and maintenance overhead.
Configure the save for later property: This may not be useful if the process is short and simple and does not require the user to resume it later. Configuring the save for later property may add unnecessary storage and retrieval logic.