Triggering Dedupe on Any Textbox in the Journey

dedupe can be triggered on a textbox at any step of the journey it can be done in a few simple steps enable the toggle docid\ w9nomhq7t3hzdtdypdjv1 for stopping dedupe on first page submission as shown below when this toggle is enabled dedupe check on first page submission is prevented and then textbox based dedupe is enabled select parameters based on which dedupe will be triggered other variable (only from the first page) radio button docid\ ichcwvxymxzb naymmzc we can select multiple parameters from the first page of the journey based on which dedupe will be triggered from the dropdown menu docid\ e vpvhftkh q5pgb9zcal this trigger happens on the submission of the first page create a textbox docid\ l 2puiqmrkb4l w2 7dt and enable the 'trigger internal dedupe' toggle (only available on forms v2 docid\ aduszklkuhq 3w jtpmgf ) add the value on which the dedupe will be triggered in the 'when current variable equals' box note the dedupe will be triggered from any page where the textbox is present, but the dedupe parameter will be taken from the first page of the journey which we defined in the above step also, when a dedupe is triggered from a textbox, the pages succeeding that page will have all the data prefilled in case of a positive dedupe the preceding pages will not be prefilled but will be available for review in the case of positive dedupe, we have two 'call to action' options we can select one or both of them by selecting the checkbox allow users to (select at least one) prefill applications if an applicant has begun the journey of some product, then when they apply for some other product of the same organization, they get an option to prefill the fields/pages that are common in the two journeys when the dedupe is triggered prevent subflow prefilling enabling this toggle will prevent prefilling of a subflow that exists in the main flow even in the case of positive dedupe select variable to filter applications select the variable from the journey based on which applications will be filtered ex product code can be a variable/field against which applications will be filtered for now, if you don’t have any such field then you can pass a hardcoded default value which will be for each applicant (you can hide it from the user and backops) resume applications if an applicant has begun the journey of some product and has dropped mid journey, then when they apply for some other product of the same organization, they get an option to resume the journey for the previous product that they dropped off when the dedupe is triggered we can also select the information that will be visible in case of a positive dedupe by checking these checkboxes application number name status reason date of last update of application getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at help\@signzy com