A method for rapid approval of business processes based on a low-code platform

Abstract

The present invention belongs to the technical field of data analysis and process mining, and is specifically a method for rapid approval of business processes based on a low-code platform. This method is based on a low-code platform and provides a comprehensive solution for the approval process. First, a custom configuration form is performed, covering field types, dynamic data binding, input verification and field linkage to ensure that the form data is accurate and valid. Then, in the configuration of the approval flow node, node control and collaboration are enhanced through automatic approval, automatic rejection, setting approval time limits and message reminders. Then the business flow and trigger are combined, the business process is sorted out and the system is integrated, and business actions are triggered according to the approval node status and external events to improve process automation and agility. Finally, in the execution stage of the approval process, process automation is realized, including instantiation, node transfer, status update and notification reminder, to ensure efficient and transparent approval, and close connection of each link, which effectively promotes the optimization of enterprise approval processes and digital management upgrades.

Description

Technical Field

[0001] The present invention belongs to the field of information processing technology, and specifically provides a method for rapid approval of business processes based on a low-code platform. Background Art

[0002] In the operation and management of today's enterprises and organizations, the approval process occupies a pivotal position. It runs through many business links, such as financial reimbursement, procurement applications, project approval, contract signing, and personnel affairs processing. It is a key management means to ensure business compliance, rational allocation of resources, and effective risk control.

[0003] The traditional way of building and managing approval processes relies heavily on professional developers writing a lot of code to implement it. This model not only consumes a lot of time, but also has a long development cycle from demand analysis, design, coding to testing, which seriously lags behind the rapidly changing needs of the business. Moreover, the development process involves many technical details and complex logic, which requires high manpower costs, including developer salaries, training costs, and communication and coordination costs. In addition, the approval process built in the traditional way has extremely poor flexibility. Once the business rules change, even minor adjustments, such as adding or removing nodes in the approval process, changing conditions, etc., may require a lot of re-writing of code and system deployment, making it difficult for companies to quickly adapt to market changes and internal management strategy adjustments.

[0004] At the same time, the traditional approval process faces many challenges in terms of coordination between various links. The approval process usually involves multiple departments and many people, and the information transmission between various links often relies on manual operations, which is prone to information gaps and delays. For example, there is a lack of effective status control and message notification mechanisms between approval nodes, which results in the inability of approval personnel to know pending tasks in a timely manner, causing the process to stagnate; the integration depth of the approval process with other business systems is not deep enough, such as the lack of seamless connection with financial systems, procurement systems, human resources systems, etc., forming data islands, making it impossible to share and update data in real time, which seriously affects the efficiency of business execution and the accuracy and timeliness of management decisions. Summary of the invention

[0005] In view of the shortcomings of the existing technology, the present invention proposes a method for rapid approval of business processes based on a low-code platform, which enables users to easily and independently configure the approval process, improve the flexibility and automation of the process, enhance the depth of interaction and collaborative efficiency with the business system, and reduce development and maintenance costs.

[0006] The technical solution of the present invention is as follows:

[0007] In a first aspect, the present invention provides a method for rapid approval of business processes based on a low-code platform, including:

[0008] Users create custom configuration forms based on business needs on the low-code platform to form business processes;

[0009] At each node of the approval process, users can configure multiple process control options to meet the needs of different approval scenarios;

[0010] By combining the approval process with the business process and defining the automatic triggering conditions of each node in the approval process through triggers, the approval process and business process can be integrated and automatically responded to;

[0011] During the approval process execution stage, the approval process is executed automatically, and users can view the execution status of the approval process in real time and track the status of each approval node through the visual interface provided by the low-code platform.

[0012] In combination with the first aspect, in some possible implementations, the custom configuration form includes: configuring field types, dynamic data binding, input verification, and field linkage mechanism.

[0013] In conjunction with the first aspect, in some possible implementations, the configuration field type is a text input box configuration, a number input box configuration, a date selector configuration, or a drop-down selection box configuration;

[0014] Among them, the mandatory information fields in the configuration field type are set as mandatory fields;

[0015] Among them, for the default galaxy in the configuration field type, set the default value;

[0016] Among them, the visibility of the fields is controlled according to different stages of the approval process or different user roles.

[0017] In conjunction with the first aspect, in some possible implementations, the dynamic data binding includes: database field binding, API interface data binding, and user input data binding;

[0018] Among them, database field binding involves database connection configuration and field mapping;

[0019] API interface data binding involves interface selection and authentication as well as data format conversion;

[0020] User input data binding involves real-time monitoring of user input events and data validation.

[0021] In conjunction with the first aspect, in some possible implementations, the input check includes: mandatory item check, format check, and range check;

