Item processing method and device, electronic equipment, storage medium and product

Abstract

The invention provides an item processing method and device, electronic equipment, a storage medium and a product. The method comprises the steps of generating a target processing item corresponding to information of a to-do list in response to the information of the to-do list of an external application system; generating a target access link corresponding to the target processing item, and sending a target message containing the target access link to the target user; in response to a click operation of the target user, generating an item processing page adapted to the target terminal, the item processing page being used for receiving a processing operation of the target user for the target processing item; and receiving a submission instruction corresponding to the processing operation, generating a processing result based on the content of the processing operation, and synchronizing the processing result to the external application system, so that the external application system updates the state of the to-do list information after receiving the processing result.

Description

Technical Field

[0001] This disclosure relates to the field of event processing technology, and in particular to an event processing method, apparatus, electronic device, storage medium, and product. Background Technology

[0002] In the handling of related matters, users typically first access a designated intranet environment through a specific software terminal or authentication medium. Then, after logging in via an account management-authentication-authorization-audit (4A) process, they can access a dedicated webpage or use a specific mobile application to view and process pending tasks. In these external application systems, approval operations often require users to manually switch between different applications or interfaces to complete the business approval process across different application systems, which is cumbersome and inefficient. Summary of the Invention

[0003] This disclosure provides a method, apparatus, electronic device, storage medium, and product for handling matters, in order to solve the problem in the related art that users need to manually switch between different applications or interfaces to complete the business processing and approval process in different application systems, which is cumbersome and inefficient.

[0004] A first aspect of this disclosure provides a method for handling events, the method comprising: In response to to-do information from external application systems, generate target processing items corresponding to the to-do information; Generate a target access link corresponding to the target processing item, and send a target message containing the target access link to the target user; In response to the target user's click operation, a task processing page adapted to the target terminal is generated. The task processing page is used to receive the target user's processing operation for the target task. Upon receiving the submission instruction corresponding to the processing operation, the system generates a processing result based on the content of the processing operation and synchronizes the processing result to the external application system so that the external application system can update the status of the pending items after receiving the processing result.

[0005] In one embodiment, generating a target access link corresponding to a target processing item includes: Get the access link template; Based on the access link template and the identifier of the target processing item, generate the original access link corresponding to the target processing item; Transform the original access link into the target access link.

[0006] In one embodiment, in response to a click operation by a target user, a task processing page adapted to the target terminal is generated, including: In response to a click by a target user, the system obtains the target user's identifier and generates an access token via the mobile phone number retrieval module. The identity status of the target user is determined based on the target user identifier and access token; In response to the target user's valid identity status, a task processing page adapted to the target terminal is generated.

[0007] In one embodiment, in response to the target user's valid identity status, a task processing page adapted to the target terminal is generated, including: In response to the valid identity status of the target user, obtain the status of the target processing item; In response to the target status of the task being processed, generate a task processing page adapted to the target terminal.

[0008] In one embodiment, after generating a task management page adapted to the target terminal in response to a click operation by a target user, the method includes: In response to receiving the target user's processing operation for the target matter, obtain the status of the target matter; In response to the target status being the target status, submit the processing result of the target status.

[0009] In one embodiment, after receiving a submission instruction corresponding to a processing operation, generating a processing result based on the content of the processing operation, and synchronizing the processing result to an external application system, the method provided in this disclosure includes: Based on the processing results of the target processing items, generate target processing records corresponding to the processing results; Synchronize the target processing records to external application systems.

[0010] A second aspect of this disclosure provides an event processing apparatus, comprising: The first generation unit is used to generate target processing items corresponding to the to-do information in response to the to-do information of the external application system. The second generation unit is used to generate a target access link corresponding to the target processing item and send a target message containing the target access link to the target user. The processing unit is used to respond to the click operation of the target user and generate a task processing page adapted to the target terminal. The task processing page is used to receive the processing operation of the target user for the target task. The synchronization unit is used to receive the submission instruction corresponding to the processing operation, generate the processing result based on the content of the processing operation, and synchronize the processing result to the external application system so that the external application system can update the status of the pending items information after receiving the processing result.

[0011] A third aspect of this disclosure provides an electronic device comprising: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the methods described in the first aspect of this disclosure.

[0012] A fourth aspect of this disclosure provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to perform the methods described in the first aspect of this disclosure.

