Browse Prior Art Database

E-form enhancement tool

IP.com Disclosure Number: IPCOM000248650D
Publication Date: 2016-Dec-22

Publishing Venue

The IP.com Prior Art Database

Abstract

For a modern enterprise as well as the top 500 enterprises, e-form as replacing the paper is used widely. The e-forms are used in many industries (banking, communication, insurance, etc) and business domains. Now enterprise has more dependencies on e-form, e-forms were used in many areas. The e-forms even to replace many traditional systems. In the real practice, enterprise business were changed very frequently. So the e-forms were often changed. Plenty of e-forms content were needed to be changed and the e-forms need to be integrated with many exisitng(third party) systems. All these has beyond the original design scope of e-forms. This invention is for above scenarios, it can help divide the e-form into some parts, the common part will be reused in many specific forms. The invetion can help merge/sync the content of e-form when needed. This can reduce the form size and decrease the cost of test, development, deployment.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 25% of the total text.

1

E-form enhancement tool

For a modern enterprise as well as the top 500 enterprises, e-form as replacing the paper is used widely. The e-forms are used in

many industries (banking, communication, insurance, etc) and business domains. Now enterprise has more dependencies on

e-form, e-forms were used in many areas. The e-forms even to replace many traditional systems. In the real practice, enterprise

business were changed very frequently. So the e-forms were often changed. Plenty of e-forms content were needed to be changed

and the e-forms need to be integrated with many exisitng(third party) systems. All these has beyond the original design scope of

e-forms. This invention is for above scenarios, it can help divide the e-form into some parts, the common part will be reused in

many specific forms. The invetion can help merge/sync the content of e-form when needed. This can reduce the form size and

decrease the cost of test, development, deployment.

Background: 1. For one complex E-FORM application, it only can be developed/maintained by one people. So as the requirements changed frequently, the delivery time will often be delayed. 2. In the real world, many E-FORM applications will have the similar functionalities, such as the ui, process, securities. But all these can not be reused cross the E-FORM applications, so the develop/maintain team need modify / develop the similar functions in different E-FORM applications. If some common requirements changed, it will bring too much more repeatedly work. 3. E-FORM application has the size limitation, if the FORM application size is too big, it will result in the big performance issues. And E-FORM application can not submit too much more data to server. 4. If one E-FORM application call another E-FORM application's functions, when deployed the FORM applications to a new environment, the call will be failed. Because the E-FORM applications were deployed to new server, the service id of FORM application will be replaced by a new UUID(Universal Unique Identifier). So developers will change the services id with new server service id by hand. 5. It is very hard to manage, deploy, modify, backup and restore thousands of E-FORM applications. 6. It is hard to change the common static JavaScript files , we can reference the JavaScript files in every E-FORM application, but it will increase the security and deployment risk and cost. 7. Along with the number of E-FORM applications increasing, the more repeated development and testing workload will be more heavy. 8. E-FORM appliation was not integrated with version controll tool.It is not easy to maintain the history of plenty of E-FORM applications. To batch backup/restore the E-FORM applications is very difficult. All the elements (UI, data types, processes, security, uses, rules, etc)of one E-FORM application were defined in one application.xml file. So the tool just merge/sync the application.xml files in different FORM applications can make all these to rea...