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 DYNAMIC
TABLE FORMS”
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 DYNAMIC TABLE
FORMS
TECHNICAL FIELD
[0001] Embodiments of the present disclosure relate to network performance management systems. More particularly, embodiments of the present disclosure relate to configuring dynamic table forms.
BACKGROUND
[0002] The following description of the related art is intended to provide 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.
[0003] The management of product sync catalogues often involves working with multiple tables along with mapping tables associated with them. Creating forms for these tables and displaying related meta table data can be a challenging task. Traditionally, the creation of the forms required the creation of individual forms for each table, along with multiple application programming interfaces (APIs) calls to fetch data from the individual forms.
[0004] In the current existing solutions, in the product sync catalogue, there are N tables with different columns and mapping tables associated with it. In order to create forms for the N tables and show their related meta table data, mapping tables data is a feasible option but a cumbersome task as well. Therefore, the creation of the N tables with the individual forms having multiple API calls to fetch data from the individual forms, was proposed. It is to be noted that the N is indicative of a

dynamic number of the tables. However, that only led to the hassle of duplication/ recreation of forms and writing same type of APIs calls for fetching data for the individual forms. This further increased the magnitude of cost, time and effort involved in the tedious process of individual forms’ creation.
[0005] Thus, there is a need to address the above-mentioned problems in creation of new forms or adding new fields in tables easily for different configuration.
SUMMARY
[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.
[0007] An aspect of the present disclosure may relate to a method for configurating dynamic table forms. The method comprises displaying, by a display unit, a user interface (UI) for selecting a table form from a dropdown menu comprising a plurality of predefined table forms. The method further comprises upon selection of the table form, displaying, by the display unit, a set of predefined fields of the selected table form along with a set of configuration options for each field. The method further comprises generating, by a generating unit, for each table column, a form field in the selected table form. The method further comprises storing, by a storage unit, the set of configuration options to configure the table form. And the method also comprises displaying, by the display unit, the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition of new fields to the plurality of predefined table forms with minimal configuration effort.

[0008] In an exemplary aspect of the present disclosure, in the disclosed method, the configuration options comprise at least one of display name, placeholder, and validation rule.
[0009] In an exemplary aspect of the present disclosure, in the disclosed method, the form field is associated with at least one of a UI display name, and a set of validation rules, and is configured to map to the set of related table entities via a dynamic lookup feature, wherein the dynamic lookup feature maps the set of related table entities based on primary key details, which uniquely identify records in the table, and foreign key details, which establish relationship between records in different tables by linking a field in one table to a unique identifier in another table.
[0010] In an exemplary aspect of the present disclosure, in the disclosed method, the dynamic lookup feature further comprises a capability to fetch the set of metadata dynamically from a database.
[0011] In an exemplary aspect of the present disclosure, the method further comprises enabling the user, by a customization unit, to customize the form field by adding or removing fields from the plurality of predefined table forms.
[0012] In an exemplary aspect of the present disclosure, in the disclosed method, the table form supports Create, Read, Update, and Delete (CRUD) operations.
[0013] In an exemplary aspect of the present disclosure, in the method further comprises validating, by an authentication unit, configuration for the form field, comprising at least one of mandatory, editable, and non-editable set of attributes.
[0014] Another aspect of the present disclosure may relate to a system for configurating dynamic table forms. The system comprises a display unit configured to display a user interface (UI) for selecting a table form from a dropdown menu comprising a plurality of predefined table forms. The display unit is further

configured to display a set of predefined fields of the selected table form along with a set of configuration options for each field. The system further comprises a generating unit configured to generate for each table column, a form field in the selected table form. The system further comprises a storage unit configured to store the set of configuration options to configure the table form. The display unit is further configured to display the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition of new fields to the plurality of predefined table forms with minimal configuration effort.
[0015] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for configurating dynamic table forms, the instructions include executable code which, when executed by a one or more units of a system, causes: a display unit to display a user interface (UI) for selecting a table form from a dropdown menu comprising a plurality of predefined table forms; and to display a set of predefined fields of the selected table form along with a set of configuration options for each field. Further, the instructions include executable code which, when executed causes a generating unit to generate for each table column, a form field in the selected table form. Further, the instructions include executable code which, when executed causes a storage unit to store the set of configuration options to configure the table form. Further, the instructions include executable code which, when executed causes the display unit to display the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition of new fields to the plurality of predefined table forms with minimal configuration effort.
[0016] Yet another aspect of the present disclosure may relate to user equipment (UE) for configuring dynamic table forms comprising a display unit configured to display a user interface (UI) for selecting a table form from a dropdown menu comprising a plurality of predefined table forms. The display unit is further

configured to display a set of predefined fields of the selected table form along with a set of configuration options for each field. The UE further comprises a generation unit configured to generate for each table column, a form field in the selected table form. The UE further comprises a storage unit configured to store the set of configuration options to configure the table form. The display unit of the system is further configured to display the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition of new fields to the plurality of predefined table forms with minimal configuration effort.
OBJECTS OF THE DISCLOSURE
[0017] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0018] An object of the disclosure is providing dynamic table configuration to create form dynamically with minimal configuration by allowing users to configure table columns with form fields.
[0019] Another object of the present disclosure is providing table fields that are mapped to one form input fields which will get created dynamically in table form.
[0020] Another object of the present disclosure is to reduce duplication/ recreation of forms and writing same type of API calls.
[0021] Another object of the present disclosure is allowing the user to view predefined fields of table with form display field details configuration.
[0022] Another object of the present disclosure is allowing the user to view table forms with validation and meta data of entities.