[0022] Among them, the mandatory field check ensures that the key fields are not empty;

[0023] Format verification ensures that the data format meets the specified requirements;

[0024] Range checking ensures that data values ​​are within the specified range.

[0025] In conjunction with the first aspect, in some possible implementations, the field linkage includes: drop-down box linkage and input box linkage;

[0026] Among them, the drop-down box linkage updates the option list of the target drop-down box according to the value change of the source drop-down box;

[0027] Input box linkage executes preset logical rules according to the triggering event.

[0028] In conjunction with the first aspect, in some possible implementations, the control options in the approval process include:

[0029] Automatic approval technology, including approval condition setting, approval result setting and approval log recording;

[0030] Automatic rejection technology, including setting rejection conditions, setting rejection reasons and post-rejection operations;

[0031] Approval time limit technology, including time limit setting, timeout processing and time limit calculation method;

[0032] Message reminder technology, including reminder method setting, reminder content customization and reminder timing setting.

[0033] In conjunction with the first aspect, in some possible implementations, the integration of the approval process and the business process and the automated response include:

[0034] Business process configuration, including process node setting, process path selection, process variable management and process exception handling;

[0035] Trigger settings, including event triggers, time triggers, condition triggers, and trigger action definitions.

[0036] In conjunction with the first aspect, in some possible implementations, the approval process execution includes:

[0037] Automated execution, including approval task allocation, approval task execution, and approval result recording;

[0038] Status update, including process status update and field status update;

[0039] Notification reminders, including notification method selection, notification content customization and notification timing control.

[0040] In a second aspect, the present invention provides a system for a method for rapid approval of business processes based on a low-code platform, including:

[0041] User interface, which allows users to create custom configuration forms according to business needs and form business processes;

[0042] The approval process configuration module allows users to configure multiple process control options at each node of the approval process;

[0043] The trigger definition module is used to define the automatic triggering conditions of each node in the approval process, so as to achieve the integration of the approval process and the business process and automatic response;

[0044] The approval process execution module is used to automatically execute the approval process and allow users to view the execution status of the approval process in real time;

[0045] Among them, the custom configuration form includes configuration field type, dynamic data binding, input validation and field linkage mechanism;

[0046] A variety of process control options include automatic approval, automatic rejection, approval time limit, and approval message reminder.

[0047] The beneficial effects of the present invention are:

[0048] Highly flexible and customizable: Users can flexibly define form fields, approval flow nodes and trigger conditions according to specific business needs, and can adapt to various complex approval scenarios.

[0049] Improve the degree of automation: Configurations such as automatic approval, automatic rejection, approval time limit, and message reminders in the approval flow make the approval process highly automated, reduce manual intervention, and improve work efficiency.

[0050] Seamless integration of business systems: Through the combination of triggers and business flows, the approval process can automatically link with other business systems of the enterprise (such as financial systems, ERP systems, etc.) to improve the automation and collaborative efficiency of the overall business process.

[0051] Lower technical threshold: The low-code platform provides a graphical configuration interface, which greatly reduces the complexity of development and management, allowing non-technical personnel to easily create and adjust approval processes.

[0052] Improve response speed: The combination of automated approval flow and business flow triggers makes the approval process more efficient and responds to business needs in real time. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 It is the overall flow chart of the present invention;

[0054] Figure 2 is a flowchart of method S100;

[0055] Figure 3 is a flow chart of method S200;

[0056] Figure 4 is a flow chart of method S300;

[0057] Figure 5 is a flow chart of method S400. DETAILED DESCRIPTION

[0058] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0059] See also Figure 1 , which shows a method for rapid approval of business processes based on a low-code platform provided by an embodiment of the present invention, including:

[0060] S100: Users create custom configuration forms on the low-code platform based on business needs to form business processes; custom configuration forms include: configuring field types, dynamic data binding, input verification, and field linkage mechanisms.

[0061] S200: At each node of the approval process, the user configures a variety of process control options to meet the needs of different approval scenarios; the various process control options include: automatic approval, automatic rejection, approval time limit, and approval message reminder.

[0062] S300: By combining the approval process with the business process and defining the automatic triggering conditions of each node in the approval process through triggers, the approval process and business process are integrated and automatically responded.

[0063] S400: During the approval process execution phase, the approval process is executed automatically, and users can view the execution status of the approval process in real time and track the status of each approval node through the visual interface provided by the low-code platform.

[0064] S100 focuses on key technologies in the form construction process. Through in-depth business research, it accurately configures field types, establishes multi-mode dynamic data binding, strictly implements input verification, and flexibly sets field linkage rules. It creates a form system that adapts to business process approval needs and ensures accurate data interaction and efficient flow.

