Information processing method, apparatus and electronic device

Abstract

The present disclosure provides an information processing method, device and electronic equipment, relates to computer technology, and particularly relates to information display, cross-application system information processing and the like. The specific implementation scheme is as follows: receiving display information indicating that a task atomic component is displayed in a first application system client; the task atomic component is obtained by a server according to received task information sent by a second application system and an atomic component template defined according to a preset rendering protocol; rendering the task atomic component based on a preset rendering interpreter; and displaying the task atomic component obtained by rendering in the first application system client. The reach rate of the task information is improved. If the information processing method is applied between enterprise internal application systems, the office efficiency of the enterprise can be improved.

Description

Technical Field

[0001] This disclosure relates to the technical fields of information display and cross-application system information processing in the field of computer technology, and in particular to an information processing method, apparatus and electronic device. Background Technology

[0002] With the development of computer technology, different users can interact with each other through networks. For enterprises, internal members can also collaborate through networks, such as for information exchange and project approval.

[0003] Enterprises typically have multiple application systems, such as ERP systems, instant messaging systems, project management systems, and weekly reporting systems. Enterprise members can collaborate using these systems. However, these systems may use different development technologies and have different vendors, making it impossible to send information from one system to another.

[0004] To improve the efficiency of collaborative work, information exchange between different application systems within an enterprise is necessary. Summary of the Invention

[0005] This disclosure provides an information processing method, apparatus, and electronic device.

[0006] According to a first aspect of this disclosure, an information processing method is provided, the method comprising: receiving display information instructing a first application system client to display a task atomic component; the task atomic component being obtained by a server based on task information received from a second application system and an atomic component template defined by a preset rendering protocol; rendering the task atomic component based on a preset rendering interpreter; and displaying the rendered task atomic component in the first application system client.

[0007] According to a second aspect of this disclosure, an information processing method is provided, the method comprising: in response to receiving task information sent by a second application system, determining an atomic component template matching the task indicated by the task information according to a preset rendering protocol; integrating the task data indicated by the task information with the atomic component template to obtain a task atomic component; generating display information including the task atomic component; and sending the display information to a first application system client, so that the first application system client renders and displays the task atomic component according to a preset interpreter engine, wherein the first application system client includes clients of other application systems besides the second application system.

[0008] According to a third aspect of this disclosure, an information processing method is provided, the method comprising: generating task information according to a task information generation instruction, the task information being used to instruct a receiving end to generate a task atomic component according to an atomic component template defined by a preset rendering protocol and task data; and sending the task information.

[0009] According to a fourth aspect of this disclosure, an information processing apparatus is provided, comprising: a first receiving unit for receiving display information instructing a first application system client to display a task atomic component; the task atomic component is obtained by a server based on task information received from a second application system and an atomic component template defined by a preset rendering protocol; a rendering unit for rendering the task atomic component based on a preset rendering interpreter; and a display unit for displaying the rendered task atomic component in the first application system client.

[0010] According to a fifth aspect of this disclosure, an information processing apparatus is provided, comprising: a determining unit, configured to, in response to receiving task information sent by a second application system, determine an atomic component template matching a task indicated by the task information according to a preset rendering protocol; an integrating unit, configured to integrate task data indicated by the task information with the atomic component template to obtain a task atomic component; and a second sending unit, configured to generate display information including the task atomic component and send the display information to a first application system client, so that the first application system client renders and displays the task atomic component according to a preset interpreter engine, wherein the first application system client includes clients of other application systems besides the second application system.

[0011] According to a sixth aspect of this disclosure, an information processing apparatus is provided, the apparatus comprising: a task information generation unit, configured to generate task information according to a task information generation instruction, the task information being used to instruct a receiving end to generate task atomic components according to an atomic component template defined by a preset rendering protocol and task data; and a fourth sending unit, configured to send the task information.

[0012] According to a seventh aspect of this disclosure, an electronic device is provided, 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, the instructions being executed by the at least one processor to enable the at least one processor to perform the methods provided in the first aspect, the second aspect, or the third aspect.

[0013] According to an eighth aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause the computer to perform the methods provided in the first, second, or third aspect.

[0014] According to a ninth aspect of this disclosure, a computer program product is provided, the computer program product comprising: a computer program stored in a readable storage medium, at least one processor of an electronic device being able to read the computer program from the readable storage medium, the at least one processor executing the computer program causing the electronic device to perform the methods of the first aspect, the second aspect, or the third aspect.

[0015] According to the scheme disclosed herein, the system receives an instruction to display task atomic components on a first application system client. The task atomic components are obtained by the server based on task information received from a second application system and an atomic component template defined by a preset rendering protocol. The task atomic components are then rendered using a preset rendering interpreter. The rendered task atomic components are then displayed on the first application system client. Because a rendering protocol and a rendering interpreter matching the protocol are pre-set, the task atomic components generated according to the rendering protocol are sent to application system clients different from the application system that initiated the task. The application system client receiving the task atomic components can render and display the task components according to the preset rendering interpreter, thus realizing the cross-application system flow of task information and presenting task information in different application system clients in the form of task atomic components. This improves the reach rate of task information. If the above information processing method is applied between application systems within an enterprise, it can improve the enterprise's office efficiency.

[0016] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0018] Figure 1 This is a scene diagram that can implement the embodiments of this disclosure;

[0019] Figure 2 This is a schematic diagram based on the first embodiment of the present disclosure;

[0020] Figure 3 This is a schematic diagram according to the second embodiment of the present disclosure;

[0021] Figure 4 This is a schematic diagram according to the third embodiment of the present disclosure;

[0022] Figure 5 This is a schematic diagram according to the fourth embodiment of the present disclosure;

[0023] Figure 6This is a schematic diagram according to the fifth embodiment of the present disclosure;

[0024] Figure 7 This is a schematic diagram according to the sixth embodiment of the present disclosure;

[0025] Figure 8 This is a schematic diagram according to the seventh embodiment of the present disclosure;

[0026] Figure 9 This is a schematic diagram according to the eighth embodiment of the present disclosure;

[0027] Figure 10 A schematic block diagram of an example electronic device that can be used to implement embodiments of the present disclosure is shown. Detailed Implementation

[0028] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0029] For internal office needs, enterprises typically have multiple application systems, such as ERP systems, instant messaging systems, project management systems, and weekly reporting systems. Enterprise users can collaborate through these systems. However, currently, these systems cannot exchange information, resulting in low information reach among users and consequently low office efficiency. For example, approval tasks in the ERP system can only be completed within the ERP application's client application.

