Service approval method based on signature multiplexing and related equipment
By introducing the signature reuse function into the business approval system and utilizing the synchronization mechanism between clients, the problem of cumbersome approval processes in the existing technology is solved, the approval efficiency is improved, and cross-platform signature reuse is achieved.
Patent Information
- Application Number
- CN202310905834.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-07-21
- Publication Date
- 2025-01-21
AI Technical Summary
In the prior art, manual signature is required in the business approval process, resulting in cumbersome approval process and inefficient efficiency.
By detecting whether the target approval object is configured with signature reuse when the client receives the business approval message, and synchronizing the signature information between different application platforms, the signature reuse function is implemented.
It reduces the number of signatures for target approval objects, improves the efficiency of business approval, and enables cross-platform signature reuse.
Smart Images

Figure CN119338137A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a business approval method based on signature reuse and related equipment. Background Art
[0002] In recent years, electronic approval has been increasingly used in various scenarios such as enterprise processes, industry applications, mobile payments, and personal information security. In daily management activities, there are usually some businesses that need to be approved by the approver before they can be executed, such as project allocation, document approval, vacation approval, and bill approval.
[0003] In the current related technologies, in order to strengthen the sense of responsibility of the business approver, a manual signature method is added to ensure that the business approver agrees with the approval. However, in this way, the business approver needs to manually sign every time he agrees to the approval, which makes the approval process more cumbersome and is not conducive to improving the approval efficiency. Summary of the invention
[0004] The embodiments of the present application provide a business approval method based on signature reuse and related equipment. The related equipment may include a business approval device based on signature reuse, an electronic device, a computer-readable storage medium and a computer program product, which can reduce the number of signatures of the target approval object and improve the efficiency of business approval.
[0005] The present application embodiment provides a business approval method based on signature reuse, including:
[0006] Receiving a first business approval message through a first client;
[0007] When it is detected that the target approval object has performed a viewing operation on the first business approval message, and the target approval object has configured signature reuse, a business approval page is displayed, the business approval page includes the approval content corresponding to the first business approval message and the target signature information for the approval content, the target signature information is obtained by synchronizing the signature information configured for signature reuse in the second client, the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms;
[0008] In response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
[0009] The present application embodiment provides a business approval method based on signature reuse, including:
[0010] Receiving a second service approval message through a second client;
[0011] When a viewing operation of the target approval object on the second business approval message is detected, and the target approval object has not been configured with signature reuse, a business approval page is displayed, and the business approval page includes approval content corresponding to the second business approval message;
[0012] In response to a signature operation on the approval content, acquiring signature information;
[0013] In response to a signature reuse operation on the signature information, the signature information is stored, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms;
[0014] In response to the approval operation on the approval content, the approval result of the approval content and the signature information are sent to the approved object corresponding to the second business approval message.
[0015] Accordingly, the embodiment of the present application provides a service approval device based on signature reuse, including:
[0016] A first receiving unit, configured to receive a first service approval message through a first client;
[0017] A first display unit is used to display a business approval page when a viewing operation of the first business approval message by a target approval object is detected, and the target approval object has configured signature reuse, wherein the business approval page includes approval content corresponding to the first business approval message and target signature information for the approval content, wherein the target signature information is obtained by synchronizing signature information configured for signature reuse in a second client, and the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms;
[0018] The first sending unit is configured to send the approval result of the approval content and the target signature information to the approved object corresponding to the first business approval message in response to the approval operation on the approval content.
[0019] Accordingly, the embodiment of the present application provides a service approval device based on signature reuse, including:
[0020] A second receiving unit, configured to receive a second service approval message through a second client;
[0021] A second display unit is used to display a business approval page when a viewing operation of the target approval object on the second business approval message is detected, and the target approval object has not been configured with signature reuse, and the business approval page includes the approval content corresponding to the second business approval message;
[0022] An acquisition unit, configured to acquire signature information in response to a signature operation on the approval content;
[0023] a storage unit, configured to store the signature information in response to a signature reuse operation on the signature information, so as to synchronize the stored signature information to the first client for signature reuse when the target approval object performs business approval through the first client, wherein the first client and the second client are different application platforms;
[0024] The second sending unit is configured to send the approval result of the approval content and the signature information to the approved object corresponding to the second business approval message in response to the approval operation on the approval content.
[0025] Optionally, in some embodiments of the present application, the style attribute information of the target signature information is determined based on the page display mode of the business approval page.
[0026] Optionally, in some embodiments of the present application, the target signature information is obtained from the first application server according to the object identifier of the target approval object, and the first application server stores the signature information of the target approval object configured for signature reuse in the second client. The signature information is synchronized from the second client to the second application server when the target approval object performs a signature reuse operation through the second client, and then synchronized from the second application server to the first application server.
[0027] Optionally, in some embodiments of the present application, the business approval page further includes a re-signature control;
[0028] The service approval device based on signature reuse may also include a clearing unit and a re-signing unit, as follows:
[0029] The clearing unit is used to clear the target signature information in the business approval page in response to a triggering operation on the re-signing control;
[0030] The re-signing unit is used to display new target signature information on the business approval page in response to the re-signing operation on the approval content.
[0031] Optionally, in some embodiments of the present application, the service approval device based on signature multiplexing may further include a signature multiplexing unit as follows:
[0032] The signature multiplexing unit is used to store the new target signature information in response to a signature multiplexing operation on the new target signature information, so as to synchronize the stored new target signature information to the third client for signature multiplexing when the target approval object performs business approval through the third client. The third client and the first client are different application platforms.
[0033] Optionally, in some embodiments of the present application, the service approval device based on signature multiplexing may further include a mode switching unit as follows:
[0034] The mode switching unit is used to switch the display of the business approval page in the target page display mode in response to a switching operation on the page display mode of the business approval page, and synchronously switch the display of the target signature information under the target style attribute information, wherein the target style attribute information is determined based on the target page display mode.
[0035] Optionally, in some embodiments of the present application, the first display unit may include a first detection subunit, a second detection subunit, a signature acquisition subunit and a page display subunit, as follows:
[0036] The first detection subunit is configured to detect whether the configuration information of the target approval object includes signature information according to the object identifier of the target approval object when detecting the viewing operation of the target approval object on the first business approval message;
[0037] A second detection subunit is used to detect whether the configuration information includes signature reuse mark information when it is detected that the configuration information of the target approval object includes signature information;
[0038] A signature acquisition subunit, configured to acquire target signature information according to an object identifier of a target approval object when signature reuse mark information in the configuration information is detected;
[0039] The page display subunit is used to display the business approval page according to the target signature information.
[0040] Optionally, in some embodiments of the present application, the storage unit can be specifically used to synchronize the signature information to a second application server for storage in response to a signature reuse operation on the signature information, and then synchronize the signature information in the second application server to the first application server, so that when the target approval object performs business approval through the first client, the signature information is synchronized from the first application server to the first client for signature reuse.
[0041] Optionally, in some embodiments of the present application, the business approval page further includes a signature control; the acquisition unit may include a display subunit and an acquisition subunit, as follows:
[0042] The display subunit is used to display the signature area on the business approval page in response to a triggering operation on the signature control;
[0043] The acquisition subunit is used to acquire the signature information for the approval content in response to the signature editing operation on the signature area.
[0044] An electronic device provided in an embodiment of the present application includes a processor and a memory, wherein the memory stores a plurality of instructions, and the processor loads the instructions to execute the steps in the business approval method based on signature multiplexing provided in an embodiment of the present application.
[0045] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps in the business approval method based on signature reuse provided in the embodiment of the present application are implemented.
[0046] In addition, an embodiment of the present application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements the steps in the business approval method based on signature reuse provided in an embodiment of the present application.
[0047] An embodiment of the present application provides a business approval method based on signature reuse and related equipment; a first business approval message can be received through a first client; when a viewing operation of the target approval object on the first business approval message is detected, and the target approval object has been configured with signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the first business approval message and the target signature information for the approval content, the target signature information is obtained by synchronizing the signature information configured with signature reuse in the second client, and the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; in response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message. The present application can provide a method of signature reuse. After the user has set up signature reuse on a certain application platform (i.e., the second client), the previous signature information can be directly displayed when performing business approval on another application platform (i.e., the first client) without the need to sign again. The present application can realize cross-platform signature reuse during the business approval process, avoiding the situation where the target approval object needs to sign repeatedly multiple times, reducing the number of signatures for the target approval object, and thus improving business approval efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0049] Figure 1a It is a scenario diagram of a business approval method based on signature reuse provided in an embodiment of the present application;
[0050] Figure 1b It is a flow chart of a business approval method based on signature reuse provided in an embodiment of the present application;
[0051] Figure 1c This is a page diagram of a business approval method based on signature reuse provided in an embodiment of the present application;
[0052] Figure 1d This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0053] Figure 1e This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0054] Figure 1f This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0055] Figure 1g This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0056] Figure 1h This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0057] Figure 1i This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0058] Figure 1j This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0059] Figure 1k This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0060] Figure 1l This is another page schematic diagram of the business approval method based on signature reuse provided in an embodiment of the present application;
[0061] Figure 2a is another flow chart of the business approval method based on signature reuse provided in an embodiment of the present application;
[0062] Figure 2b is another flow chart of the business approval method based on signature reuse provided in an embodiment of the present application;
[0063] Figure 2c is another flow chart of the business approval method based on signature reuse provided in an embodiment of the present application;
[0064] Figure 2d is another flow chart of the business approval method based on signature reuse provided in an embodiment of the present application;
[0065] Figure 3a It is a structural diagram of a business approval device based on signature reuse provided in an embodiment of the present application;
[0066] Figure 3b It is a structural diagram of a business approval device based on signature reuse provided in an embodiment of the present application;
[0067] Figure 4 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0068] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0069] The embodiments of the present application provide a business approval method based on signature reuse and related equipment. The related equipment may include a business approval device based on signature reuse, an electronic device, a computer-readable storage medium and a computer program product.
[0070] Specifically, an embodiment of the present application provides a business approval device based on signature multiplexing applicable to a first electronic device, which may be a terminal or other device; an embodiment of the present application also provides a business approval device based on signature multiplexing applicable to a second electronic device, which may be a terminal or other device.
[0071] like Figure 1a As shown, a terminal and a server jointly execute a business approval method based on signature reuse as an example. The business approval system based on signature reuse provided in the embodiment of the present application includes a terminal 100, a server 110, and a terminal 120, etc. The terminal 100 is connected to the server 110 through a network, and the terminal 120 is connected to the server 110 through a network, such as a wired or wireless network connection, etc., wherein the business approval device based on signature reuse can be integrated in the terminal.
[0072] In one embodiment, the terminal 100 can be used to: receive a second business approval message through a second client; when detecting that a target approval object has performed a viewing operation on the second business approval message and the target approval object has not been configured with signature reuse, display a business approval page, the business approval page including approval content corresponding to the second business approval message; in response to a signature operation on the approval content, obtain signature information; in response to a signature reuse operation on the signature information, synchronize the signature information to the server 110 for storage, so that when the target approval object performs business approval through the first client, the signature information is synchronized from the server 110 to the first client for signature reuse, and the first client and the second client are different application platforms; in response to an approval operation on the approval content, send the approval result of the approval content and the signature information to the approved object corresponding to the second business approval message.
[0073] The terminal 120 can be used to: receive a first business approval message through a first client; when a viewing operation of the target approval object on the first business approval message is detected, and the target approval object has configured signature reuse, display a business approval page, the business approval page including approval content corresponding to the first business approval message and target signature information for the approval content, the target signature information is obtained from the server 110 according to the object identifier of the target approval object, the server 110 stores signature information of the target approval object configured for signature reuse in the second client, the signature information is synchronized from the second client to the server 110 when the target approval object performs a signature reuse operation through the second client, the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; in response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
[0074] Among them, server 110 can be used to: when the target approval object performs a signature reuse operation through the second client on terminal 100, store the signature information configured for signature reuse in terminal 100, and when the target approval object performs business approval through the first client on terminal 120, synchronize the signature information to the first client for signature reuse.
[0075] The terminal may be a mobile phone, a tablet computer, a laptop computer, or a personal computer (PC) etc. The server may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers.
[0076] It should be noted that the description order of the following embodiments is not intended to limit the preferred order of the embodiments.
[0077] The embodiment of the present application will be described from the perspective of a business approval device based on signature multiplexing. The business approval device based on signature multiplexing can be specifically integrated in a first electronic device, and the first electronic device can be a terminal or other device.
[0078] It is understandable that in the specific implementation of the present application, if user information (such as signature information) is involved, when the above embodiments of the present application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
[0079] like Figure 1bAs shown, the specific process of the business approval method based on signature reuse is as follows:
[0080] 101. Receive a first service approval message through a first client.
[0081] The first client may be a client of a message interaction application, and the types of the message interaction application may include an instant messaging application, a live broadcast application, etc. The first client may be an application client or a browser client, etc., which is not limited in this embodiment.
[0082] Specifically, the first client may be a client on a first terminal, which may be a mobile phone, a tablet computer, a laptop computer, or other devices.
[0083] The first business approval message may be a pending approval message sent by the approved object to the target approval object, which may include approval content that needs to be reviewed by the target approval object. Specifically, the approved object and the target approval object may be members of an organization in the same application message system; the target approval object may be the superior of the approved object.
[0084] 102. When it is detected that the target approval object has performed a viewing operation on the first business approval message and the target approval object has configured signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the first business approval message and the target signature information for the approval content. The target signature information is obtained by synchronizing the signature information configured for signature reuse in the second client. The signature information is generated when the target approval object performs business approval signature through the second client. The first client and the second client are different application platforms.
[0085] The viewing operation on the first business approval message may specifically be a click operation on the first business approval message, etc. In this embodiment, when the viewing operation on the first business approval message is detected and the target approval object has configured signature reuse, the signature information previously set for signature reuse may be directly displayed on the business approval page, and the signature information specifically refers to the target signature information for the approval content corresponding to the first business approval message.
[0086] In a specific embodiment, the target signature information displayed in the business approval page and the signature information configured for signature reuse in the second client have the same signature content, but the style attribute information of the two may be different. The signature content here may specifically include the signature content and attributes, such as handwriting, etc.; the style attribute information may include font color, background color, font size, resolution, etc.
[0087] In some embodiments, if it is detected that the configuration information of the target approval object includes signature reuse marking information, it can be determined that the target approval object has configured signature reuse. Specifically, before approving the first business approval message, when the target approval object performs business approval in the second client, it signs the approval content, obtains the corresponding signature information, and performs signature reuse selection processing on the signature information. Then, the signature information can be stored, and the signature reuse marking information can be added to the configuration information of the target approval object, so that when the target approval object performs business approval in the first client, the already drawn signature information can be directly displayed, without the need for the user to sign again, thereby improving the approval efficiency.
[0088] The second client may be a client of a message interaction application, an application client or a browser client, etc., which is not limited in this embodiment.
[0089] The first client and the second client are different application platforms. In some embodiments, the first client and the second client may be clients of the same application on different versions. In other embodiments, the first client and the second client may be clients of different applications, such as the first client is a client of a first message application, and the second client is a client of a second message application, and the first message application and the second message application may be heterogeneous applications.
[0090] Specifically, the second client may be a client on the second terminal. The second terminal may be a device such as a mobile phone, a tablet computer, or a laptop computer. The first terminal and the second terminal may refer to the same terminal or different terminals. In other words, the first client and the second client may be on the same terminal device or on different terminal devices, which is not limited in this embodiment.
[0091] In some embodiments, the first client and the second client are clients of the same application on different versions, where the version may refer to a software system version, etc. Specifically, the first client and the second client are clients of the same application on different operating systems, where the version corresponds to the operating system. The operating system here may include a desktop operating system (such as Windows), a mobile device operating system (such as Android), etc.
[0092] For example, the first client may be a web terminal of a message interaction application on a computer, and the second client may be a small program of the message interaction application on a mobile phone.
[0093] For another example, the first client may be a web (webpage) end of a message interaction application on a computer, and the second client may be an app (Application) end of the message interaction application on the computer.
[0094] For another example, the first client may be a web terminal of a first message application on a computer, and the second client may be a web terminal of a second message application on a computer, and the first message application and the second message application are heterogeneous applications. Specifically, the first message application may be an enterprise message application, and the second message application may be a personal social message application.
[0095] For another example, the first client may be a web terminal of a first message application on a computer, and the second client may be an app terminal of a second message application on a mobile phone. The first message application and the second message application are heterogeneous applications.
[0096] It should be noted that the signature information that is processed for signature reuse selection in the second client can also be used in the subsequent approval signature of the second client itself; specifically, when it is subsequently detected that the target approval object has performed a viewing operation on the business approval message in the second client, the already drawn signature information can be directly displayed on the business approval page, without the need for the user to sign again.
[0097] Optionally, in this embodiment, the target signature information is obtained from the first application server according to the object identifier of the target approval object. The first application server stores the signature information of the target approval object configured for signature reuse in the second client. The signature information is synchronized from the second client to the second application server when the target approval object performs a signature reuse operation through the second client, and then synchronized from the second application server to the first application server.
[0098] The first application server may be a server corresponding to the first client, and the second application server may be a server corresponding to the second client.
[0099] It should be noted that if the first client and the second client are clients of the same application in different versions, the first application server and the second application server can be the same server, that is, the first client and the second client access the same server (referred to as the target application server). In this scenario, the target signature information is obtained from the target application server according to the object identifier of the target approval object, and the target application server stores the signature information of the target approval object configured for signature reuse in the second client, and the signature information is synchronized from the second client to the target application server when the target approval object performs a signature reuse operation through the second client.
[0100] In some embodiments, the application server (including the first application server or the second application server) may include a preset mapping relationship set, the preset mapping relationship set may include a mapping relationship between a preset object identifier and preset signature information, the preset mapping relationship set may be a relationship table between the preset object identifier and the preset signature information, and based on the object identifier, the signature information corresponding to the object identifier can be queried in the preset mapping relationship set.
[0101] In some other embodiments, the configuration information of the target approval object can be determined according to the object identifier of the target approval object, and the configuration information of the target approval object can include its signature storage address information. The signature storage address information represents the specific storage address of the signature information of the target approval object in the application server. Therefore, according to the signature storage address information, the signature information corresponding to the target approval object and configured for signature reuse can be pulled from the application server and synchronized to the first client, so as to display the target signature information on the business approval page of the first client.
[0102] Optionally, in this embodiment, the step of “when detecting that the target approval object has performed a viewing operation on the first business approval message and the target approval object has configured signature reuse, displaying a business approval page” may include:
[0103] When a viewing operation of the target approval object on the first business approval message is detected, detecting whether the configuration information of the target approval object includes signature information according to the object identifier of the target approval object;
[0104] When it is detected that the configuration information of the target approval object includes signature information, detecting whether the configuration information includes signature reuse mark information;
[0105] When the signature reuse mark information in the configuration information is detected, the target signature information is obtained according to the object identifier of the target approval object;
[0106] According to the target signature information, the business approval page is displayed.
[0107] The object identification of the target approval object may be the ID (Identity document), avatar, nickname, etc. of the target approval object. The configuration information of the target approval object may be associated with the object identification of the target approval object.
[0108] The signature reuse mark information may indicate that the target approval object has been configured with signature reuse.
[0109] Among them, the step of "obtaining target signature information according to the object identification of the target approval object" may include: determining the signature storage address information of the target approval object according to the object identification of the target approval object, and then obtaining the target signature information based on the signature storage address information.
[0110] It should be noted that the reused signature information configured in the second client may also be used in the subsequent approval signature process of the second client itself.
[0111] Optionally, in this embodiment, the style attribute information of the target signature information is determined based on the page display mode of the business approval page.
[0112] The page display mode is also called the page display theme, which may include a night display mode and a day display mode. For the night display mode, the background color of the business approval page may be black, and the page information in the business approval page may be white; for the day display mode, the background color of the business approval page may be white, and the page information in the business approval page may be black.
[0113] Specifically, the stored signature information is a signature in image mode, and its image background color is white, and the signature font color is dark. If the page display mode of the business approval page in the first client is the night display mode, the signature information can be rendered in reverse color, and its image background color is changed from white to black, and the signature font color is changed from dark to light. The style attribute information after the inversion processing is the style attribute information of the target signature information that the first client needs to display.
[0114] Optionally, in this embodiment, the business approval method based on signature reuse may further include:
[0115] In response to the switching operation of the page display mode of the business approval page, the business approval page in the target page display mode is switched to be displayed, and the target signature information under the target style attribute information is switched to be displayed synchronously, and the target style attribute information is determined based on the target page display mode.
[0116] Specifically, the switching operation of the page display mode may be switching the page display mode from the daytime display mode to the nighttime display mode, or may be switching the page display mode from the nighttime display mode to the daytime display mode.
[0117] In the case of switching the page display mode from the daytime display mode to the nighttime display mode, the target page display mode is the nighttime display mode, and the target style attribute information of the target signature information can be determined according to the nighttime display mode. Specifically, in the nighttime display mode, the target style attribute information of the target signature information can be: the image background color is dark, and the signature font color is light.
[0118] In the case of switching the page display mode from the night display mode to the day display mode, the target page display mode is the day display mode, and the target style attribute information of the target signature information can be determined according to the day display mode. Specifically, in the day display mode, the target style attribute information of the target signature information can be: the image background color is light and the signature font color is dark.
[0119] 103. In response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
[0120] The approval operation on the approval content may specifically include a rejection operation or a passing operation on the approval content, as well as corresponding approval opinions.
[0121] Optionally, in this embodiment, the business approval page further includes a re-signature control;
[0122] Before the step of "in response to the approval operation on the approval content, sending the approval result of the approval content and the target signature information to the approved object corresponding to the first business approval message", it may also include:
[0123] In response to a triggering operation on the re-signing control, clearing target signature information in the business approval page;
[0124] In response to the re-signing operation on the approval content, new target signature information is displayed on the business approval page.
[0125] The triggering operation of the re-signing control may specifically be a click operation on the re-signing control, etc. By clicking the operation, the target signature information displayed on the business approval page may be cleared.
[0126] In some embodiments, the initial business approval page does not include a re-signature control, and a trigger operation (such as a click operation) can be performed on the target signature information on the business approval page, so that a signature editing area is displayed on the business approval page, and the signature editing area may include a re-signature control and an enlarged display of the target signature information. By clicking the re-signature control, the target signature information on the signature editing area can be cleared, and the target approval object can redraw its signature information on the signature editing area.
[0127] Optionally, in this embodiment, the business approval method based on signature reuse may further include:
[0128] In response to a signature reuse operation on the new target signature information, the new target signature information is stored so that when the target approval object performs business approval through a third client, the stored new target signature information is synchronized to the third client for signature reuse. The third client and the first client are different application platforms.
[0129] The third client and the first client are different application platforms. Specifically, in some embodiments, the third client and the first client may be clients of the same application on different versions. In other embodiments, the first client and the third client may be clients of different applications, such as the first client is a client of a first message application, and the third client is a client of a third message application, and the first message application and the third message application may be heterogeneous applications.
[0130] The business approval page may include a signature reuse control. In this embodiment, the signature reuse operation on the new target signature information may be a selection operation on the signature reuse control, and the selection operation may be a click operation or a check operation.
[0131] Among them, the new target signature information can be stored in the first application server, and the new target signature information in the first application server can be synchronized to the third application server, so that the target approval object can obtain the new target signature information from the third application server for reuse when performing business approval through the third client in a future time period. Specifically, when the third client clicks to view the business approval message, the new target signature information can be directly displayed on its corresponding business approval page without the user having to sign again.
[0132] The third client may be an application client or a browser client, etc., which is not limited in this embodiment. The third application server is a server corresponding to the third client.
[0133] It should be noted that if the first client and the third client are clients of the same application in different versions, the first application server and the third application server may be the same server, that is, the first client and the third client access the same server (referred to as the target application server). In this scenario, the new target signature information may be stored in the target application server, so that the target approval object may obtain the new target signature information from the target application server for reuse when performing business approval through the third client in a future time period.
[0134] Specifically, the third client may be a client on a third terminal. The third terminal may be a device such as a mobile phone, a tablet computer, a laptop computer, etc. The first terminal, the second terminal, and the third terminal may refer to the same terminal or different terminals. In some embodiments, the third client may be the second client.
[0135] It should be noted that the new target signature information for the signature reuse operation (that is, the signature reuse selection processing) performed in the first client can also be used in the subsequent approval signature of the first client itself; specifically, when the target approval object is subsequently detected to have performed a viewing operation on the business approval message in the first client, the new target signature information can be directly displayed on the business approval page without the user having to sign again.
[0136] Optionally, in this embodiment, the business approval page includes a content rejection control and a content approval control; the step of "in response to the approval operation on the approval content, sending the approval result of the approval content and the target signature information to the approved object corresponding to the first business approval message" may include:
[0137] When a trigger operation on a content rejection control is detected, a rejection opinion on the approval content is sent to an approved object corresponding to the first business approval message;
[0138] When a triggering operation on the content through the control is detected, the approval opinion on the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
[0139] The triggering operation of the content rejection control may be a click operation on the content rejection control, etc. Similarly, the triggering operation of the content pass control may be a click operation on the content pass control, etc.
[0140] In a specific scenario, a message interaction application has clients under multiple versions, for example, it may include clients such as a Web client and a mini program. Specifically, the business approval pages of the Web client and the mini program both provide a signature function.
[0141] It should be noted that when a user approves an application for the first time or has no saved signature, the user needs to sign by hand. This process is basically the same on the Web and mini-programs.
[0142] like Figure 1c As shown in the figure, it is a business approval page on the Web. The business approval page provides a signature entry. The signature entry is the icon corresponding to the "Signature" in the lower right corner of the business approval page. The icon is the signature control. The business approval page can also include specific approval content. The approval content can include the approval number, submission time, the department where the approved object is located, and the text that needs to be approved. The target approval object can trigger the signature control. For example, click the operation to display the signature area on the business approval page. Figure 1d As shown in the figure, the signature area is a canvas for signature. The target approval object can draw signature information (such as "Zhang San") on the canvas. The signature can be drawn by mouse or by touching the screen with a finger. Figure 1e As shown, after the signature is completed, an option can be provided for the user to choose whether to continue using this signature next time, that is, whether to perform a signature reuse operation on the drawn signature information. If the user checks "Continue to use this signature when agreeing next time", the target approval object can directly display the signature information on the business approval page when performing business approval through any client of the message interaction application (other clients or the Web end) or a heterogeneous application of the message interaction application, without the need for the user to sign again.
[0143] In addition, if Figure 1c As shown, the target approval object can also fill in his or her own approval opinion on the business approval page, and can also remind relevant personnel to view the approval opinion through @, and attach relevant documents. The business approval page can also include a content rejection control (the icon corresponding to "reject") and a content approval control (the icon corresponding to "agree"). By triggering the content approval control, the approval opinion and signature information can be sent to the approved object; by triggering the content rejection control, the approval opinion can be sent to the approved object.
[0144] like Figure 1e As shown, the signature area may also include a clearing control for the signature information. In response to a triggering operation of the clearing control, such as a click operation, the signature information drawn in the signature area may be cleared.
[0145] like Figure 1fAs shown in the figure, the business approval page of the mini program also provides a signature entry. The signature entry is the icon corresponding to the "Signature" in the lower right corner of the business approval page, which is the signature control. The business approval page can also include specific approval content, which can include the approval number, submission time, the department where the approved object is located, and the text that needs to be approved. The target approval object can trigger the signature control, such as clicking to display the signature area on the business approval page. Figure 1g As shown in the figure, the signature area is a canvas for signature, and the target approval object can draw signature information (such as "Zhang San") on the canvas. Specifically, the signature can be drawn by touching the screen with a stylus or a finger. Figure 1h As shown, after the signature is completed, an option can be provided for the user to choose whether to continue using this signature next time, that is, whether to reuse the drawn signature information. If the user checks "Continue to use this signature next time I agree", the target approval object can then directly display the signature information on the business approval page when conducting business approval through any client of the message interaction application (other clients or the mini program) or heterogeneous applications of the message interaction application, without the need for the user to sign again.
[0146] In addition, if Figure 1f As shown, the target approval object can also fill in his or her own approval opinion on the business approval page, and can also remind relevant personnel to view the approval opinion through @, and attach relevant documents. The business approval page can also include a content rejection control (the icon corresponding to "reject") and a content approval control (the icon corresponding to "agree"). By triggering the content approval control, the approval opinion and signature information can be sent to the approved object; by triggering the content rejection control, the approval opinion can be sent to the approved object.
[0147] like Figure 1h As shown, the signature area may also include a clearing control for the signature information. In response to a triggering operation of the clearing control, such as a click operation, the signature information drawn in the signature area may be cleared.
[0148] If the target approval object has configured signature reuse in the historical approval process of the message interaction application or its heterogeneous application, the target approval object can automatically display the signature information on the corresponding business approval page when viewing the business approval message through any client of the message interaction application or its heterogeneous application, without the need for the user to sign again.
[0149] In a specific scenario, when the user chooses to continue using this signature next time during the previous signing process, the message interaction application will save the signature information and automatically display the signature the next time it is needed, prompting the user that it will be automatically used.
[0150] like Figure 1i As shown in FIG. 1 , when a user selects signature reuse in the historical approval process of a message interaction application or a heterogeneous application of the message interaction application, the business approval page displayed when viewing a new business approval message through the web end of the message interaction application or its heterogeneous application is shown. Figure 1i It can be seen that the last signature information can be directly displayed on the business approval page without the user having to re-sign. In addition, in this embodiment, while displaying the last signature information, a re-signing function entry is also provided, and the user can choose to re-sign and can continue to choose whether to reuse the new signature.
[0151] like Figure 1j As shown in FIG. 1 , when a user selects signature reuse in the historical approval process of a message interaction application or a heterogeneous application of the message interaction application, the business approval page displayed when viewing a new business approval message through the message interaction application or its heterogeneous application is a mini program. Figure 1j It can be seen that the last signature information can be directly displayed on the business approval page without the user having to re-sign. In addition, in this embodiment, while displaying the last signature information, a re-signing function entry is also provided, and the user can choose to re-sign and can continue to choose whether to reuse the new signature.
[0152] Among them, mini programs are applications that can be used directly without downloading and installing. They facilitate the acquisition and dissemination of applications and provide an excellent user experience.
[0153] like Figure 1k As shown, it shows the changes in the style attribute information of the target signature information in the business approval page when the system theme of the Web side (i.e., the page display mode in the above embodiment) is switched to dark mode; specifically, when the system theme is switched to dark mode, the signature is automatically displayed in reverse color, the image background color changes from white to black, and the text color changes from black to white.
[0154] like Figure 1l As shown, it shows the changes in the style attribute information of the target signature information in the business approval page when the system theme corresponding to the mini program (i.e., the page display mode in the above embodiment) is switched to dark mode; specifically, when the system theme is switched to dark mode, the signature is automatically displayed in reverse color, the image background color changes from white to black, and the text color changes from black to white.
[0155] Among them, the dark mode, also known as the night display mode, can be provided by the operating system or by application software. It can be used at night or in dim ambient light to provide users with a better screen reading experience.
[0156] The present application provides a general signature processing solution that supports both web and mini-programs. Specifically, the present application provides a signature reuse method that can reuse signatures across platforms. It can achieve the ability to sign on one platform and directly reuse it when signing on this platform and other platforms subsequently. This can greatly reduce the amount of signatures for approvers.
[0157] Among them, cross-platform specifically means that a software can run on multiple different operating systems.
[0158] The business approval method based on signature reuse provided by this application can adapt to different page display modes, so that the approval signature page has high readability in both light and dark mode themes. Specifically, when the device switches between different page display modes, the signature background and text color will change accordingly, which is conducive to improving the user reading experience.
[0159] In this embodiment, when displaying a signature, the currently running theme configuration (that is, the page display mode) can be obtained, and the signature information can be processed accordingly according to different theme configurations. Specifically, when storing the signature information, the current theme configuration can be ignored, and the signature information with black text on a white background is always saved. When displaying the signature information, it can be adapted according to the theme. If it is a light theme, the signature image with black text on a white background is directly displayed. If it is a dark theme, a filter is added to the signature image to invert the color and display it as white text on a black background. A filter is a process that applies a graphics algorithm to transform an image and then obtains a new image rendering effect. The signature image is black text on a white background, and it needs to be displayed as white text on a black background in dark mode. Therefore, by applying an inverted filter to the image, only the display effect on the device can be changed without changing the original image data.
[0160] As can be seen from the above, in this embodiment, a first business approval message can be received through a first client; when a viewing operation of the target approval object on the first business approval message is detected, and the target approval object has configured signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the first business approval message and the target signature information for the approval content, the target signature information is obtained by synchronizing the signature information configured for signature reuse in the second client, and the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; in response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message. This application can provide a signature reuse method, after the user has set signature reuse on a certain application platform (that is, the second client), the previous signature information can be directly displayed when performing business approval on another application platform (that is, the first client), without the need to sign again; this application can realize cross-platform reuse signatures in the business approval process, avoid the situation where the target approval object needs to sign repeatedly, reduce the signature amount of the target approval object, and thus improve the business approval efficiency.
[0161] This embodiment will be described from the perspective of a service approval device based on signature multiplexing. The service approval device based on signature multiplexing may be integrated in a second electronic device, which may be a terminal or other device.
[0162] like Figure 2a As shown, the specific process of the business approval method based on signature reuse is as follows:
[0163] 201. Receive a second service approval message through a second client.
[0164] The second client may be a client of a message interaction application, and the type of the message interaction application may include an instant messaging application, a live broadcast application, etc. The second client may be an application client or a browser client, etc., which is not limited in this embodiment.
[0165] Specifically, the second client may be a client on the second terminal, which may be a mobile phone, a tablet computer, a laptop computer, or other devices.
[0166] The second business approval message may be a pending approval message sent by the approved object to the target approval object, which may include approval content that needs to be reviewed by the target approval object. Specifically, the approved object and the target approval object may be organizational members in the same application message system; the target approval object may be the superior of the approved object.
[0167] 202. When it is detected that the target approval object has performed a viewing operation on the second business approval message and the target approval object has not been configured with signature reuse, a business approval page is displayed, and the business approval page includes approval content corresponding to the second business approval message.
[0168] The viewing operation on the second business approval message may specifically be a click operation on the second business approval message.
[0169] In some embodiments, if it is detected that the configuration information of the target approval object does not include signature reuse mark information, it can be determined that the target approval object has not been configured with signature reuse. The signature reuse mark information can indicate that the target approval object has been configured with signature reuse.
[0170] 203. In response to the signing operation on the approval content, signature information is obtained.
[0171] Specifically, in this embodiment, signing the approval content indicates approval of the approval content.
[0172] Optionally, in this embodiment, the business approval page further includes a signature control; the step of “obtaining signature information in response to a signature operation on the approval content” may include:
[0173] In response to a triggering operation on the signature control, displaying a signature area on the business approval page;
[0174] In response to a signature editing operation on the signature area, signature information for the approval content is acquired.
[0175] The triggering operation on the signature control may specifically be a click operation on the signature control, etc. The signature editing operation on the signature area may specifically be a handwritten signature on a canvas corresponding to the signature area.
[0176] For Web clients, you can use the canvas element provided by HTML5 (HyperText Markup Language) as the basis for the drawing board, and then implement the signature drawing algorithm yourself; for mini-program clients, you can use the canvas API (Application Program Interface) provided by the mini-program as the basis for the drawing board, and implement the signature drawing algorithm yourself. In order to ensure the cross-platform availability of signatures, the signature algorithms of the two platforms are basically the same, refer to Figure 2b , the description process is as follows:
[0177] A signature process is described as the drawing of multiple lines. The drawing of each line starts when the pointer is pressed. The movement of the pointer indicates that the drawing is in progress, and the release of the pointer indicates the end of the drawing of a line. When the user clicks Clear, it means that the entire canvas needs to be cleared and redrawn. When the entire signature is completed, the signature information is composed of all the lines drawn during the entire process.
[0178] Specifically, the drawing process may include:
[0179] 1) Initialize the canvas: According to the current application platform and the hardware information of the device, such as resolution, screen size, etc., initialize the parameters required for the signature, including: canvas size, line color, line width, minimum stroke radius, maximum stroke radius, brush pressure, brush smoothness, etc.;
[0180] 2) Pointer press event: This event indicates the start of drawing a line. On the Web platform, it refers to the mouse press event, and in the applet, it refers to the touch start event. When this event occurs, set the brush color and translucency, and record the current point as the starting point of the line;
[0181] 3) Pointer move event: This event indicates that a line is being drawn. On the Web platform, it refers to the mouse move event, and in the mini-program, it refers to the touch move event. This event will be triggered continuously, and each time it is triggered, the point where the event occurs is recorded as the middle point of the line. Based on the point information and the information of the previously recorded points, as well as the smoothing parameters set during initialization, all points from the starting point to this point are connected and drawn on the canvas.
[0182] 4) Pointer release event: This event indicates the completion of drawing a line. On the Web platform, it refers to the mouse release event, and in the mini-program, it refers to the touch end event. Record this point as the end point. Then determine whether the drawing is valid. The judgment basis can be: whether there are 10 valid points after deleting the points that exceed the canvas area. If not, delete the line drawn this time. If so, keep the line.
[0183] 204. In response to the signature reuse operation on the signature information, the signature information is stored, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms.
[0184] The first client may be a client of a message interaction application, an application client or a browser client, etc., which is not limited in this embodiment.
[0185] The first client and the second client are different application platforms. In some embodiments, the first client and the second client may be clients of the same application on different versions. In other embodiments, the first client and the second client may be clients of different applications, such as the first client is a client of a first message application, and the second client is a client of a second message application, and the first message application and the second message application may be heterogeneous applications.
[0186] Specifically, the first client may be a client on the first terminal. The first terminal may be a device such as a mobile phone, a tablet computer, or a laptop computer. The first terminal and the second terminal may refer to the same terminal or different terminals. In other words, the first client and the second client may be on the same terminal device or on different terminal devices, which is not limited in this embodiment.
[0187] In some embodiments, the first client and the second client are clients of the same application on different versions, where the version may refer to a software system version, etc. Specifically, the first client and the second client are clients of the same application on different operating systems, where the version corresponds to the operating system. The operating system here may include a desktop operating system (such as Windows), a mobile device operating system (such as Android), etc.
[0188] Optionally, in this embodiment, the step of “storing the signature information in response to a signature reuse operation on the signature information, so as to synchronize the stored signature information to the first client for signature reuse when the target approval object performs business approval through the first client” may include:
[0189] In response to a signature reuse operation on the signature information, the signature information is synchronized to a second application server for storage, and then the signature information in the second application server is synchronized to the first application server, so that when the target approval object performs business approval through the first client, the signature information is synchronized from the first application server to the first client for signature reuse.
[0190] The business approval page may include a signature reuse control. The signature reuse operation on the signature information is specifically a trigger operation on the signature reuse control, and the trigger operation may be a click operation or the like.
[0191] The first application server may be a server corresponding to the first client, and the second application server may be a server corresponding to the second client. In this embodiment, the signature information is saved to the server, thus avoiding the problem of cache being cleared locally.
[0192] It should be noted that if the first client and the second client are clients of the same application in different versions, the first application server and the second application server may be the same server, that is, the first client and the second client access the same server (referred to as the target application server). In this scenario, the signature information may be synchronized to the target application server for storage, so that when the target approval object performs business approval through the first client in a future time period, the signature information may be synchronized from the target application server to the first client for reuse.
[0193] Specifically, after the signature information is stored, signature reuse mark information can also be added to the configuration information of the target approval object, so that when the target approval object performs business approval in the first client, based on the signature reuse mark information, it is determined that the target approval object has configured signature reuse, so that the already drawn signature information is directly displayed, and the user does not need to re-sign, thereby improving the approval efficiency. In addition, the signature information can also be adapted to the page display mode of the first client.
[0194] It should be noted that the signature information that is processed for signature reuse selection in the second client can also be used in the subsequent approval signature of the second client itself; specifically, when it is subsequently detected that the target approval object has performed a viewing operation on the business approval message in the second client, the already drawn signature information can be directly displayed on the business approval page, without the need for the user to sign again.
[0195] Regarding the storage of signature information, the signature information can be exported to the format of an image for storage, or it can be saved directly as raw data without exporting the image. The data can be used to draw the signature information each time it needs to be displayed, and it can be adapted according to the platform, hardware, theme, etc. This method of drawing using raw data can better adapt to themes and cross-platforms, and the drawing algorithm can be directly upgraded later to improve the signature display effect.
[0196] In a specific embodiment, after the handwritten signature is completed, the API of the canvas of each platform can be used to export the signature information as an image, and the image can be uploaded to the server, and the object identifier of the current user can be used as the association basis to save the image as the user's configuration, such as Figure 2c The specific description is as follows:
[0197] 1) Each application platform can export the canvas containing the signature information into a unified image format and upload it to the server for storage, obtaining an image address (i.e., the signature storage address information in the above embodiment), and use the image address to obtain the signature information when the signature is reused later. The image format needs to ensure that it can be used across platforms and is forward and backward compatible. If there are modifications after the subsequent software upgrade, the old version that has been released can also be displayed normally;
[0198] 2) Generate personal configuration information for the user, which contains the image address of the signature information and whether to reuse the signature. The configuration information can be associated with the current user's unique identifier, isolated from other people's information, and ensure that the same user can obtain it on different application platforms and different devices.
[0199] Specifically, the user configuration can be saved according to whether to choose to save the signature for next use. If yes, the user configuration is saved, wherein the signature address is recorded and the signature reuse is marked as needing reuse; if no, the user configuration is saved, wherein the signature address is recorded and the signature reuse is marked as not needing reuse.
[0200] 205. In response to the approval operation on the approval content, the approval result of the approval content and the signature information are sent to the approved object corresponding to the second business approval message.
[0201] In a specific scenario, when a signature is required for approval, the user configuration is pulled from the server. If a signature is found and the signature is configured to be reusable, the previously saved signature is displayed. No new signature is required this time and it can be approved directly. Figure 2d The specific process is as follows:
[0202] When the target approval object opens the document to be approved, the user's unique ID is used to obtain the target approval object's personal configuration from the server, and whether there is a saved personal signature in the configuration. If not, it enters the waiting for signature state. If yes, it detects whether the signature is marked as reusable in the configuration. If not, it enters the waiting for signature state. If the signature is marked as reusable in the configuration, the image address is used to pull the signature information. If the signature image is not pulled successfully, it enters the waiting for signature state; when the signature image is pulled successfully, the signature information corresponding to the signature image is displayed. If it is detected that the user chooses to re-sign, it enters the signing process; otherwise, approval is performed based on the signature information.
[0203] The saved configuration is obtained by using the user's unique identifier to ensure that information saved by other users is not obtained, and that the obtained configuration is irrelevant to the current device and the currently used software version.
[0204] This application provides a cross-platform adaptive technical solution for the approver's signature in the approval process, which can enable users to obtain a consistent interactive experience on multiple terminals of the target application, reducing the user's learning cost. In addition, the signature data can be used across platforms to achieve cross-terminal and cross-device signature reuse, avoiding multiple repeated signatures and reducing the complexity of user use; and the signature can be adapted on different platforms to ensure that the display effect meets user expectations. Among them, the signature information can be saved in a universal image format, which can ensure normal use across platforms and software versions, improve the stability of the software, and solve the burden of software upgrades.
[0205] As can be seen from the above, in this embodiment, a second business approval message can be received through a second client; when a viewing operation of the target approval object on the second business approval message is detected, and the target approval object has not been configured with signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the second business approval message; in response to a signature operation on the approval content, signature information is obtained; in response to a signature reuse operation on the signature information, the signature information is stored, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms; in response to an approval operation on the approval content, the approval result of the approval content and the signature information are sent to the approved object corresponding to the second business approval message.
[0206] The present application can provide a method of signature reuse. After the user has set up signature reuse on a certain application platform (i.e., the second client), the previous signature information can be directly displayed when performing business approval on another application platform (i.e., the first client) without the need to sign again. The present application can realize cross-platform signature reuse during the business approval process, avoiding the situation where the target approval object needs to sign repeatedly multiple times, reducing the number of signatures for the target approval object, and thus improving business approval efficiency.
[0207] In order to better implement the above method, the embodiment of the present application also provides a business approval system based on signature multiplexing. The business approval system based on signature multiplexing includes a business approval device 31 based on signature multiplexing and a business approval device 32 based on signature multiplexing. Figure 3a As shown, the business approval device 31 based on signature reuse may include a first receiving unit 3101, a first display unit 3102, and a first sending unit 3103; Figure 3b As shown, the business approval device 32 based on signature reuse may include a second receiving unit 3201, a second display unit 3202, an acquisition unit 3203, a storage unit 3204 and a second sending unit 3205, as follows:
[0208] A. Business approval device based on signature reuse 31
[0209] (1) a first receiving unit 3101;
[0210] The first receiving unit is used to receive a first service approval message through a first client.
[0211] (2) first display unit 3102;
[0212] The first display unit is used to display a business approval page when it is detected that the target approval object has performed a viewing operation on the first business approval message and the target approval object has configured signature reuse. The business approval page includes approval content corresponding to the first business approval message and target signature information for the approval content, the target signature information is obtained by synchronizing signature information configured for signature reuse in the second client, and the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms.
[0213] Optionally, in some embodiments of the present application, the style attribute information of the target signature information is determined based on the page display mode of the business approval page.
[0214] Optionally, in some embodiments of the present application, the target signature information is obtained from the first application server according to the object identifier of the target approval object, and the first application server stores the signature information of the target approval object configured for signature reuse in the second client. The signature information is synchronized from the second client to the second application server when the target approval object performs a signature reuse operation through the second client, and then synchronized from the second application server to the first application server.
[0215] Optionally, in some embodiments of the present application, the business approval page further includes a re-signature control;
[0216] The service approval device based on signature reuse may also include a clearing unit and a re-signing unit, as follows:
[0217] The clearing unit is used to clear the target signature information in the business approval page in response to a triggering operation on the re-signing control;
[0218] The re-signing unit is used to display new target signature information on the business approval page in response to the re-signing operation on the approval content.
[0219] Optionally, in some embodiments of the present application, the service approval device based on signature multiplexing may further include a signature multiplexing unit as follows:
[0220] The signature multiplexing unit is used to store the new target signature information in response to a signature multiplexing operation on the new target signature information, so as to synchronize the stored new target signature information to the third client for signature multiplexing when the target approval object performs business approval through the third client. The third client and the first client are different application platforms.
[0221] Optionally, in some embodiments of the present application, the service approval device based on signature multiplexing may further include a mode switching unit as follows:
[0222] The mode switching unit is used to switch the display of the business approval page in the target page display mode in response to a switching operation on the page display mode of the business approval page, and synchronously switch the display of the target signature information under the target style attribute information, wherein the target style attribute information is determined based on the target page display mode.
[0223] Optionally, in some embodiments of the present application, the first display unit may include a first detection subunit, a second detection subunit, a signature acquisition subunit and a page display subunit, as follows:
[0224] The first detection subunit is configured to detect whether the configuration information of the target approval object includes signature information according to the object identifier of the target approval object when detecting the viewing operation of the target approval object on the first business approval message;
[0225] A second detection subunit is used to detect whether the configuration information includes signature reuse mark information when it is detected that the configuration information of the target approval object includes signature information;
[0226] A signature acquisition subunit, configured to acquire target signature information according to an object identifier of a target approval object when signature reuse mark information in the configuration information is detected;
[0227] The page display subunit is used to display the business approval page according to the target signature information.
[0228] (3) a first sending unit 3103;
[0229] The first sending unit is configured to send the approval result of the approval content and the target signature information to the approved object corresponding to the first business approval message in response to the approval operation on the approval content.
[0230] B. Business approval device based on signature reuse 32
[0231] (4) a second receiving unit 3201;
[0232] The second receiving unit is used to receive a second service approval message through a second client.
[0233] (5) second display unit 3202;
[0234] The second display unit is used to display a business approval page when it is detected that the target approval object has performed a viewing operation on the second business approval message and the target approval object has not configured signature reuse. The business approval page includes the approval content corresponding to the second business approval message.
[0235] (6) Acquisition unit 3203;
[0236] The acquiring unit is used to acquire signature information in response to a signature operation on the approval content.
[0237] Optionally, in some embodiments of the present application, the business approval page further includes a signature control; the acquisition unit may include a display subunit and an acquisition subunit, as follows:
[0238] The display subunit is used to display the signature area on the business approval page in response to a triggering operation on the signature control;
[0239] The acquisition subunit is used to acquire the signature information for the approval content in response to the signature editing operation on the signature area.
[0240] (7) storage unit 3204;
[0241] A storage unit is used to store the signature information in response to a signature reuse operation on the signature information, so as to synchronize the stored signature information to the first client for signature reuse when the target approval object performs business approval through the first client, and the first client and the second client are different application platforms.
[0242] Optionally, in some embodiments of the present application, the storage unit can be specifically used to synchronize the signature information to a second application server for storage in response to a signature reuse operation on the signature information, and then synchronize the signature information in the second application server to the first application server, so that when the target approval object performs business approval through the first client, the signature information is synchronized from the first application server to the first client for signature reuse.
[0243] (8) second sending unit 3205;
[0244] The second sending unit is configured to send the approval result of the approval content and the signature information to the approved object corresponding to the second business approval message in response to the approval operation on the approval content.
[0245] As can be seen from the above, in this embodiment, the first receiving unit 3101 can receive the first business approval message through the first client; when the first display unit 3102 detects that the target approval object has performed a viewing operation on the first business approval message and the target approval object has configured signature reuse, the business approval page is displayed, and the business approval page includes the approval content corresponding to the first business approval message and the target signature information for the approval content, the target signature information is obtained by synchronizing the signature information configured for signature reuse in the second client, and the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; in response to the approval operation on the approval content, the first sending unit 3103 sends the approval result of the approval content and the target signature information to the approved object corresponding to the first business approval message.
[0246] Alternatively, the second receiving unit 3201 receives the second business approval message through the second client; when it is detected that the target approval object has performed a viewing operation on the second business approval message and the target approval object has not been configured with signature reuse, the second display unit 3202 displays a business approval page, and the business approval page includes the approval content corresponding to the second business approval message; the acquisition unit 3203 obtains signature information in response to the signature operation on the approval content; the storage unit 3204 stores the signature information in response to the signature reuse operation on the signature information, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms; the second sending unit 3205 sends the approval result of the approval content and the signature information to the approved object corresponding to the second business approval message in response to the approval operation on the approval content.
[0247] The present application can provide a method of signature reuse. After the user has set up signature reuse on a certain application platform (i.e., the second client), the previous signature information can be directly displayed when performing business approval on another application platform (i.e., the first client) without the need to sign again. The present application can realize cross-platform signature reuse during the business approval process, avoiding the situation where the target approval object needs to sign repeatedly multiple times, reducing the number of signatures for the target approval object, and thus improving business approval efficiency.
[0248] The present application also provides an electronic device, such as Figure 4 As shown, it shows a schematic diagram of the structure of an electronic device involved in an embodiment of the present application, and the electronic device may be a terminal or a server, etc. Specifically:
[0249] The electronic device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will appreciate that Figure 4 The electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0250] The processor 401 is the control center of the electronic device, and uses various interfaces and lines to connect various parts of the entire electronic device. By running or executing software programs and / or modules stored in the memory 402, and calling data stored in the memory 402, the processor 401 performs various functions of the electronic device and processes data. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 401.
[0251] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.
[0252] The electronic device also includes a power supply 403 for supplying power to each component. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, so as to manage charging, discharging, power consumption and other functions through the power management system. The power supply 403 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.
[0253] The electronic device may further include an input unit 404, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
[0254] Although not shown, the electronic device may further include a display unit, etc., which will not be described in detail herein. Specifically in this embodiment, the processor 401 in the electronic device will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby realizing various functions, as follows:
[0255] A first business approval message is received through a first client; when a viewing operation of the first business approval message by a target approval object is detected, and the target approval object has been configured with signature reuse, a business approval page is displayed, the business approval page including approval content corresponding to the first business approval message and target signature information for the approval content, the target signature information is obtained by synchronizing signature information configured with signature reuse in a second client, the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; in response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
[0256] Alternatively, a second business approval message is received through a second client; when a viewing operation of the target approval object on the second business approval message is detected and the target approval object has not been configured with signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the second business approval message; in response to a signature operation on the approval content, signature information is obtained; in response to a signature reuse operation on the signature information, the signature information is stored, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms; in response to an approval operation on the approval content, the approval result of the approval content and the signature information are sent to the approved object corresponding to the second business approval message.
[0257] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0258] As can be seen from the above, in this embodiment, a first business approval message can be received through a first client; when a viewing operation of the target approval object on the first business approval message is detected, and the target approval object has been configured with signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the first business approval message and the target signature information for the approval content, the target signature information is obtained by synchronizing the signature information configured with signature reuse in the second client, and the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; in response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
[0259] Alternatively, a second business approval message is received through a second client; when a viewing operation of the target approval object on the second business approval message is detected and the target approval object has not been configured with signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the second business approval message; in response to a signature operation on the approval content, signature information is obtained; in response to a signature reuse operation on the signature information, the signature information is stored, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms; in response to an approval operation on the approval content, the approval result of the approval content and the signature information are sent to the approved object corresponding to the second business approval message.
[0260] The present application can provide a method of signature reuse. After the user has set up signature reuse on a certain application platform (i.e., the second client), the previous signature information can be directly displayed when performing business approval on another application platform (i.e., the first client) without the need to sign again. The present application can realize cross-platform signature reuse during the business approval process, avoiding the situation where the target approval object needs to sign repeatedly multiple times, reducing the number of signatures for the target approval object, and thus improving business approval efficiency.
[0261] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0262] To this end, an embodiment of the present application provides a computer-readable storage medium, which stores multiple instructions, which can be loaded by a processor to execute the steps in any one of the signature-based multiplexing business approval methods provided in the embodiment of the present application. For example, the instructions can execute the following steps:
[0263] A first business approval message is received through a first client; when a viewing operation of the first business approval message by a target approval object is detected, and the target approval object has been configured with signature reuse, a business approval page is displayed, the business approval page including approval content corresponding to the first business approval message and target signature information for the approval content, the target signature information is obtained by synchronizing signature information configured with signature reuse in a second client, the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; in response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
[0264] Alternatively, a second business approval message is received through a second client; when a viewing operation of the target approval object on the second business approval message is detected and the target approval object has not been configured with signature reuse, a business approval page is displayed, and the business approval page includes the approval content corresponding to the second business approval message; in response to a signature operation on the approval content, signature information is obtained; in response to a signature reuse operation on the signature information, the signature information is stored, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms; in response to an approval operation on the approval content, the approval result of the approval content and the signature information are sent to the approved object corresponding to the second business approval message.
[0265] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0266] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0267] Since the instructions stored in the computer-readable storage medium can execute the steps in any one of the business approval methods based on signature multiplexing provided in the embodiments of the present application, the beneficial effects that can be achieved by any one of the business approval methods based on signature multiplexing provided in the embodiments of the present application can be achieved. For details, please refer to the previous embodiments and will not be repeated here.
[0268] According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in various optional implementations of the above-mentioned business approval based on signature reuse.
[0269] The above is a detailed introduction to a business approval method based on signature multiplexing and related equipment provided in an embodiment of the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A business approval method based on signature reuse, characterized in that: include: Receiving a first business approval message through a first client; When it is detected that the target approval object has performed a viewing operation on the first business approval message, and the target approval object has configured signature reuse, a business approval page is displayed, the business approval page includes the approval content corresponding to the first business approval message and the target signature information for the approval content, the target signature information is obtained by synchronizing the signature information configured for signature reuse in the second client, the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; In response to the approval operation on the approval content, the approval result of the approval content and the target signature information are sent to the approved object corresponding to the first business approval message.
2. The method according to claim 1, characterized in that The style attribute information of the target signature information is determined based on the page display mode of the business approval page.
3. The method according to claim 1, characterized in that The target signature information is obtained from the first application server according to the object identifier of the target approval object. The first application server stores the signature information of the target approval object configured for signature reuse in the second client. The signature information is synchronized from the second client to the second application server when the target approval object performs a signature reuse operation through the second client, and then synchronized from the second application server to the first application server.
4. The method according to claim 1, characterized in that: The business approval page also includes a re-signature control; Before sending the approval result of the approval content and the target signature information to the approved object corresponding to the first business approval message in response to the approval operation of the approval content, the method further includes: In response to a triggering operation on the re-signing control, clearing target signature information in the business approval page; In response to the re-signing operation on the approval content, new target signature information is displayed on the business approval page.
5. The method according to claim 4, characterized in that The method further comprises: In response to a signature reuse operation on the new target signature information, the new target signature information is stored so that when the target approval object performs business approval through a third client, the stored new target signature information is synchronized to the third client for signature reuse. The third client and the first client are different application platforms.
6. The method according to claim 1, characterized in that The method further comprises: In response to the switching operation of the page display mode of the business approval page, the business approval page in the target page display mode is switched to be displayed, and the target signature information under the target style attribute information is switched to be displayed synchronously, and the target style attribute information is determined based on the target page display mode.
7. The method according to claim 1, characterized in that When it is detected that the target approval object has performed a viewing operation on the first business approval message and the target approval object has configured signature reuse, displaying a business approval page includes: When a viewing operation of the target approval object on the first business approval message is detected, detecting whether the configuration information of the target approval object includes signature information according to the object identifier of the target approval object; When it is detected that the configuration information of the target approval object includes signature information, detecting whether the configuration information includes signature reuse mark information; When the signature reuse mark information in the configuration information is detected, the target signature information is obtained according to the object identifier of the target approval object; According to the target signature information, the business approval page is displayed.
8. A business approval method based on signature reuse, characterized in that: include: Receiving a second service approval message through a second client; When a viewing operation of the target approval object on the second business approval message is detected, and the target approval object has not been configured with signature reuse, a business approval page is displayed, and the business approval page includes approval content corresponding to the second business approval message; In response to a signature operation on the approval content, acquiring signature information; In response to a signature reuse operation on the signature information, the signature information is stored, so that when the target approval object performs business approval through the first client, the stored signature information is synchronized to the first client for signature reuse, and the first client and the second client are different application platforms; In response to the approval operation on the approval content, the approval result of the approval content and the signature information are sent to the approved object corresponding to the second business approval message.
9. The method according to claim 8, characterized in that The step of storing the signature information in response to the signature reuse operation on the signature information, so as to synchronize the stored signature information to the first client for signature reuse when the target approval object performs business approval through the first client, includes: In response to a signature reuse operation on the signature information, the signature information is synchronized to a second application server for storage, and then the signature information in the second application server is synchronized to the first application server, so that when the target approval object performs business approval through the first client, the signature information is synchronized from the first application server to the first client for signature reuse.
10. The method according to claim 8, characterized in that The business approval page also includes a signature control; the step of obtaining signature information in response to the signature operation on the approval content includes: In response to a triggering operation on the signature control, displaying a signature area on the business approval page; In response to a signature editing operation on the signature area, signature information for the approval content is acquired.
11. A business approval device based on signature multiplexing, characterized in that: include: A first receiving unit, configured to receive a first service approval message through a first client; A first display unit is used to display a business approval page when a viewing operation of the first business approval message by a target approval object is detected, and the target approval object has configured signature reuse, wherein the business approval page includes approval content corresponding to the first business approval message and target signature information for the approval content, wherein the target signature information is obtained by synchronizing signature information configured for signature reuse in a second client, and the signature information is generated when the target approval object performs business approval signature through the second client, and the first client and the second client are different application platforms; The first sending unit is configured to send the approval result of the approval content and the target signature information to the approved object corresponding to the first business approval message in response to the approval operation on the approval content.
12. A business approval device based on signature multiplexing, characterized in that: include: A second receiving unit, configured to receive a second service approval message through a second client; A second display unit is used to display a business approval page when a viewing operation of the target approval object on the second business approval message is detected, and the target approval object has not been configured with signature reuse, and the business approval page includes the approval content corresponding to the second business approval message; An acquisition unit, configured to acquire signature information in response to a signature operation on the approval content; a storage unit, configured to store the signature information in response to a signature reuse operation on the signature information, so as to synchronize the stored signature information to the first client for signature reuse when the target approval object performs business approval through the first client, wherein the first client and the second client are different application platforms; The second sending unit is configured to send the approval result of the approval content and the signature information to the approved object corresponding to the second business approval message in response to the approval operation on the approval content.
13. An electronic device, characterized in that: It includes a memory and a processor; the memory stores an application, and the processor is used to run the application in the memory to perform the operations in the business approval method based on signature multiplexing described in any one of claims 1 to 7 or the business approval method based on signature multiplexing described in any one of claims 8 to 10.
14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, which are suitable for being loaded by a processor to execute the steps in the business approval method based on signature multiplexing described in any one of claims 1 to 7 or the business approval method based on signature multiplexing described in any one of claims 8 to 10.
15. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps in the business approval method based on signature multiplexing described in any one of claims 1 to 7 or the business approval method based on signature multiplexing described in any one of claims 8 to 10 are implemented.