[0065] Please refer to Figure 2 , which shows a flowchart of a method S100 for rapid approval of a business process based on a low-code platform of the present application, and its contents include:

[0066] S110: Field type configuration

[0067] Conduct in-depth research in business departments, collect the information required for forms in various business processes, and select the appropriate standard type based on the characteristics of the collected information.

[0068] Specifically include:

[0069] Text input box configuration: used to enter general text information, such as employee name, project name, notes, etc. You can set a maximum length limit, such as limiting the name field to 50 characters, to ensure the rationality and standardization of the data.

[0070] Number input box configuration: suitable for entering numerical data, such as amount, quantity, age, etc. You can specify the format of the number, such as integer, decimal, and set the number of decimal places. For example, the amount field can be set to retain two decimal places to accurately represent the monetary value.

[0071] Date picker configuration: It is convenient for users to select dates. It can be used to record the time of event occurrence, deadline, etc. Provide a date picker to ensure that the input date format is unified and valid.

[0072] Drop-down selection box configuration: used when certain information has fixed optional values, such as department name, approval status (pending, approved, rejected, etc.). By pre-defining the option list in the background, users can only select the appropriate value from the drop-down list, avoiding the possibility of entering incorrect data.

[0073] For key information, such as the subject of the approval application, the name of the applicant, etc., set them as required fields. In this way, when submitting the form, the system will automatically check whether these fields have been filled in. If they are empty, the user will be prompted to fill them in, ensuring that key information is not missing and the integrity of the approval process.

[0074] Set default values ​​for certain fields based on business logic and common situations. For example, when creating a leave application form, the default value of the leave type field can be set to "annual leave" because annual leave is a common type of leave for employees; the default value of the application date field can be automatically set to the current system date, which is convenient for user operation and reduces the possibility of input errors.

[0075] Control the visibility of fields according to different stages of the approval process or different user roles. For example, when initially submitting an application, some internal note fields that are only visible to the approver can be hidden from the applicant to avoid information confusion. During the approval process, the approver can see these hidden fields and fill in relevant comments, but the applicant cannot view or modify them.

[0076] S120: Dynamic Data Binding

[0077] Dynamic data binding is a key link in implementing the approval process in a low-code platform. It is mainly achieved through three methods: database field binding, API interface data binding, and user input data binding.

[0078] Database field binding: Database field binding is an important way to achieve data interaction in the approval process of low-code platform construction. First, it is necessary to configure the database connection, clarify the database type, accurately set key parameters such as server address, port number, database name, user name and password, so as to establish a stable and reliable connection link between the low-code platform and the database. Next, carefully analyze the database table structure, fully grasp the characteristics of each field, and use the convenient operations provided by the low-code platform, such as visual mapping tools or configuration options, to associate the fields in the form with the corresponding fields in the database table one by one to build an accurate mapping relationship. Finally, in the data synchronization link, when the form is loaded, the system automatically initiates a query request to the database according to the mapping rules, obtains the relevant field data and accurately fills it into the form, and presents it to the user; and when the user modifies the data in the form and submits it, the platform will efficiently write the updated data back to the corresponding field in the database according to the mapping relationship, ensuring that the database and form data are always highly consistent, and realizing seamless interaction and real-time update of data.

[0079] API interface data binding: API interface data binding introduces external data resources to the approval process and enriches the data source. The first is the interface selection and authentication link. According to the business needs of the approval process, carefully select the interface that can provide the required data from the many available APIs. At the same time, according to the authentication method required by the interface, accurately configure the authentication parameters in the low-code platform, such as APIKey authentication or OAuth authentication, to ensure the security and legality of data acquisition. Subsequently, in-depth research on the data format returned by the API, whether it is the common JSON format or other formats, the low-code platform can automatically complete the complex data format conversion and adaptation work according to the requirements of the form fields, ensuring that the data can perfectly meet the form display and processing requirements. Finally, in order to ensure the real-time nature of the data, the platform can send data requests to the API in a timely manner at set time intervals or when specific events are triggered, such as when the form is loaded or the user manually refreshes, etc., to obtain the latest data and dynamically update the relevant fields in the form, so that the form always displays the latest external data information, providing timely and accurate data support for the approval process.

