Business process node configuration method and device, electronic equipment and storage medium

Abstract

The invention discloses a business process node configuration method and device, electronic equipment and a storage medium. The method comprises the following steps: in response to an association form selection instruction, obtaining a target large form corresponding to a process node configuration requirement of a current service; in response to an initiating node configuration instruction, selecting a first type of target components from the target large form to realize initiating node configuration of the current service; and in response to a task node configuration instruction, selecting a second type of target component from the target large form to realize form content configuration of the task node, and realizing operation button configuration of the task node according to a service triggering demand of the task node. According to the technical scheme, the adaptability of complex service scenes and the flexibility of event triggering are improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a configuration method, device, electronic device and storage medium for a business process node. Background Art

[0002] In various low-code platforms, the process engine has always played a very important role as the core module that connects work orders and business flows, and associates forms and operating instructions. Most of the existing traditional process engines or process centers will configure forms, operating instructions, trigger events, and other content for process nodes. Among them, when configuring different forms for different nodes, it is necessary to split the business form content into different small forms or sub-forms and configure them on the corresponding nodes; the operating instructions of the process nodes are buttons that can be operated by the handlers at each link in the process flow. After the business is initiated and circulated, the operating buttons of each node are displayed on the node page; the trigger event configuration of the process node corresponds to the configuration at the node level, that is, a single node selects the corresponding trigger event content for configuration. Summary of the invention

[0003] The present invention provides a configuration method, device, electronic device and storage medium for a business process node, so as to improve the adaptability of complex business scenarios and the flexibility of event triggering.

[0004] According to one aspect of the present invention, a method for configuring a business process node is provided, the method comprising:

[0005] In response to the associated form selection instruction, the target large form corresponding to the process node configuration requirement of the current business is obtained;

[0006] In response to the initiating node configuration instruction, selecting a first type of target component from the target large list to implement the initiating node configuration of the current service;

[0007] In response to the task node configuration instruction, a second type of target component is selected from the target large form to implement the form content configuration of the task node, and the operation button configuration of the task node is implemented according to the business triggering requirements of the task node.

[0008] According to another aspect of the present invention, a device for configuring a business process node is provided, the device comprising:

[0009] A target large form acquisition module is used to respond to the associated form selection instruction and acquire the target large form corresponding to the process node configuration requirement of the current business;

[0010] An initiating node configuration module, configured to select a first type of target component from the target large list to implement the initiating node configuration of the current service in response to an initiating node configuration instruction;

[0011] The task node configuration module is used to respond to the task node configuration instruction, select the second type of target component from the target large form to implement the form content configuration of the task node, and implement the operation button configuration of the task node according to the business trigger requirements of the task node.

[0012] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0013] at least one processor; and

[0014] a memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for configuring a business process node described in any embodiment of the present invention.

[0016] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for configuring a business process node according to any embodiment of the present invention when executed.

[0017] The technical solution of the embodiment of the present invention obtains the target large form corresponding to the process node configuration requirement of the current business by responding to the associated form selection instruction; responding to the initiation node configuration instruction, selects the first type of target component from the target large form to implement the initiation node configuration of the current business; responds to the task node configuration instruction, selects the second type of target component from the target large form to implement the form content configuration of the task node, and implements the operation button configuration of the task node according to the business trigger requirement of the task node, adopts the method of selecting components from the large form according to the requirements to implement the node form content configuration, and configures the node trigger operation on the operation button, which solves the problems of high configuration complexity in complex business scenarios in the prior art, and limiting the flexibility of event triggering due to the configuration of the trigger operation at the node level, thereby improving the adaptability of complex business scenarios and the flexibility of event triggering.

[0018] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0020] Figure 1a A flowchart of a method for configuring a business process node provided by an embodiment of the present invention;

[0021] Figure 1b A schematic diagram of a configuration interface of an operation button is provided for an embodiment of the present invention;

[0022] Figure 1c A schematic diagram of a trigger event setting interface is provided for an embodiment of the present invention;

[0023] Figure 2 A schematic diagram of a form content configuration interface of a government service initiation node is provided for an embodiment of the present invention;

[0024] Figure 3 A schematic diagram of the structure of a device for configuring a business process node provided by an embodiment of the present invention;

[0025] Figure 4 It is a structural schematic diagram of an electronic device for implementing the method for configuring a business process node according to an embodiment of the present invention. DETAILED DESCRIPTION

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

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

