Approval workflow management methods and their associated electronic devices and storage media.

Abstract

This invention discloses a management method for approval workflows, as well as an electronic device and storage medium using the method. The method includes: acquiring workflow task information, which is configured by the target user and used to establish an approval workflow for data to be approved or to modify an existing approval workflow for the data to be approved; determining business information based on the workflow task information, including operational information of the target business under different management dimensions; determining approval role information based on the business information, including the approval permissions of workflow nodes and the association relationships between approval roles; and determining the target approval workflow based on the approval role information. This invention solves the technical problem that the fixed operation of existing freight rate approval workflows makes it inflexible to adapt to various approval needs.

Description

Technical Field

[0001] This invention relates to the field of information technology, and more specifically, to a management method for an approval workflow and an electronic device and storage medium having the same. Background Technology

[0002] The fare management system is the core pricing system, providing basic fare approval and price management, and completing price placement (publishing). The fare management system possesses intelligent data analysis and monitoring capabilities, achieving closed-loop management of the entire fare lifecycle. It provides optimal decision-making for the formulation of complex fare products, improving the pricing efficiency and effectiveness of airlines.

[0003] Due to objective reasons, most foreign fare management systems on the market today cannot achieve customizable approval workflows. Instead, they are mostly configured with fixed approval levels and cannot integrate the workflows of various roles in the airline's pricing, sales, and revenue departments, often failing to achieve the desired results for the airline.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This invention provides a management method for approval workflows, as well as an electronic device and storage medium thereon, to at least solve the technical problem that existing fixed freight rate approval processes cannot flexibly adapt to various approval needs.

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

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

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

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

[0010] Furthermore, the target approval process is determined based on the approval role information, including: determining associated users based on the approval role information, wherein the associated users have the permissions possessed by the approval role in the approval role information; establishing the association between the associated users, approval nodes, and process reversal rules to obtain the approval process.

[0011] Furthermore, after establishing the association between users, approval nodes, and process reversal rules, the management method also includes: generating reminder information and sending the reminder message to the associated users.

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

[0013] According to another aspect of the present invention, an electronic device is also provided, comprising: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods of various embodiments of the present invention during runtime.

[0014] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is executed, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of the present invention.

[0015] According to another aspect of the present invention, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of the present invention.

[0016] In this embodiment of the invention, a custom configuration approval workflow is adopted. By acquiring and parsing the process task information configured by the target user, the operational information of the target business under different management dimensions is determined. Then, based on this business information, the approval role information is dynamically determined. By introducing business information and approval role information, the approval process can be automatically matched according to the specific business scenario and role permissions, avoiding the tediousness and errors of manual intervention. This achieves the goal of flexibly adapting to the diverse approval needs of airlines, thereby realizing the technical effect of efficient, intelligent and dynamic approval process. This solves the technical problem that the fixed operation of the existing fare approval process makes it impossible to flexibly adapt to various approval needs. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0018] Figure 1 This is a hardware structure block diagram of a computer terminal for an approval workflow management method according to an optional embodiment of the present invention.

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

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

[0021] Figure 4 This is a schematic diagram of an approval workflow according to one optional embodiment of the present invention. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort 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, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

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

[0025] This method embodiment can be executed in an electronic device or similar computing device that includes a computer and a processor. Taking an electronic device running on a computer as an example, such as... Figure 1 As shown, the electronic device of the computer may include one or more processors 102 (processors may include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), digital signal processing (DSP) chips, microprocessors (MCUs), programmable logic devices (FPGAs), neural network processors (NPUs), tensor processors (TPUs), artificial intelligence (AI) type processors, etc.) and a memory 104 for storing data. Optionally, the electronic device of the aforementioned vehicle may also include a transmission device 106 for communication functions, an input / output device 108, and a display device 110. Those skilled in the art will understand that... Figure 1 The structures shown are for illustrative purposes only and do not limit the structure of the electronic device of the computer described above. For example, the electronic device of the computer may include more or fewer components than those described above, or have a different configuration than those described above.

[0026] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the information processing method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the aforementioned information processing method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0027] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0028] Display device 110 may be, for example, a touchscreen liquid crystal display (LCD) and a touch display (also referred to as a "touchscreen" or "touch display"). The LCD allows a user to interact with the user interface of the mobile terminal. In some embodiments, the mobile terminal has a graphical user interface (GUI), which allows the user to interact with the GUI via finger contact and / or gestures on a touch-sensitive surface. Optional human-computer interaction functions include: creating web pages, drawing, word processing, creating electronic documents, playing games, video conferencing, instant messaging, sending and receiving emails, a call interface, playing digital video, playing digital music, and / or web browsing, etc. Executable instructions for performing the above human-computer interaction functions are configured / stored in one or more processor-executable computer program products or readable storage media.

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

