There are many different ways that you can use HCL Leap and we can divide the applications in to a few different types:
This type of application is a survey, registration form, feedback form, sign up form or a simple quiz.
This type of application collects information from a target audience. It does not require an individual to login to the application and typically does not request personal information.
Sample application and walk-through guide.
Feedback Form (Authenticated users)
The definition given to a feedback form is one that is collecting information from known participants. This is typically, but not limited to, a single stage application that does not require any additional actions. An example of this type of application might be a form that captures feedback on the quality of a software product from its users/consumers.
This is a very simple application that is a quiz/test that will show the user their score after submitted.
Invited/Guest User Survey
The Invited/Guest User use case is less common and not very well understood. It allows you to send a special link to an external user (one that might not normally have access to HCL Leap) and allow them to review or update your form. An invite link can not be provided for the initial (Start) stage only for the subsequent stages.
This type of application is most commonly used as a way tracking some type of information. A simple example might be for an organizer to have a single form for tracking potluck attendees and dishes they are bringing. A more complex example would be a system used for tracking customer engagements and activity.
Deal Tracking Application
This example shows how you can create tracking applications. The tutorial will walk you through how you can build the UI in one application and a second application where the deal records are created and updated. This way you have one database for the deals - a single version of the truth if you will - and another database to keep an audit trail which tracks of all changes and updates.
Customer / Lab Involvement Tracker
The following example shows a customer tracking form that has a record locking feature implemented so that only one person can update a record at a time.
Customer Tracking Application
This application uses a custom UI to enable the end user to create and update customer records. The user can then select a customer and add notes to that record.
Keep Record History
This application uses a custom UI to create a new record any time that updates made to a record to maintain a complete change history.
Workflow Application that uses Open Roles
This type of application is a bit more complex in that it exercises dynamic workflow where the next person in the workflow is determined at run-time.
Custom UI with Data Stored in other App(s)
You may consider this type of approach if you need to customize how your application data is exposed to your audience. The primary approach to handling submitted data is to use View Responses but that can be somewhat confusing to novice or non-technical users. What you may want to do is simplify what your audience sees and what they can interact with.