Service system processing method and device, electronic equipment and storage medium

Abstract

The invention provides a service system processing method and device, electronic equipment and a storage medium. The method comprises the following steps: receiving a group creation request triggered by a user for a target processing node; obtaining a processor list corresponding to the target processing node in response to the group creation request; sending group creation request information carrying the processor list to the target communication system, so that the target communication system creates a target group and adds each processor in the processor list to the target group; and receiving a processing result sent by the target communication system. According to the invention, when the group creation request is received, the processor list is obtained, and the creation of the target group is automatically completed on the target communication system, so that the processors can determine the processing result through group real-time communication and synchronize the processing result to the business system to form a process closed loop, the cooperation efficiency and decision-making speed are improved, the cross-department cooperation experience is optimized, and the user experience is improved. And the consistency and the traceability of the process data are enhanced.

Description

Technical Field

[0001] The present invention relates to the technical field of business systems, and in particular to a processing method, device, electronic device and storage medium for a business system. Background Art

[0002] Currently, in business systems like change management systems, when it comes to change reviews, numerous personnel from different departments are involved, and offline change review meetings are often required to discuss issues and advance product design changes. This requires significant time to coordinate the schedules of personnel from various departments. Given the varying work paces of different departments and the tight schedules of personnel, determining a meeting time that accommodates everyone often requires repeated communication and confirmation, a process that can take days or even longer. Consequently, the existing review process is inefficient and hinders the progress of product design changes. Summary of the Invention

[0003] Embodiments of the present invention provide a processing method, device, electronic device, and storage medium for a business system to solve the problem of how to improve the advancement efficiency of processing nodes that require collaborative processing by multiple personnel.

[0004] In a first aspect, an embodiment of the present invention provides a processing method for a business system, the method comprising: receiving a user-triggered group creation request for a target processing node, wherein the target processing node corresponds to a plurality of processors; In response to the group creation request, obtaining a processor list corresponding to the target processing node; sending a group creation request message carrying the processor list to a target communication system, so that the target communication system creates a target group and adds each processor in the processor list to the target group; wherein the processors in the processor list communicate with each other through the target group regarding the processing content corresponding to the target processing node to determine the processing result; Receive the processing result sent by the target communication system.

[0005] In a second aspect, an embodiment of the present invention further provides a processing device for a business system, the device comprising: A first receiving module is configured to receive a group creation request for a target processing node triggered by a user, wherein the target processing node corresponds to multiple processors; A first acquisition module, configured to acquire a processor list corresponding to the target processing node in response to the group creation request; a first sending module, configured to send a group creation request message carrying the processor list to a target communication system, so that the target communication system creates a target group and adds each processor in the processor list to the target group; wherein the processors in the processor list communicate with each other through the target group regarding the processing content corresponding to the target processing node to determine the processing result; The second receiving module is configured to receive the processing result sent by the target communication system.

[0006] In a third aspect, an embodiment of the present invention further provides an electronic device comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the above-mentioned processing method of the business system when executed by the processor.

[0007] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the processing method of the above-mentioned business system is implemented.

[0008] The embodiments of the present invention include at least the following technical effects: The technical solution of the embodiment of the present invention, through the deep integration of the business system and the communication system, can obtain the list of processors when receiving a group creation request, and automatically complete the creation of the target group on the target communication system. The creation of the target group enables the processors to determine the processing results through real-time communication with the group and synchronize them to the business system, forming a closed process loop, improving collaboration efficiency and decision-making speed, optimizing the cross-departmental collaboration experience, and enhancing the consistency and traceability of process data. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for describing the embodiments or the prior art.

[0010] Figure 1 1 is a flow chart of a processing method of a business system provided by an embodiment of the present invention; Figure 2 is a schematic diagram of the interaction between the business system and the target communication system provided by an embodiment of the present invention; Figure 3 1 is a schematic diagram of the structure of a processing device of a business system provided by an embodiment of the present invention; Figure 4 A block diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0011] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0012] It should be understood that references throughout this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present invention. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0013] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0014] like Figure 1 As shown, an embodiment of the present invention provides a processing method of a business system, the method comprising: Step 101: Receive a user-triggered group creation request for a target processing node, wherein the target processing node corresponds to multiple processors.

[0015] In the processing method of the business system provided by the embodiment of the present invention, the business system may be a change management system of an automobile company.

[0016] Specifically, the business system includes multiple processing nodes, some of which require collaborative processing by multiple processors. The target processing node is the node corresponding to the collaborative processing of multiple processors. Since many processors from different departments are involved, in order to efficiently advance the work, the initiator corresponding to the node can add all the processors of the target processing node to a communication group so as to communicate and collaborate within the communication group. At this time, if the initiator manually searches for the processors to create a group, he will face many troubles. It is common for a company to have duplicate names, which makes it extremely time-consuming and labor-intensive to accurately find the processors of the corresponding department and successfully create a group, which seriously affects the efficiency of meeting organization.

[0017] In an embodiment of the present invention, a group creation request for a target processing node can be actively triggered by the initiator, or automatically triggered by a business system. For example, when the business system is a change management system of an automobile company, after the automobile company engineer submits the "chassis design change" application in the change management system, the process enters the "cross-departmental review" node. The engineer can decide whether to trigger the group creation request by clicking the "one-click group creation" button on the page based on actual needs; the trigger conditions for automatic triggering of the business system can also be pre-set. When the processing task corresponding to the target processing node meets the preset conditions, the business system will automatically trigger the group creation request. The preset condition can be that the target processing node has been pre-calibrated with the automatic group creation attribute. That is, when the process reaches the processing node that has been calibrated with the automatic group creation attribute, the business system will automatically trigger the group creation without the initiator making a group creation request.

