Approval process generation method and device, equipment and medium

Abstract

The application provides an approval process generation method and device, equipment and medium, relates to the technical field of data processing, and can be applied to the financial field. The method of the application constructs a modular approval template library, abstracts the approval process nodes into reusable node information blocks, and stores them in the modular approval template library, avoiding the redundant operation of repeatedly developing approval nodes for each business type, so that the subsequent process construction can directly call the existing node information blocks for combination, improving the generation efficiency of the approval process. By analyzing the business approval process construction instruction, the matching node information block is automatically selected and combined, and the rapid automatic generation of the business approval process template is realized. By automatically configuring the approval process requirement data to each node information block of the business approval process template based on the data mapping table, the rapid generation of the business approval process instance is realized, and the generation efficiency of the approval process is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to an approval process generation method, apparatus, equipment and medium. Background Technology

[0002] As enterprises deepen their digital transformation, the automation and intelligentization of business approval processes have become key to improving organizational operational efficiency. Existing approval workflow systems are important tools for the internal business approval systems of many financial leasing companies, adapting to the basic business development needs of most companies through visual approval interfaces and task allocation mechanisms.

[0003] However, with the frequent iterations and diversified development of financial leasing business, the existing approval workflow system has exposed obvious technical deficiencies. At the business level, financial leasing business involves multiple professional stages such as lessee qualification review, leased asset valuation, guarantee scheme design, and fund disbursement review. Each stage requires attention to different business fields, such as lessee registered capital, leased asset book value, and guarantee coverage ratio. In the medical leasing business scenario, special fields such as medical equipment registration certificate number, radiation safety permit, and departmental usage plan are also involved.

[0004] Existing approval workflow systems are typically customized for each business type, defining approval nodes and form fields through hard coding. This results in highly customized business approval processes, failing to achieve flexible configuration and real-time effectiveness mechanisms for various data structures. Consequently, they lead to repetitive code duplication and system bloat, making it impossible to quickly adapt to changing business approval needs.

[0005] Therefore, how to improve the efficiency of approval process generation and adapt to the business approval needs in business scenarios such as financial leasing and medical leasing has become an urgent technical problem to be solved. Summary of the Invention

[0006] This application provides a method, apparatus, device, and medium for generating approval processes, aiming to solve the technical problems of existing approval process generation technologies, which are highly customized, fail to achieve flexible configuration and real-time activation mechanisms for various data structures, resulting in repetitive code copying and system bloat, and thus low efficiency in generating approval processes.

[0007] Firstly, this application provides a method for generating an approval process, the method comprising the following steps: Construct a modular approval template library, which includes node information blocks for at least one approval process node; Based on the business approval process construction instructions for the target business type, at least one node information block that matches the target business type is called from the modular approval template library and combined and arranged to generate a business approval process template. Based on the approval process requirement data uploaded by the client, the node data of each node information block in the business approval process template is configured to generate a business approval process instance corresponding to the target business type.

[0008] Secondly, this application also provides an approval process generation device, the approval process generation device comprising: The template library construction module is used to build a modular approval template library, which includes a node information block of at least one approval process node. The process template generation module is used to construct a business approval process based on the target business type. It calls at least one node information block that matches the target business type from the modular approval template library and combines and arranges them to generate a business approval process template. The approval process generation module is used to configure the node data of each node information block in the business approval process template based on the approval process requirement data uploaded by the client, and generate a business approval process instance corresponding to the target business type.

[0009] Thirdly, this application also provides a computer device, the computer device including a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, it implements the steps of the approval process generation method described above.

[0010] Fourthly, this application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the approval process generation method described above.

[0011] This application provides a method, apparatus, computer device, and storage medium for generating approval processes. The method constructs a modular approval template library, abstracting approval process nodes into reusable node information blocks and centrally storing them in the library. This avoids redundant operations of repeatedly developing approval nodes for each business type, allowing subsequent process construction to directly call existing node information blocks for combination, thus improving the efficiency of approval process generation. By parsing business approval process construction instructions, it automatically filters and matches node information blocks and combines and arranges them, replacing the manual process design and code development under traditional hard-coding methods, achieving rapid and automatic generation of business approval process templates. By automatically configuring approval process requirement data to each node information block of the business approval process template based on a data mapping table, it achieves rapid generation of business approval process instances, further improving the efficiency of approval process generation. Attached Figure Description

[0012] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is a schematic diagram of an application environment for an approval process generation method according to an embodiment of the present invention; Figure 2 A flowchart illustrating a first embodiment of an approval process generation method provided in this application; Figure 3 A flowchart illustrating a second embodiment of an approval process generation method provided in this application; Figure 4 A flowchart illustrating a third embodiment of an approval process generation method provided in this application; Figure 5 A schematic diagram of an approval process management architecture provided for this application; Figure 6 This is a schematic diagram of the structure of an embodiment of an approval process generation device provided in this application. Figure 7 This is a schematic block diagram of the structure of a computer device provided in an embodiment of this application.

[0014] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0015] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0016] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0017] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] The approval process generation method provided in this embodiment of the invention can be applied to, for example... Figure 1 In this application environment, the client communicates with the server via a network. The server can build a modular approval template library, which includes node information blocks for at least one approval process node. Based on the business approval process construction instructions for the target business type, the server calls at least one node information block from the modular approval template library that matches the target business type and combines and arranges it to generate a business approval process template. Based on the approval process requirement data uploaded by the client, the server configures the node data of each node information block in the business approval process template to generate a business approval process instance corresponding to the target business type.