[0013] A fifth aspect of this disclosure provides a computer program product including a computer program that, when executed by a processor, implements the methods described in the first aspect of this disclosure.

[0014] In summary, this disclosure proposes a task processing method, which includes: generating a target task corresponding to the to-do information in response to the to-do information of an external application system; generating a target access link corresponding to the target task and sending a target message containing the target access link to the target user; generating a task processing page adapted to the target terminal in response to the click operation of the target user, the task processing page being used to receive the target user's processing operation for the target task; receiving a submission instruction corresponding to the processing operation, generating a processing result based on the content of the processing operation and synchronizing the processing result to the external application system, so that the external application system updates the status of the to-do information after receiving the processing result.

[0015] According to the solution provided in this disclosure, in response to the to-do information of an external application system, a target processing item corresponding to the to-do information is generated. A target access link corresponding to the target processing item is generated, and a target message containing the target access link is sent to the target user. In response to the click operation of the target user, a processing page adapted to the target terminal is generated. The processing page is used to receive the processing operation of the target user for the target processing item. Upon receiving the submission instruction corresponding to the processing operation, a processing result is generated based on the content of the processing operation and the processing result is synchronized to the external application system. This allows the external application system to update the status of the to-do information after receiving the processing result, thereby achieving cross-external application system integration, unifying the entry point for processing items, and improving the efficiency of item processing.

[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0018] Figure 1 A flowchart illustrating the event handling method provided in this embodiment of the disclosure; Figure 2 This is a schematic flowchart illustrating a method for handling events according to an embodiment of the present disclosure. Figure 3 A flowchart illustrating a method for establishing a correspondence between to-do items in an external application system and unified mobile quick approval items, as provided in this embodiment of the disclosure; Figure 4 A flowchart illustrating the mobile phone batch processing method provided in this embodiment of the disclosure; Figure 5 A schematic diagram of the structure of the event processing device provided in the embodiments of this disclosure; Figure 6 This is a schematic diagram of the hardware composition structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0019] Embodiments of this disclosure are described in detail below. Examples of these embodiments are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0020] Related solutions typically involve handling approval processes through internal office automation systems or specific applications. These solutions generally require users to first access a designated intranet environment via a Virtual Private Network (VPN) client, and then log in using a 4A account before accessing a dedicated webpage or using a specific mobile application to view and process pending tasks. In these systems, approval operations often require users to manually switch between different applications or interfaces, and there is a lack of a unified interface to integrate pending tasks from different business systems. Furthermore, existing solutions do not support efficient cross-platform collaboration, resulting in a poor user experience and low approval efficiency.

[0021] Users need to use specific software terminals (such as VPN clients) or identity authentication media (such as U-Key) to log in to multiple independent systems or applications using multiple application system login accounts in order to complete different business processing and approval processes. The operation is cumbersome and inefficient. The lack of a unified interface to integrate pending tasks from different business systems leads to information being scattered and difficult to manage. Furthermore, the lack of support for efficient cross-platform collaboration results in a poor user experience.

[0022] In the process of handling related matters, users typically first access a designated intranet environment through a specific software terminal or authentication medium. Only after logging in with a 4A account can they access a dedicated webpage or use a specific mobile application to view and process pending tasks. In these external application systems, approval operations often require users to manually switch between different applications or interfaces to complete the business approval process across different application systems, which is cumbersome and inefficient.

[0023] To address the issues in existing solutions, this approach generates a target processing item corresponding to the to-do list information in response to external application systems. It then sends a target message containing the target access link to the target user by generating a target access link for that item. In response to user clicks, it generates a processing page adapted for the target terminal, which receives user actions for the target processing item. Upon receiving a submission command for the action, it generates a processing result based on the action's content and synchronizes the result to the external application system. This allows the external application system to update the status of the to-do list information upon receiving the result, achieving cross-application system integration, a unified entry point for processing items, and ultimately improving processing efficiency.

[0024] The present disclosure will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0025] The present disclosure provides a method for handling matters, which can be applied to mobile terminal rapid approval scenarios. The execution subject of the method is a matter handling system, which is deployed on the server side. The matter handling system can be a mobile phone fast approval module, which communicates with external application systems, mobile phone number retrieval modules, SMS delivery gateways and user terminals. The mobile phone number retrieval module refers to the one-click authentication capability of the local number provided by the operator, which can obtain the current device's mobile phone number without the user's awareness.