[0028] Figure 1a The flowchart of a method for configuring a business process node provided by an embodiment of the present invention is applicable to the case of configuring a business process node. The method can be executed by a configuration device for a business process node. The configuration device for a business process node can be implemented in the form of hardware and / or software. The configuration device for a business process node can be configured in a server of an integrated process node configuration platform. Figure 1a As shown, the method includes:

[0029] S110 . In response to the associated form selection instruction, a target large form corresponding to the process node configuration requirement of the current business is obtained.

[0030] The associated form selection instruction may refer to an instruction for selecting a matching business form for the current business. For the associated form matching the business process, a locally configured form may be used, or a third-party form disclosed by a third party may be called, that is, in this embodiment, the form configuration engine of the process node configuration platform may be used to pre-configure the required global content form for the business process and use it as the associated form, or a third-party form may be called as the associated form.

[0031] The association form of this embodiment can be designed as a large form including multiple component levels, where each component can have a corresponding attribute selection setting. For example, the large form includes component 1, component 2, and component 3. Business process node 1 selects component 1 and component 2, business process node 2 selects component 1 and component 3, and business process node 3 selects component 2 and component 3. This setting can configure all form contents involved in the business process as a whole, without the need to split the business form into multiple different small forms or sub-forms when configuring different forms for different nodes.

[0032] The target big form may refer to a big form selected from multiple big forms that matches the current business. Configuration personnel can pre-configure different big forms for various business processes based on the form configuration engine of the process node configuration platform, and then select the required target big form from multiple big forms when configuring the business process nodes. A third party can also disclose third-party big forms required for various business processes for access by demanders. It should be noted that when a third-party big form is accessed, the form rendering structure data can be provided at the same time, and docking is performed in accordance with the third-party big form access specifications uniformly specified by the process node configuration platform, so that the component information and corresponding data information in the third-party big form can be read and identified later.

[0033] In an optional implementation, in response to an associated form selection instruction, obtaining a target large form corresponding to the process node configuration requirements of the current business may include: in response to a form type selection instruction, obtaining a target form type corresponding to the process configuration requirements of the current business; in response to a form instance selection instruction, selecting a target large form from a form list corresponding to the target form type.

[0034] The form type selection instruction may refer to a selection instruction for an associated form type, wherein the associated form type may include a locally configured large form or a third-party large form. The target form type may refer to a large form type that matches the current business, a locally configured large form or a third-party large form. The form instance selection instruction may refer to an instruction to select a specific large form from a list of subordinate large forms of a certain form type.

[0035] In this embodiment, after judging the target form type selected by the current business according to the form type selection instruction, the target large form instance required to be associated with the current business is selected from multiple forms under the target form type in response to the form instance selection instruction. The components in the associated target large form and the fields corresponding to the components can be used as variables in subsequent configurations.

[0036] S120 . In response to the initiating node configuration instruction, select a first type of target component from the target large list to implement the initiating node configuration of the current business.

[0037] The initiating node configuration instruction may be a configuration instruction for the node initiating the current service. The first type of target components may be selected from multiple components in the target large form according to the service requirements of the initiating node.

[0038] In this embodiment, in response to the configuration instruction of the initiating node from the configuration personnel, the corresponding component can be selected from the target large list to implement the configuration of the initiating node.

[0039] In an optional implementation, selecting a first type of target component from a large target form to implement the initiation node configuration of the current business may include: determining the operator type of the initiation node; based on the operator type of the initiation node, selecting a first type of target component that matches the operator type from the large target form to implement the form content configuration of the initiation node of the current business.

[0040] Since the business initiation node may be operated by different persons (e.g., the business applicant himself, the window staff acting on behalf of the applicant, etc.), the form content of the initiation node seen by different types of operators may be different. For example, the content seen by the window agent may have more components with unique attributes than the business applicant himself. In this embodiment, for example, the operator type of the initiation node can be determined by identifying the identity information of the operator (e.g., the identity of the operator can be determined by login account information, etc.), and then in response to the form content configuration instruction of the initiation node, the form content configuration of the initiation node is implemented by selecting the component corresponding to the operator type according to the operator type.