[0018] It should be noted that when receiving a group creation request, the business system needs to verify the user permissions of the user who triggered the group creation request, that is, the initiator. Only specific roles such as process creators and department heads can initiate group creation.

[0019] Step 102: In response to the group creation request, obtain a list of processors corresponding to the target processing node.

[0020] After receiving a group creation request, the system retrieves the list of handlers corresponding to the target processing node. Specifically, this list supports manual adjustments (such as temporarily adding external experts) and batch importing personnel from Excel, automatically filtering out personnel on vacation. Specifically, upon obtaining the list of handlers, the system also retrieves employee vacation status information from the attendance system. Based on this information, the system checks whether each handler in the list is on vacation. If a handler is found to be on vacation, the handler is removed from the list.

[0021] Step 103: Send a group creation request message carrying the processor list to the target communication system, so that the target communication system creates a target group and adds each processor in the processor list to the target group; wherein the processors in the processor list communicate with each other through the target group regarding the processing content corresponding to the target processing node to determine the processing result.

[0022] Specifically, a two-way API interface is developed between the business system and the target communication system for the output of process data and the input of message receipts. Figure 2As shown, process data output includes real-time push of node information (e.g., a list of review node executors and approval node responsible persons) from the business system to the target communication system. Message receipt input includes receiving group information from the target communication system, such as group creation status and user read receipts, and writing it back to the business system, creating a closed-loop management system.

[0023] The business system calls the group creation interface of the target communication system (such as WeChat for Business and DingTalk) through a two-way API interface, and sends a group creation request message with a list of handlers to the target communication system. After receiving the group creation request message, the target communication system automatically creates the target group and automatically generates a standardized group name (such as "[Change No. 2025-012] Battery Module Review Group"), associates the change order number for easy traceability, and maps the handler employee numbers in the handler list to communication system accounts for batch addition, so that each handler in the handler list can be added to the target group.