[0080] User input data binding: User input data binding focuses on the data processing of users during form operations. When users perform input operations in the form, whether it is entering text in a text box, selecting options in a drop-down box, or changing the state of a radio button or check box, the low-code platform will monitor in real time through its built-in efficient event processing mechanism. Once the input behavior is detected, the data verification and processing process is immediately started, and the data entered by the user is fully verified in strict accordance with the pre-set rich rules, including the accuracy of the data type, the standardization of the format, the rationality of the numerical range, and other aspects. If the input data does not meet the requirements, the platform will quickly give a clear and clear error prompt to guide the user to enter correctly. After the verification is passed, if there is data that needs additional processing, such as encrypting passwords and formatting text, the platform will execute it in time. At the same time, based on the data entered by the user, according to the pre-configured field linkage rules, other related fields in the form are automatically updated, and the data entered by the user can also interact closely with the complex business logic in the background, such as triggering specific calculation operations and affecting the subsequent direction of the approval process, so as to achieve highly dynamic interaction and precise flow of user input and the entire approval process data.

[0081] S130: Input verification

[0082] Input validation is crucial in the approval process. It uses a series of technical means to conduct a comprehensive check on the data entered by the user in the form, including mandatory field verification, format verification, and range verification, to ensure the accuracy, completeness, and rationality of the input data.

[0083] Required field verification: Required field verification mainly checks the key fields that must be filled in the form. In the low-code platform, developers first clearly specify which fields are required, and this setting is usually completed during the form design phase. When a user submits a form, the system will traverse all fields marked as required and check one by one whether they have been filled in. If a required field is found to be empty, the system immediately blocks the form submission and reminds the user in a striking manner on the front-end interface that the field is required, such as popping up a pop-up window with clear prompt text, or displaying a red asterisk or other mark next to the field. At the same time, detailed help information may be provided to inform users of the importance of the field and how to fill it in, and guide users to supplement the required information until all required items are filled in correctly. The form is allowed to continue to be submitted, thereby ensuring that key information is complete and correct at the beginning of the approval process.

[0084] Format validation: Format validation focuses on checking whether the format of the data entered by the user meets specific requirements. There are corresponding format rules for different types of fields, such as text, numbers, dates, emails, mobile phone numbers, etc. For text fields, regular expressions or predefined patterns may be used to verify their formats, such as verifying whether the ID number meets specific encoding rules, or checking whether the username contains only allowed characters. Numeric fields can be verified to see whether they are integers or decimals, and whether the number of decimal places meets the requirements. Date fields ensure that the entered date format is correct and within a reasonable range. Email fields must follow the standard email address format. When the user enters data, the system triggers format validation in real time or when submitting the form. If the input data does not meet the set format, the system will promptly give a prompt to inform the user of the format error, and may provide examples of the correct format to help users modify the input content so that the data format meets business requirements and ensures the standardization and consistency of the data for subsequent processing and analysis.

[0085] Range check: Range check aims to ensure that the data value entered by the user is within a reasonable range. In the low-code platform, developers set corresponding numerical range limits for different fields based on business rules and the actual meaning of the data. When the user enters data, the system obtains the input value and compares it with the preset range. If the input value exceeds the allowable range, the system will block the operation or prompt the user that the input is wrong when submitting. The prompt message will clearly inform the user that the input value is out of range and give a reasonable range interval to guide the user to adjust the input content to ensure that the data is within the range allowed by the business logic, maintain the rationality and validity of the data, and avoid the negative impact of unreasonable numerical input on the approval process and business decisions.

[0086] S140: Field linkage

[0087] Field linkage is achieved by establishing logical associations between fields. When the value of a field changes, corresponding changes in other related fields are automatically triggered according to pre-set rules, including drop-down box linkage and input box linkage.

[0088] Drop-down box linkage: Drop-down box linkage is mainly to dynamically associate multiple drop-down boxes in a form. In the configuration stage, first determine the source drop-down box that triggers the drop-down box linkage and the target drop-down box associated with it. When the value of the source drop-down box changes, the system will capture this event. Then, according to the pre-defined linkage rules, the option data related to the new value of the source drop-down box is obtained from the data source. After these data are processed, the option list of the target drop-down box is dynamically updated.

[0089] Input box linkage: Input box linkage focuses on establishing a dynamic interactive relationship between the input box and other fields. When setting, clearly define the events that trigger the input box linkage, such as changes in other field values, clicks on specific buttons, etc. When a triggering event occurs, the system performs the corresponding operation according to the pre-written logical rules.

[0090] S200 describes the intelligent processing technology of the approval process. By carefully setting the automatic approval conditions and result rules, comprehensively planning the automatic rejection mechanism, strictly setting the approval time limit and accurately configuring the message reminder strategy, it deeply realizes the automated operation of the approval process, accurate decision-making, efficient time limit control and real-time information access, thereby improving the approval efficiency and quality.

[0091] Please refer to Figure 3 , which shows a flowchart of a method S200 for rapid approval of a business process based on a low-code platform of the present application, and its contents include:

[0092] S210: Automatic approval

