Internal Dedupe

the internal dedupe feature is designed to efficiently determine if the application already exists within the system dedupes can also assist relationship managers in evaluating the quality of the application or the applicant's record a positive outcome can significantly expedite the onboarding process by automatically prefilling the application with preexisting data there can be scenarios where an internal dedupe can be used if there is an existing application for a new merchant being created the rm or the applicant can use the data to prefill the application and save a lot of effort if the dedupe is positive, rm can be suggested whether to proceed or not, depending on the checker’s comment on the previous application if the dedupe is positive then it can be brought to rm’s notice that an application of the same applicant exists in the system configuring dedupe in admin the option to enable dedupe can be provided under the 'setting' tab within the 'backops' screen we can enable the dedupe option for the flow existing in the go admin the dedupe can be triggered at three places, i e , the create merchant docid\ u2vqnqx3q sskq3ob1mxq page, the first page of the journey, or a textbox docid\ l 2puiqmrkb4l w2 7dt (if configured for dedupe check) on any page in the journey internal dedupe for a flow can be configured using the following options prevent dedupe check on submission of first page this is the toggle which when enabled prevents dedupe check on submission of the first page if this toggle is enabled then the dedupe can be triggered from either the create merchant page or from a textbox on any page the 'trigger internal dedupe' toggle needs to be enabled on a textbox element to trigger the dedupe on a textbox on any pages docid\ xsd0meic4aadzddtkedsy of the journey (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 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 ) select dedupe parameters name of the merchant/applicant and mobile number the name of the merchant as well as their mobile number can be selected as a dedupe parameter to check for a positive or negative dedupe if the above toggle docid\ w9nomhq7t3hzdtdypdjv1 is enabled, selecting this option as a dedupe parameter will trigger the dedupe on the create merchant page of the journey mobile number only the mobile number of the merchant/applicant can also be taken as a dedupe parameter selecting this option as a dedupe parameter will trigger the dedupe on the create merchant page of the journey other variable (only from the first page) variables present on the first page can also be selected from a drop down for checking dedupe if the above toggle button(prevent dedupe check on submission of first page) is enabled, selecting this option as a dedupe parameter will trigger the dedupe on the textbox on any page of the journey in case of positive dedupe allow users to (select at least one) prefill applications select the 'prefill applications' checkbox docid\ ic2sxdzd jj p0niavw86 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 subflows docid\ bexbmlr7ocy7vpthk5xjn 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 information shown in case of positive dedupe 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