[0030] Step S102: Obtain process task information. The process task information is configured by the target user and is used to establish an approval process for the data to be approved or to modify the existing approval process for the data to be approved.

[0031] Optionally, the process task information is customized by the target user (usually managers in the airline's fare management, pricing strategy, sales, or revenue departments) through the fare management system interface or specific configuration tools. Process task information is key to building or adjusting the approval process. It includes various elements of the approval process, such as nodes, flow rules between nodes, approval roles, and monitoring tasks, to adapt to the approval requirements of specific fare products or policies.

[0032] Specifically, the approval process can be divided into two, three, or five levels of approval, etc. Target users can dynamically set different levels of approval process 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 new fare policies, rule changes, or special offers, the target user will input 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.), the approval role (such as fare supervisor, revenue analyst, etc.), and the relationship between the approval role and the specific user (such as a route coordinator for a specific route, a department head, etc.). Using this information, the system can automatically construct an approval process, and the data to be approved will be reviewed by users at each approval node according to the preset process.

[0034] Specifically, the data to be approved mainly includes, but is not limited to, the following categories: (1) Fare data: including new fare settings or adjustments to existing fares, involving information such as fare base, discount rate, applicable routes, applicable cabin class, and validity period; (2) Airline operation policies: may involve changes to route rules, sales rules, refund and change rules, etc., which need to be approved to ensure compliance with the airline's policies and market strategies; (3) Special offers: specific promotional products launched by the airline, such as seasonal specials and holiday promotions, which need to be approved and confirmed at multiple levels before they are launched.

[0035] Optionally, as airlines develop their business and adjust their organizational structure, existing approval processes may need to be optimized or modified. Target users can adjust the approval process by updating process task information. For example, they can add or delete approval nodes, change the flow logic between nodes, update the permissions of approval roles, or add new monitoring and management tasks (such as automated email notifications, dynamic approver assignment, etc.). Once the process task information is updated, the system will modify the existing approval process, generating a new version. This new version of the approval process will be used to process subsequently submitted data awaiting approval, while data currently under approval will continue to follow the original process until approval is completed, ensuring business continuity and a smooth transition of process changes.

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

[0037] Step S104: Determine business information based on process task information. Business information includes operational 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 pending approval to ensure that the approval process is closely integrated with actual business scenarios and achieve more accurate decision-making. Based on business information, the system supports evaluations across multiple management dimensions, such as route operation status, product market positioning, and revenue impact analysis. For example, the system can automatically assess the operational 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 one specific embodiment, suppose an airline's fare manager has configured an approval process for approving a special offer policy for the Beijing (PEK) to Seoul (ICN) route. Based on this process task information, the system will retrieve recent sales data for the PEK-ICN route from the sales system. Through load factor analysis, revenue forecast reports, market trend analysis, and competitor fare comparisons for the PEK-ICN route, the system will analyze the route's revenue forecast to assess the impact of the special offer policy on route revenue, ensuring the effectiveness and competitiveness of the adjustment.

[0040] Optionally, this step can not only provide the necessary business data support for the approval workflow, but also help approvers to comprehensively consider the business from multiple management dimensions, ensuring the comprehensiveness and scientific nature of approval decisions.

[0041] Step S106: Determine the approval role information based on business information. The approval role information includes the approval authority of the process nodes in the approval process and the association relationship of the approval roles.

[0042] Optionally, the requirements for each step in the approval process will first be determined based on the nature and importance of the business information. For example, policies involving route promotions may require initial approval from the "sales department manager," focusing on the implementation details of the sales strategy; then, the "fare manager" will approve, focusing on assessing the policy's impact on the fare system; next, if the policy involves adjustments to cross-regional sales or marketing strategies, final approval from the "regional manager" or even the "vice president of marketing" may be required. The approval authority and task focus at each approval step are set according to the characteristics of the business information.

[0043] For each approval node, the system associates a suitable approval role based on business information. For each approval role, the system configures corresponding approval permissions based on 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 be automatically redirected to Zhang San for approval, and when approving the Beijing to Tokyo route, the approver needs to be automatically redirected to Li Si for approval.

