Changes for page Progressive Lookup

Last modified by Admin User on 2025/04/14 17:25
From version 13.1
edited by melanie@one-count_com
on 2016/12/13 14:29
Change comment: There is no comment for this version
To version 2.1
edited by melanie@one-count_com
on 2016/11/09 16:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,118 +1,0 @@
1 -{{layout}}
2 -{{layout-section ac:type="two_right_sidebar"}}
3 -{{layout-cell}}
4 -
5 -
6 -{{id name="Start ScreenSteps Content"/}}
7 - (% 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.)//
8 -
9 -(% 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.//
10 -
11 -(% 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.//
12 -
13 -=== Process ===
14 -
15 -**With No Lookup/Challenge Questions selected in Form Builder:**
16 -Example: User Enters First Name, Last Name, and City and is potentially identified
17 -
18 -~1. Record has: Email = no, Cell Phone = no
19 -
20 -user presented with prompt asking for email or cell # to send verification code
21 - user enters cell number
22 - user gets verification code from text message
23 - user enters code
24 - form auto populated, and
25 - cell # added to profile
26 -
27 -OR
28 -
29 -user enters email address
30 - user gets verification code from email
31 - user enters code
32 - form auto populated, and
33 - email address added to profile
34 -
35 -2. Record has: Email = no, Cell Phone = yes
36 -
37 -user presented with prompt asking for email or cell # to send verification code
38 - user enters cell number
39 - user gets verification code from text message
40 - user enters code
41 - form auto populated
42 -
43 -OR
44 -
45 -user enters email
46 - user gets verification code from email
47 - user enters code
48 - form auto populated
49 - email address added to profile
50 -
51 -3. Record has: Email = yes, Cell Phone = no
52 -
53 -user presented with message the verification code was sent to email address
54 - user gets code from email
55 - user enters code
56 - form auto populated
57 -
58 -4. Record has: Email = yes, Cell Phone = yes
59 -
60 -user presented with message the verification code was sent to email address
61 - user gets code from email
62 - user enters code
63 - form auto populated
64 -
65 -**With Lookup/Challenge Questions Selected in Form Builder:**
66 -Example: User enters First Name, Last Name, and City and is potentially identified
67 -
68 -~1. Record has: Email = no, Phone = no
69 -
70 -user presented with lookup question
71 - user passes lookup *
72 - user presented with "Email Required – Provide Email to Send Username & Password" pop-up
73 - user enters email address
74 -form auto populated
75 - user receives email w/username and password
76 -
77 -2. Record has: Email = no, Phone = yes
78 -
79 -user presented with lookup question
80 - user passes lookup *
81 - user presented with "Email Required – Provide Email to Send Username & Password" pop-up
82 - user enters email address
83 - form auto populated
84 - user receives email w/username and password
85 -
86 -3. Record has: Email = yes, Phone =no
87 -
88 -user presented with lookup question
89 - user passes lookup *
90 - form auto populated
91 -
92 -4. Record has: Email = yes, Phone = yes
93 -
94 -user presented with lookup question
95 - user passes lookup *
96 - form auto populated
97 -
98 -*
99 -** On fail lookup, a message to to complete the blank form is displayed.*
100 -
101 -*
102 -**
103 -*** Lookup/Challenge Questions are selected in the Question Builder. Plase see Question Builder* **documentation for more detail on how to select Lookup Questions.**
104 -
105 -**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.**
106 -
107 -
108 -
109 -
110 -
111 -{{id name="End ScreenSteps Content"/}}
112 -{{/layout-cell}}
113 -
114 -{{layout-cell}}
115 -
116 -{{/layout-cell}}
117 -{{/layout-section}}
118 -{{/layout}}
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -67414
1 +65887
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/67414/Progressive Lookup
1 +https://info.onecount.net//wiki/spaces/OD/pages/65887/Progressive Lookup