[0093] With the help of a low-code platform, automatic approval technology can set approval conditions reasonably, accurately determine the direction of the approval process, automatically process approval results based on preset approval result setting rules, and record approval logs in detail to achieve automated processing of some links in the approval process, improve approval efficiency, reduce manual intervention, and ensure the accuracy and traceability of the approval process and the consistency of approval results.

[0094] Approval condition setting: Approval condition setting is the core link of automatic approval. In the low-code platform, approval conditions are constructed based on business rules and approval requirements, taking into account various data elements in the form, such as field values, data types, data ranges, and logical relationships between different fields. Logical operators can be used to combine multiple conditions into complex judgment expressions. The setting of these conditions must be comprehensive and detailed, covering various possible business scenarios to ensure that automatic approval can accurately identify qualified approval requests, achieve efficient automated processing, and avoid approval risks caused by misjudgment.

[0095] Approval result setting: The approval result setting clarifies the final direction and processing method of the approval process when the automatic approval conditions are met. When the approval condition is judged to be true, the system will perform the corresponding approval or rejection operation according to the preset rules. For approved cases, the system will automatically update the approval status to "passed" and record the passing time as the current system time. At the same time, it can trigger subsequent business processes. If the approval fails, the system will set the approval status to "rejected" and record the rejection reasons in detail. The reasons can be based on pre-set templates or dynamically generated according to specific approval conditions and business logic. The approval result setting ensures the integrity and standardization of the automatic approval process, so that relevant personnel can clearly understand the approval results and their reasons, which is convenient for the smooth development of subsequent business.

[0096] Approval log records: Approval log records are used to track every key step and operation information in the automatic approval process in detail. During the entire automatic approval process, the system will record important information such as the judgment results of each approval condition, approval time, approver, approval action, and related data changes in real time. Approval log records provide a complete historical traceability for the approval process, which helps to discover potential problems, analyze approval efficiency, and meet compliance requirements. It also provides data support for decision-making and ensures the transparency and controllability of the approval process.

[0097] S220: Automatic rejection

[0098] Automatic rejection makes intelligent judgments on approval requests based on pre-set rejection conditions in the approval process. When the conditions are met, the applicant is provided with clear feedback on the rejection reasons according to the set rejection reasons, and the corresponding post-rejection operations are performed.

[0099] Specifically include:

[0100] Rejection condition setting: Rejection condition setting is the key basis for automatic rejection. In the low-code platform, business rules and approval requirements are fully considered, and data factors related to approval are deeply analyzed to build complex rejection conditions. This includes the judgment of the value of a single field in the form and the consideration of the logical relationship between multiple fields.

[0101] Rejection reason setting: The purpose of rejection reason setting is to provide applicants with clear and explicit feedback information so that they can understand the reasons for the rejection. According to different rejection conditions, the system presets corresponding rejection reason templates.

[0102] Post-rejection operation: Post-rejection operation clarifies the processing flow after the approval is automatically rejected. First, the system updates the approval status to "rejected" and records the rejection time. Then, according to the pre-configured notification mechanism, the rejection result and reason are promptly notified to the applicant through system messages, emails or SMS, ensuring that the applicant can obtain the information in the first time. At the same time, the system will perform some additional operations according to business needs, such as tracing the approval process back to a specific node; or in some cases, triggering the linkage of related business systems, such as automatically notifying the procurement department to pay attention to and re-evaluate the procurement plan after the procurement approval is rejected.

[0103] S230: Overall approval time limit

[0104] The approval time limit technology strictly controls the processing time of each approval node in the approval process through reasonable time limit settings, accurate time limit calculation methods and effective timeout processing mechanisms.

[0105] Specifically include:

[0106] Time limit setting: Time limit setting is the basis of approval time limit technology. According to the nature of the approval process, the urgency of the business, and the internal management requirements of the enterprise, a reasonable processing time limit is determined for each approval node. It provides clear standards for subsequent time limit calculation and monitoring to ensure that the approval process proceeds in an orderly manner as planned.

[0107] Timeout processing: Timeout processing is a response measure taken when the approval task cannot be completed within the specified time limit. When the approval task approaches or exceeds the set time limit, the system will automatically trigger the timeout reminder mechanism and send reminder notifications to the approver through various channels to ensure that the approver knows that the task is about to time out or has timed out. If the timeout is not handled, the system will automatically handle it according to the preset rules.

[0108] Time limit calculation method: The time limit calculation method is responsible for accurately calculating the remaining time and deadline of the approval task. The system usually excludes non-working days such as statutory holidays and weekends based on the pre-configured work calendar and only calculates the time on working days. At the same time, special circumstances such as the suspension of approval tasks and the time consumption during the circulation process, which affect the time limit, must also be considered.

[0109] S240: Message reminder