[0023] Another object of the present disclosure is to avoid code duplication and save time in development.
[0024] Another object of the present disclosure is for dynamic table configuration.
DESCRIPTION OF THE DRAWINGS
[0025] 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 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 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.
[0026] FIG. 1 illustrates an exemplary system architecture for dynamic table configuration upon which the features of the present disclosure may be implemented, in accordance with exemplary implementation of the present disclosure.
[0027] FIG. 2 illustrates an exemplary scenario diagram of a process of dynamic table configuration which is followed by the features of the present disclosure, in accordance with exemplary implementation of the present disclosure.
[0028] FIG. 3 illustrates an exemplary block diagram of a system for configuring dynamic table forms, in accordance with exemplary implementations of the present disclosure.

[0029] FIG. 4 illustrates a method flow diagram for configuring dynamic table forms, in accordance with exemplary implementations of the present disclosure.
[0030] FIG. 5 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0032] In the following description, for the purposes of explanation, various 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 not address any of the problems discussed above or might address only some of the problems discussed above.
[0033] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. 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.

[0034] 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 components
5 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0035] 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 structure
10 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
[0036] 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 not
20 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 inclusive—in a manner
25 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0037] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
30 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
9

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 perform signal coding data processing,
5 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.
[0038] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
10 “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 disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart
15 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 at least one of
a transceiver unit, a processing unit, a storage unit, a detection unit and any other
20 such unit(s) which are required to implement the features of the present disclosure.
[0039] As used herein, “storage unit” or “memory unit” refers to a machine 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
25 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 stores at least the data that may be required by one or more units of the system to perform their respective functions.
30
10

[0040] 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 protocols that define
communication or interaction of one or more modules or one or more units with
5 each other, which also includes the methods, functions, or procedures that may be
called.
[0041] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
10 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 Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
15
[0042] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
20
[0043] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of for configuring dynamic table forms.
25
[0044] Referring to FIG. 1, an exemplary system architecture [100] for dynamic table configuration is shown, upon which the features of the present disclosure may be implemented in accordance with the exemplary embodiments of the present disclosure.
30
11

[0045] In a preferred embodiment, the system architecture [100] 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 [100] (as shown in FIG. 1)
comprises an Enterprise Product Catalogue User Interface (EPC UI) [102], an EPC
5 [101], a fulfilment management system (FMS) [106], a plurality of channels, a load
balancer [104], a Subscription Engine (SE) [107], a Data Information framework (DIF) [109] comprising a plurality of micro-services and channels.
[0046] The channels are configured to provide input data to a Customer
10 Relationship Management (CRM) server [108]. In the system [100], the channel(s)
refer to different user interfaces, such as web applications, web browsers, the
Enterprise Product Catalogue User Interface (EPC UI) [102] or external systems,
through which REST application programming interfaces (APIs) requests are sent
to the Enterprise Product Catalogue (EPC) [101]. The channels act as a means of
15 communication between users or external systems and the EPC [101]. When a
REST API request is sent to the EPC [101], the EPC [101] goes through an
authentication and authorization process performed by an IAM (Identity Access
Management) instance [110]. The IAM instance [110] verifies identity and
permissions of the requester to ensure they have the necessary access rights to
20 interact with the EPC [101].
[0047] Once the REST API request is validated and authorized by the IAM instance [110], the REST API request is passed on to a load balancer [104]. The load balancer [104] is configured to distribute incoming REST API requests across
25 multiple backend EPC application instances. This ensures that the workload is
evenly distributed and helps improve the performance and scalability of the system [100]. The backend EPC application instance receives the REST API request from the load balancer [104]. The backend EPC instance handles and processes the REST API request by performing the necessary operations and generating the appropriate
30 response. The necessary operation may include retrieving data, applying business
logic, and interacting with other components within the EPC [101]. Further, the
12