[0020] This invention addresses the technical problems of inefficient approval process generation in existing financial leasing and medical leasing scenarios, which suffer from severe customization, lack of flexible configuration and real-time activation mechanisms for various data structures, leading to repetitive code duplication and system bloat. A modular approval template library is constructed, abstracting approval process nodes into reusable node information blocks and centrally storing them. This avoids redundant development of approval nodes for each business type, allowing subsequent process construction to directly call existing node information blocks for combination, thus improving approval process generation efficiency. By parsing business approval process construction instructions, the invention automatically filters and matches node information blocks and arranges them, replacing the traditional hard-coded manual process design and code development, achieving rapid and automatic generation of business approval process templates. Furthermore, by automatically configuring approval process requirement data to each node information block of the business approval process template based on a data mapping table, the invention enables rapid generation of business approval process instances, further improving approval process generation efficiency.

[0021] The client can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The server can be implemented using a standalone server or a server cluster consisting of multiple servers. The invention will now be described in detail through specific embodiments.

[0022] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of an approval process generation method provided in this application.

[0023] In one embodiment, the approval process generation method provided in this application can be applied to application scenarios for constructing business approval processes, such as procurement business scenarios, leasing business scenarios, and product sales business scenarios. For ease of understanding, this application embodiment uses a leasing business scenario as an example to describe each step of the approval process generation method in detail.

[0024] like Figure 2 As shown, the approval process generation method includes steps S101 to S103.

[0025] S101. Construct a modular approval template library, wherein the modular approval template library includes at least one node information block of an approval process node.

[0026] In one embodiment, in leasing business scenarios such as medical equipment leasing, vehicle leasing, and financial leasing, and in accordance with the needs of leasing business development, all leasing business-related processes, such as credit granting, contract processing, asset processing, and financial processing, are managed, and a modular approval template library covering different business approval processes involved in leasing business is developed.

[0027] Further, obtain approval process data for at least one business process; perform structured parsing on the approval process data to extract approval process nodes corresponding to at least one business type; modularize each approval process node to obtain at least one node information block; store the node information block in a preset database to obtain the modular approval template library.

[0028] In one embodiment, the approval process data can be historical approval process data for leasing transactions. Approval process data for different types of business processes can be read from a historical database, such as credit approval process data, contract approval process data, asset approval process data, and financial approval process data.

[0029] The acquired approval process data is structured and parsed to extract approval process nodes corresponding to each business type. For example, in the credit approval process data, nodes such as customer information entry, credit investigation, risk assessment, and credit limit approval can be extracted. In the contract approval process data, nodes such as contract drafting, legal review, business review, financial review, and seal approval can be extracted. In the asset approval process data, nodes such as asset procurement application, supplier evaluation, asset acceptance, and asset warehousing can be extracted. In the financial approval process data, nodes such as payment application, budget verification, fund allocation, and payment can be extracted.

[0030] Understandably, even business approval processes for the same business type may differ due to variations in the business processing steps. Therefore, when extracting approval process nodes, it is not only necessary to identify and extract the key approval process nodes for each business type, but also to identify and extract all nodes involved in the approval process so that the modular approval template library can cover all approval process nodes involved in the entire process.

[0031] In one embodiment, the approval process nodes are mapped as hierarchical structural units; the node attributes of each structural unit are configured, and the node information block is generated.

[0032] In one embodiment, the extracted approval process nodes can be modularized, converting each node into a standardized node information block. Specifically, the approval process nodes are mapped to hierarchical structural units. For example, the "customer information entry node" can be mapped to a hierarchical structural unit, which may contain sub-levels such as a basic information layer, a contact information layer, and a financial information layer, with each sub-level further subdivided into specific field units.

[0033] For node information blocks, node attributes can be configured, including required attributes and optional attributes. Required attributes include field ID, field name, and data type (dataType); optional attributes include groupId, field edit type (editType), readonly control, visibleNode for visible positions, and editNode for editable positions.

[0034] Considering the complexity and diversity of node attribute configuration rules, MongoDB, a NoSQL database that supports JSON data format, was chosen to store node information blocks containing node attributes, resulting in a modular approval template library. The stored node information blocks include metadata information such as section identifier, information block identifier, version number, and release status. When business adjustments and changes occur later, if a field needs to be added or deleted, only the corresponding node attribute needs to be modified and all parties notified to generate a new node information block, without requiring complex database structure changes.

[0035] In one specific embodiment, during the modular approval template library construction phase, template configuration personnel complete the configuration of node information block attributes, including setting the information block id to a String type, configuring the elements collection (including required and optional attributes), setting the elementsGroups submodule collection to support nested structures, configuring the codemap enumeration value collection, layoutStyle rendering style, and validateRules regular expression validation rules, etc. After the node attribute configuration is completed, it is saved and submitted for review. Configuration rule administrators review it, and if there are problems such as non-standard field naming, inappropriate data type selection, or logical errors in validation rules, it is rejected for modification; otherwise, it is approved. After all reviews are approved, system operators can release it at an appropriate time, and the released node information blocks are stored in a MongoDB database.

[0036] This embodiment achieves standardization, modularization, and reusability of approval process nodes by structuring and parsing historical approval process data of leasing business, extracting and mapping it into hierarchical node information blocks, configuring node attributes including mandatory and optional attributes, and using database storage to support flexible expansion. This significantly improves the construction efficiency of the approval process template library and the response speed of subsequent business adjustments.

[0037] S102. A business approval process construction instruction based on the target business type is used to call at least one node information block that matches the target business type from the modular approval template library for combination and arrangement to generate a business approval process template.