[0030] To improve task processing efficiency, related technologies generate task notifications from task requests generated in one application system and send these notifications to terminal devices running another application system to remind users to process the task requests. For example, in an ERP application system, approval tasks can be notified via email or instant messaging, and the approving user needs to access the ERP application system page through the link in the notification to complete the approval task. Similarly, project management tasks cannot be viewed or processed in weekly report systems, which require manual screenshots or text descriptions to summarize the progress of each project task. However, these technologies still require users to open the link provided in the task notification to access the application system that generated the task request and process it. Users cannot quickly process these task requests, resulting in continued low office efficiency.

[0031] It is evident that the internal information processing methods provided by the relevant technologies suffer from low efficiency.

[0032] This disclosure provides an information processing method, apparatus, and electronic device, which are applied in fields such as information display and cross-application information processing in computer technology, in order to improve information processing efficiency.

[0033] Figure 1 The scene diagrams that can be implemented in the embodiments of this disclosure are as follows: Figure 1 As shown, the initiating user can send a request from a second application system client running on the first terminal devices 101 and 102 to the application system server 103. The application system server 103 can then forward the request to the component server 104. The component server 104 can analyze and process the request, and send the intermediate processing results (e.g., task atomic components) to the first application system client running on the second terminal device 105. The task processing user can then view the intermediate processing results through the first application system client on the second terminal device 105. In some application scenarios, the task processing user can perform corresponding processing operations on the intermediate processing results.

[0034] Please refer to Figure 2 , Figure 2 This is a schematic diagram of the first embodiment of the present disclosure, as shown below. Figure 2 As shown, the information processing method provided in this embodiment includes:

[0035] S201. Receive instructions to display the task atomic component on the first application system client; the task atomic component is obtained by the server based on the task information received from the second application system and the atomic component template defined by the preset rendering protocol.

[0036] In this embodiment, the executing entity can be a terminal device. A first application system client can run on the terminal device.

[0037] When receiving the above-mentioned display information, the client of the first application system can run in the foreground or in the background.

[0038] In practice, the first application system client receives and sends information through the terminal device during runtime, and displays the information through the display capabilities of the terminal device.

[0039] The aforementioned terminal devices can be various user terminal devices, such as laptops, desktop computers, mobile terminals, and wearable devices.

[0040] The displayed information mentioned above can be information sent by the server. This server can be a component server that provides services for the rendering of task atomic components. In some application scenarios, this component server can reside on the same physical server as the server that provides services to various enterprise application systems.

[0041] The displayed information may include data from task atomic components. These task atomic components are generated by the server based on the task information sent by the second application system and atomic component templates that match the task information in the preset rendering protocol.

[0042] The aforementioned preset rendering protocol can be pre-developed. This preset rendering protocol can be stored on the aforementioned server or on other electronic devices that communicate with the aforementioned server. The aforementioned server can extract atomic component templates that match the task information from multiple atomic component templates defined by the preset rendering protocol; for example, it can extract atomic component templates that match the task information type from multiple atomic component templates.

[0043] S202, Atomic components for rendering tasks based on preset rendering interpreters.

[0044] The preset rendering interpreter here can be a rendering interpreter developed according to a preset rendering protocol. The aforementioned preset rendering interpreter is used to interpret and execute the task atomic component templates generated according to the preset rendering protocol.

[0045] The aforementioned preset rendering interpreter can be stored in the terminal device or bound to the first application system client as a file of the first application system client.

[0046] After receiving the above display information, the preset rendering interpreter can be invoked to interpret the bytecode of the task atomic component and perform rendering.

[0047] S203. Display the rendered task atomic components in the first application system client.

[0048] If the first application system client is running in the foreground, the rendered task atomic components can be displayed directly in the first application system client.

[0049] If the first application system client is running in the background, the terminal device can pre-render and cache the rendered task atomic components. When the first application system client switches from the background to the foreground, the aforementioned task atomic components are displayed in the first application system client interface.

[0050] The first application system here can be a different application system from the second application system, or it can be the same application system.

[0051] When the above information processing method is applied to multiple application systems within an enterprise, the first application system can be any one of the multiple application systems within the enterprise. Similarly, the second application system can be any one of the multiple application systems within the enterprise.

[0052] Enterprise application systems may include, for example, ERP systems, instant messaging systems, project management systems, and weekly reporting systems.

[0053] The rendered task atomic components can be displayed in various styles. As an illustrative example, the rendered task atomic components are displayed in card format.

[0054] In this embodiment, the system receives instructions to display task atomic components on the first application system client. The task atomic components are generated by the server according to the following steps: receiving task information sent by the second application system; determining an atomic component template matching the task information according to a preset rendering protocol; integrating the atomic component template and the task data indicated by the task instruction to obtain the task atomic components; rendering the task atomic components based on a preset rendering interpreter; and displaying the rendered task atomic components in the first application system client. Because a rendering protocol and a rendering interpreter matching the rendering protocol are preset, the task atomic components generated according to the rendering protocol are sent to application system clients different from the application system that initiated the task. The application system client receiving the task atomic components can render and display the task atomic components according to the preset rendering interpreter, realizing the cross-application system flow of task information, allowing task information to be presented in different application system clients with the same or similar display styles. This improves the reach rate of task information. If the above information processing method is applied between application systems within an enterprise, it can improve the enterprise's office efficiency.

[0055] Figure 3 This is a schematic diagram according to the second embodiment of this disclosure. (See diagram below.) Figure 3 As shown, the information processing method provided in this embodiment includes:

[0056] S301. Receive instructions to display the task atomic component on the first application system client; the task atomic component is obtained by the server based on the task information received from the second application system and the atomic component template defined by the preset rendering protocol.

[0057] S302, Atomic components for rendering tasks based on preset rendering interpreters;

[0058] S303. Display the rendered task atomic components in the first application system client.

[0059] The specific implementation of steps S301 to S303 can be related to Figure 2 The specific implementations of steps S201 to S203 in the illustrated embodiment are the same or similar, and will not be described in detail here.

[0060] S304. Receive the task operation performed by the target user in the displayed task atomic component. The task operation is used to complete the task indicated by the task information.

[0061] The aforementioned first application system client can be the target user's first application system client. The target user here can be any user, such as a user within the enterprise with the authority to approve approval tasks. The target user can log in to the aforementioned first application system client.

[0062] The target user can execute corresponding task operations using the task atomic components displayed in the first application system client. These task operations can be various actions used to complete tasks indicated by task information.

[0063] The above-mentioned task operations include, but are not limited to: selection operations performed on selectable controls in the task atomic component, and input operations for voice or text information in the information input window provided in the task atomic component.

