SMARTS™ Dynamic Questionnaires enable users to generate user interfaces that collect data for decisioning. Primarily, they apply reflexive logic for dependencies between questions. Additionally, they enforce validation rules to ensure quality of data input. Finally, they collaborate seamlessly with back-end decision logic. Think of an online application or survey where instead of going through a static list of questions, the questions change based on how you answered previous questions. Organizations can design and manage that experience with Dynamic Questionnaires. Here are a few use cases.
#1 Use Case for Dynamic Questionnaires: Online Loan Application

Online Loan Application
In the Dynamic Loan Evaluation demo, we presented an example of an online loan application. Integrating Dynamic Questionnaires, business rules, and Orchestrations, businesses can create a business application that collects applicant data and renders the underwriting decision based on the collected data. While this demo is relatively simple, business applications developed in SMARTS™ can handle hundreds if not thousands of questions. We have worked on more complex questionnaires with our financial services, insurance, and healthcare clients.
#2 Use Case: Testing Multi-Step Processes
Behind the scenes, our built-in business process like engine manages the page transitions in a Dynamic Questionnaire. When appropriate, this engine applies decision services. The goal is to support long-running transactions so that a user doesn’t have to start over if they’re interrupted midway through the questions. Users should be able to continue where they left off.

Testing Credit Bureau Data Handling
In some situations, businesses may want to use a separate business process. While SMARTS™ can easily integrate with a BPM, the business process may not always be ready from the get-go. In this situation or when a process cannot be easily tested, I use Dynamic Questionnaires for testing. Dynamic Questionnaires provides a convenient, low-risk environment to navigate a process. In this example, I’m testing how credit bureau data is retrieved and handled.
#3 Use Case: Generating Business Rules
Last but not least, I use dynamic questionnaires for capturing business rules. While most clients author and maintain business rules in our SMARTS™ environment, there are situations where using a business application built with a Dynamic Questionnaire is more ideal. If, for instance, you want to empower untrained users (non-SMARTS™ experts) to modify business rules, you can create a business app that explicitly defines what a user can do in a no-code manner.

Writing Underwriting Rules
In this example, I have a business application that enables users to create and modify underwriting rules. For each product, I can select state and age eligibility through point-and-click. As you can see, I’m not actually writing the rules. Based on my selections, the rules will be generated in the back end.
Something to note, all these screenshots are pre-styled versions of the Dynamic Questionnaires. Branding and styling can be added to the questionnaires, which is useful for any customer-facing interfaces that you want to build. I hope that these use cases will give you some ideas on how you can leverage Dynamic Questionnaires in your organization.
Learn more about Sparkling Logic’s SMARTS™ Data-Powered Decision Manager and our Low-Code, No-Code capabilities.