[0041] Exemplarily, when setting form fields, you can set whether the form fields are read-only, hidden, editable, and window-specific. When "Read-only" is checked, it means that the component corresponding to the field is only readable and not editable in the current node form; when "Hide" is checked, it means that the component corresponding to the field is invisible in the current node form; when "Edit" is checked, it means that the component corresponding to the field can be edited and operated in the current node form; the three options of "Read-only", "Hide", and "Edit" are a group of radio buttons. After the "Window-specific" option is checked, the component field will only appear in the form of the window staff, and the visibility and editability of the component field are controlled by the three options of "Read-only", "Hide", and "Edit".

[0042] S130 , in response to the task node configuration instruction, select the second type of target component from the target large form to implement the form content configuration of the task node, and implement the operation button configuration of the task node according to the business triggering requirements of the task node.

[0043] Among them, the task node configuration instruction can be a configuration instruction for the task processing link node of the current business, such as the proposed processing node, the staff 1 review node, the staff 2 review node, the transfer node, etc. The second type of target components can be certain components selected from multiple components of the target large form according to the business requirements of the task node. The business trigger requirement can refer to the trigger operation requirement of the task node.

[0044] In this embodiment, in response to the configuration instruction of the task node, the second type of target component can be selected from the target large form to implement form content configuration for the task node, and to implement business trigger requirement configuration for the operation button of the task node.

[0045] Optionally, the task node of this embodiment is operated by business staff; accordingly, selecting a second type of target component from the target large form to implement the form content configuration of the task node may include: selecting a group of second type of target components that match the business staff from the target large form to implement the form content configuration of the task node.

[0046] For example, the attribute settings of the task node's form fields, such as whether they are read-only, hidden, or editable, and other settings can be consistent with the configuration process of the initiating node. Since the task node is operated by business staff, "window-specific" attribute settings may not be involved.

[0047] In an optional implementation, implementing the operation button configuration of the task node according to the business trigger requirements of the task node may include: selecting the target operation button required by the task node from the target large form according to the business requirements of the task node; classifying the target operation button according to the task status in response to the operation button classification instruction; and triggering and configuring the target operation button in response to the operation button trigger configuration instruction.

[0048] In this embodiment, business operation buttons can be set for task nodes. Specifically, corresponding operation buttons can be selected for task nodes according to the business needs of task nodes. For example, buttons such as "process" and "return" can be set for audit nodes. The name of the operation button, whether it is the main button, whether it is associated with a sub-process, whether it is enabled (the enabled button can appear in the runtime node operation page), the default approval opinion and other contents can be configured. Operation buttons can also be distinguished according to the status of the task "to be done" and "done". Such settings can meet different operation requirements for work orders under different processing states. Exemplarily, the operation buttons that support the "to be done" status may include: add signature, process, return, terminate, entrust, forward, copy, select branch for processing, return to the person in charge and other operation buttons; the operation buttons that support the "done" status may include: withdraw, urge, copy and other operation buttons. Figure 1b A schematic diagram of a configuration interface of an operation button is provided for this embodiment.

[0049] The trigger configuration of the action button can be managed through the action settings.

[0050] Optionally, in response to an operation button trigger configuration instruction, trigger configuration of a target operation button may include: in response to an operation button trigger event configuration instruction, trigger event configuration of the target operation button according to a trigger event configuration template; in response to an operation button trigger document configuration instruction, trigger document configuration of the target operation button according to a preconfigured document template; in response to an operation button trigger notification configuration instruction, trigger notification configuration of the target operation button according to business notification requirements.

[0051] In this embodiment, the trigger configuration of the operation button may include trigger event configuration, trigger document configuration, trigger notification, etc.

[0052] Specifically, for an operation button that has a trigger event configuration requirement, a trigger event configuration may be performed for the operation button in response to an operation button trigger event configuration instruction.

[0053] For example, for a work order in the "To Do" state, enable the "Process", "Return", and "Cc" buttons, and you can associate and set trigger events in the three buttons respectively. The set event API (Application Programming Interface) supports the platform's internal API and event API calls of third-party applications. In this way, associating event triggers with operation buttons instead of process nodes can meet more flexible event trigger call requirements.

[0054] Figure 1c A schematic diagram of a trigger event setting interface is provided for this embodiment: it may include event name, event API type (platform internal API, third-party application API, etc.), event API address, event API request method, event string parallel type (serial event, parallel event, etc.), event triggering rule, etc. Event calls are made through the event API address. Serial events refer to events and process nodes being triggered serially, such as task nodes, after the trigger event is executed, the task node content is performed. Parallel events refer to trigger events and process nodes being performed in parallel at the same time.