[0064] As an illustrative example, the aforementioned task information may be approval task information sent by an ERP application system (second application system) for approving the purchase of a raw material. The aforementioned first application system client may be a client used by any target user authorized to approve the purchase. The aforementioned first application system may be any system different from the ERP application system, such as an instant messaging application system. The target user may perform task operations on the task atomic components displayed on the first application system client. For example, by performing a selection operation on an approval pass control (selectable control) indicating approval in the task atomic component, the first application system client can generate task operation information based on the selection operation. This task operation information is used to indicate to the target user that they have performed a selection operation on the approval pass control.

[0065] As another illustrative example, the aforementioned task information may be project progress report task information sent by the project management application system (second application system) to report project progress information.

[0066] The server can generate task atomic components to display project progress based on atomic component templates that match the task information in the project progress report and the task data indicated in the project progress report task information. The task atomic component requires the target user to read the project progress and provide feedback after reading it.

[0067] The aforementioned first application system client can be any application system client of the target user, such as a weekly report application system client. The target user can be any member participating in the project or a manager within the company. The target user can browse the aforementioned task atomic components used to display project progress within the first application system client running on their terminal device.

[0068] In some application scenarios, receiving the task operations performed by the target user in the displayed task atomic component includes: receiving the task operations performed by the user in the task interaction control in the task atomic component.

[0069] The aforementioned task atomic components may include task interaction controls, such as interactive controls for providing feedback on whether something has been read. The target user can perform task operations on these interactive controls. For illustration, the task operation may be a selection operation such as clicking or touching a selectable interactive control, or an input operation of text or voice information in an input window-type interactive control, such as inputting text or symbols to express "read."

[0070] By incorporating interactive controls within the task atomic component, users can more easily process the tasks indicated by the component, thus improving the efficiency of task handling.

[0071] S305. Generate task operation information and send the task operation information to the server so that the server can send the task operation information to the second application system, and the second application system can determine the task operation result based on the task operation information.

[0072] The aforementioned executing entity can generate task operation information based on the aforementioned task operations. This task operation information includes the content of the task operation and the target user's information. The content of the task operation may include which option-type interactive control was selected, or the text or symbols corresponding to text or voice information entered in an input window-type interactive control.

[0073] The aforementioned executing entity can send task operation information to the server through various communication methods, and the server will then send it to the second application system.

[0074] After receiving the aforementioned task operation information, the second application system can determine the task operation result based on that information. The task operation result can include "approved," "not approved," "read," or "unread." The result can be determined based on the specific task operation information.

[0075] In some application scenarios, the information for the aforementioned task operation may include target user information and information about the target control whose operation was triggered by the target user. The second application system can determine the operation result based on the preset title of the selectable target empty control. The preset titles of selectable controls may include, for example, "Pass," "Return," or "Reject." After determining the operation result, the second application system can update the data corresponding to the task information within the second application system. For example, updating the status data of the task information in the second application system. This status data includes whether the task has been processed.

[0076] and Figure 2 Compared to the illustrated embodiment, this embodiment emphasizes the steps of the target user performing corresponding task operations on a task initiated by the second application system within the task atomic component of the first application system client. This allows the target user to directly execute task operations within the first application system displaying the task atomic component, eliminating the need to open the second application system client. This achieves cross-application system task processing, improving information processing efficiency. When applied to application systems within an enterprise, this method can enhance office efficiency.

[0077] exist Figure 2 and Figure 3 In some embodiments of the information processing method shown, the preset rendering interpreter includes one of the following:

[0078] A preset rendering interpreter is embedded in the page script of the web client of the first application system;

[0079] The preset rendering interpreter is bound to the application client of the first application system.

[0080] In some application scenarios, the aforementioned first application system client can be a web client, meaning the first application system client does not need to be installed on a terminal device and can be opened using a web page. In these application scenarios, the aforementioned preset rendering interpreter can be a preset rendering interpreter embedded in the page script of the first application system client.

[0081] As one implementation, the preset rendering interpreter embedded in the page script can include rendering interpreters that match different terminal device types and operating systems. In this way, when the first application system client is opened on any terminal device, it can obtain the device type and operating system of the terminal device. If it receives display information for the display task atomic component, the first application system client can select a rendering interpreter from the preset rendering interpreters that matches the obtained device type and operating system of the terminal device to render the task atomic component.

[0082] In other application scenarios, the aforementioned first application system client is installed and runs as a standalone application on the terminal device. In these scenarios, a pre-defined rendering interpreter file can be configured within the first application system client. After receiving the aforementioned display information, the first application system client can invoke the pre-defined rendering interpreter file to render the task's atomic components.

[0083] The default rendering interpreter file can be developed and saved on the terminal device side, or it can be developed on the server side and then sent to the terminal device by the server.

[0084] In these application scenarios, the aforementioned preset rendering interpreter can be a rendering interpreter that matches the device type and operating system of the terminal device.

[0085] In these embodiments, regardless of whether the first application system client is opened as a web client or an application client, the received task atomic components can be displayed. This can further improve the reach rate of task information.

[0086] In some embodiments, step S302 includes:

[0087] First, the local rendering function module is called according to the preset rendering interpreter;

[0088] Secondly, the local rendering module is used to render the atomic components of the task.

[0089] The aforementioned local rendering function module may include the rendering function module of the terminal device itself running the first user system client, such as a graphics processor, image processor calling interface, etc.

[0090] In these embodiments, by having the terminal device's own rendering function module called by the preset rendering interpreter to render the task atomic components, compared to the server sending the rendered task atomic components to the first application system client for display, the amount of data transmitted can be reduced, the efficiency of information transmission can be improved, and the speed of displaying the task atomic components can be increased.

[0091] Figure 4 This is a schematic diagram according to the third embodiment of this disclosure. (See diagram below.) Figure 4 As shown, the information processing method provided in this embodiment includes:

[0092] S401. In response to receiving task information sent by the second application system, determine the atomic component template that matches the task indicated by the task information according to the preset rendering protocol.

[0093] The execution entity in this embodiment can be a component server. This server can be a server cluster or a single server.

[0094] In some application scenarios, the executing entity can provide services to multiple application systems within an enterprise.

[0095] The second application system can be any one of multiple application systems within an enterprise. The aforementioned task information can be any task information issued by the second application system. The task indicated by the task information includes instructing the target user to browse information, perform corresponding operations, etc.

[0096] As an illustration, the second application system can be an ERP application system, and the task information initiated by the ERP application system can instruct the sending of approval task information to the target user.

[0097] As another illustrative example, the second application system could be a weekly report application system. The task information sent by the weekly report application system could be task information instructing the target user to read the prepared weekly report content; or it could be task information instructing the target user to fill in the weekly report content.