[0110] Message reminder technology pushes approval-related information to relevant personnel in a timely manner during the approval process through diversified reminder method settings, personalized reminder content customization, and precise reminder timing settings, allowing users to grasp the approval dynamics in real time, improve the transparency and collaborative efficiency of the approval process, and ensure the smooth progress of the approval work.

[0111] Specifically include:

[0112] Reminder method setting: Reminder method setting means determining in the low-code platform, based on user preferences and business needs, the channels through which message reminders at each stage of the approval process will be conveyed to relevant personnel, such as system messages, emails, text messages, etc., and the parameters of each reminder method can be configured to ensure that reminders can be delivered to the recipient accurately and in a timely manner, thereby ensuring the effectiveness and stability of information transmission.

[0113] Customization of reminder content: Customization of reminder content allows the low-code platform to flexibly edit the body of the message reminder according to different links of the approval process and specific business scenarios, and present key approval-related information (such as application subject, applicant, approval status, processing time limit, etc.) to the recipient in a personalized, clear and concise manner, so that the recipient can quickly understand the progress of the approval and make corresponding decisions.

[0114] Reminder timing setting: Reminder timing setting is in the low-code platform, combining the approval process nodes and time rules to accurately set when to trigger the message reminder, such as when the approval task is assigned, when the approval deadline is approaching, after the approval is completed, and other key time points, to ensure that the reminder is sent at the most appropriate time, neither too early to cause interference nor too late to cause delays, effectively improving the timeliness and pertinence of information communication.

[0115] S300 aims to build a complete business process architecture technology. By rationally planning process node attributes, cleverly designing multiple process paths, efficiently managing process variables, and properly handling process exceptions, it strives to create a business process system that fits complex business scenarios, ensures that the approval process is robust, flexible, and accurate, and improves the efficiency of enterprise process management.

[0116] Please refer to Figure 4 , which shows a flowchart of a method S300 for rapid approval of a business process based on a low-code platform of the present application, and its contents include:

[0117] S310: Business Process Configuration

[0118] With the help of a low-code platform, business process configuration comprehensively builds and optimizes the approval process through careful planning of process node settings, reasonable design of process path selection, effective implementation of process variable management, and a complete process exception handling mechanism, so that it can adapt to complex and changing business needs, ensure the efficient, stable and accurate operation of the approval process, and improve the overall level of enterprise business process management.

[0119] Specifically include:

[0120] Process node setting: Process node setting is to clarify the key nodes of each stage of the approval process in the low-code platform, determine the role, responsibilities, operation type and related attributes of each node, build the basic framework of the approval process, and ensure that each link of the process is clear, orderly and in line with business logic.

[0121] Process path selection: Process path selection is based on conditional judgments and business rules in the approval process. Multiple possible process directions are set on the low-code platform. By analyzing the relationships between nodes and data conditions, the flow path of approval tasks between different nodes is dynamically determined, so that the approval process can flexibly adapt to various business scenarios according to actual conditions, and achieve efficient and accurate process advancement.

[0122] Process variable management: Process variable management in the low-code platform involves defining, storing, and operating variables related to the approval process. These variables can be used to record process status, transfer data, control process direction, etc. By reasonably managing the scope, initial value, and update mechanism of the variables, the consistency and accuracy of the data in the entire approval process can be ensured, providing the necessary data support for the smooth operation of the process.

[0123] Process exception handling: Process exception handling is to formulate response strategies and processing mechanisms in advance on the low-code platform for errors, interruptions or unexpected situations (such as system failures, data conflicts, approval timeouts, etc.) that may occur in the approval process. Through logging, error prompts, rollback operations, manual intervention, etc., it ensures that the approval process can maintain a certain stability and recoverability in abnormal situations, thereby minimizing the impact on the business.

[0124] S320: Trigger Settings

[0125] By carefully defining events, time, conditional triggers and the actions associated with them on the low-code platform, a sensitive automated trigger mechanism is built to perceive business events in real time, follow time plans, and accurately trigger approval processes and related operations based on conditional judgments. This deeply integrates business and process logic, effectively improving the system's level of automation and business response efficiency.

[0126] Specifically include:

[0127] Event triggers: Event triggers monitor and capture based on specific business events (such as order creation, data update, user operation, etc.). In the low-code platform, when a preset business event occurs, it immediately triggers the subsequent approval process or related business actions, realizing real-time linkage between the business system and the approval process, and ensuring that the process responds immediately to business changes.

[0128] Time trigger: Time trigger works on the low-code platform based on the set time rules (such as timed periods, specific date and time points). When the scheduled time is reached, it automatically starts the approval process or executes specific business tasks. It is often used for periodic business processing, timed reminders, or process advancement based on time nodes to ensure that the process is executed accurately in sequence.

