Description:FORM 2

THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003

COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

Title of invention:
METHOD AND SYSTEM FOR MIGRATION AND RE-CREATION OF FORMS INTO TARGET ENVIRONMENT

Applicant

Tata Consultancy Services Limited
A company Incorporated in India under the Companies Act, 1956
Having address:
Nirmal Building, 9th floor,
Nariman point, Mumbai 400021,
Maharashtra, India

Preamble to the description:

The following specification particularly describes the invention and the manner in which it is to be performed.
TECHNICAL FIELD
[001] The disclosure herein generally relates to the field of data migration and, more particularly, to a method and system for migration and re-creation of forms into target environment.
BACKGROUND
[002] Legacy data is a historical data buried in old databases and contains vital information of organizations. Being stored for ages, the legacy data becomes disordered, siloed, and segmented by different formats. Managing and processing such data becomes overly cumbersome and in vain over time, forcing organizations to consider moving legacy databases to modern environments. Microsoft InfoPath® are used to create, design, distribute and fill electronic forms. With the soon approaching End of Life of Microsoft InfoPath® Forms, an alternative to carry on its functions must be formulated while not losing information from the existing forms.
[003] Conventional approaches generally perform manual migration of legacy forms which is time consuming. Some other conventional approaches perform partially automated migration which still needed manual intervention for migration. Few existing techniques migrate only database information while few other approaches focus on migrating the design/User Interface (UI) and in fact require most of the data and business logic to reside in the same parent database. Hence the method of migrating and re-creating legacy forms from source environment to target environment along with data in a completely automated manner is yet to be realized.
SUMMARY
[004] Embodiments of the present disclosure present technological improvements as solutions to one or more of the above-mentioned technical problems recognized by the inventors in conventional systems. For example, in one embodiment, a method for migration and re-creation of forms into target environment is provided. The method includes receiving, by one or more hardware processors, a plurality of forms to be migrated from a source environment to a target environment, wherein each of the plurality of forms is associated with a design template and a source data. Further, the method includes extracting, by the one or more hardware processors, a source design data from the design template corresponding to each of the plurality of forms using a design template extraction technique. Furthermore, the method includes establishing, by the one or more hardware processors, a data connection between the source environment and the target environment. Furthermore, the method includes migrating, by the one or more hardware processors, the source design data and the source data corresponding to each of the plurality of forms from the source environment to the target environment using a data migration technique via the established data connection. Finally, the method includes re-creating, by the one or more hardware processors, the plurality of forms in the destination environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using a form re-creation technique.
[005] In another aspect, a system for migration and re-creation of forms into target environment is provided. The system includes at least one memory storing programmed instructions, one or more Input /Output (I/O) interfaces, and one or more hardware processors operatively coupled to at least one memory, wherein the one or more hardware processors are configured by the programmed instructions to receive a plurality of forms to be migrated from a source environment to a target environment, wherein each of the plurality of forms is associated with a design template and a source data. Further, the one or more hardware processors are configured by the programmed instructions to extract a source design data from the design template corresponding to each of the plurality of forms using a design template extraction technique. Furthermore, the one or more hardware processors are configured by the programmed instructions to establish a data connection between the source environment and the target environment. Furthermore, the one or more hardware processors are configured by the programmed instructions to migrate the source design data and the source data corresponding to each of the plurality of forms from the source environment to the target environment using a data migration technique via the established data connection. Finally, the one or more hardware processors are configured by the programmed instructions to re-create the plurality of forms in the destination environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using a form re-creation technique.
[006] In yet another aspect, a computer program product including a non-transitory computer-readable medium having embodied therein a computer program for migration and re-creation of forms into target environment is provided. The computer readable program, when executed on a computing device, causes the computing device to receive a plurality of forms to be migrated from a source environment to a target environment, wherein each of the plurality of forms is associated with a design template and a source data. Further, the computer readable program, when executed on a computing device, causes the computing device to extract a source design data from the design template corresponding to each of the plurality of forms using a design template extraction technique. Furthermore, the computer readable program, when executed on a computing device, causes the computing device to establish a data connection between the source environment and the target environment. Furthermore, the computer readable program, when executed on a computing device, causes the computing device to migrate the source design data and the source data corresponding to each of the plurality of forms from the source environment to the target environment using a data migration technique via the established data connection. Finally, the computer readable program, when executed on a computing device, causes the computing device to re-create the plurality of forms in the destination environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using a form re-creation technique.
[007] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
[008] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles:
[009] FIG. 1 is a functional block diagram of a system for migration and re-creation of forms into target environment, in accordance with some embodiments of the present disclosure.
[0010] FIG. 2 illustrates a functional architecture of the system of FIG. 1, for migration and re-creation of forms into target environment, in accordance with some embodiments of the present disclosure.
[0011] FIG. 3 is an exemplary flow diagram illustrating a processor implemented method 300 for migration and re-creation of forms into target environment implemented by the system of FIG. 1, in accordance with some embodiments of the present disclosure.
[0012] FIG. 4 is a sample form to be migrated from a source environment to a target environment using the processor implemented method for migration and re-creation of forms in the target environment implemented by the system of FIG. 1, in accordance with some embodiments of the present disclosure.
[0013] FIG. 5 is an exemplary flow diagram for re-creating forms in the target environment implemented by the system of FIG. 1, in accordance with some embodiments of the present disclosure.
DETAILED DESCRIPTION OF EMBODIMENTS
[0014] Exemplary embodiments are described with reference to the accompanying drawings. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. Wherever convenient, the same reference numbers are used throughout the drawings to refer to the same or like parts. While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the spirit and scope of the disclosed embodiments.
[0015] Software application for designing, distributing, filling and submitting electronic forms (for example, Microsoft InfoPath®/ InfoPath®) contains structured data and are saved in the form of an application package, which are not user readable. Further, the existing InfoPath® forms are completely dependent on thick clients for analysis and design which involves huge manual effort for processing in high volume. Furthermore, manual analysis and migration of data saved as Extensible Markup Language (XML) files in the Form Library is very effort intensive and re-creating complex forms in target platforms involve huge effort and is currently done manually.
[0016] Embodiments herein provide a method and system for migration and re-creation of forms into target environments. The method disclosed can convert on-premises forms to cloud based forms/applications that can be accessed via desktop, laptop, tablet, mobile devices. The method includes extracting source design data and source data from the forms to be migrated. Further the extracted source design data and the source data are migrated to target environment and the forms are re-created in the target environment using a form re-creation technique. The scalable solution provided by the present disclosure enables users to create new applications (apps) without the requirement for highly developed software development abilities, even if they have little or no experience with coding.
[0017] Referring now to the drawings, and more particularly to FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments and these embodiments are described in the context of the following exemplary system and/or method.
[0018] FIG. 1 is a functional block diagram of a system 100 for migration and re-creation of forms into the target environment, in accordance with some embodiments of the present disclosure. The system 100 includes or is otherwise in communication with hardware processors 102, at least one memory such as a memory 104, an I/O interface 112. The hardware processors 102, memory 104, and the Input /Output (I/O) interface 112 may be coupled by a system bus such as a system bus 108 or a similar mechanism. In an embodiment, the hardware processors 102 can be one or more hardware processors.
[0019] The I/O interface 112 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 112 may include a variety of software and hardware interfaces, for example, interfaces for peripheral device(s), such as a keyboard, a mouse, an external memory, a printer and the like. Further, the I/O interface 112 may enable the system 100 to communicate with other devices, such as web servers, and external databases.
[0020] The I/O interface 112 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, local area network (LAN), cable, etc., and wireless networks, such as Wireless LAN (WLAN), cellular, or satellite. For the purpose, the I/O interface 112 may include one or more ports for connecting several computing systems with one another or to another server computer. The I/O interface 112 may include one or more ports for connecting several devices to one another or to another server.
[0021] The one or more hardware processors 102 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, node machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the one or more hardware processors 102 is configured to fetch and execute computer-readable instructions stored in the memory 104.
[0022] The memory 104 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. In an embodiment, the memory 104 includes a plurality of modules 106. The memory 104 also includes a data repository (or repository) 110 for storing data processed, received, and generated by the plurality of modules 106.
[0023] The plurality of modules 106 include programs or coded instructions that supplement applications or functions performed by the system 100 for migration and re-creation of forms into target environment. The plurality of modules 106, amongst other things, can include routines, programs, objects, components, and data structures, which performs particular tasks or implement particular abstract data types. The plurality of modules 106 may also be used as, signal processor(s), node machine(s), logic circuitries, and/or any other device or component that manipulates signals based on operational instructions. Further, the plurality of modules 106 can be used by hardware, by computer-readable instructions executed by the one or more hardware processors 102, or by a combination thereof. The plurality of modules 106 can include various sub-modules (not shown). The plurality of modules 106 may include computer-readable instructions that supplement applications or functions performed by the system 100 for migration and re-creation of forms into target environment. In an embodiment, the plurality of modules 106 include a source design data extraction module (shown in FIG. 2), a data connection establishment module (shown in FIG. 2), a migration module (shown in FIG. 2) and a form recreation module (shown in FIG. 2). In an embodiment, FIG. 2 illustrates a functional architecture of the system of FIG. 1, for migration and re-creation of forms into target environment, in accordance with some embodiments of the present disclosure.
[0024] The data repository (or repository) 110 may include a plurality of abstracted piece of code for refinement and data that is processed, received, or generated as a result of the execution of the plurality of modules in the module(s) 106.
[0025] Although the data repository 110 is shown internal to the system 100, it will be noted that, in alternate embodiments, the data repository 110 can also be implemented external to the system 100, where the data repository 110 may be stored within a database (repository 110) communicatively coupled to the system 100. The data contained within such external database may be periodically updated. For example, new data may be added into the database (not shown in FIG. 1) and/or existing data may be modified and/or non-useful data may be deleted from the database. In one example, the data may be stored in an external system, such as a Lightweight Directory Access Protocol (LDAP) directory and a Relational Database Management System (RDBMS). Working of the components of the system 100 are explained with reference to the method steps depicted in FIG. 3 and FIG. 5.
[0026] FIG. 3 is an exemplary flow diagram illustrating a method 300 for migration and re-creation of forms into target environment implemented by the system of FIG. 1 according to some embodiments of the present disclosure. In an embodiment, the system 100 includes one or more data storage devices or the memory 104 operatively coupled to the one or more hardware processor(s) 102 and is configured to store instructions for execution of steps of the method 300 by the one or more hardware processors 102. The steps of the method 300 of the present disclosure will now be explained with reference to the components or blocks of the system 100 as depicted in FIG. 1 and the steps of flow diagram as depicted in FIG. 3. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 300 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communication network. The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300, or an alternative method. Furthermore, the method 300 can be implemented in any suitable hardware, software, firmware, or combination thereof.
[0027] At step 302 of the method 300, the one or more hardware processors 102 are configured by the programmed instructions to receive a plurality of forms to be migrated from a source environment to a target environment. For example, the source environment is any computing machine or application where the plurality of forms to be migrated resides and the target environment is any computing machine or cloud platform or any applications where the plurality of forms is to be migrated. Each of the plurality of forms is associated with a design template and a source data. The source data is the data associated with the plurality of forms.
[0028] At step 304 of the method 300, the source design data extraction module 202 executed by one or more hardware processors 102 is configured by the programmed instructions to extract a source design data from the design template corresponding to each of the plurality of forms using a design template extraction technique.
[0029] In an embodiment, the method of extracting the source design data from each of the plurality of design templates using the design template extraction technique includes receiving the design template corresponding to each of the plurality of forms, wherein each of a plurality of design templates are validated for availability in the corresponding file location. In an embodiment, a Windows® PowerShell program called as “Legacy Form Downloader” has been designed to identify the location where the design templates associated with each of the plurality of forms are stored and download the identified templates to a specific location on the system 100 from which the program is run. Further, a source list URL provided by the Legacy Form Downloader” sub module is validated. Upon successful access to the Source List URL and validation of Form templates present, all validated templates are downloaded one by one into a local file system. Default name assigned by source system/environment for design template is ‘Template.xsn’ and downloading them with the default name creates a conflict of overwriting each downloaded file. To avoid this conflict, a unique file name is generated in run time by concatenating the following parameters read from the input file. For example, List Name + “_” + + “.xsn”. After successful naming and download of the required templates, the program will log the count of entries processed from the input list and end the execution
[0030] Further, a .Net program called as “Design Template Scanner” sub module has been designed to scan the downloaded templates from previous step and create a summary report listing all design elements that are built inside the templates. The “Design Template Scanner” module converts the downloaded templates into a readable format so that design elements and complexity of the form can be extracted for further analysis and processing
[0031] In an embodiment, the pseudocode for “Legacy Form Downloader” sub module is given below:
Pseudocode 1 : Legacy Form Downloader
DECLARE
inputFilePath :=
DownloadFilePath :=
END DECLARE
Call ImportCsv with inputFilePath returning data
FOR EACH item in data
Get item.data
IF(FormUsage -eq 'FormLibrary')
templateFilePath = listUrl+"/Forms/template.xsn"
END IF
IF (FormUsage -eq 'CustomForm')
templateFilePath = listUrl+"/item/template.xsn"
END IF
TargetFilePath = FormDownloadFilePath+Listname+"_"+listId+".xsn"
CALL BinaryFileDownload with templateFilePath returing filestream
CALL System.IO.File.Open with filestream
PRINT: Downloaded template for listURL
END FOR EACH
[0032] In an embodiment, the pseudocode for “Design Template Scanner” sub module is given below:
DECLARE
csvFilePath :=
xsnFolderPath :=
extractFolderPath :=
END DECLARE
CALL RenameXSNtoCAB with xsnFolderPath returning fileInfoList
FOR EACH cabFile in fileInfoList
FOR EACH file in cabfile
IF (file.name = 'manifest.xsf')
PRINT: 'Extracting Manifest'
CALL CopyFile with extractFolderPath
CALL LoadXML with extractFolderPath returning XMLDocument
CALL XMLElement with LoadXML.Elements
CALL XMLNodes with XMLElement.ChildNodes
CALL XMLAttributesCollection with XMLElement.Attributes
CALL XMLDocument.Views returning XMLNode as views
CALL XMLDocument.Rules returning XMLNode as Rules
CALL XMLDocument.dataConnections returning XMLNode as dataConnections
numOfDataConnections := COUNT(dataConnections)
numOfRules := COUNT(Rules)
numOfViews := COUNT(views)
defaultView := views.Attributes.Default
totalControls := COUNT(views.Nodes.editing)
totalBtns := COUNT(views.Nodes.unboundControls)
END IF
END FOR EACH
END FOR EACH
PRINT: "End of Processing"
CALL GenerateCSVReport with csvFilePath
PRINT: "Complexity Report Generated"
[0033] Further, a manifest file corresponding to each of the plurality of design templates is obtained by converting each of the plurality of design templates into a corresponding Windows® cabinet file (CAB files) in an archive format. A key file within this archive is called manifest file (“manifest.xsf”). Each manifest file includes a plurality of controls, a plurality of rules and a plurality of views pertaining to the corresponding to the design template. For example, the plurality of controls includes buttons, drop-down lists, checkboxes, radio buttons and so on. The plurality of rules includes OnFocus, OnSelect and so on. The plurality of views includes Default view, Custom_view_1, Custom_view_2 and the like.
[0034] Finally, the source design data pertaining to each of the plurality of design templates is extracted from the corresponding manifest file, wherein the source design data comprises a plurality of design properties. For example, data connection, actions and the like.
[0035] In an embodiment, an example extracted design data for a sample form shown in FIG. 4 is given in Table I.
Table I
XSN Views Default view Controls in default view Buttons in default view Total controls Total buttons Rules Connections
Example_
targetListPath :=
extractFolderPath :=
END DECLARE
CALL GetList with sourceListPath returning sourceListInstance
CALL GetList with targetListPath returning targetListInstance
CALL Load with sourceListInstance returning Items
FOR EACH item in Items
CALL OpenStream with item.file returing streamData
CALL XMLItem.Load with streamData.Value
CALL GetFormFields with listOfFormFields
CALL targetListInstance.AddItem
MAP:
targetListItem with listOfFormFields
END FOR EACH
PRINT: "Data Migration Completed"
[0039] The “XML Data Extractor” sub module begins execution by validating a successful connection to the source data store containing legacy data. After establishing a connection with source data store, this sub module accesses the legacy data files that is stored in .XML format. After fetching the first .XML data file, the program performs a validation on the schema definition and ensure the data file is conforming to the source Form. Upon successful schema validation, the sub module begins the read operation on the data stored in all XML nodes. Further, the sub module validates the existence of the target data store prior to data copy from source. After connecting to the target data store, the sub module copies all the data read from XML nodes and persist them in the target entities without any data loss. The sub module continues the processing of next .XML file in the source environment and copy them to the target store. The above steps will be repeated until all .XML data files in the source environment has been successfully copied to the target. After processing all the files in source, the “XML Data Extractor” sub module logs a data migration complete message and ends the process.
[0040] At step 310 of the method 300, the form creation module 208 executed by the one or more hardware processors 102 is configured by the programmed instructions to re-create the plurality of forms in the destination environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using a form re-creation technique.
[0041] In an embodiment, the method 500 for re-creating the plurality of forms in the target environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using the form re-creation technique is explained in conjunction with FIG. 5. Now referring to FIG. 5, at step at step 502 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to receive the source design data and source data corresponding to each of the plurality of forms migrated from the source environment and a corresponding metadata associated with the target environment.
[0042] At step at step 504 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to create a Java Script Object Notation (JSON) variable for each of the plurality of design properties associated with each source design data. The JSON variable includes a plurality of JSON parameters like Overflow, Fill, DisplayMode, ZIndex and the like.
[0043] At step at step 506 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to generate a source control array based on the JSON variable corresponding to each of the plurality of JSON properties associated with the source design data. For example, the source control array is given in table II.
Table II
Source Control #1 Title Source Property #1 Source Property #2
Source Control #2 FirstName Source Property #1 Source Property #2
Source Control #3 LastName Source Property #1 Source Property #2
Source Control #4 DisplayName Source Property #1 Source Property #2
Source Control #5 Age Source Property #1 Source Property #2
Source Control #6 Gender Source Property #1 Source Property #2
[0044] At step 508 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to simultaneously extract a target design template corresponding to each of the plurality of forms from the target environment, wherein each target design template is associated with a target control array.
[0045] For example, the target control array is given in table III.
Table III
Target Control #1 Label #1 Default Property #1 Default Property #2
Target Control #2 Label #2 Default Property #1 Default Property #2
Target Control #3 Label #3 Default Property #1 Default Property #2
Target Control #4 Label #4 Default Property #1 Default Property #2
Target Control #5 Label #5 Default Property #1 Default Property #2
Target Control #6 Label #6 Default Property #1 Default Property #2
[0046] At step at step 510 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to update the target control array associated with each source design data in the target environment with the corresponding source control array.
[0047] For example, the updated target control array is given in table IV.
Table IV
Target Control #1 Title Target Property #1 Target Property #2
Target Control #2 FirstName Target Property #1 Target Property #2
Target Control #3 LastName Target Property #1 Target Property #2
Target Control #4 DisplayName Target Property #1 Target Property #2
Target Control #5 Age Target Property #1 Target Property #2
Target Control #6 Gender Target Property #1 Target Property #2
[0048] At step at step 512 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to update the manifest file of the target environment by swapping a plurality of static variables associated with the manifest file of the target environment with a plurality of target location values.
[0049] For example, the updated manifest file is as shown in table V.
Table V
Variable #1 EnvName Production
Variable #2 ListTitle EmployeeDetails
Variable #3 ListID BA4CDF4E7-5E78-43FA-8E17-77F85A8C1453
Variable #4 ListURL /Lists/EmployeeDetails/Allitems.aspx
[0050] At step at step 514 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to generate a data package based on the updated control array and the updated manifest file using a compression technique, wherein the data package is stored in a specific file location, for example the data package is stored in a server machine.
[0051] At step at step 516 of the method 500, the one or more hardware processors 102 are configured by the programming instructions to re-creating each of the plurality of forms in the target environment along with the source data based on the corresponding data package. In an embodiment, the data package is downloaded from the server machine and the plurality of forms are re-created in the target environment.
[0052] In an embodiment, re-creation of the plurality of forms in the target environment includes receiving of the data package (.zip file) and accessing the default environment available in the target server/environment. The processing continues with uploading the data package (.zip file) into the target server/environment and validating the downloaded payload. The processing continues with creation of a string variable App id and assignment of a GUID value. This value acts as the reference App id. Further, the downloaded package data is imported in the default environment by passing the validated payload and reference App id. Upon successful import, the method 500 retrieves the deployed package information using reference App id. Processing of this stage completes once the package retrieval operation returns a success message. The user can view the source data, edit the source data and submit new data on cloud after re-creation of the plurality of forms in the target environment.
[0053] In an embodiment, a Windows® PowerShell program called “form re-creation technique” has been designed to create re-create the plurality of forms in the target environment and the pseudocode for the “form re-creation technique” is given below:
Pseudocode 3: form re-creation technique
Declare
Begin
Target Json Control Array
Target site variables
End
Read the source elements from excel input file
For each source element
Begin
Create a target JSON element
Add target JSON Element into Target Json Control Array
End
CALL: Read the base file zip package
CALL: Extract the contents inside the zip package into target directory
CALL: Read the manifest file from target directory
CALL: Assign target site url, list url and Id variables read from excel sheet
CALL: Replace the static JSON variables with target variables
CALL: Replace the static control variable with Target Json Control Array
CALL: Compress the target folder into zip package
CALL: Invoke HTTP to connect with Target site
CALL: Upload the zip package into Target repository
CALL: Publish the zip package
Print “Form re-created successfully”
End
Experimentation details:
[0054] In an embodiment, the present disclosure is experimented as follows:
In an embodiment, the present disclosure was experimented with 10 forms. The entire process of migration of forms from the source environment and recreation of the forms on the target environment was completed in few minutes. Newly created forms in the target/destination environment had the ability to submit new data as well as capable of editing migrated data linked with it. Below Table VI provides a comparison of average effort consumed for the entire migration and recreation process using conventional method and present disclosure.
Table VI
Form/Data Complexity Conventional Method Present Disclosure
Simple 2 Days 3 Minutes
Medium 3 Days 3 Minutes
Complex 5 Days 3 Minutes
[0055] The written description describes the subject matter herein to enable any person skilled in the art to make and use the embodiments. The scope of the subject matter embodiments is defined by the claims and may include other modifications that occur to those skilled in the art. Such other modifications are intended to be within the scope of the claims if they have similar elements that do not differ from the literal language of the claims or if they include equivalent elements with insubstantial differences from the literal language of the claims.
[0056] The embodiments of present disclosure herein address the unresolved problem of migration and re-creation of forms into target environment. The present disclosure helps users to move from legacy forms from a source environment to modern apps with ease. This process provides step-by-step instruction that users can follow to convert their legacy forms/ forms (e.g., Microsoft InfoPath®) into a modern platform (e.g., Microsoft Power Platform®), migrate and link the existing data with newly designed apps. This process leverages automated steps that enable users to achieve the desired results within a short span of time. This is a scalable solution that enables users with low or no coding knowledge to build their new apps without the need for advanced software development skills.
[0057] It is to be understood that the scope of the protection is extended to such a program and in addition to a computer-readable means having a message therein such computer-readable storage means contain program-code means for implementation of one or more steps of the method when the program runs on a server or mobile device or any suitable programmable device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof. The device may also include means which could be e.g. hardware means like e.g. an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means can include both hardware means and software means. The method embodiments described herein could be implemented in hardware and software. The device may also include software means. Alternatively, the embodiments may be implemented on different hardware devices, e.g. using a plurality of CPUs, GPUs and edge computing devices.
[0058] The embodiments herein can comprise hardware and software elements. The embodiments that are implemented in software include but are not limited to, firmware, resident software, microcode, etc. The functions performed by various modules described herein may be implemented in other modules or combinations of other modules. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can comprise, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments. Also, the words “comprising,” “having,” “containing,” and “including,” and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise. Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e. non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[0059] It is intended that the disclosure and examples be considered as exemplary only, with a true scope of disclosed embodiments being indicated by the following claims.
, Claims:WE CLAIM:

1. A processor implemented method (300), the method comprising:
receiving (302), by one or more hardware processors, a plurality of forms to be migrated from a source environment to a target environment, wherein each of the plurality of forms is associated with a design template and a source data;
extracting (304), by the one or more hardware processors, a source design data from the design template corresponding to each of the plurality of forms using a design template extraction technique;
establishing (306), by the one or more hardware processors, a data connection between the source environment and the target environment;
migrating (308), by the one or more hardware processors, the source design data and the source data corresponding to each of the plurality of forms from the source environment to the target environment using a data migration technique via the established data connection; and
re-creating (310), by the one or more hardware processors, the plurality of forms in the destination environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using a form re-creation technique.
2. The method as claimed in claim 1, wherein the method of extracting the source design data from each of a plurality of design templates using the design template extraction technique comprises:
receiving the design template corresponding to each of the plurality of forms, wherein each of the plurality of design templates are validated for availability in the corresponding file location;
obtaining a manifest file corresponding to each of the plurality of design templates by converting each of the plurality of design templates into a corresponding cabinet file (CAB files) in an archive format, wherein each manifest file comprises a plurality of controls, a plurality of rules and a plurality of views pertaining to the corresponding to the design template; and
extracting the source design data pertaining to each of the plurality of design templates from the corresponding manifest file, wherein the source design data comprises a plurality of design properties.
3. The method as claimed in claim 1, wherein the method of re-creating the plurality of forms in the target environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using the form re-creation technique comprises:
receiving the source design data and source data corresponding to each of the plurality of forms migrated from the source environment and a corresponding metadata associated with the target environment;
creating a Java Script Object Notation (JSON) variable for each of the plurality of design properties associated with each source design data, wherein the JSON variable comprises a plurality of JSON parameters;
generating a source control array based on the JSON variable corresponding to each of the plurality of JSON properties associated with the source design data;
simultaneously extracting a target design template corresponding to each of the plurality of forms from the target environment, wherein each target design template is associated with a target control array;
updating the target control array associated with each source design data in the target environment with the corresponding source control array;
updating the manifest file of the target environment by swapping a plurality of static variables associated with the manifest file of the target environment with a plurality of target location values;
generating a data package based on the updated control array and the updated manifest file using a compression technique, wherein the data package is stored in a specific file location; and
re-creating each of the plurality of forms in the target environment along with the source data based on the corresponding data package.
4. A system (100) comprising:
at least one memory (104) storing programmed instructions; one or more Input /Output (I/O) interfaces (112); and one or more hardware processors (102) operatively coupled to the at least one memory (104), wherein the one or more hardware processors (102) are configured by the programmed instructions to:
receive a plurality of forms to be migrated from a source environment to a target environment, wherein each of the plurality of forms is associated with a design template and a source data;
extract a source design data from the design template corresponding to each of the plurality of forms using a design template extraction technique;
establish a data connection between the source environment and the target environment;
migrate the source design data and the source data corresponding to each of the plurality of forms from the source environment to the target environment using a data migration technique via the established data connection; and
re-create, the plurality of forms in the destination environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using a form re-creation technique.
5. The system of claim 4, wherein the method of extracting the source design data from each of a plurality of design templates using the design template extraction technique comprises:
receiving the design template corresponding to each of the plurality of forms, wherein each of the plurality of design templates are validated for availability in the corresponding file location;
obtaining a manifest file corresponding to each of the plurality of design templates by converting each of the plurality of design templates into a corresponding cabinet file (CAB files) in an archive format, wherein each manifest file comprises a plurality of controls, a plurality of rules and a plurality of views pertaining to the corresponding to the design template; and
extracting the source design data pertaining to each of the plurality of design templates from the corresponding manifest file, wherein the source design data comprises a plurality of design properties.
6. The system of claim 4, wherein the method of re-creating the plurality of forms in the target environment based on the migrated source design data and the source data corresponding to each of the plurality of forms using the form re-creation technique comprises:
receiving the source design data and source data corresponding to each of the plurality of forms migrated from the source environment and a corresponding metadata associated with the target environment;
creating a Java Script Object Notation (JSON) variable for each of the plurality of design properties associated with each source design data, wherein the JSON variable comprises a plurality of JSON parameters;
generating a source control array based on the JSON variable corresponding to each of the plurality of JSON properties associated with the source design data;
simultaneously extracting a target design template corresponding to each of the plurality of forms from the target environment, wherein each target design template is associated with a target control array;
updating the target control array associated with each source design data in the target environment with the corresponding source control array;
updating the manifest file of the target environment by swapping a plurality of static variables associated with the manifest file of the target environment with a plurality of target location values;
generating a data package based on the updated control array and the updated manifest file using a compression technique, wherein the data package is stored in a specific file location; and
re-creating each of the plurality of forms in the target environment along with the source data based on the corresponding data package.

Dated this 16th Day of January 2023

Tata Consultancy Services Limited
By their Agent & Attorney

(Adheesh Nargolkar)
of Khaitan & Co
Reg No IN-PA-1086