EPC [101] includes an Operation and Administration Management (OAM) instance
[111]. The OAM instance [111] serves as a broadcaster in the system [100]. The
OAM instance [111] manages the microservices registry, which contains
information about the various microservices within the EPC [101]. The OAM
5 instance [111] may include details such as dependencies, communication protocols,
and other necessary information for the microservices to effectively communicate with each other. The OAM instance [111] ensures that the different microservices can discover and interact with one another seamlessly.
10 [0048] Further, the EPC [101] is associated with a Fulfilment Management System
(FMS) [106]. The FMS [106] acts as a middleware component in the system [100]. The FMS [106] facilitates the integration of the API services provided by the EPC [101] with other system nodes or external systems. The FMS [106] handles the routing, transformation, and communication between different components,
15 allowing for smooth interoperability and data exchange. Also, the EPC [101] may
be associated with the ES cluster [103].
[0049] The Elastic Search (ES) cluster [103] refers to a database used to store data
within the system [100]. The ES cluster [103] is responsible for persisting and
20 retrieving data required by the EPC [101]. The ES cluster [103] is designed to
handle large volumes of data and provide efficient data storage and retrieval capabilities.
[0050] The FMS is associated with a subscription engine (SE) [107], a CRM server
25 [108] and a Data Information Framework (DIF) [109]. The Subscription Engine
(SE) [107] may provide a flexible solution for managing a customer lifecycle. The
customer lifecycle refers to a process followed by a consumer from joining a
subscription, to using the services and making the bill payment. The CRM server
[108] may contain different micro services which cater to different APIs. Each
30 microservice serves a particular context, for e.g.,
13

• COP_MS deals with order related APIs – submit order, query order, modify order
• CIS instances deals with customer related APIs – create, modify or deactivate customer
5 • 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
10 check-up information
[0051] The DIF [109] refers to a structured approach or system that manages and
utilizes data within an organization. The DIF [109] may include processes,
standards, technologies, and policies designed to ensure that data is collected,
15 stored, processed, and accessed in a secure manner.
[0052] Thus, summarizing from the above explanation, it is to be noted that the channels serve as user interfaces or external systems that send the REST API requests to the EPC [101]. The REST API requests undergo authentication and
20 authorization with facilitation of a firewall [105]. The REST APIs are further load
balanced with using the load balancer [104]. The REST APIs are then processed by the EPC instances. Further, the OAM instance [111] manages the microservices registry for effective communication, The FMS [106] acts as middleware for integration, and the ES cluster [103] serves as the database for data storage.
25
[0053] Referring to FIG. 2, an exemplary scenario diagram of a process [200] of dynamic table configuration is depicted, in accordance with exemplary implementation of the present disclosure.
14

[0054] The dynamic table configuration allows users to configure table columns
with form fields. This is done by mapping each table field to one form input fields
that gets created dynamically in the table form. It is to be noted the form input fields
may include static input fields (such as but not limited to textbox, radio and select).
5 It is further noted that the form input field also include dynamic lookup i.e., the
meta data which is fetched from a database (i.e., a table). The dynamic table configuration is carried as per the process [200]. The process [200] involves the following steps as mentioned below.
10 [0055] At step [202], the process [200] involves selecting dynamic table forms that
is to be configured. This is performed by configuring a table structure with a form field detail that are displayed. For instance, the table structure may consist of fields defined in the table such as but not limited to field identifier, name, address, etc. The form may be from a dropdown menu. Upon selection of the dynamic table, the
15 configuration may be loaded via an Application Programming Interface (API) for
the table and fields in the table. The table may be configured to the type of data that may be associated with the field in the table. For example, a user may be able to view predefined form fields of the table with form field details configuration. It is to be noted that the form field details configuration may include a configuration of
20 the field where the data for the field will get populated in the table. The form field
details configuration may also be indicative of validation of the data that got populated. In the form field details configuration, at least one of: the form field, the name, place holder and different validation may be configured.
25 [0056] Next, at step [204], the process [200] involves prepopulating a default
configuration of the dynamic table form. For example, for each column of the dynamic table form, one form field is created with a UI display name, validation, and mapping related table entities that have a dynamic lookup. It is important to note that the dynamic lookup refers to a dropdown for the particular field in the
30 table form also including a user interface (UI) form] that is populated from which
field of corresponding table. For instance, in a table comprising plan offering to a
15

sale channel, the mapping of the table plan offering-field of the form will get populated from the plan offering table id-field and corresponding sales channel id-field.
5 [0057] Further, at step [206], the process [200] involves configuring/customizing
the form fields of each column of the dynamic table form.
[0058] Thereafter, at step [208], the process [200] encompasses the use of the
configuration to create forms in the application to perform Create, Read, Update,
10 and Delete (CRUD) operations.
[0059] It is to be noted that in the process [200], in dynamic lookup of the column of the dynamic table form, the mapping related table entities are mapped with their primary and foreign key details. After saving the configuration details of the
15 dynamic table form, the user can view configured dynamic table forms with
validation and meta data of entities. Thus, the creation of new table or adding new field in the dynamic table form becomes easier as opposed to creating multiple forms from the dynamic table form. It is further noted that the dynamic table configuration helps in the creation of the form dynamically with minimal
20 configuration.
[0060] Referring to FIG. 3, an exemplary block diagram of a system [300] for dynamically configuring table forms, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one
25 display unit [301], at least one generating unit [302], at least one storage unit [303],
at least one database [304], at least one customization unit [305] and at least one authentication unit [306]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be
30 connected to each other. Also, in FIG. 3 only a few units are shown, however, the
system [300] may comprise multiple such units or the system [300] may comprise
16

any such numbers of said units, as required to implement the features of the present
disclosure. Further, in an implementation, the system [300] may be present in a user
device/ equipment (may also referred herein as a UE) to implement the features of
the present disclosure. The system [300] may be a part of the user device / or may
5 be independent of but in communication with the user device. In another
implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
10 [0061] The system [300] is configured for configuring dynamic table forms, with
the help of the interconnection between the components/units of the system [300]. It is to be noted that the dynamic table forms are formed by generating table structures that can adapt based on user input or other dynamic data sources.
15 [0062] The display unit [301] is configured to display a user interface (UI) for
selecting a table form from a dropdown menu comprising a plurality of predefined table forms. The display unit [301] is further configured to display a set of predefined fields of the selected table form along with a set of configuration options for each field.
20
[0063] In an implementation of the present disclosure, the table form supports Create, Read, Update, and Delete (CRUD) operations.
[0064] In an implementation of the present disclosure, the configuration options
25 comprise at least one of display name, placeholder, and validation rule.
[0065] In an implementation of the present disclosure, the set of predefined fields for the selected table may comprise at least one of a display name, a placeholder, and validation information. 30
17

[0066] The generating unit [302] is configured to generate for each table column, a form field in the selected table form. The process of generation may include creating a configuration for each of the tables with a respective field of the table.
5 [0067] In an implementation of the present disclosure, the form field is associated
with at least one of a UI display name, and a set of validation rules, and is configured to map to the set of related table entities via a dynamic lookup feature, wherein the dynamic lookup feature maps the set of related table entities based on primary key details, which uniquely identify records in the table, and foreign key details, which
10 establish relationship between records in different tables by linking a field in one
table to a unique identifier in another table. The tables are predefined but may be dynamically handled, if in future a new table arises. The new table may be easily handled. For e.g., the system [300] may prepopulate a predefined configuration of the selected table, wherein for each table column, the form field is created. This
15 form field may include but not limited to a user interface display name, a validation
criterion, and a mapping to related table entities with dynamic lookup.
[0068] The storage unit [303] is configured to store the set of configuration options
to configure the table form. To configure the table form, the storage unit [303] may
20 maintain the set of configuration of each of the table and respective fields of the
table. As soon as the storage unit [303] may be loaded with the set of configuration, the set of configuration may be fetched.
[0069] The display unit [301] is further configured to display the configured table
25 form with validation and a set of metadata of a set of related table entities to a user,
thereby facilitating creation of at least one of: new table forms and addition of new
fields to the plurality of predefined table forms with minimal configuration effort.
The user may view the configuration from the EPC UI [102] and the user may
change the validation or field type. For example, the user may change text to
30 dropdown or number field.
18

