Method And System For Configuring A User Document Validation

Jio Platforms Limited
Awaiting Request for Examination App No 202321048581 Computer Science

Patent information

IP India · live record
Application number
202321048581
Filing date
19 July 2023
Status
Awaiting Request for Examination
Publication number
04/2025
Publication type
INA
Invention field
Computer Science

Abstract

The present disclosure relates to a method and a system for configuring a user document validation. The disclosure encompasses receiving an input order; fetching preconfigured document validation sets; fetching set of documents; identifying document parameters; generating target validation sets; mapping documents; generating updated target validation sets; mapping target action and target validation sets; identifying target documents; and configuring the user document validation. [Figure 4]

Applicants

1
India
Jio Platforms Limited Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Inventors

10
India
Sandeep NarulaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Aayush BhatnagarOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Kiran Prakash JangidOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Karan GuptaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Aayushi RathoreOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Mansi AgarwalOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Yogi BotlaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
SennumChetty HarshithaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Shaileshkumar Gunvantray JhaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
India
Santosh VaidyaOffice - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Claims

11
1 A method [400] for configuring a user document validation on a customer engagement management (CEM) system [300], the method [400] comprising: 5 - receiving, by a transceiver unit [301] at the CEM system [300], an input order comprising at least an order role and an order number; - fetching, by a fetching unit [302] from a database [303] at the CEM system [300], one or more preconfigured document validation sets based on at least one of the order role and the order number; 10 - fetching, by the fetching unit [302] from the database [303], a set of documents based on the order number; - updating, by an updating unit [304], one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more 15 preconfigured document validation sets; - generating, by a generation unit [305], at the CEM system [300], one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets; 20 - mapping, by a mapping unit [306], at the CEM system [300], one or more documents from the set of documents and the one or more target validation sets; - generating, by the generating unit [305], one or more updated target validation sets based on the mapping the one or more documents from 25 the set of documents and the one or more target validation sets; - mapping, by the mapping unit [306], a set of target action and the one or more updated target validation sets; - identifying, by an identification unit [307], one or more target documents from the set of documents based on a set of target actions; 30 and - configuring, by a configuration unit [308], the user document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions. 5 2. The method [400] as claimed in claim 1, wherein the one or more preconfigured document validation sets is at least one of: a compare customer photo and proof of identity (POI) document, a compare POI document versus proof of address (POA) document and display list of documents in dropdown and on click display the clicked file only. 10 3. The method [400] as claimed in claim 1, wherein the one or more document parameters associated with each document from the set of documents, comprises, a document status, a document filename and a document URL.
4 The method [400] as claimed in claim 1, the method [400] further comprises: 15 - generating, by the generation unit [305], a validation report associated with the input order in a predefined format; and - displaying, by a user interface [300ui], at the CEM system [300], the validation report.
5 The method [400] as claimed in claim 4, wherein the predefined format of 20 the validation report associated with the input order comprises: a color code for one or more missed documents, one or more available documents and one or more corrupted documents.
6 The method [400] as claimed in claim 1, wherein the set of target actions is at least one of a download pdf URL action, and a display pdf URL action. 25 7. The method [400] as claimed in claim 1, the method [400] further comprises generating, by the generation unit [305], the one or more target validation sets based on at least one of a user input, the one or more document parameters and the one or more preconfigured document validation sets.
8 A customer engagement (CEM) system [300] for configuring a user 30 document validation, the CEM system [300] comprising: - a transceiver unit [301] configured to: o receive, an input order comprising at least an order role and an order number; - a fetching unit [302] connected to at least the transceiver unit [301], the fetching unit [302] configured to: 5 o fetch, from a database [303], one or more preconfigured document validation sets based on at least one of the order role and the order number; o fetch, from the database [303], a set of documents based on the order number; 10 - an updating unit [304] connected to at least the fetching unit [302], the updating unit [304] configured to update, one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets; 15 - a generation unit [305] connected to at least the updating unit [304], the generation unit [305] configured to generate, one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets; 20 - a mapping unit [306] connected to at least the generation unit [305], the mapping unit [306] configured to map, one or more documents from the set of documents and the one or more target validation sets; wherein the generation unit [305] is further configured to generate, one or more updated target validation sets based on mapping the one or 25 more documents from the set of documents and the one or more target validation sets; and wherein the mapping unit [306] is further configured to map, a set of target actions and the one or more updated target validation sets; - an identification unit [307] connected to at least the mapping unit [306], 30 the identification unit [307] configured to identify, one or more target documents from the set of documents based on the set of target actions; and - a configuration unit [308] connected to at least the identification unit [307], the configuration unit [308] configured to configure, the user 5 document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions.
9 The CEM system [300] as claimed in claim 8, wherein the one or more preconfigured document validation sets is at least one of: a compare of 10 customer photo and proof of identity (POI) document, a compare of POI document versus proof of address (POA) document and display list of documents in dropdown and on click display the clicked file only.
10 The CEM system [300] as claimed in claim 8, wherein the one or more document parameters associated with each document from the set of 15 documents, comprises, a document status, a document filename and a document URL.
11 The CEM system [300] as claimed in claim 8, wherein the generation unit [305] is further configured to: - generate a validation report associated with the input order in a 20 predefined format; and - display, at a user interface [300ui], the validation report.
12 The CEM system [300] as claimed in claim 11, wherein the predefined format of the validation report associated with the input order comprises: a color code for one or more missed documents, one or more available 25 documents and one or more corrupted documents.
13 The CEM system [300] as claimed in claim 8, wherein the set of target actions is at least one of a download pdf URL action, and a display pdf URL action.
14 The CEM system [300] as claimed in claim 8, wherein the generation unit 30 [305] is further configured to generate the one or more target validation sets 5 10 15 20 25 30 based on at least one of a user input, the one or more document parameters and the one or more preconfigured document validation sets. 15. A user equipment (UE) comprising: a memory; and on: - a processor connected to the memory, the processor configured to send an input order comprising at least an order role and an order number to a customer engagement (CEM) system [300], wherein the CEM system [300] configures a user document validation based receiving, by a transceiver unit [301] at the CEM system [300], the input order; - fetching, by a fetching unit [302] from a database [303] at the CEM system [300], one or more preconfigured document validation sets based on at least one of the order role and the order number; - fetching, by the fetching unit [302] from the database [303], a set of documents based on the order number; - updating, by an updating unit [304], one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets; - generating, by a generation unit [305], at the CEM system [300], one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets; - mapping, by a mapping unit [306], at the CEM system [300], one or more documents from the set of documents and the one or more target validation sets; - generating, by the generating unit [305], one or more updated target validation sets based on the mapping the one or more documents from the set of documents and the one or more target validation sets; 36 - mapping, by the mapping unit [306], a set of target action and the one or more updated target validation sets; - identifying, by an identification unit [307], one or more target documents from the set of documents based on a set of target actions; 5 and - configuring, by a configuration unit [308], the user document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions.