[0024] Specifically, after a group is successfully created, the business system will use the target communication system to send a structured notification to all members of the target group. This notification includes the change order number, a link to review materials (such as design drawings stored on the company's network drive), and a deadline (e.g., "Approval must be completed by 17:00 on May 5, 2025"). This notification will also trigger a pop-up reminder on the communication software. For handlers who fail to review the notification promptly, a pop-up reminder and / or a resend text message and / or email can be automatically triggered after a first preset timeout, such as 30 minutes. The reminder might read, "You have a new change review task. Please check the group chat." Furthermore, for handlers who still fail to review the notification after a second preset timeout (the second preset timeout is greater than the first preset timeout), another reminder can be triggered, including but not limited to a pop-up notification on the communication software, text message, and email. Furthermore, for handlers who still fail to review the notification after a third preset timeout (the third preset timeout is greater than the second preset timeout), a reminder message can be sent to their supervisor, containing the task being handled and the name of the handler who failed to review the notification promptly.

[0025] Optionally, when the user (i.e., the initiator) triggers a group creation request for the target processing node, the urgency level can be set. Different urgency levels correspond to different first preset time lengths, second preset time lengths, and third preset time lengths. The higher the urgency level, the shorter the first preset time length, the second preset time length, and the third preset time length.

[0026] Within the target group, members can access change data (such as design parameters and cost estimates) from the business system and discuss the processing content corresponding to the target processing node to determine the results. Communication records generated during the discussion (such as message content, file versions, and voting results) are synchronized to the business system's log module.

[0027] Specifically, after the discussion within the target group concludes, the initiator can initiate a vote, with options including but not limited to approval and rejection. After the target group members complete the vote, the initiator can determine the outcome based on the voting results, which will be synchronized to the business system along with the group communication records.

[0028] Step 104: Receive the processing result sent by the target communication system.

[0029] The processing result (e.g., "Approve Change," "Reject with Modification") returned by the target communication system is written back to the business system via an API. If the result is "Approve," the process automatically proceeds to the next step (e.g., "Production Scheduling"). If the result is "Reject," the business system sends detailed revision suggestions (e.g., red comments in the group discussion log) to the initiator and marks the process as "Pending Revision."

[0030] The embodiment of the present invention, through the deep integration of the business system and the target communication system, can obtain the list of processors when receiving a group creation request, and automatically complete the creation of the target group on the target communication system. The creation of the target group can enable the processors to determine the processing results through real-time communication with the group and synchronize them to the business system, forming a closed process loop, improving collaboration efficiency and decision-making speed, optimizing the cross-departmental collaboration experience, and enhancing the consistency and traceability of process data.

[0031] In an optional embodiment of the present invention, receiving a user-triggered group creation request for a target processing node includes: Determine whether the type of the current processing node is a collaborative type; When the type of the current processing node is the collaboration type, determining the current processing node as the target processing node, and displaying a group creation control on a processing interface corresponding to the current processing node; When a first input to the group creation control is received from the user, it is determined that a group creation request for the target processing node is received.

[0032] Specifically, in the business system, there are processing nodes that require collaboration of multiple people, and there are also processing nodes that do not require the assistance of multiple people. The type of processing nodes that require the assistance of multiple people is the collaborative type. During the operation of the business system, it will be judged whether the type of the current processing node is the collaborative type. When the type of the current processing node is the collaborative type, it indicates that the processing node may need to establish a group for communication. At this time, the current processing node is determined as the target processing node. At the same time, a group creation control is displayed on the processing interface corresponding to the current processing node. The group creation control is used to trigger the group creation request. An intelligent event trigger is embedded in the process engine of the business system. When the process runs to a specific node (a node of the collaborative type), the node can be automatically set as the target processing node, and the list of processors configured for the node can be automatically extracted (supporting direct association from the organizational structure, or dynamic acquisition through process variables).

[0033] When the initiator of the current processing node determines that a group needs to be created, they can click on the group creation control. At this time, the business system will receive the first input and confirm that a group creation request for the target processing node has been received. Specifically, the first input is a selection input, and the first input includes but is not limited to actions such as clicking, long pressing, and sliding. From the traditional multiple operations of searching for communication tools, manually creating a group, and adding members one by one, multiple operations are compressed to clicking the control and completed in one step, shortening the time for group creation and improving the efficiency of group creation.

[0034] The above-mentioned implementation scheme of the present invention, by judging the current processing node type, activates the group creation function in the collaborative type node that requires multi-person collaboration, avoids interface redundancy in unnecessary scenarios, and improves user operation concentration. By dynamically displaying the group creation control in the collaborative type node processing interface, it guides users to quickly initiate group creation requests through visual interaction, shortens the operation path and reduces the learning cost. By capturing the user's operation events on the control in real time, it accurately triggers the group creation process, ensures the timely matching of collaboration needs and business system responses, thereby optimizing the efficiency of collaboration startup, enhancing process standardization, reducing manual errors, and providing a digital entrance with strong scene adaptability and smooth interaction for cross-departmental collaboration, effectively improving the collaborative efficiency and user experience of business processes.

[0035] In an optional embodiment of the present invention, obtaining a list of processors corresponding to the target processing node includes: Obtaining user identifiers corresponding to multiple processors of the target processing node; Determining the handler list according to the user identifiers corresponding to the plurality of handlers; Wherein, different processors are distinguished by the user identifier in both the business system and the target communication system.

[0036] To obtain a list of handlers corresponding to the target processing node, the business system first accesses the business process configuration database. This database stores the correspondence between each processing node and handler position. The same processing node can correspond to multiple handler positions, and the same handler position can include multiple handlers. For example, in a "new product development process," if the target processing node is "product design review," the business system reads from the configuration data that this node requires positions such as "product designer," "structural engineer," and "appearance designer" to participate in the review. By accessing the process configuration database, the business system obtains the multiple handler positions corresponding to the target processing node. Then, based on these obtained handler positions, the business system searches the enterprise organizational structure database. The organizational structure database contains detailed information about each employee within the enterprise, including their work number, name, department, and position. By matching the position name with the role, the business system retrieves the employee's work number (e.g., "00123," "00456," etc.) that meets the requirements. The work number serves as the handler's user identifier in the business system.

[0037] It's important to note that in practice, for some temporary project teams, handlers aren't assigned to fixed positions but are instead temporarily designated based on project needs. In these cases, the business system retrieves relevant information from the project management database. For example, the handlers for the "Order Plan Review" node are comprised of key employees from different departments. The business system reads the list of handlers entered by the project leader in the project management module and extracts their work ID or other unique identifier as the user ID.

[0038] Furthermore, to accommodate personnel changes, the business system synchronizes data with the human resources management system in real time. If an employee transfers, leaves, or a new employee joins, the organizational database is promptly updated to ensure that the retrieved user IDs are always accurate and valid. For example, if an engineer transfers from Department A to Department B, the business system will automatically exclude the engineer's user ID the next time it retrieves the list of processors for nodes related to Department A, preventing incorrect additions.

[0039] After obtaining the handler's user ID, the business system enters the handler list construction phase. This process requires converting the abstract user ID into a concrete set of handler information that can be used in subsequent operations. For example, the business system can access the enterprise organizational structure database or user information database, using the user ID as an index to query the detailed information corresponding to each ID, including the handler's name, department, position, contact information, and so on. For example, for user ID "00123", the business system will query and find that the corresponding handler is "Zhang San", whose department is "R&D Department", whose position is "Product Designer", and whose contact information is "123@456.com". The business system will integrate this information into a handler record and repeat this process to extract and record the handler information corresponding to all obtained user IDs.

[0040] When constructing the handler list, the business system also performs a series of data validation and filtering. First, it checks the handler's permission status to ensure that only those with the appropriate permissions are included in the list. Second, the handler list may be sorted and grouped according to specific rules. For example, it could group handlers by department, arranging them together for easier review and management; or it could sort by rank, placing key decision-makers at the top.

[0041] The business system also supports manual adjustments to the list of handlers. When special circumstances arise, such as the need to temporarily invite external experts or non-regular members from other departments, users can add additional personnel to the list by searching for their user ID or name within the business system interface. They can also remove unnecessary members. When adding external experts, the business system assigns them a temporary user ID for unified management throughout the subsequent process.

[0042] It's important to note that user identifiers are used to distinguish different handlers in both the business system and the target communication system, ensuring that both systems can accurately identify and match the same handler. This means establishing a unified user information data pool, synchronizing the organizational structure (department, position, and rank) in the business system with the user account system in the target communication system. Using unique user identifiers (such as employee IDs), accurate cross-system matching of personnel information is achieved, resolving the issue of duplicate identification.

[0043] In business systems, user IDs serve as unique credentials for handlers participating in various business process operations. From task assignment and operation logging to permission control, user IDs are used to distinguish different handlers. In target communication systems (such as WeChat for Business and DingTalk), the same user IDs are used to identify handlers. When a handler list is sent to the target communication system to create a group, the target communication system maps the user IDs in the business system to the user accounts in the target communication system. Specifically, the target communication system can maintain a user mapping table that records the communication system account information corresponding to each business system user ID (such as WeChat for Business' OpenID or DingTalk's UserID). When the business system sends the handler list, it also includes the user IDs. The communication system uses the mapping table to find the corresponding account and accurately add the handler to the group.

[0044] The above-mentioned implementation scheme of the present invention realizes the accurate mapping and efficient management of the identity of the handlers between the business system and the target communication system by constructing a unified user identification system. In the process of obtaining the handler list, the user identification is first located to eliminate the risk of personnel mismatch; then the detailed information is integrated with this as an index to form a complete and accurate handler list, and supports flexible adjustment. The unified user identification avoids personnel confusion caused by identity recognition differences, ensures that the identification and operation of handlers by the two systems are consistent, improves the accuracy of collaborative personnel screening and the reliability of process execution, shortens the collaboration preparation time through automation and standardized processes, enhances the compatibility and scalability of the business system with different communication tools and business changes, and provides a clear basis for operation tracing and responsibility definition, and comprehensively optimizes the cross-system collaborative management efficiency of the enterprise.

[0045] In an optional embodiment of the present invention, after sending the group creation request message carrying the handler list to the target communication system, the method further includes: receiving a group creation status fed back by the target communication system; When the group creation status is a completed status, a processing task notification and processing data corresponding to the target processing node are sent to the target group.

[0046] After sending a group creation request to the target communication system, the business system needs to monitor the response feedback from the target communication system in real time. This process relies on the combination of asynchronous messaging mechanism and interface callback technology.

[0047] First, when the business system sends a group creation request, it assigns a unique request ID (such as GRP_20250530_001) and embeds it in the request parameters. After receiving the request, the target communication system processes the group creation task, including checking the validity of the handler list, verifying user permissions, and allocating group resources. At this point, the target communication system updates the group creation status based on the progress of the task. Common statuses include "Creating," "Completed," and "Failed."

[0048] When the target communication system completes the group creation operation, it will return the group creation status and related information to the business system through the pre-agreed API interface callback address.

[0049] After receiving the callback request, the business system first verifies the request's legitimacy, including checking whether the request identifier matches the sent request and verifying the signature information (to prevent data tampering). If verification succeeds, the business system records the group creation status in the business process database and associates it with the corresponding target processing node for subsequent query and process control. If verification fails or the callback is not received within the specified time (e.g., a timeout occurs), the business system triggers a retry mechanism and resends the status query request to the target communication system to ensure the accuracy of the status acquisition.

[0050] Once the business system confirms the group creation status as "Complete," the task notification and data push phase begins. This phase requires integrating and formatting the task information and data in the business system, and then sending them to the corresponding group through the target communication system's interface.

[0051] First, the business system extracts processing task notifications related to the target processing node from the business process database. These notifications typically include information such as the task background, processing requirements, deadlines, and key metrics. For example, in the "New Product Design Review" node, a processing task notification might include information such as "This review requires a focused assessment of the product's thermal design. Results must be provided within three working days." The business system then encapsulates this information in a message format supported by the target communication system to ensure correct display within the communication group.

[0052] The business system then retrieves the processing data associated with the target processing node. This data may be stored in various locations, such as internal file servers or cloud storage platforms. Based on the data's storage path and access permissions, the business system packages the files or generates accessible links. For example, for design drawings stored on a file server, the business system compresses them into a package and generates an encrypted download link. For online documents, the system directly retrieves the document's shared link.

[0053] When sending task notifications and processing data to a target group, the business system can call the message sending interface provided by the target communication system. Before sending, the business system will also conduct a series of permission checks and content audits to ensure that only authorized processors can access the data and check whether the content contains sensitive information.

[0054] To enhance the receiving experience for handlers, the target communication system also personalizes messages. For example, task notifications include @All Members reminders and deliver task instructions with different focuses based on the handler's role. For review team leaders, review decision requirements are highlighted; for regular members, the submission format and deadline are emphasized. Furthermore, the target communication system records the message delivery status and, if a delivery fails, automatically retries and notifies the administrator for intervention.

[0055] This embodiment of the present invention achieves a fully automated process for group creation and task collaboration by establishing a two-way interactive closed loop between the business system and the target communication system. Task processing notifications and data are automatically pushed based on the completion status, accurately and promptly delivering critical information to the target group, reducing information errors and omissions caused by manual intervention.

[0056] In an optional embodiment of the present invention, the method further includes: When the target processing node includes an approval task, obtaining the approver user identifier corresponding to the approval task and the approval information corresponding to the approval task; An approval notification message carrying the approver user ID and the approval information is sent to the target communication system, so that the target communication system sends the approval information to the approver corresponding to the approver user ID.

[0057] In the current business system, the approval process relies solely on business system message notifications, which means that users cannot learn about process tasks without logging into the business system. This leads to untimely process processing and low approval efficiency, which greatly hinders the progress of product design changes, has a negative impact on the smooth progress of the entire business process, and reduces the company's efficiency and competitiveness in product change management.

[0058] In an embodiment of the present invention, when the business system recognizes that the target processing node contains an approval task, it first accesses the business process configuration database, which stores configuration information such as the task type and approval rules of each processing node. Then, based on the approval rules, a search is performed in the enterprise organizational structure database or the authority management database. The organizational structure database records information such as the employee's work number, name, department, and position, while the authority management database stores the approval authority corresponding to each position. By matching the job title (such as "Finance Manager" or "Financial Director") with the authority rules, the business system obtains the work number of the corresponding approver, and these work numbers are the target user identifiers of the approver in the business system.

[0059] The business system integrates information from various data sources based on the type of approval task and the stage of the process. For purchase order approvals, approval information may include the order number, supplier name, purchase amount, and item details, all stored in the procurement business database. The business system uses the order number as an index to extract and aggregate relevant fields into complete approval information. Furthermore, if the approval task is associated with other documents (such as contract attachments or requirement specifications), the business system retrieves file links or summary information from the file storage server or cloud storage platform and incorporates them into the approval information.

[0060] During the information integration process, the business system also performs data validation and formatting. On one hand, it checks the completeness and accuracy of the approval information, such as ensuring that the numerical format of the purchase amount is correct and that the link to the contract attachment is accessible. On the other hand, it encapsulates the approval information in a format supported by the target communication system (such as JSON or XML) for subsequent transmission. For example, purchase order approval information can be encapsulated as a JSON object containing basic order information, a list of products, and links to attachments to ensure that it can be correctly parsed and displayed in the target communication system.

[0061] After obtaining the approver's target user identification and approval information, a secure and efficient data transmission channel will be established between the business system and the target communication system to ensure that the approval notice is accurately delivered.

[0062] First, the business system invokes the message sending interface connected to the target communication system, passing the target user ID and approval information as parameters. Taking WeChat for Business as an example, the business system uses the "Application Message Sending Interface" to encapsulate the approval notification information into a request body that complies with the interface specification. In addition to the target user ID (WeChat for Business UserID) and approval information, the request body also specifies parameters such as the message type (e.g., text message, image message), notification method (e.g., whether to @user, whether to send a reminder), etc. For example, for urgent approval tasks, the business system will @approver and send a pop-up reminder on the mobile phone.

[0063] Before sending approval notifications, the business system performs a series of pre-processing steps. These include a secondary verification of user permissions to ensure the approver corresponding to the target user ID still has approval authority. If the approver's authority has been changed or frozen, the notification is suspended and the exception logged. Sensitive data in the approval information, such as purchase amounts and contract terms, is encrypted using an encryption algorithm to ensure data security during transmission.

[0064] When the target communication system receives the approval notification, it parses and verifies the request. Once verification is successful, the target user ID is used to locate the corresponding approver account within the communication system and the approval information is sent to the approver in the specified manner. For example, in DingTalk, approval information is pushed to the approver as a work notification. Upon receiving the notification on their mobile phone or computer, the approver can click on it to view the detailed approval details and action options (such as the "Approve" and "Reject" buttons).

[0065] To ensure the effective delivery of approval notifications, the business system establishes a message delivery status tracking mechanism. After the target communication system completes message delivery, it will provide feedback to the business system via an interface callback, providing the delivery result (e.g., success, failure, or user unread status). Upon receiving this feedback, the business system will record the result in a message log database and associate it with the approval task. If delivery fails or the approver remains unread for an extended period of time, the business system will trigger a reminder strategy, such as resending the notification after a certain period of time or sending a reminder via SMS, to ensure that the approver receives the approval task promptly.

[0066] The above-mentioned implementation scheme of the present invention realizes the intelligent and automated processing of approval tasks by constructing a deep collaboration mechanism between the business system and the target communication system. By obtaining the approver and approval information, it ensures that the task-related content is complete, accurate and secure, so that the approver can receive the task in a familiar communication environment in a timely manner, comprehensively improves the processing efficiency, and ensures the smooth progress of the business process.

[0067] In an optional embodiment of the present invention, when the target processing node includes an approval task, the method further includes: Determine whether the approval task is an urgent approval task; When the approval task is the urgent approval task, after sending the approval notification information carrying the target user identifier and the approval information to the target communication system, determining whether the approval task is completed at a preset time interval; When the approval task is not completed, the approval information is sent to the mobile terminal of the approver in a targeted manner.

[0068] When the business system identifies an approval task at a target processing node, it determines its urgency. First, the business system retrieves the basic configuration information related to the approval task from the business process configuration database. During the process design phase, administrators pre-define the urgency of some approval tasks. If this isn't explicitly marked in the basic configuration, the business system dynamically determines the urgency based on real-time business data and pre-set rules.

[0069] In practice, the business system also supports manual intervention in decision-making. When special circumstances arise, the operator can manually mark the approval task as urgent in the business system and provide a description of the reason for the urgency. The business system will record this information and incorporate it into the decision-making process. During the decision-making process, the business system will conduct multiple rounds of data verification and logic validation to ensure the accuracy of the results and avoid misjudgments or omissions.

[0070] When an approval task is determined to be urgent, the business system immediately initiates the scheduled monitoring mechanism after sending the approval notification information through the target communication system. The business system reads the preset duration of the "urgent task monitoring interval" from the system configuration table. This preset duration can be set by the enterprise based on its business characteristics and approval efficiency requirements, generally between 15 minutes and 1 hour.

[0071] During the monitoring process, the business system obtains the status of approval tasks through a combination of database queries and interface calls. It queries the business process database in real time for records related to the approval task to check whether the approver has submitted the approval result (e.g., approval or rejection). If the business system has data linkages with other related systems, it will also call the interfaces of these related systems to obtain more comprehensive approval progress information.

[0072] When making judgments at preset intervals, the business system conducts rigorous logical analysis of the information it receives. If the database record associated with the approval task indicates that the approval status has been updated to "Completed," the task is considered complete; conversely, if these conditions are not met, the task is considered incomplete. To ensure the accuracy of these judgments, the business system performs multiple data checks and cross-validations to avoid misjudgments due to data delays or anomalies.

[0073] When the business system determines that an urgent approval task has not been completed, it will immediately activate a multi-channel reminder mechanism to ensure that the approval information can reach the approver in a timely and effective manner. The business system can use a targeted method to send the approval information to the approver's mobile terminal. The target method includes but is not limited to SMS, email, and other communication software notification methods. The other communication software here can be DingTalk, QQ, etc. First, the business system will retrieve the approver's mobile terminal information from the user information database, including mobile phone number, email address, and account information of other communication software. This information is uniformly entered by the human resources department when the employee joins the company and is regularly updated and maintained to ensure the accuracy of the information.

[0074] When selecting a delivery method, the business system will operate according to the pre-set priority strategy. If the enterprise sets SMS as the highest priority notification method, the business system will first call the SMS service interface to format the approval information according to SMS format requirements. For example, the approval information will be simplified to include key content such as the order number, urgency, and brief approval requirements. An approval link or operation instructions will be added to the end of the message to facilitate rapid processing by the approver. The SMS service interface will then connect to the operator's SMS gateway to ensure that the message is accurately delivered to the approver's mobile phone.

[0075] If the SMS fails to send (e.g., due to an incorrect number or carrier service anomaly), the business system automatically switches to email delivery. The business system then calls the email service interface to generate an email containing complete approval information. The email content is carefully formatted and includes a detailed description of the approval task, relevant attachments (such as contract documents and requirements), and clear approval instructions. The subject line of the email will highlight "Urgent Approval Task Reminder" to attract the approver's attention. After the email is sent, the business system will record the delivery status and continuously monitor the email's reading status. If the email remains unread for an extended period of time, the business system will consider sending another reminder or taking other supplementary measures.

[0076] Throughout the entire messaging process, the business system implements strict security controls. For sensitive information within SMS messages and email attachments, the business system utilizes encryption technology to ensure the security of information during transmission and storage. Furthermore, the business system records detailed information such as the time, method, and receipt status of each message sent, creating a complete operation log for subsequent query and audit.

[0077] The above-mentioned implementation scheme of the present invention improves the responsiveness and execution efficiency of the approval process by constructing a multi-level emergency approval task processing system.

[0078] In an optional embodiment of the present invention, after sending the processing task notification and processing data corresponding to the target processing node to the target group, the method further includes: At interval target duration, obtain the reading status of each processor in the processor list on the processing task notification; Determine the handler whose reading status is unread as the target user; The processing task notification is sent to the mobile terminal of the target user in a targeted manner.

[0079] Once the business system sends the task notification and processing data to the target group, a scheduled monitoring mechanism is activated to track the effectiveness of the information reaching the target group. First, the business system retrieves the pre-set "target duration" parameters from the system configuration center. This parameter is flexibly configured by the enterprise based on the business urgency and collaboration rhythm, aiming to balance the timeliness of information reminders with avoiding excessive user interruption. For example, for routine project tasks, the target duration might be set at 4 hours; for emergency repair tasks, the duration is shortened to 30 minutes.

[0080] The business system then retrieves the information through a deeply integrated interface with the target communication system. For example, using WeChat for Business, the business system calls its "Get Message Reading Status" API, passing in the target group ID and the unique identifier of the task notification as parameters. Upon receiving the request, the target communication system queries its internal database for all member reading records corresponding to the message and returns a response containing information such as the handler's user ID and reading timestamp.

[0081] After obtaining the processor's reading status data, the business system enters the screening and marking phase. Based on the preset judgment logic, the business system analyzes each reading status record: if the reading timestamp is empty or the timestamp is later than the current monitoring time (i.e., unread), the corresponding processor's user ID is marked as "unread."

[0082] It's important to note that to improve screening accuracy, the business system incorporates multi-dimensional auxiliary judgment. For example, considering the handler's recent activity status (such as online status and last login time), if a member has been offline for a long time, even if they haven't marked it as read, they will not be included in the target user list to avoid invalid reminders. For task notifications containing attachments, if the handler has downloaded the file but hasn't triggered the message read mark, the business system will exclude them. The screening results are stored in a temporary task reminder table, linking the task ID, handler information, and the reason for unreading, to facilitate subsequent tracking and management.

[0083] After identifying the target users, the business system activates a multi-channel outreach mechanism to ensure that critical information reaches the user's mobile device directly, bypassing the limitations of communication groups. The business system can send task notifications to the target user's mobile device using targeted methods, including but not limited to SMS, email, and other communication software notifications. These other communication software can include DingTalk, QQ, and other similar communication software. First, the business system retrieves the target user's mobile phone number, email address, and other communication software account information from the user information database. Regarding delivery strategies, the business system follows a priority rule: if the enterprise has configured SMS as a high priority, the SMS gateway interface is used to send notifications first. The business system then condenses the original task notification, extracting core content such as the task name, deadline, and key requirements, and generates a text message that meets SMS length limits. For example, the "XX Project Requirements Review Meeting" task notification can be condensed to "[Urgent] Please review the XX Project Review Materials and provide feedback before 18:00 today. Link: xxx," and a short link to the detailed task page is added at the end of the message. After the SMS is sent, the business system monitors the operator's receipt status in real time. If the sending fails (such as wrong number, channel congestion), it will automatically switch to email sending.

[0084] When sending an email, the business system calls the email service API to generate a rich text email. The email body includes the complete task notification content and the attached processing materials (if the file is too large, a cloud storage download link is generated), and key information is highlighted through formatting such as highlighting and bolding. A striking message is added to the email subject (such as "[Unread Reminder] Please process XX task immediately"), and an importance mark is set to ensure that it is displayed first in the user's mailbox. To improve reach, the business system supports personalized customization, such as adding task background and strategic value explanations for management users, while focusing on operational guidance for ordinary members.

[0085] Throughout the entire delivery process, the business system strictly adheres to data security regulations. Sensitive information within SMS messages (such as contract amounts and customer data) is encrypted for transmission; email attachments are digitally signed and permission-controlled to ensure access only by the intended user. Furthermore, the business system records the time, channel, status, and user feedback (such as email opens and link clicks) for each delivery, forming a complete analysis chain for reach effectiveness.

[0086] This embodiment of the present invention effectively addresses the challenges of overlooked and delayed information delivery during group collaboration by building an automated, intelligent task notification tracking and delivery system. This multi-channel, prioritized secondary reminder strategy transcends the limitations of communication groups and ensures that critical task information reaches the handler's mobile device in the most efficient manner.

[0087] The above describes the processing method of the business system provided by the embodiment of the present invention. The following describes the processing device of the business system provided by the embodiment of the present invention with reference to the accompanying drawings.

[0088] like Figure 3 As shown, an embodiment of the present invention further provides a processing device for a business system, the device comprising: A first receiving module 301 is configured to receive a group creation request for a target processing node triggered by a user, wherein the target processing node corresponds to multiple processors; A first acquisition module 302 is configured to acquire a list of processors corresponding to the target processing node in response to the group creation request; The first sending module 303 is configured to send a group creation request message carrying the processor list to the target communication system, so that the target communication system creates a target group and adds each processor in the processor list to the target group; wherein the processors in the processor list communicate with each other through the target group regarding the processing content corresponding to the target processing node to determine the processing result; The second receiving module 304 is configured to receive the processing result sent by the target communication system.

[0089] Optionally, the first receiving module includes: The judgment submodule is used to judge whether the type of the current processing node is a collaborative type; a first determining submodule, configured to determine the current processing node as the target processing node when the type of the current processing node is the collaboration type, and display a group creation control on a processing interface corresponding to the current processing node; The second determining submodule is configured to determine that a group creation request for the target processing node is received when a first input to the group creation control is received from the user.

[0090] Optionally, the first acquisition module includes: An acquisition submodule, configured to acquire user identifiers corresponding to multiple processors of the target processing node; A third determining submodule is configured to determine the handler list according to the user identifiers corresponding to the plurality of handlers; Wherein, different processors are distinguished by the user identifier in both the business system and the target communication system.

[0091] Optionally, after sending the group creation request message carrying the handler list to the target communication system, the apparatus further includes: A third receiving module is used to receive the group creation status fed back by the target communication system; The second sending module is configured to send the processing task notification and processing data corresponding to the target processing node to the target group when the group creation status is completed.

[0092] Optionally, the device further includes: A second acquisition module is configured to acquire, when the target processing node includes an approval task, an approver user identifier corresponding to the approval task and approval information corresponding to the approval task; The third sending module is configured to send approval notification information carrying the approver user identifier and the approval information to the target communication system, so that the target communication system sends the approval information to the approver corresponding to the approver user identifier.

[0093] Optionally, when the target processing node includes an approval task, the apparatus further includes: A first judging module is used to judge whether the approval task is an urgent approval task; A second judgment module is configured to, when the approval task is the urgent approval task, determine whether the approval task is completed at a preset time interval after sending the approval notification information carrying the target user identifier and the approval information to the target communication system; The fourth sending module is used to send the approval information to the mobile terminal of the approver in a targeted manner when the approval task is not completed.

[0094] Optionally, after sending the processing task notification and processing data corresponding to the target processing node to the target group, the apparatus further includes: A third acquisition module is used to obtain the reading status of the processing task notification by each processor in the processor list at intervals of a target time; A determination module, configured to determine the handler whose reading status is unread as a target user; The fifth sending module is used to send the processing task notification to the mobile terminal of the target user in a targeted manner.

[0095] The processing device of the business system provided by the present invention, through the deep integration of the business system and the communication system, can obtain the list of processors when receiving a group creation request, and automatically complete the creation of the target group on the target communication system. The creation of the target group can enable the processors to determine the results through real-time communication with the group and synchronize them to the business system, forming a closed process loop, improving collaboration efficiency and decision-making speed, optimizing the cross-departmental collaboration experience, and enhancing the consistency and traceability of process data.

[0096] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0097] An embodiment of the present invention also provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and runnable on the processor. When the computer program is executed by the processor, the various processes of the processing method embodiment of the above-mentioned business system are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0098] For example, Figure 4 FIG. 1 shows a schematic diagram of the physical structure of an electronic device. Figure 4 As shown, the electronic device may include: a processor 410, a communications interface 420, a memory 430, and a communications bus 440. The processor 410, the communications interface 420, and the memory 430 communicate with each other via the communications bus 440. The processor 410 may invoke logic instructions stored in the memory 430 to execute the following steps: receiving a user-triggered group creation request for a target processing node, wherein the target processing node corresponds to multiple processors; in response to the group creation request, obtaining a list of processors corresponding to the target processing node; sending a group creation request message containing the list of processors to a target communication system, causing the target communication system to create a target group and add each processor in the list of processors to the target group; wherein the processors in the list of processors communicate with each other via the target group regarding the processing content corresponding to the target processing node to determine a processing result; and receiving the processing result from the target communication system. The processor 410 may also execute other solutions in the embodiments of the present invention, which will not be further described here.