[0044] Through the above steps, the relationship between the approval authority and the approval role of each process node in the approval process is determined based on business information. This ensures that the approval process not only covers the necessary business dimensions, but also assigns the most suitable approver based on the analysis results of business information, thereby guaranteeing the business orientation and professionalism of the approval decision.

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

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

[0047] Through the above steps S102 to S108, in this embodiment of the invention, a custom configuration approval workflow is adopted. By acquiring and parsing the process task information configured by the target user, the operational information of the target business under different management dimensions is determined. Then, based on this business information, the approval role information is dynamically determined. By introducing business information and approval role information, the approval process can be automatically matched according to the specific business scenario and role permissions, avoiding the tediousness and errors of manual intervention. This achieves the goal of flexibly adapting to the diverse approval needs of airlines, thereby realizing the technical effect of efficient, intelligent, and dynamic approval process. This solves the technical problem that the fixed operation of the existing fare approval process makes it impossible to flexibly adapt to various approval needs.

[0048] Optionally, obtaining process task information includes: periodically listening to the task interface to obtain process task information, and the task interface is used to interact with the target user.

[0049] Optionally, a task interface was designed for information interaction with the target user. This interface allows users to submit change requests for the approval process, such as adding new approval nodes, modifying approval logic, or updating approval roles. Data security and access control were considered in the interface design to ensure that only authorized users can perform operations.

[0050] Optionally, a listening mechanism is set up when acquiring process task information. This mechanism periodically (e.g., every 15 minutes) queries the task interface to check for new or changed process task information. If new information is detected, the system will process it immediately, parsing the information into actionable approval process change instructions, thereby dynamically updating the approval process.

[0051] Optionally, in a specific embodiment, suppose an airline fare manager logs into the system and submits a task to change the approval process via the task interface, explicitly requesting the addition of a "Product Strategy Approval" node to the special offer product approval process, to be approved by a strategy analyst from the marketing department. The system checks the task interface every 15 minutes according to a predetermined periodic monitoring mechanism. Upon receiving the fare manager's change request, the system immediately parses the information and identifies the requirement to add a node to the approval process. Based on the parsing results, the system automatically adds a "Product Strategy Approval" node to the special offer product approval process and assigns the approval role of the "Product Strategy Approval" node to a strategy analyst from the marketing department. The changed process takes effect immediately, and all new special offer product approvals will follow the updated approval process.

[0052] By periodically monitoring the task interface through the above steps, the fare management system can quickly respond to change requests from target users, dynamically adjust the approval process, and improve the system's flexibility and responsiveness, thereby achieving automation and customization of business processes. This mechanism is particularly suitable for scenarios in airline fare management where approval processes are frequently adjusted, 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 simplifies the process of process changes and improves overall approval efficiency.

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

[0054] Optionally, the freight rate management system retrieves all historical approval processes related to the currently pending approval data from the database. It then performs a hash calculation on the retrieved historical approval process data to generate a first hash value. The hash value is a fixed-length numerical value derived from mathematical operations on the process data, capable of quickly and accurately identifying 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 and second hash values ​​are compared. If the two hash values ​​are not equal, it indicates a difference between the historical and target approval processes, meaning the approval process has changed. The system automatically updates the historical approval processes, creating a new version that includes the target approval process. Simultaneously, the system executes the target approval process.

[0055] Specifically, suppose an airline needs to approve a new fare policy for the Beijing-London route. The system has already determined a target approval process based on business information and approval role information, including four stages: "Policy Maker Approval," "Route Officer Approval," "Regional Manager Approval," and "Marketing Department General Manager Approval," and has configured corresponding approval roles and permissions. All historical approval processes related to the Beijing-London route fare policy approval are retrieved from the database. A hash calculation is performed on these historical approval processes to obtain a first hash value H1. A hash calculation is then performed on the newly determined target approval process to obtain a second hash value H2. Comparing H1 and H2, if H1 ≠ H2, it indicates a difference between the target approval process and the most recent historical approval process version, suggesting that the approval process needs to be updated. The new fare policy for the Beijing-London route is then approved according to the new version of the approval process, ensuring that the approval process follows the settings of the target approval process.

[0056] Through the above steps, not only can changes to the approval process be automatically detected, but the changes can also be accurately identified through hash values, thereby enabling automated iteration of approval process versions and immediate execution of new processes. This mechanism ensures that changes to the approval process take effect promptly, while maintaining the integrity and traceability of historical approval processes, 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 class information, department information, product type information. The approval role information is determined based on the business information, including: obtaining business configuration information, which is used to determine the mapping relationship between business information and approval role; and determining the approval role information based on the business configuration information and the business information.

