Approval processing method, device, system, electronic device, storage medium and product
By synchronizing the field library and template configuration in the approval process, generating and sending approval forms, the inefficiency of existing technologies is solved, enabling rapid response to user needs and efficient approval process management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- BEIJING XIRUIYASI TECH CO LTD
- Filing Date
- 2022-01-06
- Publication Date
- 2026-05-22
AI Technical Summary
The existing approval process is inefficient and cannot respond quickly to user needs. In addition, the workload of adding and developing new business approval templates is large, resulting in overall inefficiency.
By acquiring the field information related to the business approval request, synchronizing it to the field library to indicate the mapping relationship between each field, and using the mapping relationship to associate the field information with the form template, an approval form is generated and sent to the target terminal, thus realizing the toolization of the approval process.
It improves the efficiency of the approval process, enables rapid response to user needs, reduces business coupling and the possibility of errors, and achieves rapid configuration and deployment of approval forms.
Smart Images

Figure CN114493185B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet technology, and more specifically, to an approval processing method, apparatus, system, electronic device, storage medium, and product. Background Technology
[0002] Approval, a fundamental function of the human resources system, connects the entire employee lifecycle from onboarding to offboarding. With business expansion, the demand for flexible approval processes is increasing. Currently, the large workload of adding and developing new business approval templates leads to low template development efficiency and slow response to user needs. Furthermore, integrating new user requirements or addressing historical issues requires collaboration from developers from various parties. Therefore, the existing approval process is generally inefficient and unable to respond promptly to user needs. Summary of the Invention
[0003] This application provides an approval processing method, apparatus, system, electronic device, storage medium, and product to solve the technical problem of low overall efficiency in existing approval processes, thereby enabling rapid and timely response to user needs.
[0004] According to one aspect of the embodiments of this application, an approval processing method is provided, the method comprising:
[0005] In response to a business approval request, obtain the field information related to the business approval request;
[0006] The field information is synchronized to the field database, which is used to indicate the mapping relationship between the field information;
[0007] Using the mapping relationship, the field information is associated with the form template to obtain the approval form. The form template is generated from preset form configuration information and approval terminal configuration information.
[0008] The approval form is sent to the target terminal that corresponds to the approval terminal configuration information.
[0009] In one possible implementation, the field information includes fields and field values, and obtaining the field information related to the business approval request includes:
[0010] Based on the business information carried when the business approval request is sent, determine the fields used to define the approval form and the field types of the fields, wherein the field types include system fields and user fields;
[0011] Based on the field type, determine the field value retrieval method and the corresponding module identification information;
[0012] Send a value retrieval instruction to the module corresponding to the module identification information to indicate the value of the field, so that the module returns the field value after receiving the value retrieval instruction.
[0013] In one possible implementation, obtaining the field information related to the business approval request further includes:
[0014] When the data structure of the field value returned by the module is a preset basic structure, the field value is formatted; or,
[0015] When the data structure of the field value returned by the module is a preset specific scenario structure, an electronic signature corresponding to the field value is generated.
[0016] In one possible implementation, the module includes a service database that stores active terminal identification information; the method further includes:
[0017] Send a data read instruction to the source terminal corresponding to the source terminal identification information to indicate the value of the field, so that the source terminal returns the field value after receiving the data read instruction;
[0018] The field value of the field is stored in the business database.
[0019] In one possible implementation, sending the approval form to the target terminal corresponding to the approval terminal configuration information includes:
[0020] Determine the approval terminal configuration information, which includes target terminal identification information corresponding to the target terminal;
[0021] The approval forms are grouped according to the listening fields obtained by at least one of the target terminals, so that the grouped approval forms can be sent to the corresponding target terminals.
[0022] In one possible implementation, the step of using the mapping relationship to associate the field information with the form template to obtain the approval form includes:
[0023] The form configuration information is determined, which includes field attribute information of the fields. The field attribute information is used to indicate the display and editing of the fields and their values on the approval form.
[0024] Based on the form configuration information, the approval form is displayed, and the approval form displays multiple editable controls corresponding to the field values respectively;
[0025] In response to a triggering operation of the editable control, the field value corresponding to the editable control is edited.
[0026] In one possible implementation, obtaining the field information related to the business approval request further includes:
[0027] Retrieves the value of the specified field corresponding to the target field;
[0028] Calculate the value of the target field based on the value of the specified field.
[0029] According to one aspect of the embodiments of this application, an approval processing apparatus is provided, the apparatus comprising:
[0030] The approval request module is used to respond to a business approval request and obtain field information related to the business approval request.
[0031] A field library processing module is used to synchronize the field information to a field library, wherein the field library is used to indicate the mapping relationship between the various field information items;
[0032] The approval form creation module is used to associate the field information with the form template using the mapping relationship to obtain the approval form. The form template is generated by preset form configuration information and approval terminal configuration information.
[0033] The approval form sending module is used to send the approval form to the target terminal corresponding to the approval terminal configuration information.
[0034] According to another aspect of the embodiments of this application, an approval processing system is provided, the system comprising: a target terminal and a server, the server comprising a field library;
[0035] The server is configured as follows:
[0036] Receive business approval requests;
[0037] In response to the business approval request, obtain the field information related to the business approval request;
[0038] The field information is synchronized to the field database, which is used to indicate the mapping relationship between the various field information items;
[0039] Using the mapping relationship, the field information is associated with the form template to obtain the approval form. The form template is generated from preset form configuration information and approval terminal configuration information.
[0040] Send the approval form to the target terminal that corresponds to the approval terminal configuration information;
[0041] The target terminal is configured to receive the approval form.
[0042] According to another aspect of the present application, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the approval processing method described in the above embodiments.
[0043] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the approval processing method described in the above embodiments.
[0044] According to another aspect of the embodiments of this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the approval processing method described in the above embodiments.
[0045] The beneficial effects of the technical solutions provided in this application are:
[0046] This application provides an approval processing method, specifically including: responding to a business approval request, obtaining field information related to the business approval request, and then synchronizing the field information to a field library, wherein the field library is used to indicate the mapping relationship between each field information, thereby using the mapping relationship to associate the field information with a form template to obtain an approval form, wherein the form template is generated from preset form configuration information and approval terminal configuration information, and the approval form is sent to a target terminal corresponding to the approval terminal configuration information. In this way, by synchronizing the field library, template configuration, and landing configuration, the approval process is toolified, and the configuration of the approval form and form landing is quickly completed, solving the technical problem of low overall efficiency of the existing approval process, thereby realizing a rapid and timely response to user needs and improving the execution efficiency of the approval process. Attached Figure Description
[0047] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.
[0048] Figure 1 This application provides a schematic diagram of the architecture of an approval processing system.
[0049] Figure 2 A schematic diagram of the server architecture provided for an embodiment of this application;
[0050] Figure 3 A flowchart illustrating an approval processing method provided in an embodiment of this application;
[0051] Figure 4aThis is a schematic diagram illustrating the configuration of form template parameters provided in an embodiment of this application.
[0052] Figure 4b A schematic diagram illustrating the configuration of system fields provided in an embodiment of this application;
[0053] Figure 5 This is a schematic diagram of the structure of an approval processing device provided in an embodiment of this application;
[0054] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0055] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.
[0056] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the terms “comprising” and “including” as used in embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, operation, element, and / or component, but do not exclude implementation as other features, information, data, step, operation, element, component, and / or combinations thereof supported by the art. It should be understood that when we say that an element is “connected” or “coupled” to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. Furthermore, “connected” or “coupled” as used herein can include wireless connection or wireless coupling. The term “and / or” as used herein indicates at least one of the items defined by the term; for example, “A and / or B” can be implemented as “A,” or as “B,” or as “A and B.”
[0057] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0058] Figure 1 This is a schematic diagram of the architecture of an approval processing system provided in an embodiment of this application. The approval processing system 10 includes a server 11 and a target terminal 12. The target terminal 12 and the server 11 are connected through a communication network, and the target terminal 12 and the server 11 can be directly or indirectly connected through wired or wireless communication methods. This application does not impose any restrictions on this.
[0059] Server 11 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms.
[0060] In this application, the approval processing system 10 also includes a source terminal for initiating a business approval request, which is used to indicate the addition or modification of fields. Furthermore, the source terminal is also used to send its business-related field information, such as basic employee user information, to the server. The source terminal can be a business management terminal (e.g., a business manager) corresponding to different business types, and can be any terminal device corresponding to different business types, such as a server, smartphone, tablet, laptop, desktop computer, etc. Business types include leave and attendance, human resources, organizational, and payroll, but are not limited to these. In addition, the approval processing system 10 also includes a user terminal for receiving and responding to user (e.g., employee) operation instructions. Both the user terminal and the source terminal are equipped with application clients, providing locally running applications for business users and employee users. This allows the application client to initiate a corresponding business approval request to the server, and the server to respond to the business approval request by generating a corresponding approval form. When a user (e.g., an employee) initiates an approval process through the user terminal, the user terminal receives and responds to the employee user's touch operations, such as input parameters for the approval form, so that the server can send the approval form to the corresponding target terminal upon completion of the approval process.
[0061] The target terminal 12 corresponds to the aforementioned source terminal. Therefore, the target terminal is a business management terminal corresponding to different business types. For example, when the source terminal used for managing payroll business initiates a business approval request, the server processes the request to generate an approval form related to the payroll business, and finally sends the approved approval form to the target terminal related to the payroll business. The target terminal 12 is equipped with an application client, providing a locally running application for business users, enabling the application client to receive the approval form sent by the server 11. The target terminal 12 can be any terminal device with the application client installed, such as a smartphone, tablet, laptop, desktop computer, smart wearable device, etc., and this embodiment does not limit this. Regarding the hardware structure, the aforementioned application client includes a display screen, memory, processor, and input device, but is not limited to these.
[0062] Server 11 provides background services for applications installed and running on target terminal 12, source terminal, and user terminal. In this application, for example, see [link to example]. Figure 2This is a schematic diagram of the server architecture provided in an embodiment of this application. The server 11 is configured with a terminal interface module 111, an approval service module 112, and a database module 113. The terminal interface module 111 includes a PC unit 1111, an H5 unit 1112, and a CSM backend management unit 1113. The PC unit 1111 manages data interaction between computer device interfaces, the H5 unit 1112 manages data interaction between mobile terminal device interfaces, and the CSM backend management unit 1113 provides backend management for the server 101. The database module 113 includes a MySQL unit 1131, a MongoDB unit 1132, a Redis unit 1133, and a Kafka unit 1134. The MySQL unit 1131 stores and manages programming languages such as PHP and Java; the MongoDB unit 1132 stores and manages distributed files; the Redis unit 1133 is a cache database; and the Kafka unit 1134 is a distributed publish-subscribe messaging system. The approval service module 112 includes a process engine module 1121 and a form module 1122. The process engine module 1121 is used for field value retrieval, i.e., obtaining field information. The form module 1122 is used to configure the corresponding approval form based on the field information. The form module 1122 includes a data aggregation unit 1123 and a metadata unit 1124. The data aggregation unit 1123 is used to merge return values (i.e., field information) from different source terminals. The metadata unit 1124 is used to manage the basic field information that makes up the approval form. The metadata unit 1124 includes a field library 1125, a business database 1126, a landing configuration library 1127, a form library 1128, a control library 1129, and a template library 1130. The system comprises the following components: a field library 1125 for managing system fields and user fields, and defining the mapping relationships between field information; a landing configuration library 1127 for configuring the approval terminal configuration information of approval forms, including target terminal identification information corresponding to the target terminal; a form library 1128 for performing operations such as storing generated approval forms; a template library 1130 for performing operations such as storing form templates corresponding to different business types; a control library 1129 for managing and maintaining controls corresponding to fields, including text controls, date controls, and dropdown controls; and a business database 1126 for storing the identification information corresponding to the field value retrieval interfaces provided by each source terminal (i.e., business management terminal), as well as the returned field information. Therefore, by building the aforementioned approval process platform on server 11, such as synchronizing the field library, template configuration, and landing configuration, the approval process is tool-based. Furthermore, by defining a standard protocol for business management terminals to interface with templates, the tool-based approval process is built, solving the technical problem of low overall efficiency in existing approval processes.
[0063] Figure 3This is a flowchart illustrating an approval processing method provided in an embodiment of this application. The approval processing method is used for, for example... Figure 1 The method, as shown in the server 11, includes steps S201 to S204.
[0064] S201. In response to the business approval request, obtain the field information related to the business approval request.
[0065] In this application, when a source terminal (i.e., a business management terminal) adds or modifies a field, the source terminal needs to issue an approval notification, that is, send a business approval request to the server for the corresponding business of the source terminal. The source terminal also carries notification interface information when sending the business approval request, such as product type, business type, field key, field type, field name, field rules, timestamp, field category, and field value retrieval method. The product type indicates the type of application platform installed on the source terminal, such as HCM (Human Capital Management Platform) or ATS (Action Management Platform); the business type includes leave and attendance business, human resources business, organizational business, and payroll business; the field type includes system fields and user fields. System fields are business fields defined by product development, while user fields (i.e., tenant fields) are fields added by users from the business management end to meet business needs, such as adding a "social security" field according to business requirements; field categories include single-choice fields, multiple-choice fields, and date fields, but are not limited to these; field rules include field length and whether they are required; the field value retrieval method specifically refers to the method of obtaining the field value of the form field, such as calling the default interface, user input, or calling a custom interface.
[0066] More specifically, the default interface is invoked by calling the default data interface of the corresponding source terminal (such as the employee basic information interface and the list interface) to obtain the relevant field information. This allows the field information invoked by the aforementioned interfaces to be automatically filled when a user initiates an approval process. The employee basic information interface is used to transmit basic employee information, such as employee name, position, and address, while the list interface is used to transmit department lists and employee lists. User input is handled by retrieving the field values of the corresponding fields of the triggered editable controls when a user initiates an approval process, in response to the triggering operation of editable controls on the approval form. Calling a custom interface is used to handle special fields. Specifically, when a user initiates an approval process, in response to the triggering operation of an editable control on the approval form, the user selects the field value from the business database. For example, in an organizational business approval process, the approval form output by the server may have an editable control for the "Transfer-in Department" field. This editable control can be a drop-down list control, so that when the control is triggered, multiple field values related to the "Transfer-in Department" field stored in the business database are displayed through the drop-down list. In response to the user's selection operation command, the field value of the "Transfer-in Department" field is determined. Optionally, calling a custom interface can also calculate the field value of a target field based on the field value selected by the user and / or the field value entered. For example, in the approval process for leave applications, the approval template output by the server may have editable controls for the "Leave Start Time" and "Leave End Time" fields. These editable controls can be text controls. By triggering the control and entering the corresponding field values, the field value of the "Leave Duration" field can be calculated based on the field values of the aforementioned fields.
[0067] In some embodiments, the field information includes fields and field values of the fields, and obtaining the field information related to the business approval request includes:
[0068] Based on the business information carried when the business approval request is sent, determine the fields used to define the approval form and the field types of the fields, wherein the field types include system fields and user fields;
[0069] Based on the field type, determine the field value retrieval method and the corresponding module identification information;
[0070] Send a value retrieval instruction to the module corresponding to the module identification information to indicate the value of the field, so that the module returns the field value after receiving the value retrieval instruction.
[0071] In this embodiment, the fields in the approval form to be constructed are determined based on the business type in the business information. For example, when the business type is payroll, the fields required to create the payroll approval form are determined, such as applicant, salary, and department. When the business type is leave application, the fields required to create the leave approval form are determined, such as applicant, leave start time, leave end time, and leave duration. This application does not limit the specific fields corresponding to different business types. Furthermore, the field value retrieval method is determined based on the field name and field type carried when the business approval request is sent. It should be noted that when the field type is a system field, the field value retrieval method includes calling the default interface, user input, and calling a custom interface. In this application, since adding a user field on the source terminal will simultaneously appear in the approval form, and these user fields are all default and cannot be configured by calling a custom interface, when the field type is a user field, the field value retrieval method adopts the method of calling the default interface. Furthermore, the module responsible for retrieving a field and its identifier are determined based on the field's value retrieval method. This ensures that when the module receives a retrieval command from the server, it returns the corresponding field value, allowing the server to obtain the relevant field information. Therefore, by defining the field's value retrieval method, this application reduces the dependency between data retrieval modules, thereby reducing business coupling and minimizing the possibility of errors during approval form development.
[0072] Based on the above embodiments, in some embodiments, the module includes a service database, which stores active terminal identification information; the method further includes:
[0073] Send a data read instruction to the source terminal corresponding to the source terminal identification information to indicate the value of the field, so that the source terminal returns the field value after receiving the data read instruction;
[0074] The field value of the field is stored in the business database.
[0075] In this application, module identification information corresponding to the field value retrieval method is determined, and the module used for field value retrieval is determined based on this module identification information. This module includes the source terminal corresponding to the business approval request, the business database, and other source terminals with default data interfaces. Specifically, when the field value retrieval method is to call the default interface, module identification information is generated and sent to the source terminal corresponding to the business approval request and / or other source terminals with default data interfaces according to the fields required by the approval form. This allows the source terminal to respond to the corresponding module identification information and return the field value of the corresponding field.
[0076] In this embodiment, the business database stores field information and source terminal identification information corresponding to the source terminal used to retrieve the field information. Optionally, the server sends a data read instruction to the source terminal identification information to obtain at least one field value related to the field, so as to store the field and its field value in the business database. Therefore, when the field value is retrieved by calling a custom interface, a corresponding value retrieval instruction is sent to the business database according to the identification information corresponding to the business database, which allows the field value to be retrieved from the business database. For example, in the approval process of organizational business, for the "Transfer to Department" field in the approval form, the server sends a data read instruction to the source terminal of the corresponding source terminal identification information stored in the business database, so that the source terminal returns field values such as "Department A", "Department B", and "Department C" in response to the instruction. The server stores the "Transfer to Department" field and the above field values in the business database. In this way, when the business database receives a value retrieval instruction for the "Transfer to Department" field, it retrieves "Department A", "Department B", and "Department C" to determine the field value of the "Transfer to Department" field as "Department A" in response to the user's selection operation of the "Department A" field value.
[0077] S202. Synchronize the field information to the field library, which is used to indicate the mapping relationship between the field information.
[0078] In this application, a field library is created as the foundation for the tooling of the approval process. The field library indicates the mapping relationship between various fields and their values in a form. For example, in an approval form for organizational business, the "Transfer-in Department" field and its value are associated with the "Position" field and its value. This allows, for methods such as calling a custom interface, when the value of the "Transfer-in Department" field is "Department A," the value of the "Position" field to adaptively change to "Position a" and "Position b," which are related to "Department A." Simultaneously, a synchronous mechanism for adding, deleting, and modifying data is established, enabling the monitoring and modification of field information.
[0079] S203. Using the mapping relationship, the field information is associated with the form template to obtain the approval form. The form template is generated by preset form configuration information and approval terminal configuration information.
[0080] See also in this application. Figure 4a This is a schematic diagram illustrating the form template parameter configuration provided in this application embodiment. A form template related to the business approval request is retrieved from the template library. The template information includes a template identifier, template name, template description, and template logo. This form template consists of form configuration information and approval terminal configuration information (i.e.,...). Figure 4a The form configuration information (including field attributes, related controls, and field value retrieval methods) is generated. For example, see [link to documentation]. Figure 4b This is a schematic diagram illustrating the configuration of system fields provided in this application embodiment. When the field type is a system field, the field attribute information includes the field name, field keyword, field alias, field category, editing attributes (such as read-only and editable), status (such as enabled, disabled, and enabled but not disabled; enabled means the field value is automatically filled into the approval form, enabled but not disabled means the field value is in the approval form by default and cannot be changed to disabled, for example, the "leave duration" field in the leave approval form), whether it can be used as a branch condition, and visibility (such as hidden and shown; showing includes showing when some fields have field values, showing when some fields have selected field values, and showing by default). When the field type is a system field, the field attribute information includes status (such as disabled), visibility (such as shown), and whether it can be used as a branch condition (such as not allowed as a branch condition).
[0081] Therefore, by associating the field information with the form template according to the field attribute information and the mapping relationship between the field information, the approval form is generated. This ensures that the values of multiple fields in the approval form can be correctly matched, enabling the rapid construction of the approval template and the accurate display of the field information in the approval form, thus realizing the visual display of the approval form.
[0082] S204. Send the approval form to the target terminal corresponding to the approval terminal configuration information.
[0083] In some embodiments, sending the approval form to a target terminal corresponding to the approval terminal configuration information includes:
[0084] Determine the approval terminal configuration information, which includes target terminal identification information corresponding to the target terminal;
[0085] The approval forms are grouped according to the listening fields obtained by at least one of the target terminals, so that the grouped approval forms can be sent to the corresponding target terminals.
[0086] In this application, as Figure 4a As shown, the landing configuration information (i.e., approval terminal configuration information) includes receiving fields, the receiving interface (i.e., the target terminal used to receive the approval form), and its identification information. At the end of the approval process, the server queries the approval terminal configuration information configured in the approval form, determines the target terminal corresponding to the approval terminal configuration information, groups the fields and field values in the approval form according to the listening fields obtained by the target terminal, and then calls the interface corresponding to the target terminal to send the corresponding approval form to the target terminal. For example, as shown... Figure 4aAs shown, the server generates approval forms corresponding to leave and payroll transactions. Upon completion of the approval process, based on the terminal configuration information for the leave and payroll transactions in the approval forms, it determines the first target terminal related to the leave and payroll transaction and the second target terminal related to the payroll transaction. Then, when the server receives a listening field such as leave time from the first target terminal, it extracts the corresponding field information from the approved form and generates a first approval form, which is then sent to the first target terminal. Similarly, when the server receives a listening field such as salary from the second target terminal, it extracts the corresponding field information from the approved form and generates a second approval form, which is then sent to the second target terminal. Furthermore, the one-to-one correspondence between target terminals and their identifiers ensures the uniqueness of the terminals and their identifiers, improving the accuracy of approval form delivery and significantly reducing the possibility of sending errors.
[0087] The approval processing method provided in this application embodiment, in response to a business approval request, obtains field information related to the business approval request, and then synchronizes the field information to a field library. The field library is used to indicate the mapping relationship between the field information. Using the mapping relationship, the field information is associated with a form template to obtain an approval form. The form template is generated from preset form configuration information and approval terminal configuration information. The approval form is sent to the target terminal corresponding to the approval terminal configuration information. In this way, by synchronizing the field library, template configuration, and landing configuration, the approval process is toolified, and the configuration of the approval form and form landing is quickly completed. This solves the technical problem of low overall efficiency in the existing approval process, thereby enabling rapid and timely response to user needs and improving the execution efficiency of the approval process.
[0088] In some embodiments, the step of using the mapping relationship to associate the field information with a form template to obtain an approval form includes:
[0089] The form configuration information is determined, which includes field attribute information of the fields. The field attribute information is used to indicate the display and editing of the fields and their values on the approval form.
[0090] Based on the form configuration information, the approval form is displayed, and the approval form displays multiple editable controls corresponding to the field values respectively;
[0091] In response to a triggering operation of the editable control, the field value corresponding to the editable control is edited.
[0092] In this embodiment, field attribute information is used to indicate the display and editing of fields and their values on the approval form. For example, the "Applicant" field is used. The "Applicant" field retrieves its value by calling a default interface. Its control is a text control. The field's editability is read-only, its visibility is displayed, its status is enabled and cannot be disabled, and it can be used as a branch condition. Therefore, the value of the "Applicant" field is displayed in the generated approval form according to the above information. Similarly, the "Salary" field is used as an example. The "Salary" field retrieves its value through user input. Its control is a text control. The field's editability is editable, its visibility is displayed when a value is available, its status is enabled, and it cannot be used as a branch condition. Thus, the value of the "Salary" field is displayed in the generated approval form according to the above information. At this time, the control is in an editable state, so that after the user initiates the approval process, the field value entered by the user can be obtained in response to the triggering operation of the control in the approval form.
[0093] In some embodiments, obtaining the field information related to the business approval request further includes:
[0094] Retrieves the value of the specified field corresponding to the target field;
[0095] Calculate the value of the target field based on the value of the specified field.
[0096] In this embodiment, since some fields cannot be directly obtained and require calculation from multiple field values, one or more specified fields constituting the target field are determined so that the target field value is calculated when the value of the specified field is obtained. For example, in the approval process of leave applications, to obtain the value of the "Leave Duration" field, the values of the "Leave Start Time" and "Leave End Time" fields need to be obtained in advance. Thus, the approval template can have editable controls for the "Leave Start Time" and "Leave End Time" fields. By triggering these controls, the corresponding field values input by the user are obtained, and the value of the "Leave Duration" field is calculated based on the values of the "Leave Start Time" and "Leave End Time" fields. Therefore, this embodiment improves the efficiency of the approval process by flexibly obtaining field values.
[0097] In some embodiments, obtaining the field information related to the business approval request further includes:
[0098] When the data structure of the field value returned by the module is a preset basic structure, the field value is formatted; or,
[0099] When the data structure of the field value returned by the module is a preset specific scenario structure, an electronic signature corresponding to the field value is generated.
[0100] Currently, the inconsistent data standards and data structure formats returned by the source terminal interfaces increase the complexity of approval parsing. Therefore, this embodiment processes the data formats for both basic and scenario-specific data structures separately, ensuring the data structure of the field values returned by the source terminal is universal, reducing processing errors, and improving the efficiency of approval form creation. For example, when the data structure of the field values returned by the module is a preset basic structure, if the field value is a date, then the field value is formatted as a date; if the field value is an attachment or image, then the field value is formatted as an attachment (i.e., attachmentformat); if the field value is a single-selection personnel, multiple-selection personnel, or applicant, then the field value is formatted as personnel data (i.e., staffformat); if the field value is a department, then the field value is formatted as department information (i.e., departmentformat); if the field value is an address, then the field value is formatted as address information (i.e., addressformat); if the field value is a telephone number, then the field value is formatted as telephone information (i.e., telephone number format). The format is as follows: if the field value is a certificate, then the field value is formatted as certificate information (certificateformat); if the field value is a bank card, then the field value is formatted as bank information (bankformat); if the field value is job title, position, work location, cost center, event type, event reason, radio button, checkbox, numeric input box, radio button, checkbox, then the field value is formatted as selectbox information (selectboxformat); if the field value is plain text, then the field value is formatted as text; if the field value is job level, then the field value is formatted as job level information (titleformat).
[0101] For example, taking payroll and organizational business as business types as an example, when the source terminal corresponding to the payroll and organizational business detects a modified or added field, it sends a business approval request to the server, causing the server to respond to the business approval request and obtain the relevant field information. Furthermore, the fields related to the payroll and organizational business are determined to include the applicant, salary, current department, receiving department, responsibilities, backup, leave start time, leave end time, and leave duration. The "Applicant" field uses a default API call, its control is a text control, it is read-only, enabled and cannot be disabled, and can be used as a branching condition. The "Salary" field uses user input, its control is a text control, it is editable, enabled, and cannot be used as a branching condition. The "Current Department" field uses a default API call, its control is a text control, it is read-only, enabled and cannot be disabled, and can be used as a branching condition. The "Transfer Department" field uses a custom API call (e.g., searching for a department), its control is a dropdown list, it is editable, enabled and cannot be disabled, and can be used as a branching condition. The "Responsibilities" field uses a custom API call (e.g., searching for responsibilities). The fields listed are: "Leave Start Time", "Leave End Time", and "Leave Duration". The "Leave Duration" field is a dropdown control, editable, disabled, and can be used as a branch condition. The "Leave Duration" field uses a custom interface (e.g., a search function), is a text control, editable, disabled, and cannot be used as a branch condition. The "Leave Start Time" field uses a date control, editable, disabled, and cannot be used as a branch condition.
[0102] In addition, the approval form also includes approval terminal configuration information. For the target terminals corresponding to organizational business, the approval form sets up listening fields such as applicant, receiving department, and responsibilities, as well as target terminal identification information. For the target terminals corresponding to payroll business, the approval form sets up listening fields such as applicant and salary, as well as target terminal identification information. The approval form also configures the source terminal identification information corresponding to the method of calling custom interfaces, such as the identification information of the module used to store the "receiving department" field in the business database.
[0103] Thus, based on the form configuration information generated from the aforementioned field value retrieval methods and field attribute information, the corresponding field information is obtained, and an approval form is generated. For example, an editable control corresponding to the "Transfer-in Department" field is displayed in the approval form. In response to the triggering operation of this control, the field value of the "Transfer-in Department" field selected by the user is obtained. Furthermore, when the user initiates the approval process on the user terminal, the approval form is invoked, and the user inputs and selects the corresponding field values for approval. At the end of the approval process, based on the approval terminal configuration information configured in the approval form, the field information related to payroll business in the approval form is sent to the target terminal corresponding to the payroll business, and the field information related to organizational business in the approval form is sent to the target terminal corresponding to the organizational business. In addition, the approval form also includes approval fields, which are added during the user-initiated approval stage, such as adding emergency contact information to a leave application approval form.
[0104] Figure 5 This is a schematic diagram of an approval processing device provided in an embodiment of this application. The approval processing device 300 includes:
[0105] The approval request module 301 is used to respond to a business approval request and obtain field information related to the business approval request.
[0106] The field library processing module 302 is used to synchronize the field information to the field library, which is used to indicate the mapping relationship between the various field information.
[0107] The approval form creation module 303 is used to associate the field information with the form template using the mapping relationship to obtain the approval form. The form template is generated by preset form configuration information and approval terminal configuration information.
[0108] The approval form sending module 304 is used to send the approval form to the target terminal corresponding to the approval terminal configuration information.
[0109] In some embodiments, the field information includes fields and field values, and the approval request module 301 includes:
[0110] The field type determination unit is used to determine the fields used to define the approval form and the field types of the fields based on the business information carried when the business approval request is sent. The field types include system fields and user fields.
[0111] The field value determination unit is used to determine the field value determination method of the field and the module identification information corresponding to the field value determination method based on the field type.
[0112] The field value retrieval unit is used to send a value retrieval instruction to the module corresponding to the module identification information, so that the module returns the field value after receiving the value retrieval instruction.
[0113] In some embodiments, the approval request module 301 further includes:
[0114] A data formatting processing unit is used to perform data formatting processing on the field values when the data structure of the field values returned by the module is a preset basic structure; or,
[0115] An electronic signature generation unit is used to generate an electronic signature corresponding to the field value when the data structure of the field value returned by the module is a preset specific scenario structure.
[0116] In some embodiments, the module includes a business database that stores active terminal identification information; the approval processing device 300 further includes:
[0117] A field value reading unit is used to send a data reading instruction to the source terminal corresponding to the source terminal identification information, which is used to indicate the value of the field, so that the source terminal returns the field value after receiving the data reading instruction;
[0118] A field value storage unit is used to store the field value of the field in the business database.
[0119] In some embodiments, the approval form sending module 304 includes:
[0120] An approval terminal configuration information determining unit is used to determine approval terminal configuration information, wherein the approval terminal configuration information includes target terminal identification information corresponding to the target terminal;
[0121] The approval form grouping and sending unit is used to group the approval form according to the listening field obtained by at least one of the target terminals, so as to send the grouped approval forms to the corresponding target terminals.
[0122] In some embodiments, the approval form creation module 303 includes:
[0123] A form configuration information determining unit is used to determine form configuration information, which includes field attribute information of fields, and the field attribute information is used to indicate the display and editing of the fields and their values on the approval form;
[0124] An approval form display unit is used to display the approval form based on the form configuration information. The approval form displays multiple editable controls corresponding to the field values.
[0125] The field value editing unit is used to edit the field value corresponding to the editable control in response to the trigger operation of the editable control.
[0126] In some embodiments, the approval request module 301 further includes:
[0127] The specified field value retrieval unit is used to retrieve the field value of the specified field corresponding to the target field;
[0128] The target field value calculation unit is used to calculate the field value of the target field based on the field value of the specified field.
[0129] The apparatus in this application embodiment can execute the method provided in this application embodiment, and the implementation principle is similar. The actions performed by each module in the apparatus of each embodiment of this application correspond to the steps in the method of each embodiment of this application. For detailed functional descriptions of each module of the apparatus, please refer to the descriptions in the corresponding methods shown above, which will not be repeated here.
[0130] This application provides an electronic device, including a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of the approval processing method. Compared with related technologies, it can achieve the following: by synchronizing the field library, template configuration, and landing configuration, the approval process is tool-based, and the configuration of approval forms and form landing is quickly completed. This solves the technical problem of low overall efficiency in existing approval processes, thereby enabling rapid and timely response to user needs and improving the execution efficiency of the approval process.
[0131] In one alternative embodiment, an electronic device is provided, such as Figure 6 As shown, Figure 6The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.
[0132] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.
[0133] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0134] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation herein.
[0135] The memory 4003 stores computer programs that execute embodiments of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the computer programs stored in the memory 4003 to implement the steps shown in the foregoing method embodiments.
[0136] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps and corresponding content of the aforementioned method embodiments.
[0137] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.
[0138] The terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the figures or text.
[0139] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.
[0140] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.
Claims
1. An approval processing method, characterized in that, include: In response to a business approval request, obtain the field information related to the business approval request; The field information includes the fields and the field values of the fields; The field information is synchronized to the field database, which is used to indicate the mapping relationship between the field information; Using the mapping relationship, the field information is associated with the form template to obtain the approval form. The form template is generated from preset form configuration information and approval terminal configuration information. Send the approval form to the target terminal that corresponds to the approval terminal configuration information; Sending the approval form to the target terminal corresponding to the approval terminal configuration information includes: Determine the approval terminal configuration information, which includes target terminal identification information corresponding to the target terminal; The approval forms are grouped according to the listening fields obtained by at least one of the target terminals, so that the grouped approval forms can be sent to the corresponding target terminals.
2. The approval processing method according to claim 1, characterized in that, The step of obtaining field information related to the business approval request includes: Based on the business information carried when the business approval request is sent, determine the fields used to define the approval form and the field types of the fields, wherein the field types include system fields and user fields; Based on the field type, determine the field value retrieval method and the corresponding module identification information; Send a value retrieval instruction to the module corresponding to the module identification information to indicate the value of the field, so that the module returns the field value after receiving the value retrieval instruction.
3. The approval processing method according to claim 2, characterized in that, The step of obtaining the field information related to the business approval request also includes: When the data structure of the field value returned by the module is a preset basic structure, the field value is formatted; or, When the data structure of the field value returned by the module is a preset specific scenario structure, an electronic signature corresponding to the field value is generated.
4. The approval processing method according to claim 2, characterized in that, The module includes a service database, which stores active terminal identification information; the method further includes: Send a data read instruction to the source terminal corresponding to the source terminal identification information to indicate the value of the field, so that the source terminal returns the field value after receiving the data read instruction; The field value of the field is stored in the business database.
5. The approval processing method according to claim 1, characterized in that, The step of using the mapping relationship to associate the field information with the form template to obtain the approval form includes: The form configuration information is determined, which includes field attribute information of the fields. The field attribute information is used to indicate the display and editing of the fields and their values on the approval form. Based on the form configuration information, the approval form is displayed, and the approval form displays multiple editable controls corresponding to the field values respectively; In response to a triggering operation of the editable control, the field value corresponding to the editable control is edited.
6. The approval processing method according to claim 4 or 5, characterized in that, The step of obtaining the field information related to the business approval request also includes: Retrieves the value of the specified field corresponding to the target field; Calculate the value of the target field based on the value of the specified field.
7. An approval processing device, characterized in that, include: The approval request module is used to respond to a business approval request and obtain field information related to the business approval request. The field information includes the fields and the field values of the fields; A field library processing module is used to synchronize the field information to a field library, wherein the field library is used to indicate the mapping relationship between the various field information items; The approval form creation module is used to associate the field information with the form template using the mapping relationship to obtain the approval form. The form template is generated by preset form configuration information and approval terminal configuration information. An approval form sending module is used to send the approval form to a target terminal corresponding to the approval terminal configuration information; The approval form sending module is further configured to determine approval terminal configuration information, which includes target terminal identification information corresponding to the target terminal; and to group the approval forms according to the listening fields obtained by at least one of the target terminals, so as to send the grouped approval forms to the corresponding target terminals.
8. An approval processing system, characterized in that, include: The target terminal and server, wherein the server includes a field library; The server is configured as follows: Receive business approval requests; In response to the business approval request, obtain the field information related to the business approval request; The field information includes the fields and the field values of the fields; The field information is synchronized to the field database, which is used to indicate the mapping relationship between the various field information items; Using the mapping relationship, the field information is associated with the form template to obtain the approval form. The form template is generated from preset form configuration information and approval terminal configuration information. Send the approval form to the target terminal that corresponds to the approval terminal configuration information; The server is configured to determine approval terminal configuration information, which includes target terminal identification information corresponding to the target terminal; and to group the approval forms according to the listening fields obtained by at least one of the target terminals, so as to send the grouped approval forms to the corresponding target terminals. The target terminal is configured to receive the approval form.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the approval processing method according to any one of claims 1-6.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the approval processing method according to any one of claims 1-6.
11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the approval processing method according to any one of claims 1-6.