[0070] In an implementation of the present disclosure, the dynamic lookup feature
further comprises a capability to fetch the set of metadata dynamically from a
database [304]. The dynamic lookup feature is used to fetch list of data (or
metadata) from a table (i.e., the database [304]). For instance, if “student name” is
5 mentioned as a field in the table, then it will show names of students in the
dropdown list.
[0071] In an implementation of the present disclosure, a customization unit [305]
is further configured to enable the user to customize the form field by adding or
10 removing fields from the plurality of predefined table forms.
[0072] In an implementation of the present disclosure, an authentication unit [306] is further configured to validate configuration for the form field, comprising at least one of mandatory, editable, and non-editable set of attributes.
15
[0073] In an implementation of the present disclosure, the system [300] can be used to generate a set of recommendations for a user on one or more digital platforms. It is to be noted that the set of recommendations may include but not limited to a data that gets automatically added to the form for the user on the one or more digital
20 platforms. This is the data that automatically gets fetched/ populated in the form
that is to be filled by the user on the one or more digital platforms. For e.g., the field having plan offering id will be mapped automatically on the one or more digital platforms.
25 [0074] A person skilled in the art would appreciate that the above listed features
are only exemplary and does not limit the present disclosure in any possible manner. In an exemplary implementation, the features listed above may be considered to be in the order of their importance.
30 [0075] Referring to FIG. 4, an exemplary method flow diagram [400] for
configuring dynamic table forms, in accordance with exemplary implementations
19

of the present disclosure is shown. In an implementation the method [400] is
performed by the system [300]. Further, in an implementation, the system [300]
(partially or as a whole) 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
5 [402].
[0076] At step [404], the method [400] comprises displaying, by a display unit
[301], a user interface (UI) for selecting a table form from a dropdown menu
comprising a plurality of predefined table forms. The predefined table form here
10 refers to the table having predefined configurations such as a specific structure or a
specific format.
[0077] In an exemplary aspect of the present disclosure, in the disclosed method
[400], the table form supports Create, Read, Update, and Delete (CRUD)
15 operations.
[0078] At step [406], the method [400] comprises displaying, by the display unit [301], a set of predefined fields of the selected table form along with a set of configuration options for each field, upon selection of the table form. The set of
20 predefined fields include but may not be limited to specific column or data entry
areas that are originally included in the table form. The instances in the table form may include common use cases like a contact list having name and phone number; a project details like task name and status; etc, where the contact list and the project details represent each field.
25
[0079] In an exemplary aspect of the present disclosure, the configuration options comprise at least one of display name, placeholder, and validation rule.
[0080] At step [408], the method [400] comprises generating, by a generating unit
30 [302], for each table column, a form field in the selected table form. The each table
column refers to a collection of cells aligned vertically in a table. It is to be noted
20

that the selected table form refers to the table form for which the form field is generated.
[0081] In an exemplary aspect of the present disclosure, in the disclosed method
5 [400], the form field is associated with at least one of a UI display name, and a set
of validation rules, and is configured to map to the set of related table entities via a
dynamic lookup feature, wherein the dynamic lookup feature maps the set of related
table entities based on primary key details, which uniquely identify records in the
table, and foreign key details, which establish relationship between records in
10 different tables by linking a field in one table to a unique identifier in another table.
[0082] In an exemplary aspect of the present disclosure, in the disclosed method
[400], the dynamic lookup feature further comprises a capability to fetch the set of
metadata dynamically from a database [304]. The fetching takes place via a
15 dynamical search function that queries/ traverses the database [304] based on the
user input. The set of metadata may include multiple metadata (data about data) of the information stored in the database [304].
[0083] At step [410], the method [400] comprises storing, by a storage unit [303],
20 the set of configuration options to configure the table form.
[0084] At step [412], the method [400] comprises displaying, by the display unit [301], the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new
25 table forms and addition of new fields to the plurality of predefined table forms with
minimal configuration effort. The displaying includes the rendering the configured table form on the display unit [301]. The display unit [301] may be configured to have a user interface (UI). It is to be noted that the set of meta data of the set of related table entities may include descriptive information about the table structure,
30 relationships and the conditions of the tables and their respective fields of the
21