[0055] Specifically, for an operation button that has a trigger document configuration requirement, a trigger document configuration can be performed for it in response to an operation button trigger document configuration instruction.

[0056] The trigger document of this embodiment may refer to an official document, and specifically, the form component fields may be obtained as variables through the work order variables (work order number, business number, business subject, name of the person handling the document, processing date, name of the implementing organization, work order number_year number, etc.) to configure the document. When the operation button triggers the document setting, if the current button is operated, the document can be generated according to the work order variables.

[0057] Specifically, for an operation button that has a trigger notification configuration requirement, a trigger notification configuration may be performed for the operation button in response to an operation button trigger notification configuration instruction.

[0058] In this embodiment, various notification contents can be set on different operation buttons according to the needs of node business, including triggering conditions for notification (reference rule records in the rule engine), notification recipients (recipients can be set to be the current node processor, the previous node processor, the applicant, the business initiator, other persons in the address book, etc.), notification message content, notification message sending channels (including SMS, in-site messages, WeChat / enterprise WeChat / government WeChat, etc.), etc.

[0059] The technical solution of the embodiment of the present invention obtains the target large form corresponding to the process node configuration requirement of the current business by responding to the associated form selection instruction; responding to the initiation node configuration instruction, selects the first type of target component from the target large form to implement the initiation node configuration of the current business; responds to the task node configuration instruction, selects the second type of target component from the target large form to implement the form content configuration of the task node, and implements the operation button configuration of the task node according to the business trigger requirement of the task node, adopts the method of selecting components from the large form according to the requirements to implement the node form content configuration, and configures the node trigger operation on the operation button, which solves the problems of high configuration complexity in complex business scenarios in the prior art, and limiting the flexibility of event triggering due to the configuration of the trigger operation at the node level, thereby improving the adaptability of complex business scenarios and the flexibility of event triggering.

[0060] Optionally, the business process node configuration method may further include: responding to a timeout configuration instruction of a task node, and configuring a timeout reminder for the task node according to a business timeliness requirement of the task node.

[0061] In this embodiment, the task handling of the task node often has a time limit, so the reminder notification sending setting of the node is about to time out can be set as needed. That is, set a message reminder of certain notification channels to the receiving personnel at a certain time point when the task node is about to time out. The setting content of the timeout reminder message can be basically the same as the setting content of the notification triggered by the above-mentioned operation button, and can include the timeout reminder trigger condition, notification recipient, notification message content, notification message sending channel, etc. When the business is running, when the time limit reaches the trigger condition, the trigger timeout reminder notification message can be sent to the corresponding receiving personnel through the set sending channel.

[0062] Optionally, this embodiment can also set trigger events for the initiating node and the ending node according to business needs. The setting process can be consistent with the trigger event setting process of the task node, including event name, event type (initiating node, ending node, obtaining variable control, etc.), event API type (platform internal API, third-party application API, etc.), event API address, event API request method, event string parallel type (serial event, parallel event, etc.) and event triggering rules.

[0063] Optionally, a copy function can be set for the configuration of the above business process nodes, for example, the form field configuration content of a node can be copied to other nodes with the same requirements. This setting can reduce the settings of other links when the form field configuration volume is large. This embodiment can also set an effect preview function for the configured form content of the node.

[0064] In order to make those skilled in the art better understand the configuration method of the business process node of this embodiment, the following is an explanation of the process node configuration of government affairs business. After the configuration is completed and the business is released, the business can be run through the operation buttons configured in each node to perform business operations such as application acceptance and approval.

[0065] 1. Associated with the big form: The form of business 1 is a configuration form. For example, the big form involves 59 form components. When configuring the process attributes, select the form of business 1 for association. The subsequent configuration process will also use the components and corresponding fields of the current form for conditional judgment and combination, and set visible, editable, window-specific and other properties to meet the different requirements of each node for form content.

[0066] 2. Set the trigger events of the process start and end nodes: Since business 1 can be initiated online by user 1 who needs to handle business 1, or by the window staff who registers the information of business 1 in the system, both scenarios do not involve event triggering of the start node. At the completion node of business 1, it is completed after review by leader 1, and does not involve event triggering. Therefore, the event trigger configuration of the start and end nodes can be excluded in the process setting of business 1.