Specification

Show full textCollapse

FORM 2 THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003 COMPLETE SPECIFICATION (See section 10 and rule 13) “METHOD AND SYSTEM FOR CONFIGURING A USER DOCUMENT VALIDATION” We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India. The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR CONFIGURING A USER DOCUMENT VALIDATION TECHNICAL FIELD 5

[0001] Embodiments of the present disclosure generally relate to field of customer relationship management (CRM)/ customer engagement management (CEM)/ customer engagement manager (CEM) systems. More particularly, embodiments of the present disclosure relate to method and system for 10 configuring a user document validation for customer engagement. BACKGROUND

[0002] The following description of the related art is intended to provide 15 background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art. 20

[0003] CEM is the combination of technologies, practices and strategies that companies use to manage and analyse customer/client and/or lead interactions and data throughout the customer life cycle. Various operations such as on boarding new customer, modifying customer details such as personal 25 details, account details and services are accomplished by accepting order from front-end channels. The order is tracked from submission to completion through unique order identifier called Order ID and details of the same are also provided on custom User Interface CEM provides. The objective is to improve customer service relationships, reduce time-to-market for new business requirement, 30 modifications and adaptations and assist in customer retention and drive sales growth. CEM systems compile customer data across different channels, or points 2

of contact, between the customer and the company, which could include the company's website, telephone, live chat, mail, marketing materials, social networks and like others. CEM systems can give customer-facing staff members detailed information on customers' personal information, order history, 5 preferences and concerns.

[0004] The CEM system user interface provides various information of customer to be visible and to be fetched for accessing by a company person or agent. CRM system may provide various information of customer in split screen 10 format for accessing by the agent. In CEM system, for an example, if hardcoded Validation Sets like (Validation Set 1, Validation Set 2, Validation Set 3) are given, and if in future some new validation sets come, then again software coding is required to be done to add that new validation set. Validation Set may be for any type of information, such as: Validation Set 1 may be for – Compare 15 Customer Photo and POI Document, Validation Set 2 may be for – Compare POI Document vs POA Document, Validation Set 3 may be for – Display list of documents in dropdown and on click displays that file only. However, for accessing such information and adding new validation set, there is requirement for hardcoding process, which is less feasible and less efficient solution for 20 deploying new sets. Further, for implementing this, there will be need of subject to code change in lower or development environment, sign-off to System Integration Testing team, followed by regression and then deployment in production through Planned Activity (PE). This process itself will take at least couple of business days. 25

[0005] Thus, there exists an imperative need in the art to provide a solution to address the above-mentioned problems. SUMMARY 30 3