related table entities. The new table forms include the newly configured table forms having user preferred table structure and user preferred requirements.
[0085] In an exemplary aspect of the present disclosure, the method [400] further
5 comprises enabling the user, by a customization unit [305], to customize the form
field by adding or removing fields from the plurality of predefined table forms.
[0086] In an exemplary aspect of the present disclosure, in the method [400] further
comprises validating, by an authentication unit [306], configuration for the form
10 field, comprising at least one of mandatory, editable, and non-editable set of
attributes.
[0087] Thereafter, the method [400] terminates at step [414].
15 [0088] 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. In an implementation, the computing device [500] may also implement a method for configuring dynamic table forms. In another implementation, the computing device
20 [100] itself implements the method for configuring dynamic table forms, using one
or more units configured within the computing device [500], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
25 [0089] The computing device [500] may include a bus [502] or other
communication mechanism for communicating information, and a processor [504] coupled with the bus [502] for processing information. The processor [504] may be, for example, a general-purpose microprocessor. The computing device [500] may also include a main memory [506], such as a random-access memory (RAM),
30 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]
22

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 storage media accessible to the processor
[504], render the computing device [500] into a special-purpose machine that is
5 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].
10 [0090] 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 (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
15 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 [516], such as a mouse, a trackball, or cursor direction keys, for communicating direction
20 information and command selections to the processor [504], and for 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.
25 [0091] 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 performed by the
30 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
23

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 processor [504] to perform the
process steps described herein. In alternative implementations of the present
5 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0092] The computing device [500] also may include a communication interface
[518] coupled to the bus [502]. The communication interface [518] provides a two-
10 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 corresponding type of
telephone line. As another example, the communication interface [518] may be a
15 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 data streams representing
various types of information.
20
[0093] 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 [128], the
25 ISP [526], the local network [522], 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.
30 [0094] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for configurating dynamic table forms, the instructions include executable code which, when executed by a one or more units
24

of a system, causes a display unit [301] to display a user interface (UI) for selecting
a table form from a dropdown menu comprising a plurality of predefined table
forms; and to display a set of predefined fields of the selected table form along with
a set of configuration options for each field. The instructions which when executed,
5 causes a generating unit [302] to generate for each table column, a form field in the
selected table form and a storage unit [303] to store the set of configuration options
to configure the table form. The instructions which when executed, causes the
display unit [301] to display the configured table form with validation and a set of
metadata of a set of related table entities to a user, thereby facilitating creation of at
10 least one of: new table forms and addition of new fields to the plurality of
predefined table forms with minimal configuration effort.
[0095] Yet another aspect of the present disclosure may relate to user equipment (UE) for configuring dynamic table forms comprising a display unit [301]
15 configured to display a user interface (UI) for selecting a table form from a
dropdown menu comprising a plurality of predefined table forms. The display unit [301] is further configured to display a set of predefined fields of the selected table form along with a set of configuration options for each field. The UE further comprises a generation unit [302] configured to generate for each table column, a
20 form field in the selected table form. The UE further comprises a storage unit [303]
configured to store the set of configuration options to configure the table form. The display unit [301] of the system [300] is further configured to display the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition
25 of new fields to the plurality of predefined table forms with minimal configuration
effort.
[0096] As is evident from the above, the present disclosure provides a technically
advanced solution for configuring dynamic table form. The present solution having
30 dynamic table configuration, instead of creating multiple forms, creates forms
dynamically with minimal configuration. This reduces duplication/ recreation of forms and writing same types of API calls. Thus, the present disclosure provides
25

the following advancements over the obsolete way of creating forms in the product sync catalogue:
- The dynamic table configuration form allows user to configure table
columns with form fields which can be mapped to one form input fields that
5 are created dynamically in table form.
- Further, the input fields may be of various types that may include static input
fields such as but not limited to textbox, radio and select. Also, the input
fields may include dynamic lookup such as but not limited to meta data to
be fetched from the database.
10 - Furthermore, mandatory, editable, non-editable, place holder’s type of
validation configuration is also offered by the present disclosure.
- Additionally, flexibility can be given to remove or add fields in defined table
form template configuration.
15 [0097] While considerable emphasis has been placed herein on the 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
20 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
[0098] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be
25 implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative
30 arrangements and substitutions of units, provided they achieve the intended
26