[0038] Business personnel can initiate business approval process construction commands through the client. After receiving the command, the server can use low-code technology to call one or more corresponding node information blocks from the modular approval template library. Then, the server combines and arranges the called node information blocks, determines the execution order of each node information block, configures the flow conditions between node information blocks, and establishes the data transfer relationship between node information blocks. This forms a business approval process template that includes process name, module type, module sub-items, and personnel permissions. The template can include information such as process identifier, process name, node information block set, node execution order, flow rules, version number, and status identifier. According to the leasing business policy, differentiated module combinations are configured for different processes such as credit, contract, asset, and finance. Each module is bound to the corresponding approval position permissions to achieve dynamic display and flexible configuration of approval content according to position, ultimately generating the business approval process template.

[0039] Further, the business approval process construction instructions are parsed to obtain the business scenario parameters corresponding to the target business type; the business scenario parameters are converted into business feature vectors, and a set of node information blocks with the highest matching degree with the business feature vectors is selected from the modular approval template library, wherein the set of node information blocks includes at least one node information block; the node information blocks in the set of node information blocks are combined and arranged to generate the business approval process template.

[0040] In one embodiment, after receiving a business approval process construction instruction initiated by the client, the server parses the instruction to obtain the business scenario parameters corresponding to the target business type. These business scenario parameters are a multi-dimensional set of parameters related to the target business type, including dimensions such as type parameters, scale parameters, time limit parameters, subject parameters, guarantee parameters, region parameters, and industry parameters.

[0041] The business scenario parameters are converted into business feature vectors. Specifically, the business scenario parameters undergo data cleaning and standardization. The standardized parameters are then encoded to obtain the corresponding business feature vectors. Generally, if the business scenario parameters include multi-dimensional parameters (such as business type identifier, amount, term, payment method, etc.), each dimension parameter is encoded separately. For example, string identifier parameters are encoded and mapped to numerical values ​​or one-hot vectors; numerical range parameters are normalized and mapped to a standard numerical range; enumerated option parameters are encoded by sequence number or embedding; and Boolean flag parameters are directly mapped to 0 or 1 values. Then, the encoded results of each dimension parameter are concatenated in a fixed order, and the concatenated vector is normalized to form the business feature vector.

[0042] Similarly, for each node information block stored in the modular approval template library, feature vectorization can be performed to extract the attribute features of each node information block, including applicable business type features, adapted scale range features, adapted time period range features, subject requirement features, guarantee requirement features, regional adaptation features, industry adaptation features, etc. Each attribute feature is encoded into numerical form and concatenated to form a node feature vector.

[0043] Next, the similarity between the business feature vector and the feature vectors of each node is calculated. Specifically, the similarity calculation can use distance metrics in vector space, calculating the cosine similarity or Euclidean distance between two vectors to obtain a matching score. The higher the matching score, the better the fit between the node information block and the business scenario parameters. The node information blocks are then sorted in descending order according to the matching score, and the node information blocks with the highest scores are selected to form a set of node information blocks.

[0044] The node information blocks in the node information block set are combined and arranged. Specifically, during the arrangement process, the pre-dependency attributes and post-trigger attributes of each node information block are analyzed, a node dependency graph is constructed, loops are detected and eliminated, and the execution order of nodes without loops is determined. Flow conditions between node information blocks are configured, and flow condition expressions are set for the connection edges between adjacent node information blocks. These expressions are defined based on factors such as the output status of upstream nodes, business rule judgments, and human decision-making results. For example, if the age limit in the technology assessment information block exceeds the threshold or is marked as yes, the process is transferred to a special risk assessment branch; if the expected risk value in the risk analysis information block is greater than or equal to the risk threshold, an extended warranty or adjustment of the guarantee ratio is mandatory; if the rating in the guarantee assessment information block is lower than the standard level, the margin ratio requirement is increased or a third-party guarantee is introduced.

[0045] The orchestration results are encapsulated into a business approval process template. The generated business approval process template can include business type, process name, module type combination, version number, and personnel permission configuration corresponding to each node information block.

[0046] This embodiment obtains business scenario parameters by parsing the business approval process construction instructions and converts them into business feature vectors. Based on vector similarity calculation, it intelligently selects the set of node information blocks with the highest matching degree from the modular approval template library. Then, through dependency analysis and flow condition configuration, it realizes the automated combination and arrangement of node information blocks, replacing the manual process design and code development under the traditional hard coding method. It realizes the rapid automatic generation of business approval process templates and dynamic display by position, which significantly improves the construction efficiency and flexible adaptability of the approval process.

[0047] S103. Based on the approval process requirement data uploaded by the client, configure the node data of each node information block in the business approval process template, and generate a business approval process instance corresponding to the target business type.

[0048] In one embodiment, the server receives approval process requirement data uploaded by the client. This approval process requirement data includes a set of business data related to the target business type. For example, in a lease approval process, the approval process requirement data may include business data such as basic project information, lessee information, technical parameter information, scheme information, and usage plan information.

[0049] The approval process requirement data is parsed to extract the identifier, value, and data type of each data field. Simultaneously, the set of node information blocks in the business approval process template is traversed to obtain the data requirement definition for each node information block. Based on the preset mapping rules in the business approval process template, a mapping relationship is established between the approval process requirement data and the node information blocks, determining the target node information blocks and target field positions where each data field in the approval process requirement data should be written.

[0050] Furthermore, based on the preset data mapping table in the business approval process template, node data for data mapping is extracted from the approval process requirement data; based on the data mapping table, the node data is written into the corresponding node information block to generate the business approval process instance.

[0051] In one embodiment, a preset data mapping table is obtained from the business approval process template. Based on this preset data mapping table, the server extracts node data for data mapping from the approval process requirement data. This data mapping table defines the mapping relationship between source data fields in the approval process requirement data and target data fields in the node information blocks.