[0129] Conditional triggers: Conditional triggers evaluate conditional expressions set for business data or system status (such as data values ​​meeting a specific range, status conforming to specific logic, etc.), and trigger corresponding approval processes or operation changes when the low-code platform determines that the conditions are met. The process is driven by data, allowing the process to flexibly respond to business rules and data scenarios.

[0130] Trigger action definition: Trigger action definition is the specific operation to be performed after the event, time, or condition trigger is triggered on the low-code platform. It covers various action types such as process startup, data update, task assignment, message notification, etc., and accurately configures the action sequence corresponding to each trigger to ensure the consistency and accuracy of business processes and system behaviors after triggering.

[0131] S400 is an execution and monitoring technology that ensures efficient and collaborative approval processes. It relies on intelligent allocation of approval tasks, standardized execution of approval operations, detailed recording of approval results, real-time updating of process and field status, and proper control of notification reminders to fully achieve automated execution of approval processes, accurate status management, and timely communication of information, thereby promoting smooth operation and collaborative work of approval processes.

[0132] Please refer to Figure 5 , which shows a flowchart of a method S400 for rapid approval of a business process based on a low-code platform of the present application, and its contents include:

[0133] S410: Automated Execution

[0134] Automated execution on a low-code platform achieves automated operation and precise control of the entire approval process from task distribution to decision implementation through intelligent approval task allocation, smooth task execution process and rigorous approval result recording mechanism.

[0135] Specifically include:

[0136] Approval task allocation: Approval task allocation is based on approval process rules and role permissions. Approval tasks are accurately pushed to designated approvers or role queues on the low-code platform, taking into account node settings, personnel responsibilities and business needs to ensure that task allocation is reasonable and efficient, laying the foundation for the orderly advancement of the approval process.

[0137] Approval task execution: Approval task execution means that after receiving the task, the approver will review, judge and make decisions (such as approval, rejection, return for modification, etc.) on the approval matters based on the approval standards and business knowledge in the operation interface provided by the low-code platform. The operation may also involve auxiliary functions such as data query, collaborative communication and electronic signature to achieve effective implementation of key links in the approval process.

[0138] Approval result records: With the help of the data storage and management functions of the low-code platform, approval result records store and archive the final decision results of the approval tasks (key information such as approval, rejection, return and modification details and corresponding time, approval opinions, etc.) in a detailed, accurate and tamper-proof manner, providing solid data support for process tracing, statistical analysis and business collaboration.

[0139] S420: Status Update

[0140] Status update uses the low-code platform function mechanism to update the overall status of the process and the status of form field attributes in real time according to the evolution of the approval process, business logic drive and actual data interaction.

[0141] Specific content includes:

[0142] Process status update: The process status update on the low-code platform changes the overall status of the approval process (such as pending approval, under approval, passed, rejected, etc.) in real time and accurately based on the approval process advancement nodes, approval operation results and business rule changes, and simultaneously updates it to relevant system modules and user interfaces, providing accurate guidance for process monitoring, collaboration and subsequent business connections.

[0143] Field status update: Field status update is based on data changes, business logic verification and user interaction operations in the approval process, and dynamically adjusts specific field attributes in the form (such as editability, visibility, data validity, etc.) on the low-code platform to ensure that the field status is consistent with the process progress and business needs, assist users to accurately enter and view data, and ensure the consistency and integrity of process data.

[0144] S430: Notification reminder

[0145] Notification reminders utilize the functions of the low-code platform to send customized, high-value information to relevant personnel in a timely manner throughout the approval process by reasonably selecting notification methods, carefully crafting notification content, and accurately controlling the timing of notifications, thereby improving approval transparency and coordination, and promoting smooth and efficient operation of the approval process.

[0146] Specific contents include:

[0147] Notification method selection: Notification method selection is to determine the appropriate information delivery channel from a variety of optional channels (such as system messages, emails, SMS, instant messaging tools, etc.) on the low-code platform based on different user roles, business scenario requirements and system integration conditions, to ensure that the notification can accurately reach the target audience and achieve efficient and timely information delivery.

[0148] Notification content customization: Notification content customization on the low-code platform is based on key information at each stage of the approval process (such as application details, approval results, process progress, next operation prompts, etc.) and differences in recipients' concerns. It uses a combination of templates and personalization to carefully arrange the content of the notification body, so that it can clearly, accurately and richly convey necessary approval information to recipients, thereby enhancing information value and readability.

[0149] Notification timing control: Notification timing control uses the preset rules of the low-code platform and real-time monitoring of changes in the approval process status to accurately grasp the best time to send notifications (such as after the application is submitted, when the approval node is flowing, when the deadline is approaching, when the task is completed, etc.), avoid interference or delays caused by early or late notifications, ensure the effectiveness and guiding role of notifications, and help advance the process efficiently.