functionality described herein, are considered to be encompassed within the scope of the present disclosure.

We Claim:
1. A method [400] for configuring dynamic table forms, said method [400] comprising:
displaying, by a display unit [301], a user interface (UI) for selecting a table form from a dropdown menu comprising a plurality of predefined table forms;
upon selection of the table form, displaying, by the display unit [301], a set of predefined fields of the selected table form along with a set of configuration options for each field;
generating, by a generating unit [302], for each table column, a form field in the selected table form;
storing, by a storage unit [303], the set of configuration options to configure the table form; and
displaying, by the display unit [301], the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition of new fields to the plurality of predefined table forms with minimal configuration effort.
2. The method [400] as claimed in claim 1, wherein the configuration options comprise at least one of display name, placeholder, and validation rule.
3. The method [400] as claimed in claim 1, wherein the form field is associated with at least one of a UI display name, and a set of validation rules, and is configured to map to the set of related table entities via a dynamic lookup feature, wherein the dynamic lookup feature maps the set of related table entities based on primary key details, which uniquely identify records in the table, and foreign key details, which establish relationship between records in different tables by linking a field in one table to a unique identifier in another table.
4. The method [400] as claimed in claim 3, wherein the dynamic lookup feature further comprises a capability to fetch the set of metadata dynamically from a database [304].
5. The method [400] as claimed in claim 1, further comprises enabling the user, by a customization unit [305], to customize the form field by adding or removing fields from the plurality of predefined table forms.

6. The method [400] as claimed in claim 1, wherein the table form supports Create, Read, Update, and Delete (CRUD) operations.
7. The method [400] of claim 1, further comprising validating, by an authentication unit [306], configuration for the form field, comprising at least one of mandatory, editable, and non-editable set of attributes.
8. A system [300] for configuring dynamic table forms, the system [300] comprises:
a display unit [301] configured to:
display a user interface (UI) for selecting a table form from a dropdown menu comprising a plurality of predefined table forms;
display a set of predefined fields of the selected table form along with a set of configuration options for each field;
a generating unit [302] connected to at least the display unit [302], the generating unit [302] configured to:
generate for each table column, a form field in the selected table form; a storage unit [303] connected to at least the generating unit [302], the storage unit [303] configured to:
store the set of configuration options to configure the table form; and the display unit [301] is further configured to display the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition of new fields to the plurality of predefined table forms with minimal configuration effort.
9. The system [300] as claimed in claim 8, wherein the configuration options comprise at least one of display name, placeholder, and validation rule.
10. The system [300] as claimed in claim 8, wherein the form field is associated with at least one of a UI display name, and a set of validation rules, and is configured to map to the set of related table entities via a dynamic lookup feature, wherein the dynamic lookup feature maps the set of related table entities based on primary key details, which uniquely identify records in the table, and foreign key details, which establish relationship between records in different tables by linking a field in one table to a unique identifier in another table.

11. The system [300] as claimed in claim 10, wherein the dynamic lookup feature further comprises a capability to fetch the set of metadata dynamically from a database [304].
12. The system [300] as claimed in claim 8, where a customization unit [305] is further configured to enable the user to customize the form field by adding or removing fields from the plurality of predefined table forms.
13. The system [300] as claimed in claim 8, wherein the table form supports Create, Read, Update, and Delete (CRUD) operations.
14. The system [300] as claimed in claim 8, where an authentication unit [306] is further configured to validate configuration for the form field, comprising at least one of mandatory, editable, and non-editable set of attributes.
15. A user equipment (UE) for configuring dynamic table forms comprising:
a display unit [301] configured to:
display a user interface (UI) for selecting a table form from a dropdown menu comprising a plurality of predefined table forms;
display a set of predefined fields of the selected table form along with a set of configuration options for each field; a generation unit [302] configured to:
generate for each table column, a form field in the selected table form; a storage unit [303] configured to
store the set of configuration options to configure the table form; and the display unit [301] configured to display the configured table form with validation and a set of metadata of a set of related table entities to a user, thereby facilitating creation of at least one of: new table forms and addition of new fields to the plurality of predefined table forms with minimal configuration effort.