[0026] like Figure 1 As shown, Figure 1 This is a flowchart illustrating the event handling method provided in this embodiment of the disclosure. The event handling method provided in this embodiment of the disclosure includes the following steps: Step 101: In response to the to-do information of the external application system, generate the target processing item corresponding to the to-do information; In one embodiment, the external application system refers to the business system that initiates the approval request, such as an office automation (OA) system, a human resources (HR) system, or a financial system.

[0027] In one embodiment, the push application interface of an external application system can be called through an HTTPS interface. The request header carries appId and appSecret for authentication, and the request body is in JavaScript Object Notation (JSON) format. The to-do information includes key fields of the to-do, including at least the to-do identifier (to-do ID, used to identify a specific approval task instance), the to-do title, the to-do submitter, the approval page content (JSON structure), approval attachments (optional), and the approver's mobile phone number.

[0028] In one embodiment, the target processing item is a pending processing item that has been standardized within the mobile quick approval module. Specifically, a unique target processing item ID can be generated based on the unique identifier of the external application system, the pending item ID, and the approver's mobile phone number, and the processing status is "pending".

[0029] Step 102: Generate the target access link corresponding to the target processing item, and send a target message containing the target access link to the target user; In one embodiment, the target access link refers to a URL that, when clicked by a user, leads to the approval page; it is typically a short link.

[0030] In one embodiment, the SMS delivery gateway is an enterprise-grade SMS sending channel used to send notifications to users' mobile phones.

[0031] In one embodiment, the target message is SMS content containing an access link. The target message may include system identifiers such as mobile quick approval, item title, access short link, and validity period reminder. Specifically, the target message is generated by template, supports multiple languages ​​and multiple business types, and can be configured to include attachment previews.

[0032] Step 103: In response to the target user's click operation, generate a task processing page adapted to the target terminal. The task processing page is used to receive the target user's processing operation for the target task. In one embodiment, the target user's click action refers to the target user clicking a link in a text message on a mobile device.

[0033] In one embodiment, the task processing page is typically a HyperText Markup Language version 5 (H5) page, used to display approval content and receive actions from the target user.

[0034] In one embodiment, the task processing page is dynamically generated by a front-end framework (such as Vue / React), and the content comes from the to-do information pushed by an external application system. It supports field rendering, attachment preview, approval opinion input, and approval / rejection buttons, and adapts to different mobile phone models and screen sizes.

[0035] Step 104: Upon receiving the submission instruction corresponding to the processing operation, generate the processing result based on the content of the processing operation and synchronize the processing result to the external application system so that the external application system can update the status of the to-do item information after receiving the processing result.

[0036] In one embodiment, the submission instruction corresponding to the processing operation refers to the signal that triggers the final confirmation action after the user has completed all operations. It is usually manifested as clicking buttons such as submit, pass, or reject. The submission instruction indicates that the user has completed the processing.

[0037] In one embodiment, the processing operation may include filling in form fields, selecting approval opinions, such as agreeing, rejecting, uploading attachments, checking checkboxes, and entering remarks.

[0038] In one embodiment, the processing result is structured data generated based on the content of the processing operation. The processing result may include information such as the approval opinions submitted by the target user on the task processing interface, the approval result (approval / rejection), and the approval time.

[0039] In one embodiment, the processing result is synchronized to an external application system via an asynchronous callback interface.

[0040] In one embodiment, the external application system updating the status of the pending task information after receiving the processing result means that the external system marks the status of the pending task information as completed instead of pending.

[0041] By responding to to-do information from external application systems, a target processing item corresponding to the to-do information is generated. A target access link corresponding to the target processing item is generated, and a target message containing the target access link is sent to the target user. In response to the target user's click operation, a processing page adapted to the target terminal is generated. The processing page is used to receive the target user's processing operation for the target processing item. Upon receiving the submission instruction corresponding to the processing operation, a processing result is generated based on the content of the processing operation and synchronized to the external application system. This allows the external application system to update the status of the to-do information after receiving the processing result, achieving cross-external application system integration, unifying the entry point for processing items, and thus improving the efficiency of item processing.