[0052] For example, a data mapping table can be organized in the form of entries. Each mapping rule includes: source field path, which identifies the location of the data field in the approval process requirement data; target node identifier, which identifies the node information block where the data should be written; target field identifier, which identifies the specific field within the node information block where the data should be written; data transformation rule, which defines the transformation method from source data to target data, including options such as direct copy, type conversion, format conversion, unit conversion, encoding conversion, and default value filling; and validation rule, which defines the conditional expression for data validity validation.

[0053] Based on the pre-defined data mapping table in the business approval process template, node data for data mapping is extracted from the approval process requirement data uploaded by the client. For example, the qualification level field is mapped to the level path, and the value needs to be standardized from the standard level; the performance field is mapped to the projectHistory path, and the data type is a nested array containing subfields such as name, amount, and status; the model field is mapped to the model path, and it needs to be verified whether it conforms to the standard model naming rules; the lifting weight field is mapped to the maxLiftingCapacity path, and the data type is Number, with the unit being tons, and the numerical reasonableness needs to be verified.

[0054] Based on the data mapping table, the extracted node data is written into the corresponding node information block to generate a business approval process instance. During the writing process, format conversion and validation are performed according to the data type of each field. For example, string-type monetary data is converted into numeric types and standardized to ten thousand yuan; date formats are standardized, converting non-standard formats into standard date formats; completeness checks are performed on required fields to ensure that all required regulatory fields are provided; and value range checks are performed on enumerated fields to ensure that the values ​​are within the allowed range.

[0055] This embodiment automatically extracts and transforms node data from the approval process requirement data uploaded by the client based on a preset data mapping table, and writes the data into the corresponding node information block according to the mapping rules. This realizes the automated configuration and standardized processing of business data to approval process instances, replacing the traditional method of manually entering data node by node, and improving the generation efficiency and data accuracy of business approval process instances.

[0056] This embodiment provides a method for generating approval processes. This method constructs a modular approval template library, abstracting approval process nodes into reusable node information blocks and centrally storing them in the library. This avoids redundant operations of repeatedly developing approval nodes for each business type, allowing subsequent process construction to directly call existing node information blocks for combination, thus improving the efficiency of approval process generation. By parsing business approval process construction instructions, it automatically filters and matches node information blocks and combines and arranges them, replacing the manual process design and code development under the traditional hard-coding method, achieving rapid and automatic generation of business approval process templates. By automatically configuring approval process requirement data to each node information block of the business approval process template based on a data mapping table, it achieves rapid generation of business approval process instances, further improving the efficiency of approval process generation.

[0057] Please refer to Figure 3 , Figure 3 This is a flowchart illustrating a second embodiment of an approval process generation method provided in this application. Figure 3 As shown, based on the above Figure 2 In the illustrated embodiment, after step S103, the method further includes: S201. When it is detected that the node information block stored in the modular approval template library has undergone an attribute change, the business approval process instance associated with the node information block whose attributes have changed is determined.

[0058] S202. Based on the current version identifier of the business approval process instance, perform a version identifier increment operation on the business approval process instance associated with the node information block after attribute change, so as to realize multi-version control management of the business approval process instance.

[0059] In one embodiment, the server can detect the node attributes of a node information block to determine if those attributes have changed. For example, the detection methods for node information blocks can include an active detection mode and a passive notification mode. The active detection mode can periodically scan the node information block metadata in the modular approval template library, comparing the current attribute snapshot with historical attribute snapshots to identify attribute changes. The passive notification mode can directly obtain change information by receiving attribute change submission events initiated by the configuration server.

[0060] Generally, attribute change types may include, but are not limited to: field addition changes, i.e., adding a field definition to the element set of a node information block; field deletion changes, i.e. removing an existing field definition from the element set of a node information block; field attribute modification changes, i.e. modifying the data type, edit type, validation rules, visibility configuration, and editability configuration attributes of an existing field; and node metadata changes, i.e. modifying the version number, release status, and applicable business type range of a node information block.

[0061] In one embodiment, when a change in the attributes of a node information block is detected, the server can obtain the unique identifier of the changed node information block. Based on this unique identifier, it queries the node information block association index table to find all business approval process instances associated with the changed node information block. The association index table records the relationships between node information blocks and business approval process instances, and these relationships can be established when a business approval process instance is generated.

[0062] For each business approval process instance retrieved, an incrementing version identifier operation is performed. The version identifier can be a combination of multiple version numbers (such as a combination of major and minor version numbers) or a single incrementing sequence number. Taking the combination of major and minor version numbers as an example, when performing the version identifier increment calculation, for incrementing the minor version number, the current minor version number value is incremented by one to generate the new version identifier; for incrementing the major version number, the current major version number value is incremented by one and the minor version number is set to zero to generate the new version identifier.

[0063] Specifically, firstly, the server obtains the current version identifier of the business approval process instance, parses the current version identifier, and extracts the version value. Then, it determines the version identifier increment strategy based on the current state of the business approval process instance. Specifically, the increment strategy includes: if the current state of the business approval process instance is creation complete or data completion stage, increment the minor version number while keeping the major version number unchanged; if the current state of the business approval process instance is approval in progress or partially executed stage, increment the major version number and reset the minor version number to zero; if the current state of the business approval process instance is completed, skip the version increment operation, only mark it as a historical archived version, unaffected by current changes. Furthermore, based on this, the corresponding node information block in the business approval process instance can be replaced with the node information block after attribute changes, regenerating a new business approval process instance, and assigning a new version number to the newly generated instance. This new version number can either use the major version number of the completed business approval process instance and increment the minor version number, or it can be reassigned a new version number combining the major and minor version numbers.

[0064] For completed business approval process instances, copy all node information blocks of the current version of the business approval process instance as the base data for the new version. Replace or adapt the node information blocks that reference the changed node information blocks in the new version: if the change is a field addition, add the corresponding field in the new version node instance and mark it as pending, while retaining the already filled data of other fields; if the change is a field deletion, mark the corresponding field as deleted in the new version node instance, retain the field's historical value but set it to invisible; if the change is a field attribute modification, re-parse the field data in the new version node instance according to the new attribute, perform necessary data transformations, and mark the transformation results. Establish the reference relationship between the new version of the business approval process instance and the node information blocks after the attribute change, update the node template identifier of the node information block to point to the changed node information block, and add a version change log entry to the business approval process instance data mapping record to record the change time, changed node information block identifier, change type, old version identifier, and new version identifier. This allows the new version of the business approval process instance to coexist with the old version of the business approval process instance in the database, achieving differentiation and unique identification through the version identifier.

[0065] The above operations enable multi-version control management, allowing multiple version instances to exist simultaneously for the same business approval process. Each version instance evolves independently without affecting others. The server can provide a version query interface to support retrieving specific version instances by version identifier, a version comparison interface to display data differences between adjacent versions, and a version rollback interface to support reverting the current version to a historical version under specific conditions.

[0066] In a specific example, when a change in the attribute of a node information block stored in the modular approval template library is detected, the server automatically triggers a version control management process. Assume the attribute change is in response to the latest released business regulatory guidelines, adding a "confirmation method" field and a "registration status" field to the node information block, and adjusting the data validation rules for the "matching degree" field. At this point, the server first identifies all business approval process instances associated with the node information block whose attributes have changed. Using the node information block association index, it queries three currently executing business approval process instances A, B, and C, which are at different execution stages.

[0067] For business approval process instance A, its current version is V1.2. The server increments the version identifier for this business approval process instance, generating version V1.3. Version V1.3 includes newly added fields for authorization method, registration status, and adjusted data validation rules for the matching degree field. When business approval process instance A is upgraded, the historical data already entered remains unchanged, the newly added fields are marked as pending supplementation, and the server notifies the person in charge of the current approval node to supplement the new field data.

[0068] For business approval process instance B, its current version is V1.1, and it is at the review stage. The server increments the version identifier of this business approval process instance, generating version V1.2. Since business approval process instance B has not yet entered the decision-making stage, after the version upgrade, it is allowed to revert to the data supplementation stage, where the manager can add the new field data and resubmit for review.

[0069] For business approval process instance C, its current version is V1.0, and it has entered the signing stage. Considering that it has been partially implemented, when the server increments the version identifier of business approval process instance C, it generates version V1.1 but marks it as applicable only to subsequent projects. The current project C will continue to be executed according to version V1.0 until completion, ensuring the stability of the effective terms.

[0070] Through the aforementioned multi-version control management mechanism, a smooth transition between changes in business rules and the execution of existing processes can be achieved, which not only meets the timeliness requirements of regulatory compliance but also ensures business continuity and stability.

[0071] This embodiment automatically determines the associated business approval process instance when a change in the node information block attribute is detected, and executes a differentiated version identifier increment strategy based on the current state of the instance. This realizes the coexistence management and independent evolution of new and old version instances, which not only meets the regulatory requirements for timely updates of business rules, but also ensures the continuity and stability of existing process execution, significantly improving the efficiency of version management of approval processes and the flexibility of business adaptation.

[0072] Please refer to Figure 4 , Figure 4 This is a flowchart illustrating a third embodiment of an approval process generation method provided in this application. Figure 4 As shown, based on the above Figure 2 In the illustrated embodiment, after step S103, the method further includes: S301. Upon receiving a business process approval request initiated by the client, obtain the client's job role identifier; S302. Filter the accessible node information blocks and node data of the accessible node information blocks that match the job role identifier from the business approval process instance, generate an instance data view that matches the job role identifier, and send the instance data view to the client for display.

[0073] In one embodiment, upon receiving a project business process approval request initiated by a client, the request is parsed to obtain the job role identifier of the client initiating the request. This job role identifier may include multi-dimensional information such as a department identifier, job level identifier, professional qualification identifier, and special permission identifier. Specifically, the department identifier records the organizational unit to which the client user belongs; the job level identifier records the client user's hierarchical position within the organizational unit; the professional qualification identifier records the professional certification held by the client user; and the special permission identifier records any additional permission markers granted to the client user.

[0074] Based on the obtained business approval process instance identifier, the corresponding business approval process instance is queried from the instance database. Then, the node information blocks within the business approval process instance are traversed, and the permission configuration attributes corresponding to each node information block are extracted. These permission configuration attributes may include, but are not limited to: a set of visible job identifiers, defining the job roles that can view the node information block; a set of editable job identifiers, defining the job roles that can edit the node information block; a set of read-only job identifiers, defining the job roles that can only view and not edit the node information block; and a set of hidden job identifiers, defining the job roles that cannot see the node information block.

[0075] The obtained job role identifiers are matched with the permission configuration attributes of node information blocks to filter accessible node information blocks. Generally, accessibility includes visible and editable, and visible and read-only states. Specifically, if any of the department identifier, job level identifier, or professional qualification identifier in the job role identifier matches an entry in the set of visible job identifiers, the node information block is visible to that job role; if it matches an entry in the set of editable job identifiers, the node information block is editable to that job role; if it matches an entry in the set of read-only job identifiers, the node information block is read-only to that job role; if it matches an entry in the set of hidden job identifiers, or if none of them match the visible set, the node information block is hidden to that job role.

[0076] For each accessible node information block, extract its node data, including but not limited to the current value, data type, and field attributes of each field. Perform permission filtering on the extracted node data. For node information blocks in an editable state, retain all fields and their editing permission configurations; for node information blocks in a read-only state, force the field editing attributes to be read-only and remove the editing control configuration; for fields involving sensitive data, determine whether to display them in anonymized form or completely hide them based on the data hierarchy permissions in the job role identifier.