[0099] Furthermore, the logic instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product, stored in a storage medium, includes instructions for causing a computer device (such as a personal computer, server, or network device) to execute all or part of the steps of the methods described in various embodiments of the present invention.

[0100] An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the various processes of the aforementioned business system processing method embodiment and achieves the same technical effects. To avoid repetition, the details are omitted here. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0101] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0102] Through the above description of the embodiments, those skilled in the art will clearly understand that the methods of the above embodiments can be implemented using software plus the necessary general-purpose hardware platform. Of course, hardware can also be used, but in many cases the former is the more preferred implementation method. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, or optical disk) and includes a number of instructions for enabling a terminal (such as a mobile phone, computer, server, air conditioner, or network device) to execute the methods described in the various embodiments of the present invention.

[0103] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are protected by the present invention.

[0104] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of the present invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can 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.

[0105] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0106] In the embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0108] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0109] If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product, stored in a storage medium, includes instructions for causing a computer device (such as a personal computer, server, or network device) to perform all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include various media capable of storing program code, such as USB flash drives, removable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0110] The above description is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed by the present invention, which should be covered by the scope of protection of the present invention.

Claims

1. A processing method for a business system, characterized in that: The method comprises: receiving a user-triggered group creation request for a target processing node, wherein the target processing node corresponds to a plurality of processors; In response to the group creation request, obtaining a processor list corresponding to the target processing node; sending a group creation request message carrying the processor list to a target communication system, so that the target communication system creates a target group and adds each processor in the processor list to the target group; wherein the processors in the processor list communicate with each other through the target group regarding the processing content corresponding to the target processing node to determine the processing result; Receive the processing result sent by the target communication system.

