Date: Thu, 28 Mar 2024 19:59:16 +0000 (UTC) Message-ID: <382239199.37.1711655956328@c5d888e19e50> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_36_1986563191.1711655956327" ------=_Part_36_1986563191.1711655956327 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There are many different ways that you can use HCL Leap and we c= an 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 d= oes not request personal information.
Sample application and walk-through guide.
Feedback Form (A= uthenticated users)
The definition given to a feedback form is one that is collecting inform= ation from known participants. This is typically, but not limited to, a sin= gle stage application that does not require any additional actions. A= n example of this type of application might be a form that captures feedbac= k 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= strong>
The Invited/Guest User use case is less common and not very well underst= ood. It allows you to send a special link to an external user (one th= at 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 ty= pe of information. A simple example might be for an organizer to have a sin= gle form for tracking potluck attendees and dishes they are bringing. A mor= e complex example would be a system used for tracking customer engagements = and activity.
This example shows how you can create tracking applications. The tutoria= l will walk you through how you can build the UI in one application and a s= econd application where the deal records are created and updated. Thi= s way you have one database for the deals - a single version of the truth i= f 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 l= ocking feature implemented so that only one person can update a record at a= time.
Customer Tracking Appl= ication
This application uses a custom UI to enable the end user to create and u= pdate customer records. The user can then select a customer and add n= otes to that record.
This application uses a custom UI to create a new record any time that u= pdates made to a record to maintain a complete change history.
Workflow A= pplication that uses Open Roles
This type of application is a bit more complex in that it exercises dyna= mic workflow where the next person in the workflow is determined at run-tim= e.
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 t= o 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.