[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter. 5

[0007] An aspect of the present disclosure may relate to a method for configuring a user document validation on a customer engagement management (CEM) system. The method comprises receiving, by a transceiver unit at the CEM system, an input order comprising at least an order role and an order number. The 10 method further comprises fetching, by a fetching unit from a database at the CEM system, one or more preconfigured document validation sets based on at least one of the order role and the order number. The method further comprises fetching, by the fetching unit from the database, a set of documents based on the order number. The method further comprises updating, by an updating unit, one or more 15 document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The method further comprises generating, by a generation unit, at the CEM system, one or more target validation sets based on the updating of the one or more document parameters in each of the 20 preconfigured document validation set from the one or more preconfigured document validation sets. The method further comprises mapping, by a mapping unit, at the CEM system, one or more documents from the set of documents and the one or more target validation sets. The method further comprises generating, by the generating unit, one or more updated target validation sets based on the 25 mapping the one or more documents from the set of documents and the one or more target validation sets. The method further comprises mapping, by the mapping unit, a set of target action and the one or more updated target validation sets. The method further comprises identifying, by an identification unit, one or more target documents from the set of documents based on a set of target actions. 30 The method further comprises configuring, by a configuration unit, the user document validation associated with the input order based on identifying the one 4

or more target documents from the set of documents based on the set of target actions.

[0008] In an exemplary aspect of the present disclosure, the one or more 5 preconfigured document validation sets is at least one of: a compare customer photo and proof of identity (POI) document, a compare POI document versus proof of address (POA) document and display list of documents in dropdown and on click display the clicked file only. 10 [0009] In an exemplary aspect of the present disclosure, the one or more document parameters associated with each document from the set of documents, comprises, a document status, a document filename and a document URL.

[0010] In an exemplary aspect of the present disclosure, the method further 15 comprises generating, by the generation unit, a validation report associated with the input order in a predefined format. And the method further comprises displaying, by a user interface, at the CEM system, the validation report.

[0011] In an exemplary aspect of the present disclosure, the predefined 20 format of the validation report associated with the input order comprises: a color code for each of the at least missed documents, available documents and corrupted documents.

[0012] In an exemplary aspect of the present disclosure, the set of target 25 actions is at least one of a download pdf URL action, and a display pdf URL action.

[0013] In an exemplary aspect of the present disclosure, the method further comprises generating, by the generation unit, the one or more target validation 30 sets based on at least one of a user input, the one or more document parameters and the one or more preconfigured document validation sets. 5

[0014] Another aspect of the present disclosure may relate to a customer engagement system (CEM) for configuring a user document validation. The CEM system comprises a transceiver unit configured to receive, an input order 5 comprising at least an order role and an order number. The CEM system further comprises a fetching unit connected to at least the transceiver unit, the fetching unit is configured to fetch from a database, one or more preconfigured document validation sets based on at least one of the order role and the order number. The fetching unit is further configured to fetch, from the database, a set of documents 10 based on the order number. The CEM system further comprises an updating unit connected to at least the fetching unit, the updating unit is configured to update, one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The CEM system further comprises 15 a generation unit connected to at least the updating unit, the generation is configured to generate, one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The CEM system further comprises a mapping unit connected to at least the generation 20 unit, the mapping unit is configured to map, one or more documents from the set of documents and the one or more target validation sets. It is to be noted to that the generation unit is further configured to generate, one or more updated target validation sets based on mapping the one or more documents from the set of documents and the one or more target validation sets. It is further noted that the 25 mapping unit is further configured to map, a set of target actions and the one or more updated target validation sets. The CEM system further comprises an identification unit connected to at least the mapping unit, the identification unit is configured to identify one or more target documents from the set of documents based on the set of target actions. The CEM system further comprises a 30 configuration unit connected to at least the identification unit, the configuration unit is configured to configure, the user document validation associated with the 6

input order based on identifying the one or more target documents from the set of documents based on the set of target actions.

[0015] Yet another aspect of the present disclosure may relate to a non- 5 transitory computer-readable storage medium storing instruction for configuring a user document validation, the storage medium comprising executable code which, when executed by one or more units of a customer engagement (CEM) system, causes a transceiver unit of the CEM system to receive, an input order comprising at least an order role and an order number; a fetching unit of the CEM 10 system to fetch, from a database, one or more preconfigured document validation sets based on at least one of the order role and the order number. Further, the instructions cause the fetching unit of the CEM system to fetch, from the database, a set of documents based on the order number. Furthermore, the instructions cause an updating unit of the CEM system to update, one or more document parameters 15 associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets. Additionally, the instructions cause a generation unit of the CEM system to generate, one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured 20 document validation set from the one or more preconfigured document validation sets. Also, the instructions cause a mapping unit of the CEM system to map, one or more documents from the set of documents and the one or more target validation sets. It is to be noted that the instructions further cause the generation unit of the CEM system to generate, one or more updated target validation sets 25 based on mapping the one or more documents from the set of documents and the one or more target validation sets. It is further noted that the instructions further cause a mapping unit of the CEM system to map, a set of target actions and the one or more updated target validation sets. The instructions further cause an identification unit of the CEM system to identify, one or more target documents 30 from the set of documents based on the set of target actions. The instructions further cause a configuration unit of the CEM system to configure, the user 7

document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions. 5 [0016] Yet another aspect of the present disclosure may relate to a user equipment (UE) comprising a memory and a processor connected to the memory. The processor is configured to send an input order comprising at least an order role and an order number to a customer engagement system. The CEM system configures a user document validation based on receiving, by a transceiver unit, 10 at the CEM system, the input order. The CEM system configures the user document validation based on fetching, by a fetching unit from a database at the CEM system, one or more preconfigured document validation sets based on at least one of the order role and the order number and fetch a set of documents based on the order number. The CEM system configures the user document 15 validation based on updating, by an updating unit, one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The CEM system further configures the user document validation based on generating, by a generation unit, at the CEM system [300], 20 one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The CEM system further configures the user document validation based on mapping, by a mapping unit, at the CEM system, one or more documents from the set of documents and the one 25 or more target validation sets. The CEM system configures the user document validation based on generating, by the generating unit, one or more updated target validation sets based on the mapping the one or more documents from the set of documents and the one or more target validation sets. The CEM system further configures the user document validation based on mapping, by the mapping unit 30 [306], a set of target action and the one or more updated target validation sets and identifying, by an identification unit, the one or more target documents from the 8

set of documents based on the set of target actions. The CEM system configures the user validation document based on configuring, by a configuration unit, the user document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target 5 actions. OBJECTS OF THE DISCLOSURE

[0017] Some of the objects of the present disclosure, which at least one 10 embodiment disclosed herein satisfies are listed herein below.

[0018] It is an object of the present disclosure to provide an efficient system and method for dynamically adding new validation set or modifying any validation sets and for accessing corresponding information as per business needs 15 with minimal UI side coding.

[0019] It is an object of the present disclosure to provide a system and a method for adding or modifying or update new validation set without the need of coding at the user interface side. 20

[0020] It is another object of the present disclosure to integrate the validation sets dynamically at the backend instead of hardcoding them.

[0021] It is an object of the present disclosure to provide a system and a 25 method for adding or modifying new validation set for split screen configuration.

[0022] It is yet another object of the present disclosure to provide a system and a method for calling separate API for downloading the pdf file to display the pdf file. 30 DESCRIPTION OF THE DRAWINGS 9

[0023] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same 5 parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight 10 the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0024] FIG. 1 illustrates an exemplary block diagram of a customer 15 engagement manager/ customer engagement management (CEM) system [100], in accordance with exemplary embodiments of the present disclosure.

[0025] FIG. 2 shows an exemplary architecture of the CEM system [200] for split screen configuration, in accordance with exemplary embodiments of the 20 present disclosure.

[0026] FIG. 3 illustrates an exemplary block diagram of a system [300] for configuring a user document validation, in accordance with exemplary implementations of the present disclosure. 25