2. The processing method of the business system according to claim 1, characterized in that: Receive a user-triggered group creation request for a target processing node, including: Determine whether the type of the current processing node is a collaborative type; When the type of the current processing node is the collaboration type, determining the current processing node as the target processing node, and displaying a group creation control on a processing interface corresponding to the current processing node; When a first input to the group creation control is received from the user, it is determined that a group creation request for the target processing node is received.

3. The processing method of the business system according to claim 1, characterized in that: Obtain the list of handlers corresponding to the target processing node, including: Obtaining user identifiers corresponding to multiple processors of the target processing node; Determining the handler list according to the user identifiers corresponding to the plurality of handlers; Wherein, different processors are distinguished by the user identifier in both the business system and the target communication system.

4. The processing method of the business system according to claim 1, characterized in that: After sending the group creation request message carrying the handler list to the target communication system, the method further includes: receiving a group creation status fed back by the target communication system; When the group creation status is a completed status, a processing task notification and processing data corresponding to the target processing node are sent to the target group.

5. The processing method of the business system according to claim 1, characterized in that: The method further comprises: When the target processing node includes an approval task, obtaining the approver user identifier corresponding to the approval task and the approval information corresponding to the approval task; An approval notification message carrying the approver user ID and the approval information is sent to the target communication system, so that the target communication system sends the approval information to the approver corresponding to the approver user ID.