[0098] The preset rendering protocol here can be pre-developed. The preset rendering protocol can be stored in the execution entity or in other electronic devices that communicate with the execution entity.

[0099] The aforementioned preset rendering protocol may include multiple predefined atomic component templates.

[0100] In some application scenarios, the aforementioned preset rendering protocol can predefine atomic component templates for each application system. The atomic component templates corresponding to each application system can include atomic component templates that match different task types.

[0101] In other application scenarios, the aforementioned preset rendering protocol can predefine atomic component templates for different task types. In other words, in these scenarios, atomic component templates corresponding to the task type can be defined only based on the task type.

[0102] The definition of the above atomic component template includes, but is not limited to, specifications such as control description, template layout, event declaration, and data format.

[0103] As an illustrative example, the second application system is an ERP application system. The task information initiated by the ERP application system indicates the sending of approval task information for the approval application to the target user. The executing entity can determine the atomic component template that matches the approval task from multiple atomic component templates predefined for the ERP application system in the preset rendering protocol.

[0104] As another illustrative example, the second application system is a weekly report application system. This system sends task information instructing the target user to read the prepared weekly report content. The executing entity can determine the atomic component template that matches the information display task from multiple atomic component templates predefined by a preset rendering protocol.

[0105] S402. Integrate the task data indicated by the task information with the above atomic component template to obtain the task atomic component.

[0106] The task data indicated in the above task information includes the specific task to be executed, information about the initiator of the task, etc. This task data can be considered dynamic data. Different task information can correspond to different dynamic data. Task information of the same type can correspond to the same atomic component template.

[0107] For illustrative purposes, the task information refers to the procurement approval task information issued by the ERP application system. The task data may include: the name of the procured item, the quantity of the procured item, the unit price, the total price, the supplier of the procured item, and information from the ERP application system. In some application scenarios, the task data may also include information about the user who initiated the approval task.

[0108] Schematic illustration: The aforementioned execution entity can convert the format of the task data indicated by the task information into a data format supported by the atomic component template that matches the task information, based on the data format supported by the atomic component template. The display position corresponding to the task data is then determined according to the dynamic data filling position provided by the atomic component template.

[0109] In practice, the above-mentioned integration of task data indicating task information with the above-mentioned atomic component template includes binding the above-mentioned task data with the determined display position with the above-mentioned atomic component template and packaging them into a whole as a task atomic component.

[0110] S403. Generate display information including task atomic components and send the display information to the first application system client so that the first application system client renders and displays the task atomic components according to the preset interpreter engine. The first application system client includes clients of other application systems besides the second application system.

[0111] The aforementioned executing entity can send the task atomic components to the first application system client via wired or wireless communication connections.

[0112] In some application scenarios, the aforementioned first application system client can be a client of another application system, different from the second application system. In other application scenarios, the aforementioned first application system client can also be a client of the second application system corresponding to the target user.

[0113] The aforementioned first application system client can run on a terminal device.

[0114] In some application scenarios, the aforementioned first application system client can be a web client.

[0115] In other application scenarios, the aforementioned first application system client can be a client that runs as an application on a terminal device.

[0116] In these application scenarios, the aforementioned pre-installed interpreter can be pre-installed in the first application system client.

[0117] In some application scenarios, the display information received by the client of the first application system may include task atomic components represented in the form of multiple lines of bytecode.

[0118] The preset interpreter here can recognize the atomic component templates and data formats defined in the preset rendering protocol.

[0119] The aforementioned preset interpreter can be used to interpret and execute the atomic component templates defined in the preset rendering protocol, and fill the dynamic data into the atomic component templates that match the task information according to the display position of the dynamic data indicated in the display information.

[0120] In some application scenarios, the aforementioned pre-defined interpreter can be written in JavaScript and interpret and execute the bytecode corresponding to the atomic components of the task line by line according to the predefined specifications of the aforementioned pre-defined rendering protocol.

[0121] In this embodiment, in response to receiving task information sent by the second application system, an atomic component template matching the task indicated by the task information is determined according to a preset rendering protocol. The task data indicated by the task information is integrated with the atomic component template to obtain a task atomic component. Display information including the task atomic component is generated and sent to the first application system client, so that the first application system client renders and displays the task atomic component according to a preset interpreter engine. The first application system client includes clients of other application systems besides the second application system. Because a rendering protocol and a rendering interpreter matching the rendering protocol are preset, a task atomic component for a task initiated by one application system can be generated according to the rendering protocol. This task atomic component is then interpreted and rendered in other application system clients, allowing it to be displayed in those clients. This achieves cross-application system flow of task information, enabling task information to be presented in different application system clients. Therefore, even if the target user of the first application system client does not browse the second application system client, they can still view the task information initiated by the second application system. This improves the reach of task information and is beneficial for improving office efficiency within the enterprise.

[0122] In some embodiments, the above information processing method further includes the following steps:

[0123] First, the system receives task operation information sent by the first application system client; the task operation information is generated by the first application client based on the operation performed by the target user in the task atomic component.

[0124] Secondly, the task operation information is sent to the second application system so that the second application system can perform the following update operations: determine the task operation result based on the task operation information; and update the data of the second application system based on the task operation result.

[0125] In these embodiments, the aforementioned first application system client can be the first application system client of the target user. The target user here can be any user, such as a user within an enterprise who has the authority to approve approval tasks.

[0126] The target user can perform corresponding task operations within the task atomic components displayed in the first application system client. These task operations can be various actions used to complete tasks indicated by task information. These task operations include, but are not limited to: selection operations performed on selectable controls within the task atomic components, and input operations such as entering voice or text information into the information input windows provided within the task atomic components.

[0127] The first application system client can generate task operation information.

[0128] The aforementioned executing entity can send task operation information to the device on which the second application system runs via various communication methods. This second application system can run on the application system server.

[0129] After receiving the aforementioned task operation information, the second application system can determine the task operation result based on that information. The task operation result can include "approved," "not approved," "read," or "unread." The result can be determined based on the specific task operation information.

[0130] In some application scenarios, the information for the aforementioned task operation may include target user information and information about the target control selected by the target user. The second application system can determine the operation result based on the preset title of the target control. After determining the operation result, the second application system can update the data corresponding to the task information in the second application system. For example, updating the status data of the task information in the second application system. This status data includes whether the task has been processed.

[0131] In these embodiments, the target user can perform task operations on the task indicated by the task atomic component in the first application system client. The first application system generates task operation information based on the task operation and sends this information to the execution entity. The execution entity then sends the task operation information to the second application system. The second application system determines the operation result corresponding to the task operation information and updates the data corresponding to the task information based on the operation result. In this way, the target user can directly execute task operations in the first application system displaying the task atomic component without having to open the second application system client to perform task operations. This achieves cross-application system task processing and can improve the efficiency of collaborative work within an enterprise.