[0027] FIG. 4 illustrates a flow diagram of a method [400] for configuring a user document validation, in accordance with exemplary implementations of the present disclosure. 10

[0028] FIG. 5 illustrates an exemplary block diagram of a computing device

[500] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. 5 [0029] FIG. 6 illustrates an exemplary system architecture for configuring a user document validation, in accordance with exemplary implementations of the present disclosure.

[0030] The foregoing shall be more apparent from the following more 10 detailed description of the disclosure. DETAILED DESCRIPTION

[0031] In the following description, for the purposes of explanation, various 15 specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may 20 not address any of the problems discussed above or might address only some of the problems discussed above.

[0032] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. 25 Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth. 30 11

[0033] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other 5 components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0034] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a 10 structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. 15

[0035] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is 20 not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be 25 inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.

[0036] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic 30 circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal 12

processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may 5 perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor. 10 [0037] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present 15 disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from 20 at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.

[0038] As used herein, “storage unit” or “memory unit” refers to a machine 25 or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit 30 stores at least the data that may be required by one or more units of the system to perform their respective functions. 13

[0039] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or 5 protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0040] All modules, units, components used herein, unless explicitly 10 excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field 15 Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0041] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting 20 data, signals, information or a combination thereof between units/components within the system and/or connected with the system.

[0042] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above- 25 mentioned and other existing problems in this field of technology by providing method and system of configuring a user document validation.

[0043] FIG. 1 illustrates an exemplary block diagram of a CEM system

[100], in accordance with exemplary embodiments of the present disclosure. For 30 example, and by no way limiting the scope of the present subject matter, the system [100] comprises an Enterprise Product Catalogue (EPC) [114], a 14

Fulfilment Management System (FMS) [110], a load balancer [108], a CEM/CRM server [104] comprising a plurality of micro-services and a CEM/CRM database [106]. A plurality of channels in an embodiment, such as but are not limited to a Point of Sale (POS) [116], a Digital Marketplace Platform 5 (DMP) [118], a web portal [120] and a CEM user interface (UI) [122] are configured to provide input data to the CEM server [104] through the load balancer [108].

[0044] FIG. 2 illustrates an exemplary block diagram of a CEM system 10 [200] having split screen configuration, in accordance with exemplary embodiments of the present disclosure. The CEM system [200] is similar to the CEM system [100] of FIG. 1. For example, and by no way limiting the scope of the present subject matter, the system comprises a Split Screen UI [202], a Customer Order Processing Microservice (COP) Instance [204], a Document 15 Management Server (DMS) Instance [206] and a database (DB) [208].

[0045] The Split Screen UI [202] shows validation set details over screen. The information of role and document configuration are shared between database [208] and the COP instance [204]. The COP instance [204] is responsible for 20 allocating the role associated with the order via the database (DB) [208] upon which the DB [208] sends document configuration associated with the corresponding role to the COP instance [204]. The DMS instance [206] and the COP Instance [204] share order ID and PDF file details information between them. 25

[0046] Referring to FIG. 3, an exemplary block diagram of a customer engagement (CEM) system [300] for configuring a user document validation, is shown, in accordance with the exemplary implementations of the present disclosure. The customer engagement (CEM) system [300] comprises at least one 30 transceiver unit [301], at least one fetching unit [302], at least one database [303], at least one updating unit [304], at least one generation unit [305], at least one 15

mapping unit [306], at least one identification unit [307], at least one configuration unit [308] and at least one user interface [300ui]. Also, all of the components/ units of the customer engagement system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures 5 all units shown within the customer engagement system should also be assumed to be connected to each other. Also, in.

[0047] FIG. 3 only a few units are shown, however, the customer engagement system [300] may comprise multiple such units or the customer 10 engagement system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the customer engagement system [300] may be present in a user device to implement the features of the present disclosure. The customer engagement system [300] may be a part of the user device / or may be independent 15 of but in communication with the user device/ equipment (may also referred herein as a UE). In another implementation, the customer engagement system [300] may reside in a server or a network entity. In yet another implementation, the customer engagement system [300] may reside partly in the server/ network entity and partly in the user device. 20

[0048] The customer engagement system [300] is configured for configuring a user document validation, with the help of the interconnection between the components/units of the customer engagement system [300]. 25 [0049] The transceiver unit [301] is configured to receive, an input order comprising at least an order role and an order number. It is to be noted that the input order may include information for traversing and processing the customer requests. It is further noted that the order number role may be used to indicate the nature of the order transaction. Also, the order number may include a unique 30 number signifying the order to refer the order from the other input orders. For 16

example, the input order may include the order role-order for purchase, the order number- 771P.

[0050] The fetching unit [302] is configured to fetch, from a database [303], 5 one or more preconfigured document validation sets based on at least one of the order role and the order number. The fetching unit [302] may search for the one or more preconfigured document validation sets in the database [303] to fetch the one or more preconfigured document validation sets. The fetching unit [302] is further configured to fetch, from the database [303], a set of documents based on 10 the order number. The fetching unit [302] may search for the set of documents in the database [303] based on the order number to fetch the set of documents.

[0051] The updating unit [304] is configured to update, one or more document parameters associated with each document from the set of documents, 15 in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The one or more document parameters may refer to a unique identity of each of the one or more document parameters. To update the one or more document parameters, the updating unit [304] may monitor each document from the set of documents to check for update in the one 20 or more document parameters. The generation unit [305] is configured to generate, one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets. 25 [0052] The mapping unit [306] is configured to map, one or more documents from the set of documents and the one or more target validation sets. It is important to note that said mapping is done by integrating them dynamically instead of hardcoding them. For e.g., one of the target validation set can be having documents- Proof of Identity (POI) document and Proof of Address (POA) 30 document. Also, the other validation set will display list of documents in dropdown and on click will display that file only. 17

[0053] In an exemplary implementation of the present disclosure, the generation unit [305] is further configured to generate, one or more updated target validation sets based on the mapping of the one or more documents from the set 5 of documents and the one or more target validation sets. The process of mapping may include aligning rules or conditions in the one or more documents from the set of documents with corresponding validation criteria in the one or more target validation sets in the documents. The process of generating the one or more updated target validation sets may include the generation unit [305] to monitor 10 the set of documents and the one or more target validation sets to generate the one or more updated target validation sets.

[0054] In an exemplary implementation of the present disclosure, the mapping unit [306] is further configured to map, a set of target action and the one 15 or more updated target validation sets.

[0055] The identification unit [307] is configured to identify, one or more target documents from the set of documents based on the set of target actions. To identify the one or more target documents, the identification unit [307] may 20 analyze the set of documents.

[0056] The configuration unit [308] is configured to configure, the user document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target 25 actions. The process of configuration may involve the configuration unit [308] to create or update the one or more document parameters or may configure the user document validation.

[0057] In an exemplary implementation of the present disclosure, the one 30 or more preconfigured document validation sets is at least one of: a compare of customer photo and proof of identity (POI) document, a compare of POI 18

document versus proof of address (POA) document and display list of documents in dropdown and on click display the clicked file only.

[0058] In an exemplary implementation of the present disclosure, the one 5 or more document parameters associated with each document from the set of documents, comprises, a document status, a document filename, and a document URL.

[0059] In an exemplary implementation of the present disclosure, the 10 generation unit [305] is further configured to generate a validation report associated with the input order in a predefined format. The generation unit [305] is further configured to display, at a user interface [300ui], the validation report.

[0060] In an exemplary implementation of the present disclosure, the 15 predefined format of the validation report associated with the input order comprises: a color code for each of at least missed documents, available documents, and corrupted documents.

[0061] In an exemplary implementation of the present disclosure, the set of 20 target actions is at least one of a download pdf URL action, and a display pdf URL action.

[0062] In an exemplary implementation of the present disclosure, the generation unit [305] is further configured to generate the one or more target 25 validation sets based on at least one of a user input, the one or more document parameters and the one or more preconfigured document validation sets. The generation unit [305] may monitor the user input to generate the one or more target validation sets. In an example, the one or more target validation sets may include email addresses, phone numbers and the like. 30 19

[0063] Referring to FIG. 4, an exemplary method flow diagram [400] for configuring a user document validation on a customer engagement management (CEM) system [300], in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed 5 by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].

[0064] At step [404], the method [400] comprises receiving, by a 10 transceiver unit [301] at the CEM system [300], an input order comprising at least an order role and an order number.

[0065] At step [406], the method [400] comprises fetching, by a fetching unit [302] from a database [303] at the CEM system [300], one or more 15 preconfigured document validation sets based on at least one of the order role and the order number.

[0066] In an exemplary aspect of the present disclosure, the one or more preconfigured document validation sets is at least one of: a compare customer 20 photo and proof of identity (POI) document, a compare POI document versus proof of address (POA) document and display list of documents in dropdown and on click display the clicked file only.

[0067] At step [408], the method [400] comprises fetching, by the fetching 25 unit [302] from the database [303], a set of documents based on the order number.

[0068] At step [410], the method [400] comprises updating, by an updating unit [304], one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from 30 the one or more preconfigured document validation sets. 20

[0069] In an exemplary aspect of the present disclosure, the one or more document parameters associated with each document from the set of documents, comprises, a document status, a document filename and a document URL. 5 [0070] At step [412], the method [400] comprises generating, by a generation unit [305], at the CEM system [300], one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets. 10

[0071] In an exemplary aspect of the present disclosure, the method [400] further comprises generating, by the generation unit [305], a validation report associated with the input order in a predefined format. And the method [400] further comprises displaying, by a user interface [300ui], at the CEM system 15 [300], the validation report.

[0072] In an exemplary aspect of the present disclosure, the predefined format of the validation report associated with the input order comprises: a color code for each of the at least missed documents, available documents and 20 corrupted documents.

[0073] At step [414], the method [400] comprises mapping, by a mapping unit [306], at the CEM system [300], one or more documents from the set of documents and the one or more target validation sets. 25

[0074] At step [416], the method [400] comprises generating, by the generating unit [305], one or more updated target validation sets based on the mapping the one or more documents from the set of documents and the one or more target validation sets. 30 21

[0075] In an exemplary aspect of the present disclosure, the method [400] further comprises generating, by the generation unit [305], the one or more target validation sets based on at least one of a user input, the one or more document parameters and the one or more preconfigured document validation sets. 5

[0076] At step [418], the method [400] comprises mapping, by the mapping unit [306], a set of target action and the one or more updated target validation sets.

[0077] At step [420], the method [400] comprises identifying, by an 10 identification unit [307], one or more target documents from the set of documents based on the set of target actions.

[0078] In an exemplary aspect of the present disclosure, in the disclosed method [400], the set of target actions is at least one of a download pdf URL 15 action, and a display pdf URL action.

[0079] At step [422], the method [400] comprises configuring, by a configuration unit [308], the user document validation associated with the input order based on identifying the one or more target documents from the set of 20 documents based on the set of target actions.

[0080] Thereafter, the method [400] terminates at step [424].

[0081] The present disclosure can also be implemented on a computing 25 device [500] as shown in FIG. 5. FIG. 5 illustrates an exemplary block diagram of the computing device [500] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [500] may also implement the method [400] for configuring a user document validation utilising 30 the customer engagement system [300] data utilising the system [300]. In another implementation, the computing device [500] itself implements the method [400] 22