[0058] Specifically, the system retrieves business configuration information from the management database. This information defines the mapping relationship between business information and approval roles. For example, a specific route may be approved by a particular route coordinator or regional manager. When fare changes are involved for a specific route, the system checks the route information, retrieves the business configuration information, and determines the approval role responsible for that route, such as "route coordinator approval" or "regional manager approval." When an airline plans to adjust the fare for the Beijing-Tokyo route, the system, based on the route information and business configuration information, determines "Beijing-Tokyo route coordinator" as the approval role. Members of this role will participate in the approval process to ensure that the fare adjustment aligns with the route's operational strategy.

[0059] It should be further clarified that an approval role primarily refers to a collection of personnel or positions that perform specific functions or undertake specific approval tasks in the freight rate approval process. An approval role may include one or more actual approvers (roles are named using the character "role"). Each approval role has its specific approval authority and scope of responsibility. For example, "Line Officer Approval," "Regional Manager Approval," or "Marketing Department General Manager Approval" are all different approval roles, representing different levels of approval functions in the freight rate approval process.

[0060] Approval role information provides a more detailed description and configuration of approval roles, including the approval permissions for different process nodes and the relationships between approval roles. Specifically, approval role information covers the name, permissions, scope of operation, and binding status of approval roles to approval process nodes. It may also include dynamic matching rules for approval roles, such as matching different approval roles based on business information like flight routes, departments, and product types, as well as the specific position and flow logic of approval roles within the approval process.

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

[0062] Specifically, when the business information is departmental information, the business configuration information defines the mapping relationship between different departments and approval roles. If a fare change involves a specific department's decision, the system will determine the corresponding departmental approval role based on the business configuration information, such as "Marketing Department Approval" or "Revenue Management Department Approval." For example, if an airline plans to launch a marketing strategy involving preferential fares on multiple routes, the system will match the departmental information to the "Marketing Strategy Approval" process, where the marketing department's strategy analyst will be responsible for approval, ensuring that the fare adjustment aligns with the marketing department's strategic plan.

