CN112766910B - Document construction method, generation method, device, electronic equipment and storage medium - Google Patents
Document construction method, generation method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112766910B CN112766910B CN202110084688.6A CN202110084688A CN112766910B CN 112766910 B CN112766910 B CN 112766910B CN 202110084688 A CN202110084688 A CN 202110084688A CN 112766910 B CN112766910 B CN 112766910B
- Authority
- CN
- China
- Prior art keywords
- bill
- interface
- control
- metadata
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 90
- 238000010276 construction Methods 0.000 title claims abstract description 44
- 238000004458 analytical method Methods 0.000 claims abstract description 41
- 238000012545 processing Methods 0.000 claims abstract description 36
- 238000004590 computer program Methods 0.000 claims description 11
- 238000004364 calculation method Methods 0.000 claims description 6
- 238000011161 development Methods 0.000 abstract description 7
- 230000008901 benefit Effects 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 30
- 230000007246 mechanism Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000004931 aggregating effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Document Processing Apparatus (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the application provides a bill construction method, a bill generation device, electronic equipment and a storage medium, and relates to the technical field of data processing. Analyzing received metadata to obtain analysis data, wherein the metadata comprises interface metadata, control metadata, entity metadata and workflow setting data; sending the analysis data to a client so that the client can construct a bill interface by using the analysis data; receiving document interface data returned by a client and judging whether metadata field conditions are met; if yes, classifying and storing the bill interface data into a database; the method has the advantages that the dynamic construction is carried out on the bill, and the problems that the existing bill configuration method is poor in usability and high in development cost are solved.
Description
Technical Field
The application relates to the technical field of data processing, in particular to a bill construction method, a bill generation device, electronic equipment and a storage medium.
Background
Enterprise resource planning (Enterprise Resource Planning, ERP for short) is an enterprise information management system for performing information integration management on material information, fund information and personnel information for enterprise users, and in practical application, various business documents are required to be used in an enterprise office flow to record a business processing process.
The existing document configuration method has strict requirements on format, such as extensible markup language (Extensible Markup Language, abbreviated as XML) files, and is easy to cause file format errors so that documents cannot be normally used, so that the method has the technical threshold, is poor in usability and is high in development cost.
Disclosure of Invention
The embodiment of the application aims to provide a bill construction method, a generation device, electronic equipment and a storage medium, which are used for dynamically constructing a bill and solve the problems of poor usability and high development cost of the conventional bill configuration method.
The embodiment of the application provides a bill construction method, which is applied to a server, and comprises the following steps:
parsing the received metadata to obtain parsed data, wherein the metadata comprises interface metadata, control metadata, entity metadata and workflow setting data;
sending the analysis data to a client so that the client can construct a bill interface by using the analysis data;
receiving document interface data returned by a client and judging whether metadata field conditions are met;
if yes, the bill interface data are stored in a database in a classified mode.
In the implementation process, the metadata is analyzed through the server, specifically, the interface metadata and the control metadata are analyzed to judge which controls are displayed on the interface, the definition of the workflow node is analyzed to transmit the analysis data to the client for interface construction, and the receipt interface data is received for storage to realize dynamic construction of the receipt, so that the problem that the existing receipt configuration method is poor in usability and high in development cost is solved.
Further, before the step of parsing the received metadata to obtain parsed data, the method further includes:
receiving metadata obtained by defining database entities and entity fields by an entity editing designer, defining a document interface by an interface editing designer to obtain interface metadata and control metadata, and defining workflow setting data by a workflow definition designer.
In the implementation process, the user can dynamically design the wanted bill interface according to specific business scene requirements by defining metadata and business processes required by bill construction through the entity editing designer, the interface editing designer and the workflow definition designer.
The embodiment of the application also provides a bill generation method which is applied to the client, and comprises the following steps:
receiving analysis data sent by a server;
processing the control value and the control attribute according to the analysis data so as to construct a bill interface;
if the analysis data contains bill details, bill detail display is constructed;
and sending the constructed bill interface data to a server for storage.
In the implementation process, a dynamic construction process of the data bill interface of the client is provided, and all information required for constructing the bill interface is included in the analysis data, so that the client performs interface construction and display according to the analysis data, and the dynamic construction process of the bill detail is also included, so that different business requirements are met.
Further, the method further comprises:
when the control value of the bill interface is sent to be changed, if the current control is a carrying entity field, searching the control containing the carrying entity field on the bill interface and carrying out automatic assignment operation by using the carrying entity field attribute, wherein the bill control attribute comprises the carrying entity attribute and the carrying entity field attribute of the control, and is edited and set through an interface editing designer.
In the implementation process, a bill control value processing mechanism is provided, the client can carry out associated assignment operation according to the change of the bill control value, the server is not required to carry out control processing, usability is enhanced, and the data dynamic loading requirement is met.
Further, the method further comprises:
when the control value of the bill interface is sent to be changed, if the current control is the control associated with the conditional formula, calculating according to the conditional formula, and performing automatic calculation and assignment operation on the control, wherein the attribute of the conditional formula is edited and set through an interface editing designer.
In the implementation process, the client side realizes the automatic calculation and assignment function of the space according to the condition formula when the associated control changes.
Further, the method further comprises:
when a trigger event occurs to the control, if the current control is a designated trigger control, calling back a server interface and sending a control attribute and a control value of a bill interface to the server so that the server carries out logic judgment processing, wherein the designated trigger control is a trigger control and a control trigger event type of a bill designated by the server;
and receiving an execution instruction returned by the server side to operate the execution instruction.
In the implementation process, the triggering control and the control triggering event type of the bill are specified through the server, so that logic judgment processing can be flexibly performed according to the associated data in the database, the work of reissuing and updating by the client is omitted, and the client can perform corresponding operations such as modifying control values, changing control selection data sources, modifying control read-only properties, changing control visibility and the like according to the execution instruction.
The embodiment of the application also provides a bill dynamic construction device which is applied to the server and comprises:
the analysis module is used for analyzing the received metadata to obtain analysis data, wherein the metadata comprises interface metadata, control metadata, entity metadata and workflow setting data;
the sending module is used for sending the analysis data to the client so that the client can construct a bill interface by utilizing the analysis data;
the judging module is used for receiving the bill interface data returned by the client and judging whether the metadata field conditions are met or not;
and the storage module is used for classifying and storing the bill interface data to a database if the metadata field conditions are met.
In the implementation process, the dynamic construction of the bill interface is realized through the data interaction between the server and the client, and the requirement of a user for constructing the bill interface according to specific business scene requirements is met from the actual application requirement, so that the problems of high development cost and poor usability of the conventional bill page layout are solved.
The embodiment of the application also provides a bill generating device which is applied to the client, and the device comprises:
the receiving module is used for receiving the analysis data sent by the server;
the bill construction module is used for processing the control value and the control attribute according to the analysis data so as to construct a bill interface;
the bill detail display module is used for constructing bill detail display if the analysis data contains bill details;
and the sending module is used for sending the constructed bill interface data to the server for storage.
In the implementation process, the dynamic construction of the bill interface is performed by utilizing all data, namely analysis data, required by constructing the bill interface, so that the bill construction requirements of different service scenes are met, and the problems of high development cost and poor usability of the conventional bill page layout are solved.
The embodiment of the application also provides electronic equipment, which comprises a memory and a processor, wherein the memory is used for storing a computer program, and the processor runs the computer program to enable the computer equipment to execute the bill generation method.
The embodiment of the application also provides a readable storage medium, wherein the readable storage medium stores computer program instructions, and when the computer program instructions are read and run by a processor, the bill generation method of any one of the above is executed.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a document construction method provided by an embodiment of the present application;
FIG. 2 is a schematic diagram of data transmission in a document dynamic construction process according to an embodiment of the present application;
FIG. 3 is a flow chart of a method for document dynamic construction process according to an embodiment of the present application;
FIG. 4 is a flowchart of a document generation method according to an embodiment of the present application;
FIG. 5 is a flow chart of an automatic association assignment event provided by an embodiment of the present application;
FIG. 6 is a flow chart of a method for conditional formula auto-event provided by an embodiment of the present application;
FIG. 7 is a flowchart illustrating a method for customizing an event mechanism according to an embodiment of the present application;
FIG. 8 is a block diagram of a document dynamic construction device according to an embodiment of the present application;
fig. 9 is a block diagram of a document generation device according to an embodiment of the present application.
Icon:
101-PC end; 102-a server; 103-client; 200-an analysis module; 300-a transmitting module; 400-judging module; 500-a saving module; 600-a receiving module; 700-bill construction module; 800-bill detail display module; 900-bill sending module; 910-an automatic assignment module; 920—a conditional formula module; 930-custom event module; 931-a control data transmission module; 932-execute module.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance.
Example 1
Referring to fig. 1, fig. 1 is a flowchart of a document construction method according to an embodiment of the present application. The method may be applied to the server 102, as shown in fig. 2, and is a data transmission schematic diagram of a document dynamic construction process provided by an embodiment of the present application, where the client 103 may be a mobile client 103, such as a mobile phone, and the entity editing designer, the interface editing designer, and the workflow definition designer are set on the PC 101, so as to transmit the generated metadata to the server 102, and the server 102 sends the analysis data to the client 103, so as to construct a document interface, as shown in fig. 3, and is a method flowchart of the document dynamic construction process, where the specific construction process at the server 102 includes the following steps:
step S100: parsing the received metadata to obtain parsed data, the metadata including interface metadata, control metadata, entity metadata, and workflow setting data;
the metadata provides all data required for constructing the bill interface, and can be adaptively defined and set according to service requirements so as to improve flexibility of constructing the interface bill, for example, the metadata can be obtained through an editor arranged at a PC end, specifically, a database entity and an entity field are defined through an entity editing designer, a bill interface is defined through the interface editing designer so as to obtain interface metadata and control metadata, and workflow setting data is defined through a workflow definition designer so as to obtain metadata.
Specifically, the entity editing designer is used for designing entity metadata, and can define the database entity metadata, wherein the defined content comprises a database entity and an entity field, the database entity corresponds to a table in a database, the attribute comprises a table name, an associated program set, an entity type and the like, the attribute of the entity field corresponds to a field in the database table, and the attribute of the entity field comprises a data entity, a field name, a field type, a field length, whether the record is necessary, whether the record is visible or not and the like.
The interface editing designer is a graphical interface editing designer, can define a business bill interface, and the defined content contains bill interface attributes such as names, types, associated entities, rights, styles and the like of the bill interface and is stored in a database and called interface metadata; and the control attributes on the bill interface, such as control names, control types, control associated fields, read-only, activation, styles and the like, are included, and are control metadata.
The workflow definition designer is used for defining a business flow, wherein the workflow is associated with a business document, a business document interface associated with the workflow is designated when the workflow is defined, and an associated database entity is designated by the business document interface. In the workflow definition designer, besides the attribute of the workflow can be customized, the attribute of the workflow node can be defined, wherein in the workflow node attribute, the field attribute of the related entity of the current workflow node can be set, including the visibility, the record-necessary attribute and the read-only attribute of the entity field, and different bill fields can be displayed according to different workflow nodes through the definition of the workflow node.
The server 102 parses the metadata, finds a corresponding business document interface according to the initiated workflow, parses according to the interface metadata of the business document interface and the control metadata, and determines which controls will be displayed on the interface, including the field title and field type of the fields associated with the controls, the default values of the fields, whether read-only, whether record is necessary, and other attributes. Meanwhile, when the entity field associated with the control is parsed, entity metadata is also used for judgment, for example, when the definition of the entity metadata is the record, then the field is the record, and the data returned to the client 103 by the server 102 will include the information.
In addition to interface metadata, control metadata, and entity metadata, when parsing the interface control, the definition of the workflow node is parsed, where the workflow node definition includes attribute controls of the interface field of the current node, including whether to display, read-only, and record, and these attribute controls are transferred to the client 103 after being parsed.
Step S200: sending the analysis data to the client 103, so that the client 103 constructs a bill interface by using the analysis data;
after the server 102 finishes metadata parsing, the parsed data is returned to the client 103, wherein the parsed data comprises all information required by the client 103 to construct an interface, the client 103 constructs and displays the interface according to the data, such as field titles and names of data entity fields displayed on the interface, and controls of different types are used for display according to field types, such as a text edit box control of a character string type, a date type use date selection control, a time type use time selection control and a business type (a data type) use check box control; there is also a reference type field that can reference other data entities to obtain associated data for selection, open a new page for data source selection when processed by the client 103, return to the document page after selecting a record, and display the data on the control.
Step S300: receiving document interface data returned by the client 103 and judging whether metadata field conditions are met;
step S400: if yes, the bill interface data are stored in a database in a classified mode.
The bill interface data can be the construction data of the bill and the modification and submission data of the bill, so the method not only provides a dynamic creation method for the bill, but also provides a creation and modification and submission method for the bill. The metadata field conditions such as non-modifiable, field must-record, etc., the server 102 processes document interface data submitted by the client 103, and judges the read-only attribute and the must-record attribute; and then, according to the interface attribute, the control attribute, the corresponding entity metadata and the field metadata, the bill interface data is stored in a database, and the bill detail data is stored in a detail entity corresponding to the database.
Example 2
An embodiment of the present application provides a document generation method, which is applied to a client 103 in embodiment 1, and as shown in fig. 4, is a flowchart of the document generation method, and the method specifically may include the following steps:
step S500: receiving the analysis data sent by the server 102;
step S600: processing the control value and the control attribute according to the analysis data to construct a bill interface;
step S700: if the analysis data contains bill details, bill detail display is constructed;
in the bill detail construction process, for general ERP business bills, related detail content is generally included in addition to the content of the bill, one bill can have various bill details, and each bill detail can have a plurality of detail records. For example, when a receipt is created in warehouse management, the receipt details such as the materials applied, the amount applied, and the amount of money are included. The system automatically realizes the display of bill details according to the association relation between the data entity and the metadata of the data entity field, and supports the addition, modification and deletion of the details.
In the bill construction process, the interface display control of the client 103 mainly comprises two aspects, namely, the processing of the client 103 on the control value comprises a control data source, a control selection data source, control assignment, detail list display, detail control data source, detail control selection data source, detail control assignment and the like. On the other hand, the processing of the control attribute by the client 103 includes whether to display, edit, record, style control, and the like, and is effective for the document field and the document detail field.
When the interface is loaded with the created bill, the client 103 performs interface construction according to the metadata returned by the server 102, performs assignment processing on the control on the interface according to the data returned by the server 102, and performs assignment processing on the bill detail construction display and detail control assignment, and jumps to a new interface to realize editing processing on the detail when clicking the detail.
Step S800: and sending the constructed document interface data to the server 102 for storage.
In addition, the creation and modification submission of the bill are processed in combination with the set workflow, and a workflow instance is also created when the bill is created, and the bill can enter the next node according to the set workflow and is processed by the next processor.
The method also provides a plurality of flexible event processing mechanisms such as automatic association assignment events, conditional formula automatic events, custom events and the like, so that the flexibility and the practicability of dynamic document construction are improved, and as shown in fig. 5, the automatic association assignment event flow chart provided by the embodiment of the application is provided. And editing the control carrying entity and the carrying entity field attribute through an interface editing designer, and when the control value of the bill interface is sent to change in the process of analyzing and constructing the bill interface by the client 103, searching the control containing the carrying entity field on the bill interface and carrying out automatic assignment operation by using the carrying entity field attribute if the current control is the carrying entity field, wherein the bill control attribute comprises the carrying entity attribute and the carrying entity field attribute of the control, and is edited and set through the interface editing designer.
The interface editing designer provides a control attribute setting function, wherein the control attributes comprise a carrying entity of the control and a carrying entity field attribute, the carrying entity attribute represents that the entity field type associated with the control in the current bill is an entity type (namely a reference type field), and the carrying entity field attribute represents a certain field of the entity type. For example, a department control designates a carrying entity as an 'applicant' entity, designates a carrying entity field as a 'department', and when the applicant control in the document is assigned, the department control automatically uses the department where the applicant is located to carry out assignment.
The server 102 analyzes the interface and the control metadata and transmits the metadata to the client 103, when the document control value of the interface changes, the client 103 automatically completes the associated assignment operation of other controls according to the metadata, and the process does not need the control processing of the server 102. In addition, assignment events are automatically associated, and field processing of bill details is supported.
As shown in fig. 6, a flow chart of a method for conditional formula automation events. When the control value of the bill interface is sent to be changed, if the current control is the control associated with the conditional formula, calculating according to the conditional formula, and performing automatic calculation and assignment operation on the control, wherein the attribute of the conditional formula is edited and set through an interface editing designer.
The interface editing designer provides a control conditional formula attribute setting function, and the value of the conditional formula attribute representing the current control is obtained by calculating other control values in the bill, including bill detail control and conditional formula, and is automatically assigned. The elements of the conditional formula include control entity fields, such as document detail fields, control accumulation fields, and operation operators. Similarly, the server 102 program analyzes the interface and the metadata of the control, and then transmits the analyzed interface and metadata of the control to the client 103, and the client 103 realizes an automatic calculation and assignment function of the control, such as a commonly used function of aggregating the amounts of a plurality of bill details and displaying the aggregated amounts in a main bill when the associated control changes according to a conditional formula.
FIG. 7 is a flow chart of a method for customizing an event mechanism. The method specifically comprises the following steps:
step S811: when a trigger event occurs to the control, if the current control is a designated trigger control, calling back the interface of the server 102 and sending the control attribute and the control value of the bill interface to the server 102 so as to enable the server 102 to perform logic judgment processing, wherein the designated trigger control is the trigger control and the control trigger event type of the bill designated by the server 102;
step S812: and receiving an execution instruction returned by the server 102 to operate on the execution instruction.
Through the control of the custom code of the server 102, not only can the logic judgment processing be flexibly performed according to the associated data in the database, but also the work of reissuing the update by the mobile client 103 is omitted. The server 102 first designates a trigger control of a document and a trigger event type of the control, wherein the trigger type includes a change of a control value, a control click event, a control double click event and the like.
When the value of the control triggered by the client 103 changes, the client 103 automatically calls back the interface of the server 102, and simultaneously returns the attribute and the value of the control on the bill interface and the attribute and the value of each bill detail, after the service logic processing is performed by the server 102 in the callback event, the execution instruction is returned to the client 103, the client 103 analyzes and executes the execution instruction, and the operation can be performed on the bill interface and the control of the client 103, such as modifying the control value, changing the control selection data source, modifying the control read-only attribute, changing the control visibility, and the like.
Therefore, the method can meet the data dynamic loading requirement and interface interaction requirement of the user and the requirement of combining the ERP system workflow to dynamically control the interface in the approval node, and compared with the document page layout, the method has the advantages of lower development cost and higher usability.
In addition, the executable instructions of the client 103 are executable codes defined and encapsulated by the client 103, and are used for providing the executable codes to the server 102 and executing on the interface of the client 103 for interface display and interaction control, including processing of control values, such as control data sources, control selection data sources, control assignment, list display, detail control data sources, detail control selection data sources, detail control assignment, and the like, and processing of control attributes, such as whether the control is displayed, editable, whether the control is recorded, style control, and the like; and simultaneously, interactive operations of the interface, such as a prompt box and a confirmation box, are also provided.
In addition, the method also comprises a bill initializing event: the method is provided by the server 102, and is defined at the server 102, when the server 102 analyzes and initializes the bill interface, the server 102 provides an initialization event, and bill initialization logic processing, such as bill control initialization assignment, bill control data source assignment, control attribute control and the like, can be performed according to specific service requirements in the event. After the processing is completed, the server 102 returns the metadata to the client 103 for analysis and display.
Unified server 102 control code: optionally, the server 102 may encapsulate the code executed by the client 103, and use the unified control code of the server 102 to expose the code to the caller of the server 102 in the manner of the language of the server 102, so as to improve the usability of the frames and reduce the coupling between the frames, and the caller no longer needs to consider the implementation and the calling method of the frames of the client 103. For the bill initializing event and the custom event mechanism, unified control codes of the server 102 can be used for operating the interface.
Custom menu events: in the method of the present application, the custom menu is added and defined in the interface editing designer, and is used for displaying on the menu bar of the bill interface, and is generally used for specific operations, such as saving operation, approval operation, deletion operation, etc. and other custom operations, and the client 103 automatically analyzes according to the metadata of the designer and displays on the bill interface. When the custom menu is clicked, a custom menu event is triggered, which is recalled by the client 103 to the server 102, and menu event logic processing is performed in the server 102. The implementation of the custom menu event is based on a unified custom event mechanism, but does not need to specify a trigger control at the server 102, and can judge and execute different service logics according to the menu name.
New interface opening mechanism: optionally, the method of the application provides a mechanism for opening a new interface on the bill interface and a mechanism for data interaction between the original bill interface and the new interface. The mechanism is based on a unified self-defined event mechanism, and the implementation process is as follows: the server 102 designates a trigger control, when the control triggers an event, the client 103 automatically calls back the server 102, performs business logic processing on the server 102 and obtains data to be transmitted to a new interface, meanwhile, the server 102 needs to analyze metadata related to the interface according to the opened new interface and execute a bill initializing event of the new interface, data transmitted by an original bill interface is provided in the initializing event, finally, an executing code instruction for opening the new interface and the metadata and control data of the new interface are returned to the client 103, and the client 103 executes a new bill interface construction process.
Data source processing events: optionally, an event mechanism is provided in the method of the application in which the document interface processes data referencing a selected data source interface of the type control. For example, when staff selecting a bill interface and opening the staff selecting interface, staff can be filtered according to the filtering condition of the organization according to the control value of the organization of the current bill interface. The implementation flow is as follows: when the user clicks the controls, the client 103 automatically calls back the server 102, and returns the attribute and value of the controls on the bill interface, the attribute and value of each bill detail, the server 102 executes the data source processing event, processes the selectable data source, and finally returns the processed data source to the client 103, and the client loads and displays the interface according to the data source.
As can be seen from the above, the document interface is designed and described by the interface editing designer, the entity editing designer and the workflow definition designer, and the user can dynamically design the document interface according to specific business scene requirements. Meanwhile, from the actual application requirement, the construction requirement of the bill interface is comprehensively provided, and the bill detail processing, the bill control value processing and the bill control attribute processing are included; not only is a method for dynamically constructing the bill by the client 103 provided, but also a method for creating and modifying and submitting the bill is provided. In addition, a plurality of bill event interaction mechanisms are provided, the realization of low codes is guaranteed to the greatest extent, meanwhile, the diversity and the flexibility of the realization of the bill service logic are guaranteed, and support is provided for the expansibility of the bill service logic.
Example 3
An embodiment of the present application provides a dynamic document construction device, which is applied to a server 102 in embodiment 1, as shown in fig. 8, and is a structural block diagram of the dynamic document construction device, where the device includes:
the parsing module 200 is configured to parse the received metadata to obtain parsed data, where the metadata includes interface metadata, control metadata, entity metadata, and workflow setting data;
the sending module 300 is configured to send the parsing data to the client 103, so that the client 103 builds a document interface by using the parsing data;
a judging module 400, configured to receive document interface data returned by the client 103 and judge whether metadata field conditions are satisfied;
and the storage module 500 is configured to store the document interface data in a database in a classified manner if the metadata field condition is satisfied.
The embodiment of the present application further provides a document generating device, which is applied to the client 103 in embodiment 2, as shown in fig. 9, and is a structural block diagram of the document generating device, where the device includes:
a receiving module 600, configured to receive the parsed data sent by the server 102;
the bill construction module 700 is configured to process the control value and the control attribute according to the analysis data so as to construct a bill interface;
the bill detail display module 800 is configured to construct bill detail display if the analysis data includes a bill detail;
and the bill sending module 900 is configured to send the constructed bill interface data to the server 102 for storage.
The apparatus further comprises:
and the automatic assignment module 910 is configured to, when the control value of the bill interface is sent to change, if the current control is a carrying entity field, find a control containing the carrying entity field on the bill interface and perform automatic assignment operation by using a carrying entity field attribute, where the bill control attribute includes a carrying entity attribute and a carrying entity field attribute of the control, and is edited and set by an interface editing designer.
The conditional formula module 920 is configured to calculate according to a conditional formula and perform automatic calculation assignment operation on the control when the control value of the bill interface is changed, if the current control is a control associated with the conditional formula, where the attribute of the conditional formula is edited and set by the interface editing designer.
Custom event module 930 includes:
the control data sending module 931 is configured to, when a trigger event occurs to a control, call back the server 102 interface and send the control attribute and the control value of the bill interface to the server 102 if the current control is a specified trigger control, so that the server 102 performs logic judgment processing, where the specified trigger control is a trigger control and a control trigger event type of a bill specified by the server 102;
the execution module 932 is configured to receive an execution instruction returned by the server 102, so as to operate on the execution instruction.
The embodiment of the application also provides electronic equipment, which comprises a memory and a processor, wherein the memory is used for storing a computer program, and the processor runs the computer program to enable the computer equipment to execute the bill construction method in the embodiment 1 and the bill generation method in the embodiment 2.
The embodiment of the present application also provides a readable storage medium, in which computer program instructions are stored, which when read and executed by a processor, perform the document construction method of embodiment 1 and the document generation method of embodiment 2.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, of the flowcharts and block diagrams in the figures that illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and variations will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application. It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. The bill construction method is characterized by being applied to a server, and comprises the following steps:
parsing the received metadata to obtain parsed data, wherein the metadata comprises interface metadata, control metadata, entity metadata and workflow setting data;
sending the analysis data to a client so that the client can construct a bill interface by using the analysis data;
receiving document interface data returned by a client and judging whether metadata field conditions are met;
if yes, the bill interface data are stored in a database in a classified mode.
2. The document construction method according to claim 1, wherein before the step of parsing the received metadata to obtain parsed data, the method further comprises:
receiving metadata obtained by defining database entities and entity fields by an entity editing designer, defining a document interface by an interface editing designer to obtain interface metadata and control metadata, and defining workflow setting data by a workflow definition designer.
3. A document generation method, applied to the client of any one of claims 1-2, the method comprising:
receiving analysis data sent by a server;
processing the control value and the control attribute according to the analysis data so as to construct a bill interface;
if the analysis data contains bill details, bill detail display is constructed;
and sending the constructed bill interface data to a server for storage.
4. A document generation method according to claim 3, wherein the method further comprises:
when the control value of the bill interface is changed, if the current control is a carrying entity field, searching the bill interface for the control containing the carrying entity field and performing automatic assignment operation by using the carrying entity field attribute, wherein the bill control attribute comprises the carrying entity attribute and the carrying entity field attribute of the control, and is edited and set by an interface editing designer.
5. A document generation method according to claim 3, wherein the method further comprises:
when the control value of the bill interface is changed, if the current control is the control associated with the conditional formula, calculating according to the conditional formula, and performing automatic calculation and assignment operation on the control, wherein the attribute of the conditional formula is edited and set through an interface editing designer.
6. A document generation method according to claim 3, wherein the method further comprises:
when a trigger event occurs to the control, if the current control is a designated trigger control, calling back a server interface and sending a control attribute and a control value of a bill interface to the server so that the server carries out logic judgment processing, wherein the designated trigger control is a trigger control and a control trigger event type of a bill designated by the server;
and receiving an execution instruction returned by the server side to operate the execution instruction.
7. A document construction apparatus, for application to a server, the apparatus comprising:
the analysis module is used for analyzing the received metadata to obtain analysis data, wherein the metadata comprises interface metadata, control metadata, entity metadata and workflow setting data;
the sending module is used for sending the analysis data to the client so that the client can construct a bill interface by utilizing the analysis data;
the judging module is used for receiving the bill interface data returned by the client and judging whether the metadata field conditions are met or not;
and the storage module is used for classifying and storing the bill interface data to a database if the metadata field conditions are met.
8. A document generation apparatus for application to the client of any one of claims 1-2, the apparatus comprising:
the receiving module is used for receiving the analysis data sent by the server;
the bill construction module is used for processing the control value and the control attribute according to the analysis data so as to construct a bill interface;
the bill detail display module is used for constructing bill detail display if the analysis data contains bill details;
and the sending module is used for sending the constructed bill interface data to the server for storage.
9. An electronic device comprising a memory for storing a computer program and a processor that runs the computer program to cause the computer device to perform the document generation method according to any one of claims 3 to 6.
10. A readable storage medium having stored therein computer program instructions which, when read and executed by a processor, perform the document generation method of any one of claims 3 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110084688.6A CN112766910B (en) | 2021-01-21 | 2021-01-21 | Document construction method, generation method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110084688.6A CN112766910B (en) | 2021-01-21 | 2021-01-21 | Document construction method, generation method, device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112766910A CN112766910A (en) | 2021-05-07 |
| CN112766910B true CN112766910B (en) | 2023-10-27 |
Family
ID=75702567
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110084688.6A Active CN112766910B (en) | 2021-01-21 | 2021-01-21 | Document construction method, generation method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112766910B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5790790A (en) * | 1996-10-24 | 1998-08-04 | Tumbleweed Software Corporation | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
| JP2003157210A (en) * | 2001-11-20 | 2003-05-30 | Hitachi Ltd | Method for collecting data and implementation device therefor |
| CN1588369A (en) * | 2004-09-06 | 2005-03-02 | 杭州恒生电子股份有限公司 | Relation type data base system and its search and report method |
| CN102479355A (en) * | 2010-11-30 | 2012-05-30 | 金蝶软件（中国）有限公司 | Method and device for loading business documents and mobile terminal |
| WO2013126826A1 (en) * | 2012-02-24 | 2013-08-29 | Winshuttle, Llc | Dynamic web services workflow system and method |
| CN103577197A (en) * | 2013-11-18 | 2014-02-12 | 深圳市远行科技有限公司 | Method for achieving android application program dynamic form |
| CN104376068A (en) * | 2014-11-07 | 2015-02-25 | 北京思特奇信息技术股份有限公司 | Data representation system and method based on dynamic report template |
| CN109271411A (en) * | 2018-09-28 | 2019-01-25 | 中国平安财产保险股份有限公司 | Report form generation method, device, computer equipment and storage medium |
| CN110795475A (en) * | 2019-09-24 | 2020-02-14 | 金蝶软件（中国）有限公司 | Report generation method and device, computer equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10699067B2 (en) * | 2016-06-08 | 2020-06-30 | Hexagon Technology Center Gmbh | Form design and data input in which a server provides a repository of form templates that are distributed to multiple form filing client systems |
| CN109657178B (en) * | 2018-11-12 | 2024-03-01 | 平安科技（深圳）有限公司 | Page form processing method and device, computer equipment and storage medium |
-
2021
- 2021-01-21 CN CN202110084688.6A patent/CN112766910B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5790790A (en) * | 1996-10-24 | 1998-08-04 | Tumbleweed Software Corporation | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
| JP2003157210A (en) * | 2001-11-20 | 2003-05-30 | Hitachi Ltd | Method for collecting data and implementation device therefor |
| CN1588369A (en) * | 2004-09-06 | 2005-03-02 | 杭州恒生电子股份有限公司 | Relation type data base system and its search and report method |
| CN102479355A (en) * | 2010-11-30 | 2012-05-30 | 金蝶软件（中国）有限公司 | Method and device for loading business documents and mobile terminal |
| WO2013126826A1 (en) * | 2012-02-24 | 2013-08-29 | Winshuttle, Llc | Dynamic web services workflow system and method |
| CN103577197A (en) * | 2013-11-18 | 2014-02-12 | 深圳市远行科技有限公司 | Method for achieving android application program dynamic form |
| CN104376068A (en) * | 2014-11-07 | 2015-02-25 | 北京思特奇信息技术股份有限公司 | Data representation system and method based on dynamic report template |
| CN109271411A (en) * | 2018-09-28 | 2019-01-25 | 中国平安财产保险股份有限公司 | Report form generation method, device, computer equipment and storage medium |
| CN110795475A (en) * | 2019-09-24 | 2020-02-14 | 金蝶软件（中国）有限公司 | Report generation method and device, computer equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| Heresy: a Serverless Web Application to Store Compressed and Encrypted Document in the Form of URL;Gottfried Prasetyadi等;2019 Fourth International Conference on Informatics and Computing (ICIC). Proceedings;5 * |
| 基于 ActiveX 的 EIP 动态报表系统;陈叶能等;软件开发与应用;第26卷(第5期);86-88 * |
| 多数据源自动化报表的研究与开发;黄敏;中国优秀硕士学位论文全文数据库信息科技辑(第12期);I138-79 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112766910A (en) | 2021-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11704479B2 (en) | Methods and systems for creating, interacting with, and utilizing a superactive document | |
| CN110325961B (en) | Spreadsheet-based software application development | |
| RU2421797C2 (en) | Indication, definition and detection of electronic table document parameters | |
| CN101373431B (en) | Enhanced widget composition platform | |
| US8452818B2 (en) | Dimension-based relation graphing of documents | |
| US8429527B1 (en) | Complex data merging, such as in a workflow application | |
| US7680823B2 (en) | Custom report generation | |
| US11126968B2 (en) | Custom application builder for supply chain management | |
| US8495510B2 (en) | System and method for managing browser extensions | |
| US9342300B2 (en) | Analyzing components related to a software application in a software development environment | |
| CN103518220A (en) | Changes to documents automatically summarized in electronic messages | |
| KR20090120481A (en) | A consistent method system and computer program for developing software asset based solutions | |
| US20070067714A1 (en) | Modularized web page editing system and method thereof | |
| EP1744254A1 (en) | Information management device | |
| US20070179642A1 (en) | System and method for interactive process management | |
| WO2005094500A2 (en) | Document development platform | |
| KR102187322B1 (en) | System for business rule management | |
| CN112766910B (en) | Document construction method, generation method, device, electronic equipment and storage medium | |
| US8924420B2 (en) | Creating logic using pre-built controls | |
| EP1744271A1 (en) | Document processing device | |
| KR102164607B1 (en) | System for business rule management | |
| KR20010076778A (en) | System and Method for Component Customization | |
| CN117453268A (en) | Quick development platform for data management | |
| CN117667056A (en) | Coding-free configurable simulation model multidimensional management method, device and medium | |
| CN116225406A (en) | Method and device for constructing universal single-screen page |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |