Management method of approval workflow, electronic equipment with management method and storage medium

Abstract

The invention discloses an approval workflow management method, electronic equipment with the approval workflow management method and a storage medium. The method comprises the steps that process task information is acquired, the process task information is configured by a target user, and the process task information is used for establishing an approval process of to-be-approved data or changing an existing approval process of the to-be-approved data; determining service information based on the process task information, wherein the service information comprises operation information of the target service under different management dimensions; determining approval role information based on the business information, wherein the approval role information comprises an association relationship between an approval permission of a process node in the approval process and an approval role; and determining a target approval process based on the approval role information. The technical problem that various approval requirements cannot be flexibly met due to the fact that an existing freight rate approval process is fixed in operation is solved.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a method for managing approval workflows and an electronic device and a storage medium having the same. Background Art

[0002] The freight rate management system is the core pricing system, providing basic freight rate approval management and price management, and completing price placement (release). The freight rate management system has intelligent data analysis and monitoring capabilities, and realizes closed-loop management of the entire life cycle of freight rates. It provides the best decision-making for complex freight rate product formulation and improves the pricing efficiency and effectiveness of airlines.

[0003] Due to objective reasons, most of the foreign freight rate management systems in the current market are unable to achieve customizability of approval workflows. Most of them have fixed approval level configurations and cannot integrate the workflows of various roles in the pricing, sales, and revenue departments of airlines, and often fail to achieve the desired results for airlines.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiment of the present invention provides a method for managing an approval workflow and an electronic device and a storage medium having the same, so as to at least solve the technical problem that the existing freight rate approval process cannot flexibly adapt to various approval requirements due to the fixed operation.

[0006] According to one aspect of an embodiment of the present invention, a method for managing an approval workflow is provided, comprising: obtaining process task information, the process task information is configured by a target user, the process task information is used to establish an approval process for data to be approved or to change an existing approval process for data to be approved; determining business information based on the process task information, the business information includes operation information of the target business under different management dimensions; determining approval role information based on the business information, the approval role information includes the approval authority of the process nodes in the approval process and the association relationship between the approval roles; and determining the target approval process based on the approval role information.

[0007] Furthermore, obtaining the process task information includes: periodically monitoring the task interface to obtain the process task information, and the task interface is used to exchange information with the target user.

[0008] Furthermore, after determining the target approval process based on the approval role information, the management method also includes: obtaining the historical approval process; performing a hash calculation on the historical approval process to obtain a first hash value; performing a hash calculation on the target approval process to obtain a second hash value; in response to the first hash value and the second hash value being unequal, performing a version increment on the historical approval process and executing the target approval process.

[0009] Furthermore, the business information includes at least one of the following: route information, cabin information, department information, and product type information. Determining the approval role information based on the business information includes: obtaining business configuration information, the business configuration information is used to determine the mapping relationship between business information and approval roles; determining the approval role information based on the business configuration information and the business information.

[0010] Further, the target approval process is determined based on the approval role information, including: determining an associated user based on the approval role information, wherein the associated user has the authority owned by the approval role in the approval role information; establishing an association between the associated user and the approval node and process reversal rules to obtain the approval process.

[0011] Furthermore, after establishing the association between the associated user and the approval node and the process reversal rule, the management method further includes: generating reminder information, and sending the reminder message to the associated user.

[0012] Furthermore, after determining the target approval process based on the approval role information, the processing method also includes: performing a process conflict rule check on the target approval process, the process conflict rule check is used to determine whether the execution logic of different process branches of the target approval process is contradictory; in response to the process conflict rule check passing, executing the target approval process.

[0013] According to another aspect of an embodiment of the present invention, there is further provided an electronic device, comprising: a memory storing an executable program; and a processor for running the program, wherein the method in each embodiment of the present invention is executed when the program is running.

[0014] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the methods in various embodiments of the present invention.

[0015] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the method in each embodiment of the present invention is implemented.

[0016] In an embodiment of the present invention, a custom configuration approval workflow is adopted. By acquiring and parsing the process task information configured by the target user, the operation information of the target business under different management dimensions is determined, and then the approval role information is dynamically determined based on these business information. By introducing business information and approval role information, the approval process can be automatically matched according to specific business scenarios and role permissions, avoiding the tediousness and errors of manual intervention, and achieving the purpose of flexibly adapting to the diversified approval needs of airlines, thereby achieving the technical effect of efficient, intelligent and dynamic approval process, and thus solving the technical problem that the existing freight rate approval process cannot flexibly adapt to various approval needs due to the fixed operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0018] Figure 1 It is a hardware structure block diagram of a computer terminal of a method for managing approval workflow according to one optional embodiment of the present invention;

[0019] Figure 2 is a flowchart of a method for managing approval workflow according to one optional embodiment of the present invention;

[0020] Figure 3 is a structural block diagram of a control device of a method for managing approval workflow according to one optional embodiment of the present invention;

[0021] Figure 4 It is a schematic diagram of an approval workflow according to one optional embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] According to one embodiment of the present invention, an embodiment of a method for managing an approval workflow is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0025] The method embodiment can be executed in an electronic device including a memory and a processor in a computer or a similar computing device. For example, the electronic device running on the computer, such as Figure 1 As shown, the electronic device of the computer may include one or more processors 102 (the processor may include but is not limited to a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microprocessor (MCU), a field programmable logic device (FPGA), a neural network processor (NPU), a tensor processing unit (TPU), an artificial intelligence (AI) type processor, etc.) and a memory 104 for storing data. Optionally, the electronic device of the above-mentioned car may also include a transmission device 106 for communication functions, an input and output device 108, and a display device 110. It can be understood by those skilled in the art that Figure 1 The structure shown is for illustration only and does not limit the structure of the electronic device of the computer. For example, the electronic device of the computer may include more or fewer components than the above structure description, or have a configuration different from the above structure description.

[0026] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the information processing method in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, the above-mentioned information processing method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0027] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0028] The display device 110 may be, for example, a touch screen type liquid crystal display (LCD) and a touch display (also referred to as a "touch screen" or a "touch display screen"). The liquid crystal display may enable a user to interact with a user interface of the mobile terminal. In some embodiments, the mobile terminal has a graphical user interface (GUI), and a user may interact with the GUI by finger contact and / or gestures on a touch-sensitive surface, wherein the human-computer interaction functions here may optionally include the following interactions: creating web pages, drawing, word processing, making electronic documents, games, video conferencing, instant messaging, sending and receiving emails, call interfaces, playing digital videos, playing digital music and / or web browsing, etc. The executable instructions for executing the above human-computer interaction functions are configured / stored in a computer program product or a readable storage medium executable by one or more processors.

[0029] Figure 2 is a method according to an embodiment of the present invention, such as Figure 1 As shown, the method comprises the following steps:

[0030] Step S102, obtaining process task information, which is configured by the target user and used to establish an approval process for the data to be approved or to modify an existing approval process for the data to be approved;

[0031] Optionally, the process task information is customized by the target user (usually the managers of the fare management, pricing strategy, sales or revenue department within the airline) through the fare management system interface or a specific configuration tool. The process task information is the key to building or adjusting the approval process. It contains various elements of the approval process, such as nodes, flow rules between nodes, approval roles, monitoring tasks, etc., to meet the approval needs of specific fare products or policies.

[0032] Specifically, the approval process can be divided into two-level, three-level or five-level approval, etc. Target users can dynamically set different levels of approval processes according to their own needs, which can meet the different approval requirements of different airlines and break the rigid layout of the approval process.

[0033] Optionally, when an airline needs to set up an approval process for a new fare policy, rule changes, or special products, the target user will enter the process task information through the system's workflow editor or approval process configuration interface. This information includes the starting point of the process, each approval node (such as sales department approval, fare supervisor approval, regional manager approval, etc.), the flow conditions between nodes (such as automatic flow, conditional flow, etc.), approval roles (such as fare supervisor, revenue analyst, etc.), and the relationship between the approval role and the specific user (such as the lineman of a certain route, the head of a certain department, etc.). With this information, the system can automatically build an approval process, and the data to be approved will be reviewed by the users of each approval node according to the preset process.

[0034] Specifically, the data to be approved mainly include but are not limited to the following categories: (1) fare data: including new fare settings or adjustments to existing fares, involving information such as fare basis, discount rate, applicable routes, applicable cabin space, validity period, etc.; (2) aviation operating policies: may involve changes in route rules, sales rules, refund and change rules, etc. These changes need to be approved to ensure that they comply with the airline's policies and market strategies; (3) special products: specific promotional products launched by airlines, such as seasonal specials, holiday promotions, etc. These products need to go through multiple levels of approval and confirmation before they are launched.

[0035] Optionally, as the airline's business develops and its organizational structure adjusts, the original approval process may need to be optimized or changed. The target user can adjust the approval process by updating the process task information. For example, you can add or delete approval nodes, change the flow logic between nodes, update the permissions of the approval role, or add new monitoring management tasks (such as automated email notifications, dynamic approver assignments, etc.). When the process task information is updated, the system will change the existing approval process and generate a new approval process version. This new version of the approval process will be used to process subsequent submitted data for approval, while the data in the approval process will continue to follow the original process until the approval is completed, ensuring business continuity and a smooth transition of process changes.

[0036] Through the above embodiment, the operation of obtaining process task information in step S102 not only provides a basis for establishing or changing the approval process, but also ensures through dynamic configuration that the approval process can be flexibly adjusted according to the business needs and organizational structure changes of the airline, thereby realizing intelligent management of the approval process.

[0037] Step S104, determining business information based on the process task information, where the business information includes operation information of the target business under different management dimensions;

[0038] Optionally, based on the process task information configured by the target user, the fare management system will automatically or semi-automatically collect and analyze business information related to the data to be approved, to ensure that the approval process is closely integrated with the actual business scenario and achieve more accurate decision-making. Based on business information, the system supports evaluation under multiple management dimensions, such as route operation status, product market positioning, and revenue impact analysis. For example, the system can automatically evaluate the operating efficiency of routes, analyze the impact of preferential products on market positioning, and predict the potential impact of fare adjustments on airline revenue.

[0039] Optionally, in a specific embodiment, assume that a certain airline's fare supervisor configures an approval process for approving a preferential product policy involving the Beijing (PEK) to Seoul (ICN) route. Based on this process task information, the system will obtain the recent sales data of the PEK-ICN route from the sales system, and analyze the revenue forecast of the route through the passenger load factor analysis, revenue forecast report, market trend analysis, competitor fare comparison and other information of the PEK-ICN route, so as to evaluate the impact of the preferential product policy on the route revenue and ensure the effectiveness and competitiveness of this adjustment.

[0040] Optionally, this step can not only provide necessary business data support for the approval workflow, but also assist the approval personnel to comprehensively consider the business from multiple management dimensions to ensure the comprehensiveness and scientificity of the approval decision.

[0041] Step S106, determining approval role information based on the business information, the approval role information including the approval authority of the process node in the approval process and the association relationship between the approval role;

[0042] Optionally, the requirements of each node in the approval process will first be determined based on the nature and importance of the business information. For example, for a policy involving route promotions, it may require preliminary approval from the "sales department head", focusing on the implementation details of the sales strategy; then the "freight rate head" will review and evaluate the impact of the policy on the freight rate system; then, if the policy involves adjustments to cross-regional sales or marketing strategies, it may also require final approval from the "regional manager" or even the "vice president of marketing". The approval authority and task focus of each approval node are set according to the characteristics of the business information.

[0043] For each approval node, the system associates the appropriate approval role based on the business information. For each approval role, the system configures the corresponding approval authority based on the business information and role attributes. For example, the Qingdao to Seoul route is managed by Zhang San, and the Beijing to Tokyo route is managed by Li Si. When approving the Qingdao to Seoul route, the approver needs to automatically jump to Zhang San for approval, and the Beijing to Tokyo route needs to automatically jump to Li Si for approval.

[0044] Through the above steps, the approval authority of each process node in the approval process and the relationship between the approval roles are determined based on business information, ensuring that the approval process not only covers the necessary business dimensions, but also specifies the most appropriate approvers based on the analysis results of the business information, thereby ensuring the business orientation and professionalism of the approval decision.

[0045] Step S108: determining the target approval process based on the approval role information.

[0046] Optionally, a specific target approval process is determined based on the approval role information, which will guide the approval process of the data to be approved, ensure that appropriate personnel are involved in each step of the approval, and follow the preset approval logic, thereby improving the efficiency and transparency of the approval process.

[0047] Through the above steps S102 to S108, in an embodiment of the present invention, a custom configuration approval workflow is adopted, and by obtaining and parsing the process task information configured by the target user, the operation information of the target business under different management dimensions is determined, and then the approval role information is dynamically determined based on these business information. By introducing business information and approval role information, the approval process can be automatically matched according to specific business scenarios and role permissions, avoiding the tediousness and errors of manual intervention, and achieving the purpose of flexibly adapting to the diversified approval needs of airlines, thereby achieving the technical effect of efficient, intelligent and dynamic approval process, and thus solving the technical problem that the existing freight rate approval process cannot flexibly adapt to various approval needs due to the fixed operation.

[0048] Optionally, acquiring the process task information includes: periodically monitoring a task interface to acquire the process task information, where the task interface is used to perform information interaction with a target user.

[0049] Optionally, a task interface is designed for information exchange with target users. This interface allows users to submit change requests for approval processes, such as adding new approval nodes, modifying approval logic, or updating approval roles. The interface is designed with data security and permission control in mind to ensure that only authorized users can perform operations.

[0050] Optionally, when obtaining process task information, a monitoring mechanism is set up to periodically (e.g., every 15 minutes) query the task interface to check whether there is new or changed process task information. If new information is detected, the system will immediately process it and parse the information into actionable approval process change instructions, thereby dynamically updating the approval process.

[0051] Optionally, in a specific embodiment, suppose that a fare supervisor of an airline logs into the system and submits an approval process change task through the task interface, explicitly requesting that a "product policy approval" node be added to the preferential product approval process, to be approved by the policy analyst of the marketing department. The system checks the task interface every 15 minutes according to a predetermined periodic monitoring mechanism. After receiving the change request from the fare supervisor, the system immediately parses the information and identifies the requirement to add a node to the approval process. Based on the parsing results, a "product policy approval" node is automatically added to the preferential product approval process, and the approval role of the "product policy approval" node is designated as the policy analyst of the marketing department. The changed process takes effect immediately, and all new preferential product approvals will follow the updated approval process.

[0052] Through the above steps, the task interface is monitored periodically, and the fare management system can quickly respond to the change request of the target user, realize the dynamic adjustment of the approval process, improve the flexibility and response speed of the system, and achieve the automation and customization of the business process. This mechanism is particularly suitable for the scenario of frequent adjustment of the approval process in the fare management of airlines, ensuring that the approval process can always adapt to business changes and management needs. At the same time, the interaction between the task interface and the target user also simplifies the process of process change and improves the overall approval efficiency.

[0053] Optionally, after determining the target approval process based on the approval role information, the management method also includes: obtaining the historical approval process; performing a hash calculation on the historical approval process to obtain a first hash value; performing a hash calculation on the target approval process to obtain a second hash value; in response to the first hash value and the second hash value being unequal, performing a version increment on the historical approval process and executing the target approval process.

[0054] Optionally, the freight rate management system retrieves all historical approval processes related to the current data to be approved from the database, performs hash calculation on the acquired historical approval process data, and generates a first hash value. The hash value is a fixed-length value obtained by performing mathematical operations on the process data, and can quickly and accurately identify the specific content of the process. Similarly, a hash calculation is performed on the newly determined target approval process to generate a second hash value. The first hash value is compared with the second hash value. If the two hash values ​​are not equal, it means that there is a difference between the historical approval process and the target approval process, that is, the approval process has changed. The system will automatically increment the version of the historical approval process and create a new version that includes the target approval process. At the same time, the system will execute the target approval process.

[0055] Specifically, suppose an airline needs to approve a new fare policy for the Beijing-London route. The system has determined a target approval process based on business information and approval role information, including four stages: "policy maker approval", "route staff approval", "regional manager approval" and "marketing general manager approval", and configured corresponding approval roles and permissions. Retrieve all historical approval processes related to the approval of the fare policy for the Beijing-London route from the database, perform hash calculations on the historical approval processes, and calculate the first hash value to be H1. Perform hash calculations on the newly determined target approval process to obtain the second hash value of the target approval process to be H2. Compare H1 and H2. If H1≠H2, it means that there is a difference between the target approval process and the most recent historical approval process version, indicating that the approval process needs to be updated. Approve the new fare policy for the Beijing-London route according to the new version of the approval process to ensure that the approval process follows the settings of the target approval process.

[0056] Through the above steps, not only can the changes in the approval process be automatically detected, but the changes can also be more accurately identified through the hash value, thereby realizing the automatic increment of the approval process version and the immediate execution of the new process. This mechanism ensures that the changes in the approval process can take effect in a timely manner, while maintaining the integrity and traceability of the historical approval process, which is of great significance for the continuous optimization and adjustment of the freight rate management approval workflow.

[0057] Optionally, the business information includes at least one of the following: route information, cabin information, department information, product type information, and determining the approval role information based on the business information includes: obtaining business configuration information, the business configuration information is used to determine the mapping relationship between business information and approval roles; determining the approval role information based on the business configuration information and the business information.

[0058] Specifically, the system obtains business configuration information from the management database, which defines the mapping relationship between business information and approval roles. For example, a specific route operator or regional manager is responsible for the approval of a certain route. When it comes to fare changes for a specific route, the system will check the route information, obtain the business configuration information, and determine the approval role responsible for the route, such as "route operator approval" or "regional manager approval." When an airline plans to adjust the fare of the Beijing-Tokyo route, the system determines the "Beijing-Tokyo route operator" as the approval role based on the route information and the business configuration information. Members of this role will participate in the approval process to ensure that the fare adjustment is in line with the route operation strategy.

[0059] It should be further explained that the approval role mainly refers to the collection of personnel or positions that play a specific function or undertake a specific approval task in the freight rate approval process. An approval role may contain one or more actual approvers (the role name is named after role). Each approval role has its specific approval authority and scope of responsibility. For example, "line operator approval", "regional manager approval" or "marketing department general manager approval" are all different approval roles, which represent different levels of approval functions in the freight rate approval process.

[0060] Approval role information is a more detailed description and configuration of the approval role, including the approval authority of different process nodes in the approval process and the relationship between the approval role. Specifically, the approval role information covers the name, authority, operation scope and binding status of the approval role with the approval process nodes. It may also include dynamic matching rules for approval roles, such as matching different approval roles according to business information such as routes, departments, product types, etc., as well as the specific position and flow logic of the approval role in the approval process.

[0061] Specifically, when the business information is cabin information, the business configuration information defines the mapping relationship between fare changes and approval roles for different cabins (first class, business class, economy class, etc.). If the fare change involves a specific cabin, the system will determine the role responsible for approving the fare for that cabin, such as "cabin fare supervisor approval" based on the cabin management configuration information. For example, an airline plans to adjust the fare for business class. The system matches the cabin information to the "business class fare supervisor approval" in the cabin management configuration information, and the business class fare supervisor is responsible for approval to ensure that the fare adjustment is in line with the market positioning of the business class.

[0062] Specifically, when the business information is department information, the business configuration information defines the mapping relationship between different departments and approval roles. If the fare change involves the decision of a specific department, the system will determine the corresponding department approval role based on the business configuration information, such as "marketing department approval" or "revenue management department approval". An airline is planning to launch a marketing strategy involving preferential fares on multiple routes. The system matches the "marketing strategy approval" process through department information, and the strategy analyst of the marketing department is responsible for approval to ensure that the fare adjustment is in line with the strategic planning of the marketing department.

[0063] Specifically, when the business information is product type information, the business configuration information defines the mapping relationship between different product types and approval roles. If the freight rate change involves the release of a new product type, the system will determine the corresponding approval role based on the business configuration information, such as the "new product approval process", which may involve multiple approval nodes such as "product manager approval" and "market analysis approval". An airline currently plans to launch a new "family vacation package" product. The system matches the "new product approval process" through product type information, and multiple roles such as product managers, market analysts, and financial analysts participate in the approval to ensure that the new product is in line with market trends, financially feasible, and in line with the company's overall product line planning.

[0064] Through the above steps, the approval role information is determined based on the business information, ensuring that the approval process can be flexibly adjusted according to the specific business scenarios of the fare change. Moreover, through the setting of mapping relationships, the determination of approval roles can be automated, which greatly improves the efficiency and accuracy of the approval process and enables dynamic expansion and innovation for different airlines to achieve different business models.

[0065] Optionally, determining the target approval process based on the approval role information includes: determining an associated user based on the approval role information, wherein the associated user has the authority owned by the approval role in the approval role information; establishing an association between the associated user and the approval node and process reversal rules to obtain the approval process.

[0066] Specifically, according to the role name in the approval role information, users with the same role name are searched. These users are associated users and have the permissions of the approval role in the approval role information. There may be one or more associated users, depending on the number and allocation of users under the approval role information.

[0067] Optionally, in the approval process, an associated user is assigned to each approval node. For example, for the "Lineman Approval" node, the system will find all users associated with the approval role and bind these users to the node. The association relationship between the approval node and the associated user can be many-to-one (multiple users can have the same approval authority, but only one of them can approve it) or one-to-many (one approval node can be approved by multiple users with the same authority). The associated user is determined based on the approval role information, that is, if the user name user1 has the role role1, then the user user1 has the approval authority and other system permissions of the role role1.

[0068] The process reversal rules define how to handle the situation of approval failure in different situations in the approval process. The rules can be configured to return to the specified approval node or terminate the process directly when the approval fails. The setting of process reversal rules enhances the controllability and adaptability of the approval process, ensures that the process can be flexibly adjusted according to different approval situations, and improves the efficiency and effectiveness of the approval process.

[0069] Specifically, an airline plans to adjust the fare policy of the "Long-term Promotional Product for Business Class on European Routes". The adjustment of this policy needs to go through multiple levels of approval before it can be finally released and implemented. The approval process includes the following approval nodes: approval by the sales department supervisor, approval by the fare supervisor, approval by the regional manager, and approval by the general manager of the marketing department. If the approval fails at the "fare supervisor approval" node, the process will return to the "sales department supervisor approval" node so that the sales department supervisor can make adjustments based on the feedback. If the approval fails at the "regional manager approval" node, the process will return to the "fare supervisor approval" node, and the fare supervisor will review it again based on the feedback from the regional manager. If the approval fails at the "general manager approval" node, the process will terminate directly, and the sales department will need to resubmit the revised policy for approval. The application of process reversal rules not only ensures that the adjustment of fare policies can be comprehensively reviewed, but also improves the efficiency and accuracy of approval by automatically returning to specific nodes, avoiding unnecessary process delays.

[0070] Specifically, the determined approval roles and associated users are associated with the nodes in the approval process, and the process reversal rules are embedded in the approval process. This means that when the approval process reaches a certain node, the system will automatically identify and activate the approval roles and associated users related to the node, and automatically execute the corresponding process reversal rules based on the approval results.

[0071] Through the above steps, a dynamic approval process is formed that can be automatically adjusted according to business information and approval results. Each node is bound to a specific approval role and associated user, and the direction of the process is preset through the process reversal rules, forming a closed-loop approval management system. Through dynamic configuration and process adjustment, the approval process is ensured to be both efficient and accurate, while being highly customizable, meeting the flexibility and personalized needs of airlines for the approval process of freight rate management.

[0072] Optionally, after establishing the association between the associated user and the approval node and the process reversal rule, the management method further includes: generating reminder information, and sending the reminder message to the associated user.

[0073] Specifically, the system sends the generated reminder information to the associated users via email, SMS, internal system messages, or mobile app notifications, etc. This ensures that the approver is immediately aware of new approval tasks waiting to be processed. The reminder information usually includes key information such as a brief description of the policy to be approved, the name of the approval node, the actions that the approver needs to perform, and the approval deadline.

[0074] Through the above steps, it is ensured that the approvers at each node in the approval process can receive notifications of pending approval tasks in a timely manner, thereby avoiding approval delays and improving approval efficiency.

[0075] Optionally, after determining the target approval process based on the approval role information, the processing method also includes: performing a process conflict rule check on the target approval process, the process conflict rule check is used to determine whether the execution logic of different process branches of the target approval process is contradictory; in response to passing the process conflict rule check, executing the target approval process.

[0076] Specifically, the process conflict rule check mainly checks whether there are logical conflicts in the approval process, involving the flow direction of the approval node, the authority of the approval role, and the setting of the process reversal rules. For example, check whether there are contradictory settings that require the same approval node to be turned around and terminated in different situations; check whether the authority of the approval role in the process node conforms to the preset business logic; and check whether the process reversal rules lead to an infinite loop of the approval process. If the process conflict rule check passes, it means that the setting of the approval process is logically coherent and consistent, and the system can continue to execute the target approval process. If a conflict is detected, the system will terminate the process and make adjustments until the check passes.

[0077] Through the above embodiments, it can be seen that process conflict rule verification is a key link in the approval process setting. It ensures the logical consistency and rationality of the set target approval process, avoids approval delays or inefficiencies caused by logical errors, and thus ensures a smooth and efficient approval process.

[0078] It needs to be further explained that if Figure 4 As shown in the figure, the process task information is obtained by the target user configuration. The user mainly uses SVG to draw the approval process. Four legends are defined in the process definition, mainly startEvent, sequenceFlow, exclusiveGateway, userTask, and endEvent. StartEvent is mainly defined as the start node of the process. This node must exist in each process and is the beginning of a process. SequenceFlow is a connection line, which mainly links the path between nodes. Rules are defined in the sequenceFlow node. When the rules are matched, jump to the corresponding node. ExclusiveGateway is an exclusive gateway node. Its main function is to jump to the corresponding node according to the result of the user operation when the user performs the approval operation. UserTask is the approval node of the process. In this node, you can set the roles or users that need to be approved by the node according to the role data and user data. You can also define the monitoring task during the execution of the approval node according to the data in the monitoring management. You can execute other related business logic before and after the execution of the approval node. The endEvent node is the end node of the process. It is a necessary node for each process. This node marks the end of the entire process.

[0079] According to an embodiment of the present invention, a device embodiment of a method for managing an approval workflow is provided. It should be noted that the device can be used to execute the method for managing the approval workflow.

[0080] Figure 3 A structural block diagram of a control device of a method for managing approval workflow according to an optional embodiment of the present invention. Figure 3 As shown, the device comprises:

[0081] Acquisition module 301, acquires process task information, which is configured by the target user and is used to establish an approval process for the data to be approved or to change the existing approval process for the data to be approved;

[0082] A determination module 302 determines business information based on the process task information, where the business information includes operation information of the target business under different management dimensions;

[0083] The association module 303 determines the approval role information based on the business information, where the approval role information includes the approval authority of the process node in the approval process and the association relationship between the approval role;

[0084] The control module 304 determines the target approval process based on the approval role information.

[0085] Optionally, acquiring the process task information based on the acquisition module 301 includes: periodically monitoring the task interface to acquire the process task information, where the task interface is used to perform information interaction with the target user.

[0086] Optionally, the historical approval process is obtained through the control module 304; a hash calculation is performed on the historical approval process to obtain a first hash value; a hash calculation is performed on the target approval process to obtain a second hash value; in response to the first hash value and the second hash value being unequal, the historical approval process is versioned and the target approval process is executed.

[0087] Optionally, the business information is determined by determining module 302 to include at least one of the following: route information, cabin information, department information, and product type information, and the approval role information is determined based on the business information, including: obtaining business configuration information, the business configuration information is used to determine the mapping relationship between business information and approval roles; and determining the approval role information based on the business configuration information and the business information.

[0088] Optionally, the association module 303 determines an associated user based on the approval role information, wherein the associated user has the authority of the approval role in the approval role information; an association is established between the associated user and the approval node and the process reversal rule to obtain the approval process.

[0089] Optionally, reminder information is generated by the control module 304, and the reminder message is sent to the associated user.

[0090] Optionally, the control module 304 performs a process conflict rule check on the target approval process, and the process conflict rule check is used to determine whether the execution logics of different process branches of the target approval process are inconsistent; in response to the process conflict rule check passing, the target approval process is executed.

[0091] In an embodiment of the present invention, a custom configuration approval workflow is adopted. By acquiring and parsing the process task information configured by the target user, the operation information of the target business under different management dimensions is determined, and then the approval role information is dynamically determined based on these business information. By introducing business information and approval role information, the approval process can be automatically matched according to specific business scenarios and role permissions, avoiding the tediousness and errors of manual intervention, and achieving the purpose of flexibly adapting to the diversified approval needs of airlines, thereby achieving the technical effect of efficient, intelligent and dynamic approval process, and thus solving the technical problem that the existing freight rate approval process cannot flexibly adapt to various approval needs due to the fixed operation.

[0092] An embodiment of the present application further provides an electronic device, comprising: a memory storing an executable program; and a processor for running the program, wherein when the program is running, the method for managing the approval workflow in each embodiment of the present invention is executed.

[0093] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0094] Step S102, obtaining process task information, which is configured by the target user and used to establish an approval process for the data to be approved or to modify an existing approval process for the data to be approved;

[0095] Step S104, determining business information based on the process task information, where the business information includes operation information of the target business under different management dimensions;

[0096] Step S106, determining approval role information based on the business information, the approval role information including the approval authority of the process node in the approval process and the association relationship between the approval role;

[0097] Step S108: determining the target approval process based on the approval role information.

[0098] An embodiment of the present application further provides a computer-readable storage medium, which includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the approval workflow management method in each embodiment of the present invention.

[0099] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0100] Step S102, obtaining process task information, which is configured by the target user and used to establish an approval process for the data to be approved or to modify an existing approval process for the data to be approved;

[0101] Step S104, determining business information based on the process task information, where the business information includes operation information of the target business under different management dimensions;

[0102] Step S106, determining approval role information based on the business information, the approval role information including the approval authority of the process node in the approval process and the association relationship between the approval role;

[0103] Step S108: determining the target approval process based on the approval role information.

[0104] The embodiments of the present application further provide a computer program product, including a computer program, which implements the management method of the approval workflow in each embodiment of the present invention when executed by a processor.

[0105] Optionally, in this embodiment, the computer program product may be configured as a computer program for executing the following steps:

[0106] Step S102, obtaining process task information, which is configured by the target user and used to establish an approval process for the data to be approved or to modify an existing approval process for the data to be approved;

[0107] Step S104, determining business information based on the process task information, where the business information includes operation information of the target business under different management dimensions;

[0108] Step S106, determining approval role information based on the business information, the approval role information including the approval authority of the process node in the approval process and the association relationship between the approval role;

[0109] Step S108: determining the target approval process based on the approval role information.

[0110] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0111] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0112] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0113] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0114] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0115] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for managing approval workflow, characterized in that: include: Acquire process task information, which is configured by the target user and is used to establish an approval process for the data to be approved or to change an existing approval process for the data to be approved; Determine business information based on the process task information, where the business information includes operation information of the target business under different management dimensions; Determining approval role information based on the business information, the approval role information including the approval authority of the process node in the approval process and the association relationship between the approval role; A target approval process is determined based on the approval role information.

2. The management method according to claim 1, characterized in that: Obtaining process task information includes: The task interface is periodically monitored to obtain the process task information, and the task interface is used to exchange information with the target user.

3. The management method according to claim 1, characterized in that: After determining the target approval process based on the approval role information, the management method further includes: Get the historical approval process; Performing hash calculation on the historical approval process to obtain a first hash value; Performing hash calculation on the target approval process to obtain a second hash value; In response to the first hash value and the second hash value being unequal, the historical approval process is version-incremented and the target approval process is executed.

4. The management method according to claim 1, characterized in that: The business information includes at least one of the following: route information, space information, department information, and product type information. The approval role information is determined based on the business information, including: Acquire business configuration information, where the business configuration information is used to determine a mapping relationship between the business information and the approval role; The approval role information is determined based on the business configuration information and the business information.

5. The management method according to claim 1, characterized in that: Determining a target approval process based on the approval role information includes: Determining an associated user based on the approval role information, wherein the associated user has the authority possessed by the approval role in the approval role information; An association is established between the associated user, the approval node, and the process reversal rule to obtain the approval process.

6. The management method according to claim 1, characterized in that: After establishing the association between the associated user and the approval node and the process reversal rule, the management method further includes: Generate reminder information, and send the reminder message to the associated user.

7. The management method according to claim 1, characterized in that: After determining the target approval process based on the approval role information, the processing method further includes: Performing a process conflict rule check on the target approval process, wherein the process conflict rule check is used to determine whether the execution logics of different process branches of the target approval process are inconsistent; In response to the process conflict rule verification being passed, the target approval process is executed.

8. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 7 when running.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is run, the device where the storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

10. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 7.

Images