BenArticleThis is a summary of the past work. The content is based on the smart form system that has been run. Here we only discuss the implementation of Asp.net.
There are already a lot of content about smart forms on the market. As part of the quick development platform, many smart forms come with the OA system, and some professional development platforms, including Microsoft's infopath, provides a similar rapid development framework. Each framework has its own advantages and disadvantages, and it is difficult to have a perfect solution. These shortcomings are listed as follows:
-
- Database support is not provided. Some smart forms use XML as the data access medium, or use pre-defined table structures to access data, rather than using the form engine to create a corresponding database based on user-designed content. Of course, using XML has the advantages of using XML, such as being simple and flexible. However, in this case, the enterprise-level application market has been lost and the access to large data volumes is not supported, you cannot use the features of the database to optimize the data.
-
- Secondary extension is not supported. Many smart form systems use system-defined events or functions to support secondary extension development. The consequence of this implementation is that customers can only expand within a specified and limited range, however, the customer's requirements are not limited. We cannot preassume the scope of the customer's requirements, so as to extend the scope of the restrictions.
- No form operation is generatedSource codeFile: the problem is basically the same as the previous one. If the source of the form operation generated by the smart form systemCodeFile.
-
- Or for developers or end users: for example, some OA automatic smart form systems are mainly for end users, while some professional development platforms are for developers, it is difficult to unify the two. Is there a uniform tool for developers to speed up development and end users to speed up demand response?
-
- Too simple: Some OA smart form systems are relatively simple to implement and cannot process some advanced interaction elements. For example, sub-tables, cascading drop-down boxes, computing domains, tree structures, topology charts, and data verification.
-
- Based on the C/S structure: the B/S and C/S structures are not compared here. Some professional development tools are doing well and provide the C/S structure similar to the vs.net development platform tools for design. However, this restricts the customer to be a developer, it cannot be used by end users. And wouldn't it be better to perform secondary development directly in vs.net?
-
- Unable to respond quickly to customer requirements: to use smart forms designed by professional development platforms, you must compile and deploy the project. Applications with high requirements cannot meet the requirements.
-
- Only data access is implemented, regardless of permissions: The designed form can be delivered for use, but permissions cannot be set for the form, such as Operation permissions (add, delete, modify, query, etc ), field permissions (visible, writable, etc.), record permissions (visibility of personnel on each record)
- There is no corresponding workflow system: Of course, the workflow system is useless for forms that do not require a process. However, for forms that require a process, a corresponding workflow system must be provided to assist the work. In terms of product design, the interaction between the workflow system and the form is not enough. The process cannot read the form data through configuration, but must be completed through secondary development.
-
- The interface is not user-friendly and is not easy to use. For example, if there are only a few dozen data sources in a selection field, you can use a drop-down box to implement the selection. However, if there are millions of data entries, the drop-down box is obviously unrealistic, it must be implemented in other ways.
-
- No built-in intelligent report and statistics functions. The customer cannot implement automatic report and statistical functions for the data collected by smart forms.
-
- No detailed form operation logs exist. Since intelligent forms are implemented, it is better to add, delete, modify, and query detailed records for this form in one step.
This article will discuss how to implement an intelligent form system that can solve the above problems. Of course, you can also list more questions or look at the other side of the problem from different perspectives.
Paste some images for reference.
Form Designer:
Organizational Structure Topology
Tree list
Chart statistics