[0042] In one embodiment, the mobile phone number of the approver in the pending item information of the external application system can be one or more, and this application does not limit this. Specifically, when there are multiple mobile phone numbers of the approver, the external application system splits the pending item information into multiple pending items that only include a single mobile phone number of the approver, and then pushes the pending items that only include a single mobile phone number of the approver to the mobile quick approval module. For the mobile quick approval module, all the pending items received include a single mobile phone number of the approver, and the mobile quick approval module generates a corresponding target processing item for each pending item.

[0043] In one embodiment, when a task requires multiple approvers to process simultaneously, the external application system can generate task information independently for each approver without interference. Each target user only receives the approval tasks related to them, which can avoid information leakage or misoperation.

[0044] In one embodiment, generating a target access link corresponding to a target processing item includes: Get the access link template; Based on the access link template and the identifier of the target processing item, generate the original access link corresponding to the target processing item; Transform the original access link into the target access link.

[0045] In one embodiment, the access link template is a preset Uniform Resource Locator (URL) string template containing placeholders (such as {itemId}) used to dynamically concatenate and generate the original access link.

[0046] In one embodiment, a complete, accessible original access link is generated by concatenating an access link template with the target processing item ID.

[0047] In one embodiment, the target access link refers to the final access link after being encapsulated as a short link or after security processing. It is usually a short link, which is used to automatically identify the mobile phone number after the user clicks it, so as to achieve seamless login.

[0048] In one embodiment, the target access link can be set to expire (e.g., 30 minutes), after which it will automatically become invalid, preventing the link from being abused for a long time.

[0049] In one embodiment, one or more access link templates are preset in the configuration file or database for different business types. The access link template is loaded when the mobile quick batch module starts. Alternatively, it can be dynamically configured through the management backend. The placeholder {itemId} can be replaced with the actual target processing item ID using string replacement or a template engine, thereby generating the original access link corresponding to the target processing item. The encapsulation link capability of the mobile number retrieval module is called to convert the original access link into a short link. Specifically, the encapsulation link capability includes at least URL shortening capability, that is, compressing long links into short forms to enhance security; and embedding identity recognition capabilities, such as binding a mobile phone number and generating temporary credentials (token).

[0050] In one embodiment, by obtaining an access link template, generating an original access link corresponding to the target processing item based on the access link template and the identifier of the target processing item, and converting the original access link into the target access link, the problems of the original access link being too long, easily being truncated by SMS, exposing parameters, and posing security risks can be avoided.

[0051] In one embodiment, in response to a click operation by a target user, a task processing page adapted to the target terminal is generated, including: In response to a click by a target user, the system obtains the target user's identifier and generates an access token via the mobile phone number retrieval module. The identity status of the target user is determined based on the target user identifier and access token; In response to the target user's valid identity status, a task processing page adapted to the target terminal is generated.

[0052] In one embodiment, a user clicks a target access link (i.e., a short link) in a text message on their mobile device, triggering the browser to load a page. After the page loads, the mobile phone number retrieval module is automatically invoked to obtain the target user identifier. The target user identifier is a core credential for identifying the user's identity; in this application, the target user identifier is the mobile phone number of the current device.

[0053] In one embodiment, the access token is used to identify the legitimacy of the target user in this login session, preventing replay attacks.

[0054] In one embodiment, the identity status of the target user refers to the verification result of the user's identity by the event processing system, including a valid identity status (identity matches and is operable) or an invalid identity status (not the target user or has expired).

[0055] In one embodiment, when a user clicks the target access link in a text message on a mobile device, the browser loads the page. After the page loads, the mobile phone number retrieval module is automatically invoked to obtain the target user's identifier, verify the access token returned by the mobile phone number retrieval module, and verify it with the operator's server. If the verification is successful, the target user's identity status is determined to be legitimate. Specifically, verifying the access token may include verifying whether the access token is within its validity period and whether the access token has been used or canceled.

[0056] In one embodiment, in response to a target user's click operation, the target user's identifier is obtained through the mobile phone number retrieval module and an access token is generated; based on the target user's identifier and access token, the target user's identity status is determined; in response to the target user's valid identity status, a task processing page adapted to the target terminal is generated. The user does not need to enter an account password, and the identity is automatically recognized after clicking the link, which can improve the efficiency of task processing, especially suitable for mobile office scenarios such as field work and management.

[0057] In one embodiment, in response to the target user's valid identity status, a task processing page adapted to the target terminal is generated, including: In response to the valid identity status of the target user, obtain the status of the target processing item; In response to the target status of the task being processed, generate a task processing page adapted to the target terminal.