[0067] 3. Set the form content of the application (initiation) node: According to business needs, set the form for user 1 in the online business 1 application page in the business 1 initiation link, refer to Figure 2 , set the "read-only", "hide", and "edit" attributes of 59 components respectively. When it is judged that the component is a window-specific component, check the corresponding "window-specific". At this time, the component will only appear on the page where the window staff registers the business 1 information, and the "read-only", "hide", and "edit" attributes of the component are still valid, and the effect of its settings only corresponds to the window registration page. This can meet the needs of window registration personnel to increase the real record of the on-site business 1 situation. For example, if the "abnormal" drop-down selection component is set to be window-specific, when an abnormal situation occurs at the business 1 window, the window staff can register the abnormal situation. In addition, the initial node form configuration content is quite different from the form content of the subsequent processing link, so it is not set to be copied to other links in this link. At this time, you can click "Form Preview" to view the effect of the current node form.

[0068] 4. Set the form field content of the manual task node: When setting the form content of other nodes (such as the proposed node) of the business 1 process, the visible and operable form content needs to be set according to the processor of the proposed node (generally the person in charge). For example, the "feedback content" filled in by user 1 is not allowed to be modified by subsequent processors, and it needs to be set to "read-only" in the proposed node; the "notify user 1" button can only be operated to send a text message to user 1 in the proposed node, so it is only set to "editable / operable" in this node, and other nodes are set to "read-only" or "hidden". Considering that the form content of the proposed node and the subsequent transfer, transfer, transfer, and handling nodes are basically the same, it can be copied to the above four nodes to reduce the overall configuration workload.

[0069] 5. Set the operation buttons of the manual task node: Taking the proposed node of business 1 as an example, the proposed node needs to use the "add signature", "process", "copy" and "copy" operation buttons of the pending state, and the "copy", "withdraw", "urge" and other operation buttons of the completed state, so the above 6 operation buttons can be enabled in the operation attribute configuration. Configure the name of the above operation buttons, whether it is the main button, whether it is associated with the sub-process, whether it is enabled, the default approval opinion, etc.

[0070] (1) Set the triggering events of each operation button: According to the needs of business 1, configure the events to be triggered in the above 6 operation buttons. If no other events need to be triggered at the processing node, there is no need to configure the corresponding events. In the transfer node, the processing button needs to trigger the file sending, call the file generation and sending event, which is provided by the official document system. Configure its event API address, event name (transfer document sending), event parallel, etc. This event is triggered when the button is clicked, and there is no need to configure the triggering conditions of the event.

[0071] (2) Set the trigger documents for each operation button: Configure the trigger documents for the above 6 operation buttons according to the needs of Business 1. The 6 operation buttons of the proposed node do not involve document triggering, so the corresponding trigger documents do not need to be configured. In the "Process" button of the "Transfer" node, you need to select and configure the "Letter for Transferring Business 1 Matters" document, that is, when you click the "Process" button in the transfer node, the "Letter for Transferring Business 1 Matters" document will be triggered. The variables in the document are replaced with the work order variables and form variables of the current node.

[0072] (3) Set the trigger notification of each operation button: Configure the trigger notification of the above 6 operation buttons according to the needs of business 1. For example, the "Handle" button is configured to notify user 1 to receive the business 1 file. The recipient is user 1, and the message content is "{{$metadata_1699XXXXXXXXX}}: The business 1 matter you reported has been registered with the letter number ${workOrderNum!}. After research, it falls within the prescribed acceptance scope. Our office will accept it. XX Province Business Office ${handlerDate!}" Among them, the work order variables such as initiator, work order change, and processing date are replaced by the work order content during business handling. Similarly, the "Handle" button of the "Transfer", "Transfer", "Transfer and Delivery" nodes are all configured with trigger message notifications.

[0073] 6. Set timeout reminders for manual task nodes: According to the timeliness requirements of business 1 node, set timeout reminders for certain nodes. For example, set timeout reminders for review nodes such as "Leader 1 Review" and "Leader 2 Review". When a work order has not been processed for more than 24 hours after arriving at the node, a message with the content "You have a business work order that is about to time out, please process it in time, work order number ${code}" is sent to the node processor. When the business flow is transferred to the node and the reminder conditions are met, a message is sent to the node processor.