[0150] The basic principles of the present application are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present application are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present application. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, not for limitation, and the above details do not limit the present application to being implemented by adopting the above specific details.

[0151] The block diagrams of the devices, apparatuses, equipment, and systems involved in this application are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagram. As will be appreciated by those skilled in the art, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including", "comprising", "having", etc. are open words, referring to "including but not limited to", and can be used interchangeably with them. The words "or" and "and" used here refer to the words "and / or" and can be used interchangeably with them, unless the context clearly indicates otherwise. The words "such as" used here refer to the phrase "such as but not limited to", and can be used interchangeably with them.

[0152] It should also be noted that in the apparatus, device and method of the present application, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present application.

[0153] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present application. Therefore, the present application is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features of the present invention.

[0154] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for rapid approval of business processes based on a low-code platform, characterized in that: include: Users create custom configuration forms based on business needs on the low-code platform to form business processes; At each node of the approval process, users can configure multiple process control options to meet the needs of different approval scenarios; By combining the approval process with the business process and defining the automatic triggering conditions of each node in the approval process through triggers, the approval process and business process can be integrated and automatically responded to; During the approval process execution stage, the approval process is executed automatically, and users can view the execution status of the approval process in real time and track the status of each approval node through the visual interface provided by the low-code platform.

2. The method for rapid approval of business processes based on a low-code platform according to claim 1 is characterized in that: The custom configuration form includes: configuring field types, dynamic data binding, input verification and field linkage mechanism.

3. The method for rapid approval of business processes based on a low-code platform according to claim 2 is characterized in that: The configuration field types include text input box configuration, number input box configuration, date selector configuration, and drop-down selection box configuration; Among them, the mandatory information fields in the configuration field type are set as mandatory fields; Among them, for the default galaxy in the configuration field type, set the default value; Among them, the visibility of the fields is controlled according to different stages of the approval process or different user roles.

4. The method for rapid approval of business processes based on a low-code platform according to claim 2 is characterized in that: The dynamic data binding includes: database field binding, API interface data binding and user input data binding; Among them, database field binding involves database connection configuration and field mapping; API interface data binding involves interface selection and authentication as well as data format conversion; User input data binding involves real-time monitoring of user input events and data validation.

5. The method for rapid approval of business processes based on a low-code platform according to claim 2 is characterized in that: The input verification includes: required item verification, format verification and range verification; Among them, the mandatory field check ensures that the key fields are not empty; Format verification ensures that the data format meets the specified requirements; Range checking ensures that data values ​​are within the specified range.

6. The method for rapid approval of business processes based on a low-code platform according to claim 2 is characterized in that: The field linkage includes: drop-down box linkage and input box linkage; Among them, the drop-down box linkage updates the option list of the target drop-down box according to the value change of the source drop-down box; Input box linkage executes preset logical rules according to the triggering event.

7. The method for rapid approval of business processes based on a low-code platform according to claim 1 is characterized in that: The control options in the approval process include: Automatic approval technology, including approval condition setting, approval result setting and approval log recording; Automatic rejection technology, including setting rejection conditions, setting rejection reasons and post-rejection operations; Approval time limit technology, including time limit setting, timeout processing and time limit calculation method; Message reminder technology, including reminder method setting, reminder content customization and reminder timing setting.

8. The method for rapid approval of business processes based on a low-code platform according to claim 1 is characterized in that: The integration of approval process and business process and automated response include: Business process configuration, including process node setting, process path selection, process variable management and process exception handling; Trigger settings, including event triggers, time triggers, condition triggers, and trigger action definitions.

9. The method for rapid approval of business processes based on a low-code platform according to claim 1 is characterized in that: The approval process execution includes: Automated execution, including approval task allocation, approval task execution, and approval result recording; Status update, including process status update and field status update; Notification reminders, including notification method selection, notification content customization and notification timing control.

10. A system for a method for rapid approval of business processes based on a low-code platform according to any one of claims 1 to 9, characterized in that: include: User interface, which allows users to create custom configuration forms according to business needs and form business processes; The approval process configuration module allows users to configure multiple process control options at each node of the approval process; The trigger definition module is used to define the automatic triggering conditions of each node in the approval process, so as to achieve the integration of the approval process and the business process and automatic response; The approval process execution module is used to automatically execute the approval process and allow users to view the execution status of the approval process in real time; Among them, the custom configuration form includes configuration field type, dynamic data binding, input validation and field linkage mechanism; A variety of process control options include automatic approval, automatic rejection, approval time limit, and approval message reminder.

Images