[0058] In one embodiment, the legitimate identity status of the target user means that the system has verified the user's identity through mobile phone number retrieval and access token verification, confirming that the current user is the target user in the target processing matter and has access rights.

[0059] In one embodiment, if the target user's identity is valid, the system further determines whether the target processing item is in a pending state. If the target processing item is in a completed state, the target user is notified that they do not need to continue. If the target processing item is in a pending state (i.e., the target state), the mobile quick batch processing process can be performed.

[0060] In one embodiment, the target terminal can be a mobile terminal, such as a smartphone, tablet computer, wearable device, etc., or a fixed terminal, such as a desktop computer, laptop computer, etc., or an in-vehicle terminal, such as an in-vehicle infotainment system, vehicle networking terminal, etc.

[0061] In one embodiment, when the target user's identity is valid and the target matter is pending, the matter processing system generates a matter processing page adapted to the target terminal. The content of the matter processing page is determined by the content of the approval page of the pending matter information pushed by the external application system. The generated matter processing page adapted to the target terminal may include a matter processing page adapted to mobile terminals and a matter processing page adapted to fixed terminals.

[0062] In one embodiment, the status of the target processing item is obtained in response to the legitimate identity status of the target user; in response to the target status of the processing item being the target status, a processing page adapted to the target terminal is generated. Even if the user clicks the link multiple times, as long as the item has been processed, the system will no longer allow further approval, thus avoiding data conflicts.

[0063] In one embodiment, after generating a task processing page adapted to the target terminal in response to a click operation by the target user, the task processing method includes: In response to receiving the target user's processing operation for the target matter, obtain the status of the target matter; In response to the target status being the target status, submit the processing result of the target status.

[0064] In one embodiment, the target user simultaneously opens a task processing page adapted for mobile terminals and a task processing page adapted for fixed terminals, such as a mobile phone and a computer. On the task processing page of the mobile phone, the target user clicks the "agree" or "reject" button, and the status of the target task changes from "pending" to "completed". However, the status of the target task on the computer remains "pending". Therefore, before submitting the processing result of the target task on the computer, it is necessary to obtain the status of the target task again to further determine the status of the target task. If it is "completed", it will not be submitted on the computer; if it is "pending", it will be submitted.

[0065] In one embodiment, such as Figure 2 As shown, Figure 2This is a schematic diagram of a task processing method provided in an embodiment of this application. It includes an external application system, a user, a mobile quick approval module (mobile quick approval front-end and mobile quick approval back-end), a mobile number retrieval module, and an SMS delivery gateway. Specifically, after triggering the approval flow internally, the external application system calls the push interface, providing at least the following key fields: to-do item ID, to-do item title, submitter, approval page content (JSON), approval attachments (optional), and approver's mobile phone number. If multiple approvers are pushed, the application system is responsible for splitting them into individual items before pushing. 2. The mobile quick approval back-end generates a unique mobile quick approval item ID based on "application ID + to-do item ID + approver's mobile phone number," with the processing status set to "pending." 3-5. The original mobile quick approval URL is assembled, with the red part representing the mobile quick approval item ID. Then, the "encapsulated link" capability of the mobile number retrieval module is called to convert the entire URL into a short link. 6-8. The SMS content is concatenated and sent to the user corresponding to the mobile phone number via SMS service. 9-12. The user receives the SMS on their mobile phone and clicks the "short link." The mobile number retrieval module is responsible for obtaining the user's mobile phone number, generating a token for it, adding it to the mobile quick approval URL, and sending it to the mobile quick approval backend. 13-14. The mobile quick approval backend uses the token to call the "authentication login" capability of the mobile number retrieval module to obtain the user's mobile phone number. 15. The verification logic needs to make the following judgments: Logic ①: Verify whether the processing status of the to-do item corresponding to the to-do item ID is "completed". If it is "completed", inform the user that no further action is needed. Logic ②: If the processing status of the to-do item is "pending", query the corresponding mobile phone number through the mobile quick approval ID and compare it with the obtained mobile phone number. If they are different, it is considered unauthorized access. 16-19. Assemble the "approval page content" pushed by the application system into an H5 page adapted for mobile terminals, push it to the user through the mobile quick approval frontend, and the user can see the approval content and attachments (if any) on this page, and submit the approval result and approval comments on this page. 20-21. Update the operation record of the mobile quick approval and display the approval result page to the user through the mobile quick approval frontend. 22-23. The approval results of the mobile quick approval are synchronized to the relevant application system in an asynchronous manner. At the same time, the application system should also update the processing status of the pending item according to its internal processing logic and return the processing status as part of the response message to the mobile quick approval module.