[0077] Then, based on the accessible node information blocks and their corresponding node data, an instance data view matching the job role identifier is generated, and the instance data view is sent to the client for display. The instance data view can include view metadata, an accessible node set, a process progress indicator, and operation button configurations. Specifically, the view metadata records the instance identifier, view generation time, target job role identifier, etc.; the accessible node set includes the node instance identifier, node name, node status, access permission level (editable or read-only), and field data set for each accessible node information block; the process progress indicator records the overall execution stage of the current instance, the list of completed node identifiers, the list of pending node identifiers, and the currently active node identifiers; the operation button configuration configures available operation buttons based on the node access permission level and operation type, including save, submit, return, transfer, and terminate.

[0078] Understandably, the approval process data uploaded by the client comes from various heterogeneous data sources. Different client systems use different data serialization formats, including JSON and XML. Therefore, the generated instance data view needs to be formatted according to the client's device type to adapt to the client's display requirements. For example, the web client format can use JSON Schema to define the rendering component type of fields, validation rules, and linkage logic; the mobile client format uses a compressed binary protocol to reduce network transmission overhead.

[0079] The instance data view is sent to the client. The transmission process can use an encrypted channel, with end-to-end encryption of sensitive field values. Upon receiving the data, the client parses the instance view data, renders the page framework based on the view metadata, renders the display area for each node based on the set of accessible nodes, renders the status bar based on the progress indicator, and renders the operation bar based on the configured operation buttons.

[0080] In one embodiment, the client display effect can be differentiated according to the access permission level: editable nodes are marked with a highlighted border, and the fields are displayed as interactive input controls; read-only nodes are marked with a gray background, and the fields are displayed as static text or controls in a disabled state; hidden nodes are not displayed in the interface, but their position marks are retained in the process progress indicator.

[0081] This embodiment obtains the client's job role identifier and matches it with the permission configuration attributes of the node information block. It automatically filters the accessible node information blocks and their node data, and then generates a differentiated instance data view that matches the job role identifier. This achieves refined permission control and on-demand display of approval information, so that personnel in different positions can only see the operable or viewable content within their permission scope. This significantly improves the security of the approval process, the efficiency of information display, and the user experience.

[0082] To facilitate understanding of the technical solutions of this application, the embodiments of this application are combined with Figure 5 The diagram illustrating the approval process management architecture provides a detailed explanation of the aforementioned approval process generation method. Figure 5 The approval process management architecture diagram shown includes four components: a configuration module, a database, a server, and a client. The configuration module is used by architecture template configuration personnel and architecture operations personnel to build a modular approval template library and configure business approval process templates. The database uses MongoDB to store configuration rule templates and business data. The server is used for process generation, access control, and version management. The client supports multi-role access, including web and mobile app versions.

[0083] This architecture employs a low-code configuration approach and supports flexible business process construction through a modular template library. The following section provides a detailed description of the technical solution in this embodiment, using a specific application scenario of the financial leasing business approval process.

[0084] First, during the construction of the modular approval template library, the architecture template configuration personnel log in to the configuration terminal and create a modular approval template library for the "financial leasing business" domain. The configuration personnel first define the process type dimension, including business types such as credit granting processes, contract processes, asset processes, and financial processes. For different business types of approval processes, relevant node modules are configured, such as the customer information module, self-investigation module, and credit granting scheme module in the credit granting process. After completing the module configuration, the configuration personnel submit it for review. The configuration rule administrator reviews the module structure integrity, field naming standardization, and validation rule rationality on the review interface. After approval, the configuration personnel publish the module, the module status is updated to "published," and it is stored in the MongoDB module template library.

[0085] In one example, such as Figure 5The configuration attributes of the node information block in the configuration module field template shown are explained as follows: `id` serves as the module identifier, designed as a String type, used for comparison with resource blocks to ensure the uniqueness of the module. `elements` is a collection of elements, containing all elements to be rendered, covering both required and optional attributes. `elementsGroups` is a collection of sub-modules under the resource block, suitable for resource block scenarios with nested sub-modules. For example, in credit approval, the customer basic information module may nest sub-modules such as enterprise qualification information and shareholder information. `codemap` is an enumeration set of all rendered elements, used to define the option values ​​of controls such as dropdown selections and radio buttons. `layoutStyle` is the rendering style of the resource block, supporting both Info information blocks and List collection modes. Info information blocks are suitable for simple detail display scenarios, while List collections are suitable for resource block scenarios requiring list rendering. `validateRules` is used for regular expression rule validation of complex fields, such as format validation of fields like unified social credit code, mobile phone number, and amount format.

[0086] Taking the credit approval process as an example, when a business approval process template needs to be generated, the operations staff logs into the configuration terminal and initiates a "Corporate Credit Approval Process" construction command. The architecture parses the command and obtains the target business type as "Financial Leasing - Corporate Credit," with business scenario parameters including customer type as "Corporate Customer," credit limit range as "1 million to 50 million," and risk level as "Medium Risk." The architecture converts the business scenario parameters into business feature vectors, specifically including: mapping the business type code to a one-hot vector for credit business, encoding the credit limit range as a medium-scale numerical feature, and encoding the risk level as a medium-risk coefficient. After normalization, the business feature vectors are compared with the feature vectors of each node information block in the modular approval template library to calculate the matching degree. The set of node information blocks with the highest matching degree is then selected, such as the customer information module, credit investigation module, guarantee assessment module, credit scheme module, risk review module, and approval decision module.