[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 a fare change involves the release of a new product type, the system will determine the corresponding approval roles 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." For example, an airline plans to launch a brand new "family vacation package" product. The system matches the product type information to the "new product approval process," with multiple roles such as product manager, market analyst, and financial analyst participating in the approval process to ensure that the new product aligns with market trends, is financially feasible, and fits the company's overall product line plan.

[0064] Through the above steps, the approval role information is determined based on business information, ensuring that the approval process can be flexibly adjusted according to the specific business scenario of fare changes. Moreover, by setting up 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, the target approval process is determined based on the approval role information, including: determining the associated user based on the approval role information, wherein the associated user has the permissions possessed by the approval role in the approval role information; establishing the association between the associated user and the approval node and the process reversal rules to obtain the approval process.

[0066] Specifically, based on the role name in the approval role information, users with the same role name are searched. These users are considered associated users and possess 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, associated users are assigned to each approval node in the approval process. For example, for the "Airline Crew Approval" node, the system will find all users associated with this approval role and bind these users to the node. The association between the approval node and associated users can be many-to-one (multiple users can have the same approval permissions, but only one user can approve) or one-to-many (an approval node can be approved by multiple users with the same permissions). The associated users are determined based on the approval role information; that is, the username user1 has the role role1, meaning user1 has the approval permissions and other system permissions for role role1.

[0068] Process reversal rules define how to handle approval failures under different circumstances within the approval process. Rules can be configured to either redirect to a specified approval node or terminate the process directly upon failure. Setting process reversal rules enhances the controllability and adaptability of the approval process, ensuring that the process can be flexibly adjusted according to different approval situations, thereby improving the efficiency and effectiveness of the approval process.

[0069] Specifically, an airline plans to adjust its fare policy for "long-term promotional business class products on European routes." This policy adjustment requires multi-level approval before final implementation. The approval process includes the following stages: Sales Department Supervisor, Fare Supervisor, Regional Manager, and Marketing General Manager. If approval fails at the "Fare Supervisor" stage, the process is redirected to the "Sales Department Supervisor" stage so the Sales Department Supervisor can adjust the policy based on feedback. If approval fails at the "Regional Manager" stage, the process is redirected to the "Fare Supervisor" stage for further review based on the Regional Manager's feedback. If approval fails at the "Marketing General Manager" stage, the process terminates, and the Sales Department must resubmit the revised policy for approval. This process reversal rule not only ensures comprehensive review of fare policy adjustments but also improves efficiency and accuracy by automatically redirecting to specific stages, avoiding unnecessary delays.

[0070] Specifically, the identified approval roles and associated users are linked to nodes in the approval process, and process reversal rules are embedded into 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 that node, and automatically execute the corresponding process reversal rules based on the approval result.

[0071] Through the above steps, a dynamic approval process is formed that can automatically adjust based on business information and approval results. Each node is bound to a specific approval role and associated user, and the flow of the process is preset through 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 also possessing a high degree of customizability, meeting the airline's flexible and personalized needs for fare management approval processes.

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

[0073] Specifically, the system will send the generated reminder information to the associated users via email, SMS, internal system messages, or mobile application notifications. This ensures that approvers are immediately aware that new approval tasks are pending. The reminder information typically includes a brief description of the policy to be approved, the name of the approval node, the actions the approver needs to take, and the approval deadline, among other key information.

[0074] By following the steps above, it is ensured that approvers at each stage of the approval process receive timely notifications of tasks pending approval, 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 further includes: performing process conflict rule verification on the target approval process, which is used to determine whether the execution logic of different process branches of the target approval process is contradictory; and executing the target approval process in response to the successful verification of the process conflict rule.

[0076] Specifically, process conflict rule verification primarily checks for logical conflicts within the approval process, involving the flow of approval nodes, the permissions of approval roles, and the setting of process reversal rules. For example, it checks for contradictory settings where the same approval node needs to be both reversed and terminated under different circumstances; it checks whether the permissions of approval roles within process nodes conform to the preset business logic; and it checks whether process reversal rules lead to an infinitely looping approval process. If the process conflict rule verification passes, it means that the approval process is logically coherent and consistent, and the system can continue executing the target approval process. If a conflict is detected, the system will terminate the process, make adjustments, and continue until the verification passes.

[0077] As can be seen from the above examples, process conflict rule verification is a key step in setting up an approval process. It ensures the logical consistency and rationality of the set target approval process, avoids approval delays or inefficiencies caused by logical errors, and thus guarantees the smoothness and efficiency of the approval process.

[0078] It needs to be further explained that, such as Figure 4 As shown, the workflow task information is configured by the target user. Users primarily use SVG to draw the approval workflow. Four types of legends are defined in the workflow definition: startEvent, sequenceFlow, exclusiveGateway, userTask, and endEvent. startEvent is defined as the start node of the workflow; this node is mandatory for every workflow and marks its beginning. sequenceFlow is a connection that links the paths between nodes. Rules are defined in the sequenceFlow node, and when a rule matches, the user is redirected to the corresponding node. exclusiveGateway is the exclusive gateway node, primarily used to redirect the user to the appropriate node based on the user's approval action. userTask is the approval node of the workflow. Based on role and user data, this node can be configured to specify which roles or users need to approve the workflow. Listening tasks can also be set based on data from the listening management system, allowing other related business logic to be executed before and after the approval node. endEvent is the end node of the workflow, a mandatory node for every workflow, marking the end of the entire workflow.

[0079] According to an embodiment of the present invention, an apparatus embodiment of an approval workflow management method is provided. It should be noted that the apparatus can be used to execute the above-described approval workflow management method.

[0080] Figure 3 A structural block diagram of a control device for an approval workflow management method according to an optional embodiment of the present invention. (See diagram below.) Figure 3 As shown, the device includes:

[0081] Module 301 retrieves process task information. The process task information is configured by the target user and is used to establish an approval process for the data to be approved or to modify the existing approval process for the data to be approved.

[0082] Module 302 determines business information based on process task information. The business information includes the operational information of the target business under different management dimensions.

[0083] The associated module 303 determines the approval role information based on business information. The approval role information includes the approval authority of the process nodes in the approval process and the association relationship of the approval roles.

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

[0085] Optionally, obtaining process task information based on the acquisition module 301 includes: periodically listening to the task interface to obtain process task information, and the task interface is used to interact 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 determined by the determining module 302 includes at least one of the following: route information, cabin class information, department information, and product type information. The approval role information is determined based on the business information, including: obtaining business configuration information, which is used to determine the mapping relationship between business information and approval role; and determining the approval role information based on the business configuration information and the business information.

[0088] Optionally, the associated user is determined based on the approval role information through the association module 303, wherein the associated user has the permissions possessed by the approval role in the approval role information; the association between the associated user and the approval node and the process reversal rule is established to obtain the approval process.

[0089] Optionally, a reminder message can be generated by the control module 304 and sent to the associated user.

[0090] Optionally, the control module 304 performs process conflict rule verification on the target approval process. The process conflict rule verification 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 verification passing, the target approval process is executed.

[0091] In this embodiment of the invention, a custom configuration approval workflow is adopted. By acquiring and parsing the process task information configured by the target user, the operational information of the target business under different management dimensions is determined. Then, based on this business information, the approval role information is dynamically determined. By introducing business information and approval role information, the approval process can be automatically matched according to the specific business scenario and role permissions, avoiding the tediousness and errors of manual intervention. This achieves the goal of flexibly adapting to the diverse approval needs of airlines, thereby realizing the technical effect of efficient, intelligent and dynamic approval process. This solves the technical problem that the fixed operation of the existing fare approval process makes it impossible to flexibly adapt to various approval needs.

[0092] Embodiments of this application also provide an electronic device, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the approval workflow management method of various embodiments of the present invention during runtime.

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

[0094] Step S102: Obtain process task information. The process task information is configured by the target user and is used to establish an approval process for the data to be approved or to modify the existing approval process for the data to be approved.

[0095] Step S104: Determine business information based on process task information. Business information includes operational information of the target business under different management dimensions.

[0096] Step S106: Determine the approval role information based on business information. The approval role information includes the approval authority of the process nodes in the approval process and the association relationship of the approval roles.

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

[0098] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to execute the approval workflow management method of various embodiments 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: Obtain process task information. The process task information is configured by the target user and is used to establish an approval process for the data to be approved or to modify the existing approval process for the data to be approved.

[0101] Step S104: Determine business information based on process task information. Business information includes operational information of the target business under different management dimensions.

[0102] Step S106: Determine the approval role information based on business information. The approval role information includes the approval authority of the process nodes in the approval process and the association relationship of the approval roles.

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

[0104] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the approval workflow management method in various embodiments of the present invention.

[0105] Optionally, in this embodiment, the above-mentioned computer program product can be configured as a computer program that performs the following steps:

[0106] Step S102: Obtain process task information. The process task information is configured by the target user and is used to establish an approval process for the data to be approved or to modify the existing approval process for the data to be approved.

[0107] Step S104: Determine business information based on process task information. Business information includes operational information of the target business under different management dimensions.

[0108] Step S106: Determine the approval role information based on business information. The approval role information includes the approval authority of the process nodes in the approval process and the association relationship of the approval roles.

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

[0110] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer 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. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

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

[0113] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0114] If the integrated unit is implemented as 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. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0115] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A management method for an approval workflow, characterized in that, include: Obtain 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 modify an existing approval process for the data to be approved. Business information is determined based on the process task information, and the business information includes the operational information of the target business under different management dimensions. Based on the business information, approval role information is determined, which includes the approval authority of process nodes in the approval process and the association relationship of approval roles. The target approval process is determined based on the aforementioned approval role information; Obtaining process task information includes: The task interface is periodically monitored to obtain the process task information, and the task interface is used to interact with the target user. After determining the target approval process based on the approval role information, the management method further includes: Obtain historical approval processes; 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 fact that the first hash value and the second hash value are not equal, the historical approval process is versioned and the target approval process is executed. The business information includes at least one of the following: route information, cabin class information, department information, and product type information. Approval role information is determined based on the business information, including: Obtain business configuration information, which is used to determine the 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.

2. The management method according to claim 1, characterized in that, Based on the aforementioned approval role information, the target approval process is determined, including: The associated user is determined based on the approval role information, wherein the associated user has the permissions possessed by the approval role in the approval role information; The associated user, approval node, and process reversal rules are established to obtain the approval process.

3. The management method according to claim 2, characterized in that, After establishing the associations between the associated users, approval nodes, and process reversal rules, the management method further includes: Generate a reminder message and send the reminder message to the associated user.

4. 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: The target approval process is subjected to process conflict rule verification, which is used to determine whether the execution logic of different process branches of the target approval process is contradictory. If the process conflict rule verification passes, the target approval process is executed.

5. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 4.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the storage medium is located to perform the method according to any one of claims 1 to 4.

7. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 4.

Images