[0066] In one embodiment, after receiving a submission instruction corresponding to a processing operation, generating a processing result based on the content of the processing operation, and synchronizing the processing result to an external application system, the event processing method includes: Based on the processing results of the target processing items, generate target processing records corresponding to the processing results; Synchronize the target processing records to external application systems.

[0067] In one embodiment, the target processing record includes at least the external application system identifier, the target processing item identifier, the processor's mobile phone number, the processing result, the processing opinion, and the processing time.

[0068] In one embodiment, the target processing record can be synchronized to the corresponding external application system asynchronously.

[0069] In one embodiment, a target processing record corresponding to the processing result is generated based on the processing result of the target processing item; the target processing record is synchronized to the external application system, which can realize the structured encapsulation of the processing result and the reliable cross-system transmission, ensuring that the external application system can accurately and timely update the status of the pending items.

[0070] In one embodiment, such as Figure 3 As shown, Figure 3 This illustration shows the correspondence between to-do items in an external application system and unified mobile quick approval items, as provided in this application embodiment. One to-do item in the external application system can correspond to multiple approvers' mobile phones for joint participation, and a single request can generate multiple to-do items in the external application system. After a to-do item is successfully created, its processing status defaults to "Pending". For mobile quick approval items, after each approver completes the quick approval and submits it successfully on their mobile phone, the system needs to generate a mobile quick approval record for them and synchronize this record to the external application system. Only after receiving the synchronization message can the external application system refresh its internal approval records and perform logical processing of to-do items (such as updating the processing status of to-do items). For items in the query results with a processing status of "completed", the processing status of the local mobile quick approval item needs to be updated promptly.

[0071] In one embodiment, such as Figure 4 As shown, Figure 4 This is a flowchart illustrating the mobile quick approval processing method provided in this application embodiment. To control the legitimate identity of visitors and access permissions for pending tasks, the method mainly includes the following three key node judgments: First, visitor number matching judgment. Before displaying the quick approval operation page (item processing page), considering that the target user may forward the target message to other personnel, it is necessary to verify whether the visitor's (the person who clicked the target link) mobile phone number matches the mobile phone number specified in the current pending task. Second, pending task status judgment. Based on the current approver's mobile phone number, judgments are made at the following nodes, where it is necessary to determine whether the pending task status is "pending" to prevent duplicate approvals. Scenario 1: Before displaying the quick approval operation page; Scenario 2: When submitting the current approval result. Finally, approval submission result judgment. If the submission cannot be completed smoothly due to network problems, backend interface problems, etc., the system needs to judge and provide an error prompt and guidance.

[0072] In one embodiment, the mobile quick approval module is a core functional module, whose main purpose is to provide external application systems with a quick approval service based on a mobile H5 adaptive page. Through this module, users can quickly complete the approval process for pending tasks using various mobile devices without requiring a specific security VPN or authentication, greatly improving work efficiency and convenience. Taking an internet billing platform as an example, this module can be seamlessly integrated with a mobile office client. After user authentication through the application client, they can directly access their relevant quick approval list within the mobile office app and complete the corresponding approval operations.

[0073] In one embodiment, specific application systems are granted access to the mobile office platform so that they can use various services, including mobile quick approval. Currently, the scope of allowed application systems is limited to authorized system objects. The system uniformly issues a unique appId and appSecret for each object. Visitors provide agreed-upon information fields, assemble them in sequence, perform symmetric encryption, and the mobile quick approval server decrypts them to verify the visitor's legitimacy. Specifically, this is executed in the following parts: I. Registration and Authorization: External application systems need to submit an access request to the mobile quick-application authorization module to obtain a unique appId and corresponding appSecret. The appId is used to identify different application systems, while the appSecret serves as a key to ensure communication security.

[0074] II. Request Preparation: When an authorized application system wishes to call the mobile office platform's services (e.g., triggering a mobile quick approval workflow), it needs to prepare necessary business parameters, including but not limited to the to-do item ID, title, and submitter information. Additionally, a timestamp or random number needs to be generated as a measure to prevent replay attacks and added to the data packet to be sent.

