Wiki source code of Progressive Lookup

Version 5.1 by melanie@one-count_com on 2016/11/09 16:35
Show last authors
1
2
3 {{id name="Start ScreenSteps Content"/}}
4 (% style="color: rgb(128,128,128);" %)//ONEcount forms have a progressive lookup feature whereby an existing user can be identified by demographic information as it's being entered. The system will look up the user based on the information being progressively entered in the form – e.g. email, first name, last name, city – and auto-populate the form when the user is identified. (The fields used for lookup are set in the Question Manager. See Question Manager documentation for more detail.)//
5
6 (% style="color: rgb(128,128,128);" %)//If a user is trying to log in and/or subscribe to a product and fails Lookup and/or Login on the Lookup/Login page or if Lookup/Login functionality has been overridden/bypassed, the user will be directed to the blank subscription/registration form. Even though a registered/subscribed user has failed Lookup/Login based on entering incorrect/unidentifiable information in Lookup or not having his/her username and password for Login, if in your ONEcount database, he/she can still be identified by the ONEcount system by progressive lookup functionality.//
7
8 (% style="color: rgb(128,128,128);" %)//Following is detail of the functionality and process as the user will experience it after failing initial Lookup/Login or bypassing Lookup/Login and being presented with a blank form.//
9
10 === Process ===
11
12 **With No Lookup/Challenge Questions selected in Form Builder:**
13 Example: User Enters First Name, Last Name, and City and is potentially identified
14
15 ~1. Record has: Email = no, Cell Phone = no
16
17 user presented with prompt asking for email or cell # to send verification code
18 user enters cell number
19 user gets verification code from text message
20 user enters code
21 form auto populated, and
22 cell # added to profile
23
24 OR
25
26 user enters email address
27 user gets verification code from email
28 user enters code
29 form auto populated, and
30 email address added to profile
31
32 2. Record has: Email = no, Cell Phone = yes
33
34 user presented with prompt asking for email or cell # to send verification code
35 user enters cell number
36 user gets verification code from text message
37 user enters code
38 form auto populated
39
40 OR
41
42 user enters email
43 user gets verification code from email
44 user enters code
45 form auto populated
46 email address added to profile
47
48 3. Record has: Email = yes, Cell Phone = no
49
50 user presented with message the verification code was sent to email address
51 user gets code from email
52 user enters code
53 form auto populated
54
55 4. Record has: Email = yes, Cell Phone = yes
56
57 user presented with message the verification code was sent to email address
58 user gets code from email
59 user enters code
60 form auto populated
61
62 **With Lookup/Challenge Questions Selected in Form Builder:**
63 Example: User enters First Name, Last Name, and City and is potentially identified
64
65 ~1. Record has: Email = no, Phone = no
66
67 user presented with lookup question
68 user passes lookup *
69 user presented with "Email Required – Provide Email to Send Username & Password" pop-up
70 user enters email address
71 form auto populated
72 user receives email w/username and password
73
74 2. Record has: Email = no, Phone = yes
75
76 user presented with lookup question
77 user passes lookup *
78 user presented with "Email Required – Provide Email to Send Username & Password" pop-up
79 user enters email address
80 form auto populated
81 user receives email w/username and password
82
83 3. Record has: Email = yes, Phone =no
84
85 user presented with lookup question
86 user passes lookup *
87 form auto populated
88
89 4. Record has: Email = yes, Phone = yes
90
91 user presented with lookup question
92 user passes lookup *
93 form auto populated
94
95 *
96 ** On fail lookup, a message to to complete the blank form is displayed.*
97
98 *
99 **
100 *** Lookup/Challenge Questions are selected in the Question Builder. Plase see Question Builder* **documentation for more detail on how to select Lookup Questions.**
101
102 **You should set at least three lookup questions in the Question Builder. With more questions there is more probability that the system will present the user a challenge question instead of sending a verification code. Challenge/Lookup questions will only pop up if the question value is not empty; and they should be questions that are not being answered in the form. More selected lookup/challenge questions means more of a chance that a user has a response in the database to one of them and will be able to answer rather than requiring a verification code.**
103
104
105
106
107
108 {{id name="End ScreenSteps Content"/}}