for configuring a user document validation on the customer engagement system [300], wherein said one or more units/ components are capable of implementing the features as disclosed in the present disclosure. 5 [0082] The computing device [500] may include a bus [502] or other communication mechanism for communicating information, and a hardware processor [504] coupled with bus [502] for processing information. The hardware processor [504] may be, for example, a general-purpose microprocessor. The computing device [500] may also include a main memory [506], such as a 10 random-access memory (RAM), or other dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504]. The main memory [506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [504]. Such instructions, when stored in non-transitory 15 storage media accessible to the processor [504], render the computing device

[500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [500] further includes a read only memory (ROM) [508] or other static storage device coupled to the bus [502] for storing static information and instructions for the processor [504]. 20

[0083] A storage device [510], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [502] for storing information and instructions. The computing device [500] may be coupled via the bus [502] to a display [512], such as a cathode ray tube (CRT), Liquid crystal Display 25 (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [514], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [502] for communicating information and command selections to the processor [504]. Another type of user input device may be a cursor controller 30 [516], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [504], and for 23

controlling cursor movement on the display [512]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane. 5 [0084] The computing device [500] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [500] causes or programs the computing device [500] to be a special-purpose machine. According to one implementation, the techniques herein are 10 performed by the computing device [500] in response to the processor [504] executing one or more sequences of one or more instructions contained in the main memory [506]. Such instructions may be read into the main memory [506] from another storage medium, such as the storage device [510]. Execution of the sequences of instructions contained in the main memory [506] causes the 15 processor [504] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0085] The computing device [500] also may include a communication 20 interface [518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface

[518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a 25 corresponding type of telephone line. As another example, the communication interface [518] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [518] sends and receives electrical, electromagnetic or optical signals that carry digital 30 data streams representing various types of information. 24

[0086] The computing device [500] can send messages and receive data, including program code, through the network(s), the network link [520] and the communication interface [518]. In the Internet example, a server [530] might transmit a requested code for an application program through the Internet [528], 5 the ISP [526], the local network [522], the host [524] and the communication interface [518]. The received code may be executed by the processor [504] as it is received, and/or stored in the storage device [510], or other non-volatile storage for later execution. 10 [0087] Referring to FIG. 6, an exemplary system architecture diagram

[600] for configuring a user document validation, in accordance with exemplary implementations of the present disclosure.

[0088] In an exemplary embodiment, the system architecture [600] may 15 include sub-components of the system [100] (as shown in FIG. 1) of the current disclosure. In another embodiment, the architecture [600] may be used to implement the steps of method [400] (as shown in FIG. 4) for configuring a user document validation along with the system [200] (as shown in FIG. 2) which is based on the architecture [600] of the system. In a preferred embodiment, the 20 architecture [600] of the system comprises a plurality of components. For example, and by no way limiting the scope of the present subject matter, the system architecture [600] (as shown in FIG. 6 ) comprises an evolved packet core (EPC) [602], a fulfilment management system (FMS) [604], a plurality of channels [606], a load balancer [608], a Data Information framework (DIF) [610] 25 comprising a plurality of micro-services and a database [612]. The channels [606] are configured to provide input data to the CRM server [616] through a load balancer [608]. In an embodiment, some examples of the channels include but are not limited to a POS [620], a data management platform DMP [622], a web portal [624] and a CRM user interface (UI) [626]. It is to be noted that the workflow 30 engine is mix of generic configurations and it also provides space for custom logic so that all the milestones / order journeys can be autonomous and segregated. It is to be noted that the EPC [602], the FMS [604], the load balancer [608], the 25

[POS [620], the DMP [622], the web portal [624], the CRM UI [626] are similar to the EPC [114], the FMS [110], the load balancer [108], the POS [116], the DMP [118], the web portal [120], and the CRM UI [122] respectively of FIG. 1. 5 [0089] The CRM server [616] contains different microservices which cater to different APIs. Each microservices serves a particular context, for e.g., 10 15 • COP_MS deals with order related APIs – submit order, query order, modify order • CIS instances deal with customer related APIs – create, modify or deactivate customer • L2O instances deals with APIs that manages the lifecycle of leads and prospects • OAM instance deals with the maintenance and operation of all the microservice instances and communicate with outer products related to alarms, KPIs or other management, health check-up information

[0090] Channels [606] are used to send requests for APIs to servers, for 20 25 example, the POS (Point of Sale) [620], the Digital Marketplace (DMP) [622], the web portal [624], the CRM UI [626] etc. These channels are connected to servers using the load balancer [608] or FMS [604]. The channels [606] which are tightly coupled to CRM server [616] e.g., the CRM UI [626] communicates directly via the load balancer [608] while other systems which belong to different product such as the web portal [624], the POS [620] communicates to servers using the FMS [604]. The FMS [604] is a middleware which links two different products and performs language translations or workflow management. The CRM server [616] is similar to the CRM server [104] of FIG. 1.

[0091] The EPC (Enterprise Product Catalogue) [602] is a centralised data repository which drives BSS telecom operations and some network nodes. For 30 e.g., 5G charging system, called PCF. 26

[0092] The FMS (Fulfilment Management System) [604], a middleware, which acts a mediator between two different products and at the same time, provides language translation. E.g., if one product understands SOAP protocol 5 while other one understands RESTful services, the FMS [604] will translate the messages between these 2 nodes and ensure seamless communication.

[0093] The Databases [612] connected to servers which persist the business data related to customers, orders, leads, prospects and server configurations. 10

[0094] SMP [628] refers to a Service Management Platform, which deals with the installation processes at customer premises, handling repair mechanism and technician visit to network sites. 15 [0095] The web portal [624] refers to a self-help portal via which a user/customer can login, view his/her profile and manage his/her services.

[0096] The present disclosure further discloses a non-transitory computer-readable storage medium storing instruction for configuring a user document 20 validation, the storage medium comprising executable code which, when executed by one or more units of a customer engagement (CEM) system [300], causes a transceiver unit [301] of the CEM system [300] to receive, an input order comprising at least an order role and an order number; a fetching unit [302] of the CEM system [300] to fetch, from a database [303], one or more preconfigured 25 document validation sets based on at least one of the order role and the order number. Further, the instructions cause the fetching unit [302] of the CEM system [300] to fetch, from the database [303], a set of documents based on the order number. Furthermore, the instructions cause an updating unit [304] of the CEM system [300] to update, one or more document parameters associated with each 30 document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets. 27

Additionally, the instructions cause a generation unit [305] of the CEM system

[300] to generate, one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets. Also, 5 the instructions cause a mapping unit [306] of the CEM system [300] to map, one or more documents from the set of documents and the one or more target validation sets. It is to be noted that the instructions further cause the generation unit [305] of the CEM system [300] to generate, one or more updated target validation sets based on mapping the one or more documents from the set of 10 documents and the one or more target validation sets. It is further noted that the instructions further cause a mapping unit [306] of the CEM system [300] to map, a set of target actions and the one or more updated target validation sets. The instructions further cause an identification unit [307] of the CEM system [300] to identify, one or more target documents from the set of documents based on the 15 set of target actions. The instructions further cause a configuration unit [308] of the CEM system [300] to configure, the user document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions. 20 [0097] The present disclosure further discloses a user equipment (UE) comprising a memory and a processor connected to the memory. The processor is configured to send an input order comprising at least an order role and an order number to a customer engagement (CEM) system [300]. The CEM system [300] configures a user document validation based on receiving, by a transceiver unit 25 [301], at the CEM system [300], the input order. The CEM system [300] configures the user document validation based on fetching, by a fetching unit [302] from a database [303] at the CEM system [300], one or more preconfigured document validation sets based on at least one of the order role and the order number and fetch a set of documents based on the order number. The CEM system 30 [300] configures the user document validation based on updating, by an updating unit [304], one or more document parameters associated with each document from 28

the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The CEM system [300] further configures the user document validation based on generating, by a generation unit [305], at the CEM system [300], one or more target validation sets 5 based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets. The CEM system [300] further configures the user document validation based on mapping, by a mapping unit [306], at the CEM system, one or more documents from the set of documents and the one or more 10 target validation sets. The CEM system [300] configures the user document validation based on generating, by the generating unit [305], one or more updated target validation sets based on the mapping the one or more documents from the set of documents and the one or more target validation sets. The CEM system [300] further configures the user document validation based on mapping, by the 15 mapping unit [306], a set of target action and the one or more updated target validation sets and identifying, by an identification unit [307], the one or more target documents from the set of documents based on the set of target actions. The CEM system [300] configures the user validation document based on configuring, by a configuration unit, the user document validation associated with the input 20 order based on identifying the one or more target documents from the set of documents based on the set of target actions.

[0098] As is evident from the above, the present disclosure provides a technically advanced solution for configuring a user document validation. The 25 present solution thus provides an efficient system [300] and method [400] for adding new validation set or modifying any validation sets and for accessing corresponding information as per business needs without UI side coding. The present method [400] uses an API to fetch document validation set configuration from the database [303] based on role and order number. Based on Order Id, the 30 API fetches documents from DMS [206], enriches the configurations with updated document status update document status, filename, and URL in each 29

validation set, and return them to the UI. Further, the number of validation sets and the name of the validation sets is received, for integrating them dynamically instead of hardcoding them. From this API, the information on which validation set and which documents need to be compared can also be received. 5

[0099] Thus, the present solution absolves the need for hardcoding process, which is less feasible and less efficient solution for deploying new validation sets. Further, the present disclosure overcome the problems stated in the background section by providing an efficient system [300] and method [400] for adding new 10 validation set or modifying any validation sets and for accessing corresponding information as per business needs without the user interface (UI) [300ui] side coding. The present disclosure uses an API to fetch document validation sets configuration from the database [303] based on role and order number. The number of validation sets and the name of the validation sets are received and 15 dynamically integrated instead of having the need to hardcode them. From this API, the information on which validation set and which documents need to be compared can also be received.

[0100] While considerable emphasis has been placed herein on the 20 disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to 25 be implemented is illustrative and non-limiting.

[0101] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose 30 a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. 30

The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within 5 the scope of the present disclosure.

We Claim: 1. A method [400] for configuring a user document validation on a customer engagement management (CEM) system [300], the method [400] comprising: 5 - receiving, by a transceiver unit [301] at the CEM system [300], an input order comprising at least an order role and an order number; - fetching, by a fetching unit [302] from a database [303] at the CEM system [300], one or more preconfigured document validation sets based on at least one of the order role and the order number; 10 - fetching, by the fetching unit [302] from the database [303], a set of documents based on the order number; - updating, by an updating unit [304], one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more 15 preconfigured document validation sets; - generating, by a generation unit [305], at the CEM system [300], one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets; 20 - mapping, by a mapping unit [306], at the CEM system [300], one or more documents from the set of documents and the one or more target validation sets; - generating, by the generating unit [305], one or more updated target validation sets based on the mapping the one or more documents from 25 the set of documents and the one or more target validation sets; - mapping, by the mapping unit [306], a set of target action and the one or more updated target validation sets; - identifying, by an identification unit [307], one or more target documents from the set of documents based on a set of target actions; 30 and

- configuring, by a configuration unit [308], the user document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions. 5 2. The method [400] as claimed in claim 1, wherein the one or more preconfigured document validation sets is at least one of: a compare customer photo and proof of identity (POI) document, a compare POI document versus proof of address (POA) document and display list of documents in dropdown and on click display the clicked file only. 10 3. The method [400] as claimed in claim 1, wherein the one or more document parameters associated with each document from the set of documents, comprises, a document status, a document filename and a document URL. 4. The method [400] as claimed in claim 1, the method [400] further comprises: 15 - generating, by the generation unit [305], a validation report associated with the input order in a predefined format; and - displaying, by a user interface [300ui], at the CEM system [300], the validation report. 5. The method [400] as claimed in claim 4, wherein the predefined format of 20 the validation report associated with the input order comprises: a color code for one or more missed documents, one or more available documents and one or more corrupted documents. 6. The method [400] as claimed in claim 1, wherein the set of target actions is at least one of a download pdf URL action, and a display pdf URL action. 25 7. The method [400] as claimed in claim 1, the method [400] further comprises generating, by the generation unit [305], the one or more target validation sets based on at least one of a user input, the one or more document parameters and the one or more preconfigured document validation sets. 8. A customer engagement (CEM) system [300] for configuring a user 30 document validation, the CEM system [300] comprising: - a transceiver unit [301] configured to:

o receive, an input order comprising at least an order role and an order number; - a fetching unit [302] connected to at least the transceiver unit [301], the fetching unit [302] configured to: 5 o fetch, from a database [303], one or more preconfigured document validation sets based on at least one of the order role and the order number; o fetch, from the database [303], a set of documents based on the order number; 10 - an updating unit [304] connected to at least the fetching unit [302], the updating unit [304] configured to update, one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets; 15 - a generation unit [305] connected to at least the updating unit [304], the generation unit [305] configured to generate, one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets; 20 - a mapping unit [306] connected to at least the generation unit [305], the mapping unit [306] configured to map, one or more documents from the set of documents and the one or more target validation sets; wherein the generation unit [305] is further configured to generate, one or more updated target validation sets based on mapping the one or 25 more documents from the set of documents and the one or more target validation sets; and wherein the mapping unit [306] is further configured to map, a set of target actions and the one or more updated target validation sets; - an identification unit [307] connected to at least the mapping unit [306], 30 the identification unit [307] configured to identify, one or more target

documents from the set of documents based on the set of target actions; and - a configuration unit [308] connected to at least the identification unit

[307], the configuration unit [308] configured to configure, the user 5 document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions. 9. The CEM system [300] as claimed in claim 8, wherein the one or more preconfigured document validation sets is at least one of: a compare of 10 customer photo and proof of identity (POI) document, a compare of POI document versus proof of address (POA) document and display list of documents in dropdown and on click display the clicked file only. 10. The CEM system [300] as claimed in claim 8, wherein the one or more document parameters associated with each document from the set of 15 documents, comprises, a document status, a document filename and a document URL. 11. The CEM system [300] as claimed in claim 8, wherein the generation unit

[305] is further configured to: - generate a validation report associated with the input order in a 20 predefined format; and - display, at a user interface [300ui], the validation report. 12. The CEM system [300] as claimed in claim 11, wherein the predefined format of the validation report associated with the input order comprises: a color code for one or more missed documents, one or more available 25 documents and one or more corrupted documents. 13. The CEM system [300] as claimed in claim 8, wherein the set of target actions is at least one of a download pdf URL action, and a display pdf URL action. 14. The CEM system [300] as claimed in claim 8, wherein the generation unit 30 [305] is further configured to generate the one or more target validation sets

5 10 15 20 25 30

based on at least one of a user input, the one or more document parameters and the one or more preconfigured document validation sets. 15. A user equipment (UE) comprising: a memory; and on: -a processor connected to the memory, the processor configured to send an input order comprising at least an order role and an order number to a customer engagement (CEM) system [300], wherein the CEM system [300] configures a user document validation based receiving, by a transceiver unit [301] at the CEM system [300], the input order; -fetching, by a fetching unit [302] from a database [303] at the CEM system [300], one or more preconfigured document validation sets based on at least one of the order role and the order number; -fetching, by the fetching unit [302] from the database [303], a set of documents based on the order number; -updating, by an updating unit [304], one or more document parameters associated with each document from the set of documents, in each of the preconfigured document validation set from the one or more preconfigured document validation sets; -generating, by a generation unit [305], at the CEM system [300], one or more target validation sets based on the updating of the one or more document parameters in each of the preconfigured document validation set from the one or more preconfigured document validation sets; -mapping, by a mapping unit [306], at the CEM system [300], one or more documents from the set of documents and the one or more target validation sets; -generating, by the generating unit [305], one or more updated target validation sets based on the mapping the one or more documents from the set of documents and the one or more target validation sets;

36

- mapping, by the mapping unit [306], a set of target action and the one or more updated target validation sets; - identifying, by an identification unit [307], one or more target documents from the set of documents based on a set of target actions; 5 and - configuring, by a configuration unit [308], the user document validation associated with the input order based on identifying the one or more target documents from the set of documents based on the set of target actions.

Documents

Sign in to open
Application documents
1 202321048581-STATEMENT OF UNDERTAKING (FORM 3) [19-07-2023(online)].pdf 19 Jul 2023
2 202321048581-PROVISIONAL SPECIFICATION [19-07-2023(online)].pdf 19 Jul 2023
3 202321048581-FORM 1 [19-07-2023(online)].pdf 19 Jul 2023
4 202321048581-FIGURE OF ABSTRACT [19-07-2023(online)].pdf 19 Jul 2023
5 202321048581-DRAWINGS [19-07-2023(online)].pdf 19 Jul 2023
6 202321048581-FORM-26 [18-09-2023(online)].pdf 18 Sep 2023
7 202321048581-Proof of Right [10-10-2023(online)].pdf 10 Oct 2023
8 202321048581-ORIGINAL UR 6(1A) FORM 1 & 26)-041223.pdf 09 Dec 2023
9 202321048581-FORM-5 [18-07-2024(online)].pdf 18 Jul 2024
10 202321048581-ENDORSEMENT BY INVENTORS [18-07-2024(online)].pdf 18 Jul 2024
11 202321048581-DRAWING [18-07-2024(online)].pdf 18 Jul 2024
12 202321048581-CORRESPONDENCE-OTHERS [18-07-2024(online)].pdf 18 Jul 2024
13 202321048581-COMPLETE SPECIFICATION [18-07-2024(online)].pdf 18 Jul 2024
14 Abstract-1.jpg 30 Sep 2024