[0075] 3. Signature Generation: Sort all parameters to be sent lexicographically. Concatenate these parameters and their values ​​into a string using a specific format, typically key1=value1&key2=value2. Append the appSecret to this string to form the final string to be encrypted. Encrypt this string using a pre-agreed algorithm (such as HMAC-SHA256) and the key (appSecret) to obtain the signature value.

[0076] 4. Sending the Request: When constructing an HTTPS request, include all previously prepared parameters (excluding appSecret) and the calculated signature in the header or body. Also, ensure that the correct Content-Type and other necessary header information are set.

[0077] V. Server-side Verification: After receiving a request, the mobile office platform first extracts the appId from the request to confirm whether it belongs to the authorized list; then, it reassembles and calculates the signature of the request parameter string according to the same rules; finally, it compares the signature provided by the client with the result recalculated by the server. If the match is successful, the request is considered to come from a legitimate user; otherwise, the service is rejected and an error message is returned.

[0078] VI. Complete subsequent processing: Once verification is successful, you can continue to execute specific business logic, such as creating new mobile quick batch tasks, updating status, etc.

[0079] To implement the event processing method provided in this disclosure, this disclosure also provides an event processing device, such as... Figure 5 As shown. Figure 5 This is a schematic diagram of the structure of the event processing device provided in an embodiment of the present disclosure. The event processing device 500 includes: The first generation unit 501 is used to generate target processing items corresponding to the to-do items information in response to the to-do items information of the external application system. The second generation unit 502 is used to generate a target access link corresponding to the target processing item and send a target message containing the target access link to the target user. The processing unit 503 is used to respond to the click operation of the target user and generate a task processing page adapted to the target terminal. The task processing page is used to receive the processing operation of the target user for the target task. The synchronization unit 504 is used to receive the submission instruction corresponding to the processing operation, generate the processing result based on the content of the processing operation, and synchronize the processing result to the external application system so that the external application system can update the status of the pending items information after receiving the processing result.

[0080] In one embodiment, the first generation unit 501 is specifically used for: In response to to-do list information from external application systems, obtain at least one target user from the to-do list information; Generate the target processing items corresponding to each target user in the to-do list information.

[0081] In one embodiment, the second generation unit 502 is specifically used for: Get the access link template; Based on the access link template and the identifier of the target processing item, generate the original access link corresponding to the target processing item; Transform the original access link into the target access link.

[0082] In one embodiment, the processing unit 503 is specifically used for: In response to a click by a target user, the system obtains the target user's identifier and generates an access token via the mobile phone number retrieval module. The identity status of the target user is determined based on the target user identifier and access token; In response to the target user's valid identity status, a task processing page adapted to the target terminal is generated.

[0083] In one embodiment, the processing unit 503 is specifically used for: In response to the valid identity status of the target user, obtain the status of the target processing item; In response to the target status of the task being processed, generate a task processing page adapted to the target terminal.

[0084] In one embodiment, the event processing apparatus 500 further includes a submission unit, which is used for: In response to receiving the target user's processing operation for the target matter, obtain the status of the target matter; In response to the target status being the target status, submit the processing result of the target status.

[0085] In one embodiment, the synchronization unit 504 is specifically used for: Based on the processing results of the target processing items, generate target processing records corresponding to the processing results; Synchronize the target processing records to external application systems.

[0086] It should be noted that the above-described task processing device, when running in a model, is only illustrated by the division of the above-described program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the task processing device can be divided into different program modules to complete all or part of the processing described above. Furthermore, the task processing device provided in the above-described embodiments and the task processing method embodiments provided in this disclosure belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0087] Figure 6 This is a schematic diagram of the hardware composition structure of the electronic device provided in the embodiments of this disclosure, such as... Figure 6As shown, the electronic device 600 includes at least one processor 602; and a memory 601 communicatively connected to the at least one processor 602; wherein the memory 601 stores instructions executable by the at least one processor 602, the instructions being executed by the at least one processor 602 to implement the steps of the event processing method of the present disclosure embodiments.

[0088] Optionally, the electronic device may specifically be a task processing device in the embodiments of this application, and the electronic device may implement the corresponding processes implemented by the task processing device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0089] It is understood that the electronic device also includes a communication interface 603. Various components in the electronic device are coupled together via a bus system 604. It is understood that the bus system 604 is used to implement communication between these components. In addition to a data bus, the bus system 604 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 6 The general designated all buses as Bus System 604.