[0132] In some embodiments, step S401 includes: in response to receiving task information, determining an atomic component template that matches both the second application system and the task indicated by the task information according to a preset rendering protocol.

[0133] In these embodiments, the aforementioned preset rendering protocol can predefine multiple atomic component templates for different application systems. For each application system, atomic component templates matching different tasks within that application system can be defined.

[0134] After receiving a task message, the aforementioned execution entity can identify the second application system that sent the task message based on the sender information carried in the task message. It then determines the task category based on the task indicated in the task message. Finally, it selects the atomic component template corresponding to that task category from multiple atomic task templates under the aforementioned second application system in the preset rendering protocol.

[0135] In these embodiments, a preset rendering protocol predefines multiple atomic component templates corresponding to multiple application systems. The aforementioned execution entity can determine the atomic component template corresponding to the task information from the atomic component templates corresponding to the application system, making the determined atomic component template highly compatible with the second application system. In addition, the task atomic components obtained from the aforementioned atomic component templates facilitate the target user's quick identification of which application system the task atomic components come from.

[0136] In some embodiments, step S403 includes: sending display information to at least one first application system client of the target user, so that the at least one first application system client renders the task atomic components according to a preset rendering interpreter matched with its corresponding terminal device; the at least one first application system client runs on different terminal devices, and the different terminal devices run different operating systems.

[0137] In these embodiments, each client in the at least one first application system client described above can run on different terminal devices. These different terminal devices can be terminal devices running different operating systems. The rendering hardware in different terminal devices can be different; furthermore, the rendering programs supported by different operating systems can also be different. Therefore, for different terminal devices running different operating systems, a corresponding rendering interpreter needs to be developed in advance for each combination of terminal device and operating system. The rendering interpreter can be stored in the terminal device, or in the execution entity, or in other electronic devices that are communicatively connected to the execution entity.

[0138] In some application scenarios, the rendering interpreter described above runs on the terminal device, and the execution entity can send the task atomic components to the terminal device running the first application system client. After receiving the task atomic components, the first application system client can invoke the rendering interpreter stored on the terminal device to interpret and render the task atomic components.

[0139] As one implementation, the aforementioned rendering interpreter can be a file of the first application system client and bound to the first application system client. In this implementation, after receiving the task atomic component, the first application system client can directly call the rendering interpreter in its own file to interpret and render the task atomic component.

[0140] In other application scenarios, the aforementioned rendering interpreter can be stored within the execution entity or in other electronic devices that communicate with the execution entity. In these scenarios, when the execution entity sends a task atomic component to a first application system client running on a terminal device, the data of the task atomic component needs to carry a preset rendering interpreter that matches the terminal device and its operation diagram. If the first application system client is a web application client, the execution entity can embed preset rendering interpreters that match different combinations of terminal devices and operating systems into the web script. Thus, when the first application client receives the data of the task atomic component, it can extract a target rendering interpreter from the web script that matches both the local terminal device and operating system, and perform the rendering operation of the task atomic component based on that target rendering interpreter.

[0141] In these application scenarios, the second application system proactively generates task information based on business requirements and sends it to the aforementioned execution entity. The execution entity then generates task atomic components based on the task information and sends these components to the target user's first application system client. This facilitates the target user's timely receipt and processing of task information corresponding to the business requirements, improving the efficiency of task information delivery and enhancing office efficiency within the enterprise.

[0142] In these embodiments, by pre-setting a preset rendering interpreter that matches different terminal devices and operating systems, the same or similar rendering results of task atomic components can be obtained on different terminal devices and operating systems. This allows task atomic components to obtain similar display results on different terminal devices and operating systems. Therefore, task atomic components will not have significantly different display effects on different terminal devices, avoiding inconvenience in task operation execution caused by different display effects, and further improving the efficiency of cross-device and cross-system collaborative work.

[0143] Figure 5 This is a schematic diagram according to the fourth embodiment of this disclosure. (See diagram below.) Figure 5 As shown, the information processing method provided in this embodiment includes:

[0144] S501. Generate task information according to the task information generation instruction. The task information is used to instruct the receiving end to generate task atomic components according to the atomic component template and task data defined by the preset rendering protocol.

[0145] The execution entity in this embodiment can be a server running a second application system. This server can include a server cluster or a single server.

[0146] The second application system can be any application system, such as any one of the multiple application systems within an enterprise.

[0147] In some application scenarios, the above-mentioned task information generation instructions are actively generated by the aforementioned executing entity based on business needs.

[0148] In these application scenarios, the aforementioned task information is proactively generated by the second application system based on business requirements. In these scenarios, the second application system can pre-store business requirement settings. Business requirements may include, for example, monthly or quarterly report tasks. These business requirement settings may include time settings and target user settings. In these application scenarios, the second application system can proactively generate task information corresponding to the business requirements based on the time settings and send this task information to the atomic component server. This task information may carry target user information. In these application scenarios, the executing entity can generate task information generation instructions based on business requirement settings. For tasks requiring periodic generation, task information can be automatically generated without manual intervention, saving the manual operation required to initiate task information and thus improving office efficiency.

[0149] In other application scenarios, the above task information generation instructions are generated based on the task request sent by the initiating user.

[0150] In these application scenarios, the second application system described above can generate tasks based on task requests received from the initiating user. These task requests can be arbitrary. Task requests include instructing the target user to browse information, perform corresponding operations, etc.

[0151] The aforementioned task request can be sent by the initiating user through their second application system client. In these application scenarios, the second application system can generate task information based on the received task request from the initiating user and send the task information to the atomic component server. The task information can carry the initiating user's information. In these application scenarios, the executing entity can generate a task information generation instruction based on the task request initiated by the initiating user and generate task information according to the task information generation instruction, providing convenience for the initiating user to initiate task information according to their own needs.

[0152] As an illustration, the second application system could be an ERP application system, where the task information initiated by the ERP application system can instruct the sending of approval application information to the target user.

[0153] As another illustrative example, the second application system could be a weekly report application system. The task information sent by the weekly report application system could instruct the target user to send information displaying the content of the prepared weekly report, or information for filling in the weekly report content.

[0154] S502, Send task information.

[0155] The aforementioned task information can be sent to the atomic component server. After receiving the task information, the atomic component server can then... Figure 4 The method provided in the illustrated embodiment generates task atomic components and sends the task atomic components to the first application system client of the target user.