[0087] The selected node information blocks are combined and arranged. For example, in the credit approval process, the combination and arrangement order of the node information blocks is as follows: starting with the customer information module, the credit investigation module and guarantee assessment module are triggered in parallel after the customer information module; after both are completed, the credit granting scheme module is entered; after the credit granting scheme module is completed, the risk review module and approval decision module are entered sequentially. Simultaneously, the flow conditions between each module are configured, such as the process terminating when the credit score in the credit investigation module is below 60 points; and triggering a supplementary guarantee branch when the guarantee coverage rate in the guarantee assessment module is below 100%. Completing the combination and arrangement of the node information blocks generates a business approval process template, including the process name "Enterprise Credit Approval Process," module type combination, version number V1.0, and release status as draft. Furthermore, the personnel permissions for each node information block in the enterprise credit approval process are configured, such as configuring the customer information module so that sales staff can edit and business supervisors can view; configuring the credit investigation module so that risk control specialists can edit and risk control supervisors can view; and configuring the approval decision module so that approval committee members can edit and other personnel can only view.

[0088] Operations personnel can preview the workflow on the configuration page, viewing the field display order, grouping method, and editing control type of each node's information block. After confirming everything is correct, they submit it for review. The architecture policy-designated personnel review the workflow node order and permission configuration compliance. Once approved, the operations personnel publish the business approval workflow template, and the template's status is updated to "Published".

[0089] When the client uploads approval process requirements data for a financial leasing project, the server extracts node data from the requirements data based on a pre-defined data mapping table in the business approval process template. The extracted node data is then written into the corresponding node information blocks, thus generating a business approval process instance. For example, the customer information module is filled with data such as the company name, unified social credit code, registered capital of 50 million yuan, and establishment date; the credit investigation module is initialized to a pending state, waiting for risk control personnel to supplement data; and the credit scheme module is filled with data such as the applied amount of 8 million yuan and a term of 36 months.

[0090] After a business approval process instance is generated, the server obtains the role identifier of the client that initiated the business process approval request. Based on this role identifier, the server filters the accessible modules from the business approval process instance. For example, a risk control manager can access the customer information module (editable) and the credit scheme module (editable), can only view the credit investigation module (read-only), and cannot access the approval decision module (hidden). Then, the server generates an instance data view and sends it to the client for the risk control manager to view.

[0091] This architecture enables flexible construction of approval processes through modular configuration, decouples templates and instances through data mapping tables, provides fine-grained access control through role identifiers, and manages process evolution through incremental version identifiers. The MongoDB database stores configuration rule templates, supporting complex nested structures in JSON format to meet the configuration flexibility requirements of low-code platforms.

[0092] Please see Figure 6 , Figure 6 This is a schematic diagram of the current embodiment of an approval process generation device provided in this application. The approval process generation device is used to execute the aforementioned approval process generation method.

[0093] like Figure 6 As shown, the approval process generation device 400 includes: a template library construction module 401, a process template generation module 402, and an approval process generation module 403.

[0094] The template library construction module 401 is used to construct a modular approval template library, wherein the modular approval template library includes at least one node information block of an approval process node; The process template generation module 402 is used to construct a business approval process based on the target business type by calling at least one node information block that matches the target business type from the modular approval template library and combining and arranging it to generate a business approval process template. The approval process generation module 403 is used to configure the node data of each node information block in the business approval process template based on the approval process requirement data uploaded by the client, and generate a business approval process instance corresponding to the target business type.

[0095] In one embodiment, the template library construction module 401 includes: The data acquisition unit is used to acquire approval process data for at least one business process. The node extraction unit is used to perform structured parsing on the approval process data and extract approval process nodes corresponding to at least one business type. The node information block acquisition unit is used to modularize each of the approval process nodes to obtain at least one node information block. The template library acquisition unit is used to store the node information block into a preset database to obtain the modular approval template library.

[0096] In one embodiment, the node information block obtaining unit includes: A node mapping subunit is used to map the approval process nodes into hierarchical structural units. The node attribute configuration subunit is used to configure the node attributes of each of the structural units and generate the node information block.

[0097] In one embodiment, the process template generation module 402 includes: The instruction parsing unit is used to parse the business approval process construction instruction and obtain the business scenario parameters corresponding to the target business type. The node information block filtering unit is used to convert the business scenario parameters into a business feature vector and filter the set of node information blocks with the highest matching degree with the business feature vector from the modular approval template library, wherein the set of node information blocks includes at least one of the node information blocks; The template generation unit is used to combine and arrange the node information blocks in the node information block set to generate the business approval process template.

[0098] In one embodiment, the approval process generation module 403 includes: The node data extraction unit is used to extract node data for data mapping from the approval process requirement data based on the preset data mapping table in the business approval process template. The instance generation unit is used to write the node data into the corresponding node information block based on the data mapping table to generate the business approval process instance.

[0099] In one embodiment, the approval process generation device 400 further includes a version control module, the version control module comprising: The attribute change detection unit is used to determine the business approval process instance associated with the node information block whose attribute has changed when an attribute change is detected in the node information block stored in the modular approval template library. The version control unit is used to increment the version identifier of the business approval process instance associated with the node information block after attribute change, based on the current version identifier of the business approval process instance, so as to realize multi-version control management of the business approval process instance.

[0100] In one embodiment, the approval process generation device 400 further includes a view generation module, the view generation module comprising: The job role identifier acquisition unit is used to obtain the job role identifier of the client when a business process approval request is received from the client. The view generation unit is used to filter accessible node information blocks and node data of accessible node information blocks that match the job role identifier from the business approval process instance, generate an instance data view that matches the job role identifier, and send the instance data view to the client for display.