[0090] It is understood that memory 601 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 601 described in this embodiment of the invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0091] The methods disclosed in the above embodiments can be applied to or implemented by processor 602. Processor 602 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the hardware of processor 602 or by instructions in software form. Processor 602 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 602 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically memory 601. Processor 602 reads information from memory 601 and, in conjunction with its hardware, completes the steps of the aforementioned methods.

[0092] In an exemplary embodiment, the electronic device may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0093] This public security embodiment also provides a non-transitory computer-readable storage medium storing computer instructions, which are used to cause a computer to execute the steps of the event processing method of this embodiment.

[0094] Optionally, the computer-readable storage medium can be applied to the event processing apparatus in the embodiments of this application, and the computer instructions cause the computer to execute the corresponding processes implemented by the event processing apparatus in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0095] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the event handling method provided in this embodiment of the invention.

[0096] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and 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 coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

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

[0098] In addition, in the various embodiments of the present invention, each functional unit can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0099] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0100] Alternatively, if the integrated units of this invention are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0101] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A transaction processing method, characterized by, The method comprises the following steps: in response to the to-do information of the external application system, a target processing matter corresponding to the to-do information is generated; a target access link corresponding to the target processing matter is generated, and a target message containing the target access link is sent to a target user; in response to a click operation of the target user, a matter processing page adapted to a target terminal is generated, and the matter processing page is used to receive a processing operation of the target user for the target processing matter; after receiving a submission instruction corresponding to the processing operation, a processing result is generated based on the content of the processing operation, and the processing result is synchronized to the external application system, so that the external application system updates the state of the to-do information after receiving the processing result.

2. The method of claim 1, wherein, The generation of the target access link corresponding to the target processing matter comprises the following steps: an access link template is obtained; based on the access link template and the identifier of the target processing matter, an original access link corresponding to the target processing matter is generated; the original access link is converted into a target access link.

3. The method of claim 1, wherein, The generation of the matter processing page adapted to the target terminal in response to the click operation of the target user comprises the following steps: in response to the click operation of the target user, a target user identifier is obtained through a mobile phone number taking module, and an access token is generated; based on the target user identifier and the access token, the identity state of the target user is determined; in response to the legal identity state of the target user, a matter processing page adapted to the target terminal is generated.

4. The method of claim 3, wherein, The generation of the matter processing page adapted to the target terminal in response to the legal identity state of the target user comprises the following steps: in response to the legal identity state of the target user, the state of the target processing matter is obtained; in response to the target state of the target processing matter, a matter processing page adapted to the target terminal is generated.

5. The method of claim 1, wherein, After the generation of the matter processing page adapted to the target terminal in response to the click operation of the target user, the method comprises the following steps: in response to the processing operation of the target user for the target processing matter, the state of the target processing matter is obtained; in response to the target state of the target processing matter, the processing result of the target processing matter is submitted.

6. The method of claim 5, wherein, After the receiving of the submission instruction corresponding to the processing operation, the generation of the processing result based on the content of the processing operation, and the synchronization of the processing result to the external application system, the method comprises the following steps: based on the processing result of the target processing matter, a target processing record corresponding to the processing result is generated; the target processing record is synchronized to the external application system.

7. A transaction processing apparatus characterized by comprising: The method comprises the following steps: a first generation unit is configured to generate a target processing matter corresponding to to-do information of an external application system in response to the to-do information; a second generation unit is configured to generate a target access link corresponding to the target processing matter, and send a target message containing the target access link to a target user; a processing unit is configured to generate a matter processing page adapted to a target terminal in response to a click operation of the target user, and the matter processing page is used to receive a processing operation of the target user for the target processing matter. A synchronization unit is configured to receive a submission instruction corresponding to the processing operation, generate a processing result based on the content of the processing operation, and synchronize the processing result to the external application system, so that the external application system updates the state of the to-do item information after receiving the processing result.

8. An electronic device, comprising: Comprise: at least one processor; and a memory connected to the at least one processor in communication; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium having stored thereon computer instructions, wherein, The computer instructions are used to make the computer execute the method of any one of claims 1 to 6.

10. A computer program product comprising a computer program which, when executed by a processor, implements the method of any one of claims 1 to 6.

Images