[0156] In this embodiment, task information is generated according to the task information generation instruction. The task information is used to instruct the receiving end to generate task atomic components based on the atomic component template and task data defined by the preset rendering protocol; the task information is then sent. This task information can be subsequently processed into task atomic components and sent to the first application system client, thereby facilitating flow and display between different application systems, improving information reach, and enhancing enterprise office efficiency within the enterprise.

[0157] In some implementations, the information processing method also includes the following steps:

[0158] First, receive task operation information, which is used to instruct the target user to perform task operations in the task atomic component.

[0159] The information regarding the aforementioned task operations can be information about task operations sent by the atomic component server. This information can also include information about task operations displayed by the target user within the task atomic component in the first application system client.

[0160] The information for the aforementioned task operations may include the target user's information, the content of the task operations, etc.

[0161] Secondly, determine the result of the task operation based on the information from the task operation.

[0162] The aforementioned executing entity can determine the result of the task operation based on the information provided by the task operation.

[0163] For example, the result of an operation can be determined based on the title of an option control that the target user selected, as indicated in the task's instructions. Typically, the title of an option control represents the meaning of the option it represents. The meaning of the option might include, for example, "Agree" or "Decline."

[0164] If the task operation includes text or symbols input by the target user, semantic recognition can be performed on these text or symbols to determine the task operation result. For example, the task information might be a request for the target user to approve an approval task. If the task operation includes the text "supplementary materials" entered by the target user in an input control, semantic recognition can be performed on this text to determine the operation result: the approval was not approved, and supplementary materials are required.

[0165] Schematic representation: The results of the above task operations include agree, refuse, return, pass, fail, read, and other task operation results.

[0166] Finally, the data in the second application system is updated based on the task operation results.

[0167] For each task, a task record can be generated for the second application system. The task record can record the initiator of the task, the target user to whom it was sent, and the task data. For each received task operation, the result of that operation can also be recorded.

[0168] This allows for the preservation of relatively complete task records for the second application system, making it convenient for users to query task information and task operation results.

[0169] In some embodiments, the above information processing method further includes: sending information about the task operation result to the initiating user who initiated the task request.

[0170] The task information described above can be generated based on a task request initiated by the user. The user initiating the request can be any user within the enterprise.

[0171] The information sent to the initiating user regarding the task operation result may include a second application system client sent to the initiating user, as well as other application system clients sent to the initiating user. These other application system clients could be, for example, instant messaging application system clients.

[0172] In these embodiments, the executing entity can send the task operation results to the initiating user. Thus, the initiating user can quickly understand the task operation results without logging into a second application system, further improving the efficiency of information exchange. Within an enterprise, this can improve the efficiency of collaborative work.

[0173] Figure 6 This is a schematic diagram based on the fifth embodiment of the present disclosure, as shown below. Figure 6 As shown, the information processing device 600 provided in this embodiment includes:

[0174] The first receiving unit 601 is used to receive display information indicating that the task atomic component should be displayed on the client of the first application system; the task atomic component is obtained by the server according to the task information sent by the second application system and the atomic component template defined by the preset rendering protocol.

[0175] Rendering unit 602 is used to render task atomic components based on a preset rendering interpreter;

[0176] Display unit 603 is used to display the rendered task atomic components in the first application system client.

[0177] In some embodiments, the information processing apparatus further includes: a second receiving unit 604 and a first transmitting unit 605; wherein

[0178] The second receiving unit 604 is used to receive the task operation performed by the target user in the displayed task atomic component. The task operation is used to complete the task indicated by the task information.

[0179] The first sending unit 605 is used to generate task operation information and send the task operation information to the server so that the server can send the task operation information to the second application system, and the second application system can determine the task operation result based on the task operation information.

[0180] In some embodiments, the second receiving unit 604 includes a control operation receiving module 6041;

[0181] The control operation receiving module 6041 is used to receive the task operations performed by the user in the task interaction control in the task atom component.

[0182] In some embodiments, the preset rendering interpreter includes one of the following:

[0183] A preset rendering interpreter is embedded in the page script of the web client of the first application system;

[0184] The default rendering interpreter is bound to the application client of the first application system.

[0185] In some embodiments, the rendering unit 602 includes a calling module 6021 and a rendering module 6022;

[0186] Module 6021 is used to call the local rendering function module according to the preset rendering interpreter;

[0187] Rendering module 6022 is used to render task atomic components using the local rendering function module.

[0188] The device in this embodiment can perform Figure 2 or Figure 3 The technical solutions described above are implemented in the same way, and their specific implementation processes and technical principles are the same, so they will not be repeated here.

[0189] Figure 7 This is a schematic diagram based on the sixth embodiment of the present disclosure, as shown below. Figure 7 As shown, the information processing device 700 provided in this embodiment includes:

[0190] The determining unit 701 is used to determine the atomic component template that matches the task indicated by the task information according to a preset rendering protocol in response to receiving task information sent by the second application system.

[0191] Integration unit 702 is used to integrate the task data indicated by the task information with the atomic component template to obtain the task atomic component;

[0192] The second sending unit 703 is used to generate display information including task atomic components and send the display information to the first application system client so that the first application system client renders and displays the task atomic components according to the preset interpreter engine. The first application system client includes clients of other application systems other than the second application system.

[0193] In some embodiments, the determining unit 701 includes a first determining module 7011;

[0194] The first determining module 7011 is used to determine, in response to receiving task information, an atomic component template that matches the task indicated by the second application system and the task information according to a preset rendering protocol.

[0195] In some embodiments, the second sending unit 703 includes a multi-client sending module 7031;

[0196] The multi-client sending module 7031 is used to send display information to at least one first application system client of the target user, so that the at least one first application system client renders the atomic components of the task according to the preset rendering interpreter matched with their respective terminal devices; the at least one first application system client runs on different terminal devices, and the different terminal devices run different operating systems.

[0197] In some embodiments, the information processing apparatus further includes: a third receiving unit 704 and a third sending unit 705; wherein

[0198] The third receiving unit 704 is used to receive task operation information sent by the first application system client; the task operation information is generated by the first application client based on the operation performed by the target user in the task atomic component.

[0199] The third-party sending unit 705 is used to send task operation information to the second application system so that the second application system can perform the following update operations: determine the task operation result based on the task operation information; and update the data of the second application system based on the task operation result.

[0200] The device in this embodiment can perform Figure 4 The technical solutions described above are implemented in the same way, and their specific implementation processes and technical principles are the same, so they will not be repeated here.

[0201] Figure 8 This is a schematic diagram based on the seventh embodiment of the present disclosure, as shown below. Figure 8 As shown, the information processing device 800 provided in this embodiment includes:

[0202] The task information generation unit 801 is used to generate task information according to the task information generation instruction. The task information is used to instruct the receiving end to generate task atomic components according to the atomic component template and task data defined by the preset rendering protocol.

[0203] The fourth sending unit 802 is used to send task information.

[0204] In some embodiments, the task information generation unit 801 includes an active generation module 8011 and a passive generation module 8012.

[0205] The proactive generation module 8011 is used to set proactive generation task information generation instructions according to business needs;

[0206] The passive generation module 8012 is used to generate task information generation instructions based on the task request sent by the initiating user.

[0207] In some embodiments, the information processing apparatus 800 further includes a fourth receiving unit 803, a second determining unit 804, and an updating unit 805;

[0208] The fourth receiving unit 803 is used to receive task operation information, which is used to instruct the target user to perform task operations in the task atomic component.

[0209] The second determining unit 804 is used to determine the result of the task operation based on the information of the task operation.

[0210] Update unit 805 is used to update the data of the second application system based on the results of the task operation.

[0211] In some embodiments, the information processing apparatus 800 further includes a fifth transmitting unit 806;

[0212] The fifth sending unit 806 is used to send information about the task operation result to the initiating user who initiated the task request.

[0213] The device in this embodiment can perform Figure 5 The technical solutions described above are implemented in the same way, and their specific implementation processes and technical principles are the same, so they will not be repeated here.

[0214] Figure 9 This is a schematic diagram based on the eighth embodiment of the present disclosure, as shown below. Figure 9 As shown, the electronic device 900 in this embodiment may include a processor 901 and a memory 902.

[0215] Memory 902 is used to store programs. Memory 902 may include volatile memory, such as random-access memory (RAM), such as static random-access memory (SRAM), double data rate synchronous dynamic random-access memory (DDR SDRAM), etc.; memory may also include non-volatile memory, such as flash memory. Memory 902 is used to store computer programs (such as application programs, functional modules, etc. that implement the above methods), computer instructions, etc. The computer programs, computer instructions, etc., can be partitioned and stored in one or more memories 902. Furthermore, the computer programs, computer instructions, data, etc., can be accessed by processor 901.

[0216] The aforementioned computer programs and instructions can be stored in one or more partitions of memory 902. Furthermore, the aforementioned computer programs and instructions can be invoked by processor 901.

[0217] The processor 901 is configured to execute the computer program stored in the memory 902 to implement the various steps in the methods described in the above embodiments.

[0218] For details, please refer to the relevant descriptions in the preceding method embodiments.

[0219] The processor 901 and the memory 902 can be independent structures or integrated structures. When the processor 901 and the memory 902 are independent structures, the memory 902 and the processor 901 can be coupled together via bus 903.

[0220] The electronic device in this embodiment can execute the technical solution in the above method. Its specific implementation process and technical principle are the same, and will not be repeated here.

[0221] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0222] According to embodiments of this disclosure, this disclosure also provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to execute the scheme provided in any of the above embodiments.

[0223] According to embodiments of this disclosure, this disclosure also provides a computer program product comprising: a computer program stored in a readable storage medium, at least one processor of an electronic device being able to read the computer program from the readable storage medium, and the at least one processor executing the computer program causing the electronic device to perform the scheme provided in any of the above embodiments.

[0224] Figure 10 A schematic block diagram of an example electronic device that can be used to implement embodiments of the present disclosure is shown. The electronic device 1000 can be a terminal device or a server. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0225] like Figure 10As shown, device 1000 includes a computing unit 1001, which can perform various appropriate actions and processes according to a computer program stored in read-only memory (ROM) 1002 or a computer program loaded from storage unit 1008 into random access memory (RAM) 1003. The RAM 1003 may also store various programs and data required for the operation of device 1000. The computing unit 1001, ROM 1002, and RAM 1003 are interconnected via bus 1004. Input / output (I / O) interface 1005 is also connected to bus 1004.

[0226] Multiple components in device 1000 are connected to I / O interface 1005, including: input unit 1006, such as keyboard, mouse, etc.; output unit 1007, such as various types of monitors, speakers, etc.; storage unit 1008, such as disk, optical disk, etc.; and communication unit 1009, such as network card, modem, wireless transceiver, etc. Communication unit 1009 allows device 1000 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0227] The computing unit 1001 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 1001 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1001 performs the various methods and processes described above, such as the electronic medical record form generation operation processing. For example, in some embodiments, the electronic medical record form generation operation processing may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 1008. In some embodiments, part or all of the computer program may be loaded and / or installed on device 1000 via ROM 1002 and / or communication unit 1009. When the computer program is loaded into RAM 1003 and executed by the computing unit 1001, one or more steps of the electronic medical record form generation operation processing described above may be performed. Alternatively, in other embodiments, the computing unit 1001 may be configured by any other suitable means (e.g., by means of firmware) to perform the generation operation of the electronic medical record form.

[0228] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0229] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0230] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

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

[0232] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0233] Computer systems can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. A server can be a cloud server, also known as a cloud computing server or cloud host, a hosting product within the cloud computing service ecosystem, addressing the shortcomings of traditional physical hosts and VPS (Virtual Private Server, or simply "VPS") services, such as high management difficulty and weak business scalability. Servers can also be servers for distributed systems or servers incorporating blockchain technology.

[0234] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0235] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. An information processing method, comprising: The system receives an instruction to display the task atomic component's information on the first application system client. The task atomic component is obtained by the server based on the task information received from the second application system and the atomic component template defined by the preset rendering protocol. The task atomic components are rendered based on a preset rendering interpreter that matches the preset rendering protocol; The rendered task atomic components are displayed in the first application system client.

2. The method according to claim 1, characterized in that, The method further includes: Receive a task operation performed by the target user in the displayed task atom component, the task operation being used to complete the task indicated by the task information; The system generates task operation information and sends it to the server, so that the server can send it to the second application system, and the second application system can determine the task operation result based on the task operation information.

3. The method according to claim 2, characterized in that, The receiving of task operations performed by the user in the displayed atomic components includes: Receives task operations performed by the user in the task interaction controls within the task atom component.

4. The method according to any one of claims 1-3, characterized in that, The preset rendering interpreter includes one of the following: A preset rendering interpreter is embedded in the page script of the web client of the first application system; The default rendering interpreter is bound to the application client of the first application system.

5. The method according to any one of claims 1-3, characterized in that, The rendering of the task atomic components based on a preset rendering interpreter that matches the preset rendering protocol includes: The local rendering function module is invoked based on the preset rendering interpreter; The task atomic component is rendered using the local rendering function module.