[0074] After setting up the form and nodes of business process 1 as above, publish the business and enter the business operation stage.

[0075] When the business is running, user 1 and the window staff can register the business on their respective access pages. User 1 and the window staff each see different business registration forms to fill in the business information. After completing the registration and submitting, the business work order will generate a to-do task corresponding to the next node.

[0076] When the person handling the pending tasks at each node enters the pending task details page to process, he can view the corresponding form page to view the content and modify the editable content. And select the operation button to perform the operation processing of the pending status.

[0077] When you click the operation button, the system triggers event calls, document generation, and notification message delivery according to the configuration content. For example, when the "Plan to Handle", "Transfer", "Transfer", "Transfer and Delivery" nodes are pending, the "Handle" button triggers a notification message; when the "Transfer" node is pending, click the "Handle" button to trigger the generation of the "Letter on Transferring Business 1" document; in the "Transfer and Delivery" node, the "Handle" button needs to trigger the transfer and delivery of official documents, etc.

[0078] Figure 3 A schematic diagram of a configuration device for a business process node provided by an embodiment of the present invention. Figure 3As shown, the device includes: a target large form acquisition module 310, an initiating node configuration module 320 and a task node configuration module 330. Among them:

[0079] The target large form acquisition module 310 is used to respond to the associated form selection instruction and acquire the target large form corresponding to the process node configuration requirement of the current business;

[0080] An initiating node configuration module 320, configured to select a first type of target component from the target large list to implement the initiating node configuration of the current service in response to an initiating node configuration instruction;

[0081] The task node configuration module 330 is used to respond to the task node configuration instruction, select the second type of target component from the target large form to implement the form content configuration of the task node, and implement the operation button configuration of the task node according to the business triggering requirements of the task node.

[0082] The technical solution of the embodiment of the present invention obtains the target large form corresponding to the process node configuration requirement of the current business by responding to the associated form selection instruction; responding to the initiation node configuration instruction, selects the first type of target component from the target large form to implement the initiation node configuration of the current business; responds to the task node configuration instruction, selects the second type of target component from the target large form to implement the form content configuration of the task node, and implements the operation button configuration of the task node according to the business trigger requirement of the task node, adopts the method of selecting components from the large form according to the requirements to implement the node form content configuration, and configures the node trigger operation on the operation button, which solves the problems of high configuration complexity in complex business scenarios in the prior art, and limiting the flexibility of event triggering due to the configuration of the trigger operation at the node level, thereby improving the adaptability of complex business scenarios and the flexibility of event triggering.

[0083] Optionally, the target large form acquisition module 310 may be specifically used for:

[0084] In response to the form type selection instruction, obtaining a target form type corresponding to the process configuration requirement of the current business;

[0085] In response to the form instance selection instruction, the target large form is selected from the form list corresponding to the target form type.

[0086] Optionally, the initiating node configuration module 320 may be specifically used for:

[0087] Determining the operator type of the initiating node;

[0088] According to the operator type of the initiating node, a first type of target component matching the operator type is selected from the target large form to implement form content configuration for the initiating node of the current business.

[0089] Optionally, the task node is operated by a business staff;

[0090] Accordingly, the task node configuration module 330 may be specifically used for:

[0091] A second type of target component matching the business staff is selected from the target large form to implement form content configuration for the task node.

[0092] Optionally, the task node configuration module 330 may include:

[0093] A target operation button selection unit, used to select a target operation button required by the task node from the target large form according to the business requirements of the task node;

[0094] a target operation button classification unit, for classifying the target operation button according to the task status in response to the operation button classification instruction;

[0095] The target operation button trigger configuration unit is used to trigger the target operation button in response to the operation button trigger configuration instruction.

[0096] Optionally, the target operation button triggers the configuration unit, which can be used to:

[0097] In response to the operation button trigger event configuration instruction, performing a trigger event configuration on the target operation button according to a trigger event configuration template;

[0098] In response to the operation button trigger document configuration instruction, the target operation button is configured with a trigger document according to a pre-configured document template;

[0099] In response to the operation button trigger notification configuration instruction, the target operation button is configured for trigger notification according to the service notification requirement.

[0100] Optionally, the business process node configuration device further includes a task node timeout reminder configuration module, which is used to:

[0101] In response to a timeout configuration instruction of a task node, a timeout reminder configuration is performed on the task node according to a service timeliness requirement of the task node.

