Process service center
By designing the UI, integration, and service layers of the process service center, the problem that existing technologies could not meet the business development needs of the nuclear power group was solved, enabling efficient process application development and rapid deployment of business modules, and meeting the requirements for multi-channel access and switching of process services.
Patent Information
- Application Number
- CN202411046703.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-11-29
AI Technical Summary
The existing process service centers cannot meet the needs of the nuclear power group's business development in terms of performance, functionality, and scalability, and cannot support the sustainable development of the business.
A process service center was designed, comprising a UI layer, an integration layer, and a service layer. The UI layer receives service requests input by users, the integration layer obtains service information from the business system and transmits it to the service layer, and the service layer responds to user requests and outputs results. It supports functions such as process design, monitoring, alarms, and access control, integrates a multi-level organizational structure model and a risk management model, and provides full lifecycle management of processes.
It improved the efficiency and quality of process application development, shortened the business module launch cycle, met the needs of process business applications and projects, and supported multi-channel access and switching of process services.
Smart Images

Figure CN119045925A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of process services, and in particular to a process service center. Background Art
[0002] PSC is a process service center, which mainly encapsulates the functions of workflow engines and reduces the technical requirements for process development. The current process service center supports most of the core business processes of the group's collaborative office, has a large usage, and is a key basic service application of the group. However, the current process service center can no longer meet the needs of the nuclear power group's business development in terms of performance, function, and scalability. Under the new international situation, it has put forward requirements based on sustainable business development. Summary of the invention
[0003] The technical problem to be solved by the present invention is to provide a process service center.
[0004] The technical solution adopted by the present invention to solve the technical problem is: a process service center, comprising:
[0005] The UI layer is used to receive service requests input by users;
[0006] The integration layer is used to obtain the service information of the business system and transmit it to the service layer; the service information includes at least one of technical service information, business service information, and business data information;
[0007] The service layer is in communication with the UI layer, responds to the service request determined by the user through the UI layer, outputs the corresponding request result based on the service information, and sends it to the UI layer for display; wherein the service result includes at least one of process service, form service, and business rule service.
[0008] In one embodiment, the service request includes a process design request, and the process management platform of the service layer is used to perform process design in a preset process model according to the process design request input by the user from the interface of the UI layer and call the relevant service information in the integration layer according to the process design request, and generate a graphical flow chart; wherein the process design request includes process design parameters, engineering flow direction, flow rules, and flow conditions;
[0009] The process engine of the service layer is used to initiate the process corresponding to the flowchart according to the process start instruction determined by the user to drive the process flow.
[0010] In one of the embodiments, the process management platform is also used to monitor the process flow status, abnormal situation monitoring and activity status tracking of the initiated process; the process flow status includes process scheduling, process cancellation, process end, process activation and process deletion.
[0011] In one embodiment, the process management platform is further configured to include at least one of the following configurations:
[0012] Customize process alarm indicators;
[0013] Customize process alarm rules;
[0014] Collect and download alarm data for a preset time period;
[0015] Record the alarm event in the log;
[0016] Real-time notification of alarm events through preset notification methods;
[0017] The alarm indicators are displayed through the alarm dashboard.
[0018] In one embodiment, the process design request includes a business process design request, and the integration layer is used to obtain the routing and process node processor information determined by the business system according to the business process through a preset interface and submit it to the process engine;
[0019] The process engine is used to drive the process flow of the business process diagram generated by the process management platform according to the routing and process node processor information.
[0020] In one of the embodiments, the process engine is further configured to include at least one of the following configurations:
[0021] Serial or parallel operation of active nodes in the control process;
[0022] The state of active nodes in the control flow blocks the operation;
[0023] Approve the processes in groups;
[0024] Conduct parallel sign-off on the process;
[0025] Nesting of sub-processes;
[0026] The main process and sub-process are automatically associated.
[0027] In one of the embodiments, the UI layer is further used to receive a form submitted by a business system and a determined process definition, and the service layer is used to trigger a corresponding process according to the form to flow according to the process definition.
[0028] In one of the embodiments, the service layer is also used to create a predetermined model according to user needs; the predetermined model includes at least one of a process model, a multi-level organizational model, a data form model in the process, a risk management model, and a system management model.
[0029] In one embodiment, the service layer further includes an agent setting module, the agent setting module is used to set agent information for a specified process, so that the set agent can perform approval instead of the original approver; and / or
[0030] The service layer also includes a rights management module, which is used to configure roles and perform rights management during process flow.
[0031] In one of the embodiments, the service layer further includes a switching module, and the switching module is used to switch between different process engines when a preset condition is met.
[0032] The implementation of the process service center of the present invention has the following beneficial effects: the process service center of the present invention can improve the efficiency and quality of process application development, shorten the service module launch cycle, and support process business applications and process service requirements in various projects. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:
[0034] Figure 1 It is a structural diagram of a process service center according to an embodiment of the present invention;
[0035] Figure 2 is a flowchart of process application operation mode 1 of some embodiments of the present invention;
[0036] Figure 3 It is a flowchart of process application operation mode 2 of some embodiments of the present invention. DETAILED DESCRIPTION
[0037] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, specific embodiments of the present invention are now described in detail with reference to the accompanying drawings.
[0038] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present invention. However, it should be clear to those skilled in the art that the present invention may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present invention.
[0039] In order to facilitate the understanding of the present invention, the present invention will be described more fully below, and the present invention can be implemented in many different forms and is not limited to the embodiments described herein. On the contrary, the purpose of providing these embodiments is to make the disclosure of the present invention more thorough and comprehensive.
[0040] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present invention, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. It is not necessarily required or implied that there is any such actual relationship or order between these entities or operations.
[0041] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in the specification of the present invention herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention.
[0042] In a preferred embodiment, reference Figure 1 The process service center of this embodiment includes:
[0043] The UI layer is used to receive service requests input by users.
[0044] It can be understood that the UI layer mainly provides the capabilities of the process service center in the form of a user interface, including functional modules that users can interact with and shared UI components that can be directly referenced by applications.
[0045] The integration layer is used to obtain the service information of the business system and transmit it to the service layer. It can be understood that the service information includes but is not limited to technical service information, business service information, business data information, etc.
[0046] It can be understood that the integration layer mainly supports the access of the middle platform's technical services, business services and data services to the process service center for use by process services, form services and business rule services.
[0047] The service layer is connected to the UI layer in communication, responds to the service request determined by the user through the UI layer, outputs the corresponding request result based on the service information, and sends it to the UI layer for display. The service results include but are not limited to process services, form services, business rule services, etc. The service layer mainly provides the capabilities of the process service center in a service-oriented manner.
[0048] In some embodiments, the service request includes a process design request, and the process management platform of the service layer is used to perform process design in a preset process model according to the process design request input by the user from the interface of the UI layer and to call the relevant service information in the integration layer according to the process design request to generate a graphical flow chart. The process design request includes process design parameters, engineering flow direction, flow rules, and flow conditions.
[0049] The process engine of the service layer is used to initiate the process corresponding to the flowchart according to the process start instruction determined by the user to drive the process flow.
[0050] Optionally, the process management platform is also used to monitor the process flow status, abnormal situation monitoring and activity status tracking of the initiated process. The process flow status includes process scheduling, process cancellation, process end, process activation and process deletion.
[0051] Specifically, the process management platform can be configured to include at least one of the following configurations:
[0052] Customize process alarm indicators, such as server resources.
[0053] Customize process alarm rules, such as server resource usage going online.
[0054] Collect and download alarm data for a preset time period, such as server resource alarms within half a month.
[0055] The alarm events are recorded in the log and log download is supported.
[0056] Real-time notification of alarm events is provided through preset notification methods. For example, email and SMS services can be provided to realize alarm time subscription.
[0057] The alarm indicators are displayed through the alarm dashboard, which can display customized alarm indicators in all aspects.
[0058] The process management platform can also customize analysis indicators, such as process to-do timeout. The dimensions of analysis indicators can be defined, such as analyzing a certain type of process. Analysis data can be downloaded, analysis reports can be preset, and analysis reports can be customized. The process management platform also includes an analysis dashboard that can fully display analysis indicators.
[0059] Specifically, the process engine may also be configured to include at least one of the following configurations:
[0060] Serial or parallel operation of activity nodes in a control flow.
[0061] The state of the active node in the control flow blocks the operation.
[0062] Approve processes in groups.
[0063] Sign off on the process in parallel.
[0064] Nest sub-processes.
[0065] The main process and sub-process are automatically associated.
[0066] It can be understood that from the user's perspective, the process service center of this embodiment can realize functions such as process initiation, my to-do list, my done list, my working list, my to-read list, my read list, initiated by me, approved by me, acted as an agent by me, process monitoring, comprehensive query, shared tasks, agent settings, batch processing, my attention, my draft, task suspension, process operation, process tracking function, process designer, etc.
[0067] From the perspective of system functions, the process service center of this embodiment includes: a custom graphical process configuration tool, which can realize the expression of process design through a graphical interface, which is clear, intuitive and easy to understand. It includes but is not limited to the following functions: creating a new activity node, setting the node name, type, content, executor, role, execution condition, processing time limit, setting logical judgment rules, node form rules and other related attributes. Determine the direction of project flow and set flow rules and flow conditions through connections. Implement workflow management, including flow process monitoring, abnormal monitoring, tracking activity status, process scheduling, cancellation, end, activation, deletion, modification and other intervention flow functions. Implement a workflow engine, which can control the flow process, the creation, activation, suspension, termination, etc. of process instances; control the serial and parallel operations of active nodes, node status blocking and other operations, support process group approval, parallel signing and sub-process nested flow, automatic association within the main sub-process, etc.
[0068] The process service center of this embodiment supports the management of the entire life cycle of the process. The service layer is also used to create a predetermined model according to user needs. The predetermined model includes but is not limited to a process model, a multi-level organizational model, a data form model in the process, a risk management model, a system management model, etc.
[0069] It can be understood that the process service center of this embodiment can achieve: 1. Process modeling: create process models; organizational modeling: create multi-level organizational models; data and form modeling: create data form models in the process; risk modeling: create risk models and manage risks; system modeling: create system models and manage systems; organize team collaboration: better manage team collaboration; data display and output: display process data. 2. Process design: design various processes; form design: design process forms; business rule design: design business rules in the process; process role design: design different role permissions in the process; service integration design: design different service integrations in the process.
[0070] The process service center of this embodiment can provide underlying process flow and process design services, underlying form design and submission services, business rule flow capabilities, and process service integration capabilities. The running and completed lists of processes can be viewed in the background, and the tasks to be done, to be read, completed, and read generated in the process can be viewed in the background. The running process instances can be invalidated and suspended in the background.
[0071] In some embodiments, the service layer further includes an agent setting module, which is used to set agent information for a specified process so that the set agent can perform approval instead of the original approver. And / or
[0072] The service layer also includes a rights management module, which is used to configure roles and manage rights during process flow.
[0073] The service layer also includes a switching module, which is used to switch between different process engines when preset conditions are met.
[0074] The process service center of this embodiment can meet the business sustainability management requirements, can manage the business process throughout the entire cycle, can switch between different process engines, can access the system from multiple channels, and can be directly called or accessed through cud4.0.
[0075] Exemplarily, in a specific process establishment process implementation, it mainly includes: process model design: custom process model design; process rule customization: define process rules; process rule configuration: configure process rules in the model; form design customization: custom form design; form configuration: configure form in the process model; process alarm: customize process timeout settings; alarm event subscription: send SMS or email reminders; complete process design, initiate process; manage and monitor process instances.
[0076] Process services include: 1. Process service API: RESTful-based process running services and process design services, which can be called by other applications that are connected to the process service center and authorized.
[0077] 1.1 Process initiation: The business system initiates the process by calling the API of the PSC process service center, and the process service center generates process instances and pending tasks. The specific logic is as follows:
[0078] (1) When the business system is submitted, the initiation API interface of PSC is called. The interface parameters need to pass in the tenant ID, application code, process ID, current link instance ID, operator, copy recipient, and next link information. The next link information has the following scenarios: ① Scenario 1: When there is no co-signature item in the serial link, a single set of next link ID, next link name, handler and other information needs to be passed in the next link information. After submission, the process engine will generate one or more to-do tasks for everyone to approve; ② Scenario 2: When there is no co-signature item in the parallel link, multiple sets of next link ID, next link name, handler and other information need to be passed in the next link information. After submission, the process engine will generate multiple sets of to-do tasks. When a branch task is approved, it will not affect the to-do tasks of another branch. ③Scenario 3: When the countersignature method of a serial link or a parallel link is serial countersignature, the next link information needs to pass in the next link ID, the next link name, and a group of countersignature item IDs, countersignature item names, countersignature order, countersigners and other information. After submission, the process engine will generate one or more to-dos. All to-do tasks will be approved in sequence according to the countersignature items. Multiple approvers for the same countersignature item will approve in parallel. ④Scenario 4: When the countersignature method of a serial link or a parallel link is parallel countersignature, the next link information needs to pass in the next link ID, the next link name, and multiple groups of countersignature item IDs, countersignature item names, countersigners, and countersignature rules. After submission, the process engine will generate one or more multi-person to-dos. Any one of the countersignature items will approve or all of them will approve.
[0079] (2) After the process engine generates a task, it will also be recorded in the PSC service center and call back the interface of the business system.
[0080] (3) After the callback to the business system is successful, the person handling the transaction will receive an email notification of pending actions. If there are any CC recipients, they will also receive a notification of pending actions.
[0081] 1.2 Task submission: The user enters the detailed process form from the to-do list, fills in the approval opinion, and the next link approver and copy person submit to the process service center API. The process service center generates a new task for the next link or ends the process. The specific logic is as follows:
[0082] (1) When the business system is submitted, the submission API interface of PSC is called. The interface parameters need to pass in the tenant ID, application code, process instance ID, process ID, current link instance ID, operator, CC person, and next link information. The next link information has the following scenarios: ① Scenario 1: When there is no co-signature item in the serial link, a single set of next link ID, next link name, handler and other information needs to be passed in the next link information. After submission, the process engine will generate one or more to-do tasks, which need to be approved by all. ② Scenario 2: When there is no co-signature item in the parallel link, multiple sets of next link ID, next link name, handler and other information need to be passed in the next link information. After submission, the process engine will generate multiple sets of to-do tasks. When a branch task is approved, it will not affect the to-do tasks of another branch. ③Scenario 3: When the countersigning method of the serial link or parallel link is serial countersigning, the next link information needs to pass in the next link ID, the next link name and a group of countersigning item IDs, countersigning item names, countersigning order, countersigners and other information. After submission, the process engine will generate one or more to-do tasks. All to-do tasks will be approved in sequence according to the countersigning items. Multiple approvers for the same countersigning item will approve in parallel. ④Scenario 4: When the countersigning method of the serial link or parallel link is parallel countersigning, the next link information needs to pass in the next link ID, the next link name and multiple groups of countersigning item IDs, countersigning item names, countersigners, and countersigning rules. After submission, the process engine will generate one or more multi-person to-do tasks. Any one of the countersigning items will approve or all of them will approve. ⑤Scenario 5: When ending the link, the next link ID and the next link name need to be passed in the next link information. After submission, all tasks in the previous link disappear and the current process instance ends.
[0083] (2) After the process engine generates a task, it will also be recorded in the PSC service center and call back the interface of the business system.
[0084] (3) After the callback to the business system is successful, the person handling the transaction will receive an email notification of pending actions. If there are any CC recipients, they will also receive a notification of pending actions.
[0085] 1.3 Task opening: When the user enters the detailed process form from the to-do list, the current task will be marked as viewed when it is opened. The processing logic is as follows:
[0086] (1) When the business system opens the process form details interface, it calls the task opening API interface of the PSC process service center.
[0087] (2) When calling the interface, you need to pass in data such as tenant ID, application code, process instance ID, process ID, current link instance ID, etc.
[0088] (3) When the PSC process service center receives the data, it will modify the opening time of the current task.
[0089] 1.4 Task return: Users can return to the previous step by entering the detailed process form from the to-do list. Currently, there are two ways to return: true return and false return. The processing logic is as follows:
[0090] (1) When the business system returns the task, it calls the task return API interface of the process service center. The interface needs to pass in the tenant ID, application code, process instance ID, process ID, current link instance ID, target link to be returned, return method, approver of the returned link, and other information. There are several scenarios for return methods: 1. True return: ① Scenario 1: When the serial link is returned, it returns directly to the link specified by the user; the user submits again, and the previously passed links need to be re-approved. ② Scenario 2: When the parallel link is returned, it returns to the previous link in the parallel branch, and the pending tasks of the other branch link are retained; it returns outside the parallel branch and ends the tasks of all parallel branch links; or it prompts that the return is not allowed due to the existence of parallel branch active links; submit again, and the previously passed links need to be re-approved. ③ Scenario 3: When the serial link or parallel link is signed in a serial way, if there are multiple signed items, it can be returned to other signed items; it can be returned to the previous link; when it is submitted again, the previously passed signed items or links need to be re-approved. ④Scenario 4: When the countersignature method of a serial link or a parallel link is parallel countersignature, if there are multiple countersignature items in parallel, you can only return to the previous link; if you submit again, the previously passed link needs to be re-approved. 2. False return: ①Scenario 1: When a serial link is returned, it will return directly to the link specified by the user; if the user submits again, it will go directly to the link when it is returned. ②Scenario 2: When a parallel link is returned, it will return to the previous link in the parallel branch, and the to-do tasks of the other branch link will be retained; it does not support returning outside the parallel branch, because there are parallel branch active links, so return is not allowed. ③Scenario 3: When the countersignature method of a serial link or a parallel link is serial countersignature, if there are multiple countersignature items, you can return to other countersignature items; you can return to the previous link; submit between countersignature items, and the next countersignature item will only be submitted after all approvers of the current countersignature item pass; submit the previous link, and all countersignature items of this link need to be re-approved. ④Scenario 4: When the serial or parallel link signing method is parallel signing, and multiple signing items are running in parallel, you can only return to the previous link; submit again and go directly to the link when you return. All signing items in the current link need to be re-approved.
[0091] (2) After PSC receives the returned task, it calls the process engine to generate a new task for the target link, records the task information in PSC, and calls back the interface of the business system.
[0092] (3) After the callback to the business system is successful, the person handling the return will receive a pending email notification. If there are any CC recipients, they will also receive a pending email notification.
[0093] 1.5 Task withdrawal: If the current task handler has not processed the task, the previous user who submitted the task can withdraw it from the completed task. After withdrawing, the user can re-fill in the processing form and submit it. If the current task handler has submitted the task, the previous user will not be able to perform the withdrawal operation. The processing steps are as follows:
[0094] (1) When the business system performs a withdrawal operation in the completed list, it calls the task withdrawal interface of the PSC process service center. The interface needs to pass in parameters such as tenant ID, application code, process instance ID, process ID, and current link instance ID. ① Scenario 1: When the serial link is withdrawn, if the task is not opened: return to the previous link, and the current task to-do disappears; if the current task is already opened, it prompts that the withdrawal failed and the process is already being processed; if the task has been transferred, it is not allowed to withdraw. ② Scenario 2: When the parallel link is withdrawn, if all groups of branch tasks are not opened: the multiple groups of parallel tasks to-do disappear; if one of the multiple groups of branch tasks is opened: it prompts that the withdrawal failed and the process is already being processed; if the task has been transferred, it is not allowed to withdraw. ③ Scenario 3: When the serial link is withdrawn, if the task is not opened: return to the previous link or the countersigned matter, and the current task to-do disappears; if the current task is already opened, it prompts that the withdrawal failed and the process is already being processed; if the task has been transferred, it is not allowed to withdraw. ④Scenario 4: When the parallel link is returned, when multiple parallel signing tasks are not opened: return to the previous link or signing matter, the current link pending tasks disappear; if the current task has been opened, it will prompt that the cancellation failed and the process is being processed; if the task has been transferred, it is not allowed to be cancelled. ⑤Scenario 5: In the shared link, the task can be cancelled before it is claimed; the task cannot be cancelled after it is claimed.
[0095] (2) After the PSC process service center receives the data, the completed tasks are activated and entered into the pending tasks, and the tasks in the next link disappear.
[0096] 1.6 Task CC: Users can CC the current task to designated personnel for review. After the task is CCed, the viewing authority can perform copy operations. The CC recipient cannot modify the process data. The processing steps are as follows:
[0097] (1) The business system can copy other people when completing a task. When copying, the task copy interface of the PSC process service center is called. The interface requires the input of tenant ID, application code, process instance ID, process ID, current link instance ID, current link name, current copy recipient, and copy reason.
[0098] (2) After the PSC receives the data, a new piece of information to be read is added to the waiting list, and the callback interface of the business system is called at the same time.
[0099] (3) The CC recipients will receive a CC email notification.
[0100] (4) The cc recipient can send a cc again while the message is waiting to be read.
[0101] 1.7 Task Read: The user enters the detailed process form from the waiting list and clicks the [Read] button to support CC again. The processing steps are as follows:
[0102] (1) When the business system user reads the task and marks it as read, the process service center task read API interface is called. The interface needs to pass in the tenant ID, application code, operator, process instance ID, process ID, current link instance ID, current link name, CC recipient, CC reason and other information.
[0103] (2) After the PSC receives the data, it marks the data in the waiting list as read and informs the business system that the data has been modified successfully.
[0104] (3) If other CC recipients are sent, they will also receive a CC email notification.
[0105] 1.8 Task jump: When the process flows to a certain processing link, the person in charge of the current processing link cannot handle it for some reason and has not authorized others to handle it on his behalf. At this time, the user can request the administrator to jump to the processing link of the process. The processing steps are as follows:
[0106] (1) When calling the task jump interface of the PSC process service center, you need to enter the tenant ID, application code, process instance ID, process ID, current link instance ID, current link name, target link ID, target link name, target link handler, jump reason and other information. When jumping, the target link is required in the following situations: ① Scenario 1: When the serial link is returned, jump to the specified node. ② Scenario 2: When the parallel link is returned, jump to the specified node, but do not support jumping to other parallel branch links in the same group; do not support jumping to a node outside the parallel branch node, jump to a node inside the parallel branch; do not support jumping to a node outside the parallel branch node. ③ Scenario 3: When the serial link or parallel link is signed in serial mode, you can jump to any signed item in the serial link; you can jump to other links. ④ Scenario 4: When the serial link or parallel link is signed in parallel mode, it does not support jumping to any signed item in the parallel sign; you can jump to other links.
[0107] (2) After receiving the transferred task, the PSC calls the process engine to generate a new task for the target link, records the task information in the PSC, and calls back the interface of the business system.
[0108] (3) After the callback to the business system is successful, the person in charge of the target link will receive an email notification of pending actions.
[0109] 1.9 Task urging: When a task is stuck at a certain stage and has not been processed, the user can send an email to the current processor to urge the task. In addition, when a task is stuck at a certain step and exceeds the timeout period allowed by the step, the system can automatically send an email to the current processor to urge the task. The processing steps are as follows:
[0110] (1) The user performs a reminder operation in the completed list and calls the PSC process service center task reminder API interface. The interface needs to pass in parameters such as tenant ID, application code, process instance ID, operator, process ID, to-do link ID, to-do link name, and to-do link handler.
[0111] (2) When there are multiple tasks, the user can select one or more tasks for urging. After the PSC receives the data, the person handling the task will receive an email notification for urging the task to be completed.
[0112] 1.10 Process instance cancellation: When a process needs to be deleted for some reason, the user or system administrator can cancel the current process instance. The process cannot be activated after it is cancelled. The processing steps are as follows:
[0113] (1) When the business system invalidates the current process instance, it calls the invalidation interface of the PSC call process center. The interface needs to pass in parameters such as tenant ID, application code, process instance ID, process ID, operator, etc.
[0114] (2) After receiving the parameters, PSC will invalidate the current process instance and all pending tasks will disappear.
[0115] 1.11 Task forwarding: A user can forward a task that he is processing to other users. After forwarding, the user no longer has the processing authority for the task, but the user to whom the task is forwarded has the same authority as the forwarder. The processing steps are as follows:
[0116] (1) When the business system transfers the task, it calls the task transfer API interface provided by the PSC process service center. The interface needs to pass in information such as tenant ID, application code, operator, process instance ID, process ID, current link ID, current link name, transfer recipient, and transfer opinion;
[0117] (2) After receiving the data, the PSC process service center will call the process engine to generate a new task for the transfer recipient. The PSC will record the task and call back the callback interface of the business system.
[0118] (3) The transferee will receive an email notification of the pending task.
[0119] 1.12 Task Editing: You can edit the current task in the task instance management. The processing steps are as follows:
[0120] (1) When the business system background needs to be edited, the task editing API interface provided by the process service center is called. The interface supports editing of priority, process subject, initiator number, initiator name, initiator department ID, initiator department name, initiation time, end time, process instance status, application code, parent process instance ID, creator number, creator name, and creation time;
[0121] (2) After receiving the data, the process service center modifies the current task and informs the business system of the status of the modification.
[0122] 2. Personal workbench services include: 2.1 To-do list: When the user enters the to-do page, a list of all to-do tasks that the current user needs to handle will be displayed, and the to-do task list can be filtered out and operated according to process classification or process name and date conditions. The to-do list displays the flowchart, agent / transfer information, priority, work subject, current task, process name, initiator, and task start time information. The processing steps are as follows:
[0123] (1) When the business system user enters the to-do page, the task to-do API provided by the process service center is called. The interface needs to pass in the tenant ID; application code, process instance ID, process ID, current user ID and other information. (2) All to-do tasks of the current user of the current application are returned based on the parameters passed by the business. (3) The API interface supports paging of data and can be sorted according to specific conditions. (4) After receiving the data returned by the process service center, the business system parses and displays it.
[0124] 2.2 To-be-read list: When the user enters the To-be-read page, a list of all the tasks to be processed by the current user will be displayed. In the To-be-read task list, the user can view the process form data, processing records and flow chart of a task in detail. The processing steps are as follows:
[0125] (1) When the business system user enters the task to be read page, the task to be read API interface provided by the process service center is called, and the tenant ID, application code, process instance ID, process ID, current user ID and other information are passed into the interface; (2) All the tasks to be read for the current user of the current application are returned according to the parameters passed by the business; (3) The API interface supports paging of data and can be sorted according to specific conditions; (4) After the business system receives the data returned by the process service center, it parses and displays it; (5) After the user views the task, the current task to be read will be marked as read, and the task status API interface of the process service center will also be called at this time.
[0126] 2.3 Completed list: When the user enters the completed page, a list of all completed tasks of the current user will be displayed. In the completed task list, the user can view the process form data, processing history and flow chart of a task in detail. The processing steps are as follows:
[0127] (1) When the business system user enters the completed task page, the API interface provided by the process service center is called. The interface requires the tenant ID, application code, process instance ID, process ID, current user ID and other information to be passed in; (2) All completed tasks of the current user of the current application are returned based on the parameters passed by the business; (3) The API interface supports paging of data and can be sorted according to specific conditions; (4) After the business system receives the data returned by the process service center, it parses and displays it.
[0128] 2.4 Read list: When the user enters the read page, a list of all tasks that the current user has read will be displayed. In the read task list, the user can view the process form data, processing history and flowchart of a task in detail. The processing steps are as follows: (1) When the business system user enters the read page, the task read API interface provided by the process service center is called. The interface needs to pass in information such as tenant ID, application code, process instance ID, process ID, current user ID, etc.; (2) All read tasks of the current user of the current application are returned based on the parameters passed by the business; (3) The API interface supports paging of data and can be sorted according to specific conditions; (4) After the business system receives the data returned by the process service center, it parses and displays it;
[0129] 2.5 Process Agent: When the user enters the agent page, he can modify and delete the agent tasks that have been set, and can also add new agent tasks. The agent's permissions are copied, and the current user still retains the permissions for the process task, while the delegated user has the owner's permissions for the task. The processing logic is as follows: (1) The business system sets the agent's process (all processes, specified processes) and agent and agent time parameters, calls the task agent API provided by the process service center, chooses whether to send an email reminder and sets the email reminder content, and clicks the "OK" button; (2) The process service center copies the permissions of the current task to the agent and returns the processing results to the business system;
[0130] 3. Process service shared UI component: A reusable UI component that serves the user-side personal task center. Other application systems can use this shared UI component. However, when using the shared UI component, the current application needs to be registered in the PSC process service center, and the corresponding parameters need to be passed for authentication in accordance with the specifications of the shared UI component before it can be used normally.
[0131] 4. Management portal section: 4.1 Permission management: You can maintain system role permissions; you can add roles, set role permissions, authorize roles, and delete operations. 4.2 Application access management: Register applications that access this system. All process data, system parameters, and log data belong to the application. You can add / edit applications, set process engine adapters, and provide connection test functions to verify whether the application and process engine are connected normally. 4.3 Service permission management: Manage the authentication and authorization of psc published service interface applications. The service interface can only be called after authorizing the application system. You can select the service interface to be called by the application and the authorization time, and generate an authorization key. 4.4 System log management: Record and track the scheduled operation (scheduled synchronization, real-time monitoring) processing data logs in the system. 4.5 Operation log: Record system user operation log audits, such as login, data addition, deletion, modification, and query logs. 4.6 Service log: Record and track the application system's call to the psc service interface information and status, view log details, and call abnormal logs manually and retry. 4.7 Callback log: record and track the call information and status of the psc callback application system service interface, view the log details, and call the abnormal log to manually retry. 4.8 Performance monitoring: track the performance of the published API and the callback API provided by the application system; and track the performance of the message queue operation / process execution.
[0132] 5. Process engine adapter. The adapter of the process engine product mainly needs to provide the following two functions: 5.1 Implement interface adaptation and parameter mapping from the PSC process service interface to the process engine API. The adapter needs to implement an interface consistent with the 3.2 service interface module, and complete the adaptation of each method in the interface to the process engine API (call the API corresponding to the process engine, and map and convert the parameters passed in by the 3.2 service interface module to the parameters required by the API method corresponding to the process engine, and convert the results returned by the process engine API into the return results defined in the 3.2 service interface module).
[0133] 2. Implement the event listener of the process engine: The adapter also needs to provide the global event listening function of the corresponding process engine product. Listen to the model events, process instance events, node instance events, and task instance events of the process engine, obtain the data required by PSC from the monitored information, and push it to the corresponding data model of the PSC database.
[0134] In some embodiments, the process design request includes a business process design request, and the integration layer is used to obtain the routing and process node processor information determined by the business system according to the business process through a preset interface and submit it to the process engine.
[0135] The process engine is used to drive the process flow of the business process diagram generated by the process management platform based on the routing and process node processor information.
[0136] The UI layer is also used to receive forms submitted by the business system and the determined process definitions. The service layer is used to trigger the corresponding process based on the form and flow according to the process definition.
[0137] In some embodiments, reference Figure 2 and Figure 3 , the process application includes two operating modes:
[0138] Mode 1: The form is implemented by the application end, and the process is supported by PSC in a service-oriented manner. In this mode, the form is implemented in the business system in a development manner. After the developers of the business system design the process definition, they publish it to the PSC service center. When the form in the business system is submitted, the process service is called to trigger the process to flow according to the process definition. The business system can directly reference the process sharing UI components provided by the process service center.
[0139] Mode 2: PSC provides an integrated operation platform from form to process. In this mode, forms, processes, business rules, and external service integration all run on the PSC platform. PSC provides an integrated low-code operation platform. In this mode, a process application consists of four parts: form definition, process definition, business rule definition, and integrated service definition. During design, process definition, form definition, business rule definition, and integrated service definition are performed on PSC according to business requirements and published to PSC. During runtime, users access the user portal of PSC to initiate and process the process. The form service will call the integration service to obtain business data for form data binding and presentation. When the form is submitted, the process service will be called for process flow. When the process flows, the process service will call the business rule service for routing judgment. When the business rule service executes the rule, it will call the integration service to obtain external business data for rule judgment.
[0140] In this embodiment, a new generation of process service center is built based on the requirements of business sustainable development management. A service-oriented development architecture is adopted to publish process public services to support the process requirements of front-end business applications. The SLA requirements of high performance, high availability, high reliability, high scalability and multi-tenancy are met. The efficiency and quality of process application development are improved, and the launch cycle of business modules is shortened. Support process business applications and process service requirements in various projects.
[0141] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0142] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
[0143] It can be understood that the above embodiments only express the preferred implementation modes of the present invention, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the patent scope of the present invention. It should be pointed out that, for ordinary technicians in this field, the above technical features can be freely combined without departing from the concept of the present invention, and several deformations and improvements can be made, which all belong to the protection scope of the present invention. Therefore, all equivalent changes and modifications made to the scope of the claims of the present invention should belong to the coverage of the claims of the present invention.
Claims
1. A process service center, It is characterized in that include: The UI layer is used to receive service requests input by users; The integration layer is used to obtain the service information of the business system and transmit it to the service layer; The service information includes at least one of technical service information, business service information, and business data information; The service layer is in communication with the UI layer, responds to the service request determined by the user through the UI layer, outputs the corresponding request result based on the service information, and sends it to the UI layer for display; wherein the service result includes at least one of process service, form service, and business rule service.
2. The process service center according to claim 1, It is characterized in that The service request includes a process design request. The process management platform of the service layer is used to perform process design in a preset process model according to the process design request input by the user from the interface of the UI layer and to call the relevant service information in the integration layer according to the process design request, and generate a graphical flow chart; wherein the process design request includes process design parameters, engineering flow direction, flow rules, and flow conditions; The process engine of the service layer is used to initiate the process corresponding to the flowchart according to the process start instruction determined by the user to drive the process flow.
3. The process service center according to claim 2, It is characterized in that The process management platform is also used to monitor the process flow status, abnormal situation monitoring and activity status tracking of the initiated process; the process flow status includes process scheduling, process cancellation, process end, process activation and process deletion.
4. The process service center according to claim 3, It is characterized in that The process management platform is also configured to include at least one of the following configurations: Customize process alarm indicators; Customize process alarm rules; Collect and download alarm data for a preset time period; Record the alarm event in the log; Real-time notification of alarm events through preset notification methods; The alarm indicators are displayed through the alarm dashboard.
5. The process service center according to claim 2, It is characterized in that The process design request includes a business process design request, and the integration layer is used to obtain the routing and process node processor information determined by the business system according to the business process through a preset interface and submit it to the process engine; The process engine is used to drive the process flow of the business process diagram generated by the process management platform according to the routing and process node processor information.
6. The process service center according to claim 2, It is characterized in that The process engine is further configured to include at least one of the following configurations: Serial or parallel operation of active nodes in the control process; The state of active nodes in the control flow blocks the operation; Approve the processes in groups; Conduct parallel sign-off on the process; Nesting of sub-processes; The main process is automatically associated with the sub-process.
7. The process service center according to claim 1, It is characterized in that The UI layer is also used to receive a form submitted by the business system and a determined process definition, and the service layer is used to trigger a corresponding process according to the form and to circulate according to the process definition.
8. The process service center according to claim 1, It is characterized in that The service layer is also used to create a predetermined model according to user needs; the predetermined model includes at least one of a process model, a multi-level organizational model, a data form model in the process, a risk management model, and a system management model.
9. The process service center according to claim 1, It is characterized in that The service layer further comprises an agent setting module, wherein the agent setting module is used to set agent information for a specified process so that the set agent can perform approval instead of the original approver; and / or The service layer also includes a rights management module, which is used to configure roles and perform rights management during process flow.
10. The process service center according to claim 1, It is characterized in that The service layer also includes a switching module, which is used to switch between different process engines when a preset condition is met.