6. An information processing method, comprising: In response to receiving task information from the second application system, determine the atomic component template that matches the task indicated by the task information according to the preset rendering protocol; The task data indicated by the task information is integrated with the atomic component template to obtain the task atomic component; The system generates display information including the task atomic components and sends the display information to a first application system client, so that the first application system client renders and displays the task atomic components according to a preset interpreter engine that matches the preset rendering protocol. The first application system client includes clients of other application systems besides the second application system.

7. The method according to claim 6, characterized in that, The step of responding to receiving task information from the second application system and determining the atomic component template matching the task indicated by the task information according to a preset rendering protocol includes: In response to receiving the task information, an atomic component template that matches both the second application system and the task indicated by the task information is determined according to a preset rendering protocol.

8. The method according to claim 6, characterized in that, Sending the display information to the first application system client, so that the first application system client renders and displays the task atomic component according to a preset rendering interpreter engine that matches the preset rendering protocol, includes: The display information is sent to at least one first application system client of the target user, so that the at least one first application system client renders the task atomic component according to a preset rendering interpreter matched with its corresponding terminal device; the at least one first application system client runs on different terminal devices and the different terminal devices run different operating systems.

9. The method according to any one of claims 6-8, characterized in that, The method further includes: Receive task operation information sent by the first application system client; the task operation information is generated by the first application client based on the operation performed by the target user in the task atomic component; The task operation information is sent to the second application system, so that the second application system performs the following update operations: determines the task operation result based on the task operation information; and updates the data of the second application system based on the task operation result.

10. An information processing method, characterized in that, include: According to the task information generation instruction, task information is generated. The task information is used to instruct the receiving end to generate task atomic components according to the atomic component template and task data defined by the preset rendering protocol, so that the first application system client can render and display the task atomic components according to the preset interpreter engine that matches the preset rendering protocol. Send the task information.

11. The method according to claim 10, characterized in that, The task information generation instruction is generated according to one of the following: Configure automatic generation based on business needs; Generate based on the task request sent by the initiating user.

12. The method according to claim 10, characterized in that, Receive task operation information, which is used to instruct the target user to perform a task operation in the task atomic component; Determine the task operation result based on the information provided in the task operation; Update the data of the second application system based on the results of the task operation.

13. The method according to any one of claims 10-12, characterized in that, The method further includes: Send information about the task operation results to the user who initiated the task request.

14. An information processing apparatus, comprising: The first receiving unit is used to receive display information indicating that the task atomic component should be displayed on the first application system client; The task atomic component is generated by the server according to the following steps: receiving task information sent by the second application system; determining the atomic component template that matches the task information according to a preset rendering protocol; The task atomic component is obtained by integrating the atomic component template and the task data indicated by the task instruction. A rendering unit is used to render the task atomic components based on a preset rendering interpreter that matches the preset rendering protocol; The display unit is used to display the rendered task atomic components in the first application system client.

15. The apparatus according to claim 14, characterized in that, The device further includes: a second receiving unit and a first transmitting unit; wherein The second receiving unit is used to receive the task operation performed by the target user in the displayed task atomic component, the task operation being used to complete the task indicated by the task information. The first sending unit is used to generate task operation information and send the task operation information to the server so that the server can send the task operation information to the second application system, and the second application system can determine the task operation result based on the task operation information.

16. The apparatus according to claim 15, characterized in that, The second receiving unit includes a control operation receiving module; The control operation receiving module is used to receive task operations performed by the user in the task interaction control of the task atom component.

17. The apparatus according to any one of claims 14-16, characterized in that, The preset rendering interpreter includes one of the following: A preset rendering interpreter is embedded in the page script of the web client of the first application system; The default rendering interpreter is bound to the application client of the first application system.

18. The apparatus according to any one of claims 14-16, characterized in that, The rendering unit includes a calling module and a rendering module; The calling module is used to call the local rendering function module according to the preset rendering interpreter; The rendering module is used to render the task atomic components using the local rendering function module.

19. An information processing apparatus, comprising: The determining unit is used to determine the atomic component template that matches the task indicated by the task information in response to receiving task information sent by the second application system, according to a preset rendering protocol; The integration unit is used to integrate the task data indicated by the task information with the atomic component template to obtain the task atomic component; The second sending unit is used to generate display information including the task atomic component and send the display information to the first application system client, so that the first application system client renders and displays the task atomic component according to a preset interpreter engine that matches the preset rendering protocol. The first application system client includes clients of other application systems besides the second application system.

20. The apparatus according to claim 19, characterized in that, The determining unit includes a first determining module; The first determining module is used for: In response to receiving the task information, an atomic component template that matches both the second application system and the task indicated by the task information is determined according to a preset rendering protocol.

21. The apparatus according to claim 19, characterized in that, The second sending unit includes a multi-client sending module; The multi-client sending module is used to send the display information to at least one first application system client of the target user, so that the at least one first application system client renders the task atomic component according to a preset rendering interpreter matched with its corresponding terminal device. The at least one first application system client runs on different terminal devices, and the different terminal devices run different operating systems.

22. The apparatus according to any one of claims 19-21, characterized in that, The device further includes: a third receiving unit and a third transmitting unit; wherein The third receiving unit is used to receive task operation information sent by the first application system client; the task operation information is generated by the first application client based on the operation performed by the target user in the task atomic component. A third-party sending unit is used to send the task operation information to the second application system, so that the second application system performs the following update operations: determining the task operation result based on the task operation information; and updating the data of the second application system based on the task operation result.

23. An information processing device, characterized in that, include: The task information generation unit is used to generate task information according to the task information generation instruction. The task information is used to instruct the receiving end to generate task atomic components according to the atomic component template and task data defined by the preset rendering protocol, so that the first application system client can render and display the task atomic components according to the preset interpreter engine that matches the preset rendering protocol. The fourth sending unit is used to send the task information.

24. The apparatus according to claim 23, characterized in that, The task information generation unit includes an active generation module and a passive generation module; The active generation module is used to set active generation task information generation instructions according to business needs; The passive generation module is used to generate task information generation instructions based on the task request sent by the initiating user.

25. The apparatus according to claim 23, characterized in that, The device further includes a fourth receiving unit, a second determining unit, and an updating unit; The fourth receiving unit is used to receive task operation information, which is used to instruct the target user to perform task operations in the task atomic component. The second determining unit is used to determine the task operation result based on the information of the task operation. The update unit is used to update the data of the second application system based on the results of the task operation.

26. The apparatus according to claim 24, characterized in that, The device also includes a fifth transmitting unit; The fifth sending unit is used to send information about the task operation result to the initiating user.

27. An electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-13.

28. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-13.

29. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1-13.

Images