[0102] The device for configuring a business process node provided in the embodiment of the present invention can execute the method for configuring a business process node provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0103] Figure 4A schematic diagram of an electronic device 400 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers or various forms of mobile devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0104] like Figure 4 As shown, the electronic device 400 includes at least one processor 401, and a memory connected to the at least one processor 401 in communication, such as a read-only memory (ROM) 402, a random access memory (RAM) 403, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 401 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 402 or the computer program loaded from the storage unit 408 to the random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the electronic device 400 can also be stored. The processor 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0105] Multiple components in the electronic device 400 are connected to the I / O interface 405, including: an input unit 406, such as a keyboard, a mouse, etc.; an output unit 407, such as various types of displays, speakers, etc.; a storage unit 408, such as a disk, an optical disk, etc.; and a communication unit 409, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 409 allows the electronic device 400 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0106] Processor 401 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of processor 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. Processor 401 executes the various methods and processes described above, such as a configuration method for a business process node.

[0107] In some embodiments, the configuration method of the business process node can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 408. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 400 via the ROM 402 and / or the communication unit 409. When the computer program is loaded into the RAM 403 and executed by the processor 401, one or more steps of the configuration method of the business process node described above can be performed. Alternatively, in other embodiments, the processor 401 can be configured to execute the configuration method of the business process node in any other appropriate manner (for example, by means of firmware).

[0108] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0109] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0110] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0111] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0112] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0113] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0114] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0115] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for configuring a business process node, characterized in that: include: In response to the associated form selection instruction, the target large form corresponding to the process node configuration requirement of the current business is obtained; In response to the initiating node configuration instruction, selecting a first type of target component from the target large list to implement the initiating node configuration of the current service; In response to the task node configuration instruction, a second type of target component is selected from the target large form to implement the form content configuration of the task node, and the operation button configuration of the task node is implemented according to the business triggering requirements of the task node.

2. The method according to claim 1, characterized in that In response to the associated form selection instruction, the target large form corresponding to the process node configuration requirements of the current business is obtained, including: In response to the form type selection instruction, obtaining a target form type corresponding to the process configuration requirement of the current business; In response to the form instance selection instruction, the target large form is selected from the form list corresponding to the target form type.

3. The method according to claim 1, characterized in that: Selecting a first type of target component from the target large form to implement the initiating node configuration of the current business includes: Determining the operator type of the initiating node; According to the operator type of the initiating node, a first type of target component matching the operator type is selected from the target large form to implement form content configuration for the initiating node of the current business.

4. The method according to claim 3, characterized in that The task nodes are operated by business staff; Selecting the second type of target component from the target large form to implement form content configuration of the task node includes: A second type of target component matching the business staff is selected from the target large form to implement form content configuration for the task node.

5. The method according to claim 1, characterized in that Implementing the configuration of the operation button of the task node according to the business triggering requirement of the task node includes: According to the business requirements of the task node, select the target operation button required by the task node from the target large form; In response to the operation button classification instruction, classifying the target operation button according to the task status; In response to the operation button trigger configuration instruction, the target operation button is triggered and configured.

6. The method according to claim 5, characterized in that In response to the operation button trigger configuration instruction, trigger configuration of the target operation button includes: In response to the operation button trigger event configuration instruction, performing a trigger event configuration on the target operation button according to a trigger event configuration template; In response to the operation button trigger document configuration instruction, the target operation button is configured with a trigger document according to a pre-configured document template; In response to the operation button trigger notification configuration instruction, the target operation button is configured for trigger notification according to the service notification requirement.

7. The method according to claim 1, characterized in that Also includes: In response to a timeout configuration instruction of a task node, a timeout reminder configuration is performed on the task node according to a service timeliness requirement of the task node.

8. A configuration device for a business process node, characterized in that: include: A target large form acquisition module is used to respond to the associated form selection instruction and acquire the target large form corresponding to the process node configuration requirement of the current business; An initiating node configuration module, configured to respond to an initiating node configuration instruction and select a first type of target component from the target large list to implement the initiating node configuration of the current service; The task node configuration module is used to respond to the task node configuration instruction, select the second type of target component from the target large form to implement the form content configuration of the task node, and implement the operation button configuration of the task node according to the business trigger requirements of the task node.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for configuring a business process node according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for configuring a business process node according to any one of claims 1 to 7 when executed.

Images