6. The processing method of the business system according to claim 5, characterized in that: When the target processing node includes an approval task, the method further includes: Determine whether the approval task is an urgent approval task; When the approval task is the urgent approval task, after sending the approval notification information carrying the target user identifier and the approval information to the target communication system, determining whether the approval task is completed at a preset time interval; When the approval task is not completed, the approval information is sent to the mobile terminal of the approver in a targeted manner.

7. The processing method of the business system according to claim 4, characterized in that: After sending the processing task notification and processing data corresponding to the target processing node to the target group, the method further includes: At interval target duration, obtain the reading status of each processor in the processor list on the processing task notification; Determine the handler whose reading status is unread as the target user; The processing task notification is sent to the mobile terminal of the target user in a targeted manner.

8. A processing device for a business system, characterized in that: include: A first receiving module is configured to receive a group creation request for a target processing node triggered by a user, wherein the target processing node corresponds to multiple processors; A first acquisition module, configured to acquire a processor list corresponding to the target processing node in response to the group creation request; a first sending module, configured to send a group creation request message carrying the processor list to a target communication system, so that the target communication system creates a target group and adds each processor in the processor list to the target group; wherein the processors in the processor list communicate with each other through the target group regarding the processing content corresponding to the target processing node to determine the processing result; The second receiving module is configured to receive the processing result sent by the target communication system.

9. An electronic device, characterized in that: The system comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the processing method of the business system according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processing method of the business system according to any one of claims 1 to 7 is implemented.

Images