[0101] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the above-described apparatus and modules can be referred to the corresponding processes in the aforementioned approval process generation method embodiments, and will not be repeated here.

[0102] The apparatus provided in the above embodiments can be implemented as a computer program, which can be used in, for example... Figure 7 It runs on the computer device shown.

[0103] Please see Figure 7 , Figure 7 This is a schematic block diagram illustrating the structure of a computer device according to an embodiment of this application. The computer device may be a server.

[0104] See Figure 7 The computer device includes a processor, memory, and network interface connected via a system bus, wherein the memory may include non-volatile storage media and internal memory.

[0105] Non-volatile storage media can store operating systems and computer programs. These computer programs include program instructions that, when executed, cause the processor to perform any approval process generation method.

[0106] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0107] Internal memory provides an environment for the execution of computer programs in non-volatile storage media, which, when executed by a processor, enable the processor to perform any approval process generation method.

[0108] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0109] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0110] In one embodiment, the processor is configured to run a computer program stored in memory to perform the following steps: Construct a modular approval template library, which includes node information blocks for at least one approval process node; Based on the business approval process construction instructions for the target business type, at least one node information block that matches the target business type is called from the modular approval template library and combined and arranged to generate a business approval process template. Based on the approval process requirement data uploaded by the client, the node data of each node information block in the business approval process template is configured to generate a business approval process instance corresponding to the target business type.

[0111] The embodiments of this application also provide a computer-readable storage medium storing a computer program, the computer program including program instructions, and the processor executing the program instructions to implement any of the approval process generation methods provided in the embodiments of this application.

[0112] The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, SmartMediaCard (SMC), SecureDigital (SD) card, or FlashCard equipped on the computer device.

[0113] It should be noted that any AI models, software tools, or components not belonging to this company appearing in the embodiments of this application are merely illustrative examples and do not represent actual use. All user personal information involved in the embodiments of this application has been authorized (with the knowledge and consent) by the relevant parties or has been fully authorized by all parties, and the executing entity may obtain it through various legal and compliant means. The collection, storage, use, processing, transmission, provision, and disclosure of the information, data, and signals involved all comply with relevant laws and regulations and do not violate public order and good morals.

[0114] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for generating an approval process, characterized in that, The method includes: Construct a modular approval template library, which includes node information blocks for at least one approval process node; Based on the business approval process construction instructions for the target business type, at least one node information block that matches the target business type is called from the modular approval template library and combined and arranged to generate a business approval process template. Based on the approval process requirement data uploaded by the client, the node data of each node information block in the business approval process template is configured to generate a business approval process instance corresponding to the target business type.

2. The approval process generation method according to claim 1, characterized in that, The construction of the modular approval template library includes: Obtain approval process data for at least one business process; The approval process data is structured and parsed to extract approval process nodes corresponding to at least one business type; Each of the approval process nodes is modularized to obtain at least one node information block. The node information block is stored in a preset database to obtain the modular approval template library.

3. The approval process generation method according to claim 2, characterized in that, The step of modularizing each of the approval process nodes to obtain at least one node information block includes: Map the approval process nodes as hierarchical structural units; Configure the node attributes of each structural unit to generate the node information block.

4. The approval process generation method according to claim 1, characterized in that, The business approval process construction instruction based on the target business type calls at least one node information block matching the target business type from the modular approval template library for combination and arrangement to generate a business approval process template, including: Parse the business approval process construction instructions to obtain the business scenario parameters corresponding to the target business type; The business scenario parameters are converted into business feature vectors, and the set of node information blocks with the highest matching degree with the business feature vectors is selected from the modular approval template library, wherein the set of node information blocks includes at least one of the node information blocks; The node information blocks in the set of node information blocks are combined and arranged to generate the business approval process template.

5. The approval process generation method according to claim 1, characterized in that, The process involves configuring node data for each node information block in the business approval process template based on the approval process requirement data uploaded by the client, and generating a business approval process instance corresponding to the target business type, including: Based on the preset data mapping table in the business approval process template, node data for data mapping is extracted from the approval process requirement data; Based on the data mapping table, the node data is written into the corresponding node information block to generate the business approval process instance.

6. The approval process generation method according to claim 1, characterized in that, After configuring the node data of each node information block in the business approval process template based on the approval process requirement data uploaded by the client, and generating the business approval process instance corresponding to the target business type, the method further includes: When an attribute change is detected in the node information block stored in the modular approval template library, the business approval process instance associated with the node information block whose attributes have changed is determined. Based on the current version identifier of the business approval process instance, the version identifier of the business approval process instance associated with the node information block after the attribute change is incremented to realize multi-version control and management of the business approval process instance.

7. The approval process generation method according to claim 1, characterized in that, After configuring the node data of each node information block in the business approval process template based on the approval process requirement data uploaded by the client, and generating the business approval process instance corresponding to the target business type, the method further includes: Upon receiving a business process approval request from a client, obtain the client's role identifier; From the business approval process instance, select accessible node information blocks and node data of accessible node information blocks that match the job role identifier, generate an instance data view that matches the job role identifier, and send the instance data view to the client for display.

8. An approval process generation device, characterized in that, The approval process generation device includes: The template library construction module is used to build a modular approval template library, which includes a node information block of at least one approval process node. The process template generation module is used to construct a business approval process based on the target business type. It calls at least one node information block that matches the target business type from the modular approval template library and combines and arranges them to generate a business approval process template. The approval process generation module is used to configure the node data of each node information block in the business approval process template based on the approval process requirement data uploaded by the client, and generate a business approval process instance corresponding to the target business type.

9. A computer device, characterized in that, The computer device includes a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, it implements the steps of the approval process generation method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the approval process generation method as described in any one of claims 1 to 7.

Images