Data processing method and device, equipment and medium

Abstract

The invention discloses a data processing method and device, equipment and a medium, and the method comprises the steps: obtaining a first business starting and ending time sent by a client, calculating a first business duration through the first business starting and ending time, and returning the first business duration to the client; when the business starting and ending time in the to-be-submitted business document is changed from the first business starting and ending time to the second business starting and ending time and the business duration on the to-be-submitted business document is kept as the first business duration, acquiring the second business starting and ending time and the first business duration sent by the client; and calculating to obtain a second service duration according to the starting and ending time of the second service, comparing the second service duration with the first service duration, and returning the second service duration to the client when the second service duration is inconsistent with the first service duration, so that the client updates and displays the service duration on the to-be-submitted service document from the first service duration to the second service duration. By adopting the method and the device, the consistency of service durations can be ensured when the service receipts are submitted.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, device, equipment and medium. Background Art

[0002] With the continuous development of Internet technology, electronic approval has gradually replaced traditional paper approval. In the electronic approval scenario, the business request object (for example, user A) can send the electronic business document to the business approval object (for example, user B) for approval through the corresponding client (for example, instant messaging client), thereby realizing the electronic business approval of entities such as enterprises, institutions, and organizations.

[0003] The inventor has found in practice that before a business request object (e.g., user A) submits a business document, the corresponding business duration will be automatically calculated through the front-end and back-end interactions. However, for the back-end, a certain calculation duration is required to calculate the above-mentioned business duration (e.g., 1 hour). If user A manually corrects the business start and end time corresponding to the business duration (e.g., 1 hour) on the aforementioned business document and submits the document quickly, the back-end will trigger a new round of duration calculation based on the manually corrected business start and end time, and then recalculate the new business duration (e.g., 2 hours) within the new calculation duration. It can be seen from this that within the new calculation duration, it is difficult for the back-end to quickly feed back the recalculated new business duration (e.g., 2 hours) to the front-end, so that there is a phenomenon that the business duration (e.g., 1 hour) on the business document displayed by the front-end is inconsistent with the new business duration recalculated by the back-end. Summary of the invention

[0004] The embodiments of the present application provide a data processing method, apparatus, device and medium, which can ensure the consistency of service duration when submitting service documents.

[0005] On the one hand, an embodiment of the present application provides a data processing method, which is executed by a client and includes:

[0006] When the first service start and end time is displayed in the service document to be submitted, the first service duration returned by the service server for the first service start and end time is received, and the service duration on the service document to be submitted is configured as the first service duration;

[0007] When the service start and end time in the service document to be submitted is changed from the first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains the first service duration, in response to the document submission operation for the service document to be submitted, the second service start and end time and the first service duration are sent to the service server, so that when the service server calculates the second service duration corresponding to the second service start and end time, the second service duration is compared with the first service duration, and when the duration comparison is inconsistent, the second service duration is returned to the client;

[0008] When the second service duration returned by the service server is received, the service duration on the service document to be submitted is updated from the first service duration to the second service duration.

[0009] An embodiment of the present application provides a data processing method, which is executed by a service server and includes:

[0010] When the first service start and end time is displayed in the service document to be submitted, the first service start and end time sent by the client is obtained, the first service duration is calculated according to the first service start and end time, and the first service duration is returned to the client, so that when the client receives the first service duration, the service duration on the service document to be submitted is configured as the first service duration;

[0011] When the service start and end time in the service document to be submitted is changed from the first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains the first service duration, the second service start and end time and the first service duration sent by the client are obtained; the second service start and end time and the first service duration are sent when the client responds to the document submission operation for the service document to be submitted;

[0012] The second business duration is calculated by the start and end time of the second business, and the second business duration is compared with the first business duration. When the duration comparison is inconsistent, the second business duration is returned to the client, so that when the client receives the second business duration, the business duration on the business document to be submitted is updated from the first business duration to the second business duration.

[0013] An embodiment of the present application provides a data processing device, including:

[0014] A duration configuration module, for receiving the first service duration returned by the service server for the first service start and end time when the first service start and end time is displayed in the service document to be submitted, and configuring the service duration on the service document to be submitted as the first service duration;

[0015] A document submission module, for, when the business start and end time in the business document to be submitted is changed from the first business start and end time to the second business start and end time, and the business duration on the business document to be submitted remains the first business duration, in response to a document submission operation for the business document to be submitted, sending the second business start and end time and the first business duration to a business server, so that when the business server calculates the second business duration corresponding to the second business start and end time, it compares the second business duration with the first business duration, and when the duration comparison is inconsistent, returns the second business duration to the client;

[0016] The duration updating module is used to update the service duration on the service document to be submitted from the first service duration to the second service duration when receiving the second service duration returned by the service server.

[0017] The duration configuration module includes:

[0018] A first editing unit is used to display the first service start and end time in the service document to be submitted on the document display interface in response to the first time editing operation on the service document to be submitted, and send the first service start and end time to the service server, so that the service server returns the first service duration to the client when calculating the first service start and end time corresponding to the first service start and end time;

[0019] The duration configuration unit is used to configure the service duration on the service document to be submitted as the first service duration when receiving the first service duration returned by the service server, and display the first service duration on the document display interface.

[0020] The document display interface is determined by the business document template corresponding to the business document to be submitted;

[0021] The first editing unit includes:

[0022] A configuration display subunit is used to configure the business start and end time in the business document to be submitted as the first business start and end time on the document display interface in response to the first time editing operation on the business document to be submitted, and display the first business start and end time in the business document to be submitted;

[0023] The data sending sub-unit is used to obtain the template identifier of the business document template, and send the template identifier and the first business start and end time to the mini-program end used for document processing, so that the mini-program end sends a first business request to the business server based on the template identifier and the first business start and end time; the first business request is used to instruct the business server to calculate the first business duration based on the template data information and the first business start and end time when obtaining the template data information corresponding to the business document template from the business database through the template identifier, and return the first business duration to the client through the mini-program end.

[0024] The document submission module includes:

[0025] A second editing unit is used to change the business start and end time in the business document to be submitted from the first business start and end time to the second business start and end time on the document display interface in response to a second time editing operation on the business document to be submitted;

[0026] A document submission unit is used to send the template identifier of the business document template, the second business start and end time, and the first business duration to the mini-program end in response to the document submission operation for the business document to be submitted when the business duration on the business document to be submitted remains at the first business duration, so that the mini-program end sends a second business request to the business server based on the template identifier, the second business start and end time, and the first business duration; the second business request is used to instruct the business server to calculate the second business duration based on the template data information and the second business start and end time when obtaining the template data information corresponding to the business document template from the business database through the template identifier, compare the second business duration with the first business duration, and when the duration comparison is inconsistent, return the second business duration to the client through the mini-program end.

[0027] An embodiment of the present application provides a data processing device, including:

[0028] The duration calculation module is used to obtain the first service start and end time sent by the client when the first service start and end time is displayed in the service document to be submitted, calculate the first service duration by the first service start and end time, and return the first service duration to the client, so that the client configures the service duration on the service document to be submitted as the first service duration when receiving the first service duration;

[0029] The document acquisition module is used to acquire the second business start and end time and the first business duration sent by the client when the business start and end time in the business document to be submitted is changed from the first business start and end time to the second business start and end time, and the business duration on the business document to be submitted remains the first business duration; the second business start and end time and the first business duration are sent by the client when responding to the document submission operation for the business document to be submitted;

[0030] The duration comparison module is used to calculate the second business duration through the start and end time of the second business, compare the second business duration with the first business duration, and when the duration comparison is inconsistent, return the second business duration to the client, so that when the client receives the second business duration, it will update the business duration on the business document to be submitted from the first business duration to the second business duration.

[0031] The duration calculation module includes:

[0032] A first acquisition unit is used to acquire a first business request sent by a mini program end for document processing; the mini program end is called by a client when a first business start and end time is displayed in a business document to be submitted; the first business request is generated based on the first business start and end time when the mini program end receives the first business start and end time sent by the client; the first business request carries a template identifier of a business document template corresponding to the business document to be submitted;

[0033] A second acquisition unit, configured to acquire a template identifier from the first business request, and acquire template data information corresponding to the business document template from a business database according to the template identifier;

[0034] The first calculation unit is used to calculate the first service duration based on the template data information and the first service start and end time in the first service request, and return the first service duration to the mini program end, so that the mini program end returns the first service duration to the client.

[0035] Among them, the business server includes a service end and a logic end; the service end includes a duration calculation interface; the service end is used to receive the first business request sent by the mini-program end through the duration calculation interface, and transmit the first business request to the logic end; the logic end is used to obtain template data information corresponding to the business document template from the business database according to the template identifier carried in the first business request when receiving the first business request; the template data information includes business configuration parameters; the first business start and end time includes the first business start time and the first business end time;

[0036] The first computing unit comprises:

[0037] The duration calculation subunit is used to obtain the service configuration parameters in the template data information through the logic end, and perform duration calculation according to the service configuration parameters, the first service start time and the first service end time to obtain the first service duration;

[0038] The duration return subunit is used to return the first service duration to the server through the logic end, and the server generates the first service response information based on the first service duration, and returns the first service response information carrying the first service duration to the mini program end.

[0039] Among them, the business server includes the server side and the logic side; the server side includes the document submission interface;

[0040] The document acquisition module includes:

[0041] The request receiving unit is used to receive the second business request sent by the mini program end for document processing through the document submission interface by the server end, and transmit the second business request to the logic end; the mini program end is called when the client responds to the document submission operation for the business document to be submitted; the second business request is generated based on the second business start and end time and the first business duration when the mini program end receives the second business start and end time and the first business duration sent by the client;

[0042] The third acquisition unit is used to acquire, by the logic end, the start and end time of the second service and the duration of the first service from the received second service request.

[0043] The second business request carries a template identifier of a business document template corresponding to the business document to be submitted;

[0044] The duration comparison module includes:

[0045] A second calculation unit is used to obtain the template identifier from the second service request through the logic end, obtain the template data information corresponding to the service document template from the service database according to the template identifier, and calculate the second service duration based on the template data information and the second service start and end time in the second service request;

[0046] The duration comparison unit is used to compare the second service duration with the first service duration by the logic end, and when the duration comparison is inconsistent, return the second service duration to the server end;

[0047] The duration returning unit is used for the server to generate second service response information based on the second service duration, and return the second service response information carrying the second service duration to the mini program end, so that the mini program end returns the second service duration to the client end.

[0048] The template data information includes the service configuration parameters; the second service start and end time includes the second service start time and the second service end time;

[0049] The second calculation unit is specifically used to obtain the service configuration parameters in the template data information through the logic end, and calculate the duration according to the service configuration parameters, the second service start time and the second service end time to obtain the second service duration.

[0050] The above device further comprises:

[0051] The first prompt module is used to return the first prompt information to the client when the duration comparison is inconsistent.

[0052] The above device further comprises:

[0053] The second prompt module is used to return a second prompt message to the client when the duration comparison is consistent; the second prompt message is used to indicate that the business document to be submitted is submitted successfully.

[0054] The above device further comprises:

[0055] A parameter configuration module, configured to obtain a verification mark parameter associated with the business document to be submitted after comparing the second business duration with the first business duration, configure the parameter value of the verification mark parameter to a verified parameter value, and save the second business start and end time in the business document to be submitted; the verified parameter value is used to indicate that the business duration on the business document to be submitted has been verified;

[0056] The third prompt module is used to use the business document to be submitted after the updated duration as a duration update business document when the business duration on the business document to be submitted is updated from the first business duration to the second business duration; when the received business document is a duration update business document, the business start and end time in the duration update business document is compared with the saved second business start and end time, and when the time comparison is consistent, based on the verification mark parameter with the verified parameter value, a third prompt message is returned to the client; the third prompt message is used to indicate that the duration update business document is submitted successfully.

[0057] Among them, the business document template corresponding to the business document to be submitted includes any one of the leave document template, business trip document template, out-of-office document template and overtime document template; the template data information corresponding to the leave document template includes the first type of business configuration parameters; the first type of business configuration parameters include the leave type, the first time scale parameter and the first duration calculation parameter; the template data information corresponding to the business trip document template includes the second type of business configuration parameters; the second type of business configuration parameters include the second time scale parameter, the second duration calculation parameter and the first unit conversion parameter; the template data information corresponding to the out-of-office document template includes the third type of business configuration parameters; the third type of business configuration parameters include the third time scale parameter, the third duration calculation parameter and the second unit conversion parameter; the template data information corresponding to the overtime document template includes the fourth type of business configuration parameters; the fourth type of business configuration parameters include the fourth time scale parameter, the fourth duration calculation parameter and the third unit conversion parameter.

[0058] On the one hand, an embodiment of the present application provides a data processing system, which includes a client, a mini-program end, a server end, and a logic end;

[0059] The client is used to send the second business start and end time and the first business duration to the mini program end in response to a document submission operation for the business document to be submitted, when the business start and end time in the business document to be submitted is changed from the first business start and end time to the second business start and end time, and the business duration on the business document to be submitted is maintained as the first business duration corresponding to the first business start and end time; the first business duration is calculated by the logic end based on the first business start and end time;

[0060] The mini program end is used to send the received second service start and end time and the first service duration to the logic end through the server end;

[0061] The logic end is used to calculate the second service duration by using the start and end time of the second service, compare the second service duration with the first service duration, and when the durations are inconsistent, return the second service duration to the mini program end through the server end, so that the mini program end returns the second service duration to the client end;

[0062] The client is used to update the service duration on the service document to be submitted from the first service duration to the second service duration when receiving the second service duration.

[0063] An embodiment of the present application provides a computer device, including: a processor and a memory;

[0064] The processor is connected to the memory, wherein the memory is used to store a computer program. When the computer program is executed by the processor, the computer device executes the method provided in the embodiment of the present application.

[0065] On the one hand, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program is suitable for being loaded and executed by a processor so that a computer device having the processor executes the method provided by the embodiment of the present application.

[0066] In one aspect, the present application provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method provided in the present application.

[0067] In an embodiment of the present application, when the first service start and end time is displayed in the service document to be submitted, the service server can obtain the first service start and end time sent by the client, and then calculate the first service duration through the first service start and end time, and return the first service duration to the client, so that when the client receives the first service duration, it configures the service duration on the service document to be submitted as the first service duration; further, when the service start and end time in the service document to be submitted is changed from the aforementioned first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains as the first service duration , the second business start and end time and the first business duration sent by the client can be obtained; wherein, the second business start and end time and the first business duration here are sent when the client responds to the document submission operation for the business document to be submitted; further, the second business duration can be calculated by the second business start and end time, and then the second business duration can be compared with the first business duration, and when the duration comparison is inconsistent, the second business duration is returned to the client, so that when the client receives the second business duration, the business duration on the business document to be submitted is updated from the first business duration to the second business duration. It can be seen that the embodiment of the present application provides a solution for ensuring the consistency of duration calculation in the document submission scenario. The core of the solution is to perform a secondary check on the business duration on the business document to be submitted, that is, when a business document (such as the aforementioned business document to be submitted) is submitted through the front-end client, the back-end business server can recalculate the corresponding business duration based on the business start and end time (such as the aforementioned second business start and end time) input by the client, and then the business duration (such as the aforementioned second business duration) calculated by the business server at this time can be compared with the business duration (such as the aforementioned first business duration) input by the client, and when the duration comparison is inconsistent, the business duration (such as the aforementioned second business duration) calculated by the business server can be used as a benchmark to correct the business duration on the business document displayed by the aforementioned client, so that the consistency and accuracy of the business duration can be guaranteed when submitting the business document. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0069] Figure 1 This is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0070] Figure 2aIt is a schematic diagram of a data processing scenario provided by an embodiment of the present application;

[0071] Figure 2b This is a schematic diagram of a data processing scenario provided by an embodiment of the present application;

[0072] Figure 2c This is a schematic diagram of a data processing scenario provided by an embodiment of the present application;

[0073] Figure 3 This is a flow chart of a data processing method provided in an embodiment of the present application. Figure 1 ;

[0074] Figure 4 Schematic diagram 2 of a data processing method provided in an embodiment of the present application;

[0075] Figure 5 It is a schematic diagram of a leave document template provided in an embodiment of the present application;

[0076] Figure 6 It is a schematic diagram of a business trip document template provided in an embodiment of the present application;

[0077] Figure 7 It is a schematic diagram of an outbound document template provided in an embodiment of the present application;

[0078] Figure 8 It is a schematic diagram of an overtime document template provided in an embodiment of the present application;

[0079] Fig. 9 It is a schematic diagram of a venue reservation document template provided in an embodiment of the present application;

[0080] Fig.10 This is a flow chart of a data processing method provided in an embodiment of the present application. Figure 3 ;

[0081] Fig.11 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. Figure 1 ;

[0082] Fig.12 A second structural diagram of a data processing device provided in an embodiment of the present application;

[0083] Fig.13 is a structural schematic diagram of a computer device provided in an embodiment of the present application;

[0084] Fig.14 It is a schematic diagram of a data processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] 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 ordinary technicians in this field without creative work are within the scope of protection of this application.

[0086] See also Figure 1 , Figure 1 Schematic diagram of a network architecture provided by an embodiment of the present application. Figure 1 As shown, the network architecture may include a business server 100 and a terminal cluster, and the terminal cluster may include multiple terminal devices. The embodiment of the present application does not limit the number of terminal devices contained in the terminal cluster. For example, the terminal cluster may specifically include: terminal device 200a, terminal device 200b, terminal device 200c, ..., terminal device 200n, wherein there may be a communication connection between the terminal clusters, for example, there is a communication connection between terminal device 200a and terminal device 200b, and there is a communication connection between terminal device 200a and terminal device 200c. At the same time, any terminal device in the terminal cluster may have a communication connection with the business server 100, for example, there is a communication connection between terminal device 200a and business server 100. Among them, the above-mentioned communication connection does not limit the connection method, and can be directly or indirectly connected through a wired communication method, or directly or indirectly connected through a wireless communication method, or through other methods, and the present application does not limit it here.

[0087] The business server 100 may be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud database, cloud service, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and big data and artificial intelligence platform. The terminal device may be a smart phone, tablet computer, laptop computer, desktop computer, PDA, mobile internet device (MID), wearable device (such as smart watch, smart bracelet, etc.), smart computer, smart car, etc., which can process business documents. The terminal device and the business server may be directly or indirectly connected by wire or wireless means, and the embodiments of the present application are not limited here.

[0088] It should be understood that Figure 1 Each terminal device in the terminal cluster shown in the figure may be installed with a client. When the client runs in each terminal device, it can communicate with the above-mentioned Figure 1Data is exchanged between the business servers 100 shown. The client may be an instant messaging client, a social client, an entertainment client (e.g., a game client, a live broadcast client, a novel client), a multimedia client (e.g., a short video client, a music client), a shopping client, a tool client (e.g., a payment client, a document editing client), a car client, a smart home client, a browser, and other applications with document processing functions. The client may be an independent client or an embedded sub-client integrated in a client (e.g., an instant messaging client, a social client, etc.), which is not limited here. Among them, the document processing function refers to the function of the business request object submitting the business document to the business approval object for business approval. The business document here can be understood as the application voucher filled in by the business request object when requesting to participate in a certain business. The business here can include but is not limited to leave (i.e. vacation, such as annual leave, personal leave, sick leave, adjustment leave, marriage leave, etc.), business trips, going out (i.e. going out for business), overtime, shift transfer, dispatch, attendance card replacement, regularization, home office, venue (such as conference room, classroom, etc.) reservation, items (such as office equipment, signature, transportation, etc.) collection, reimbursement, application for activities (such as competitions, parties, team building, training, etc.), etc., which require approval; for different businesses, you can use Different business documents, such as leave application documents (such as annual leave application documents, personal leave application documents, sick leave application documents, vacation application documents, marriage leave application documents, etc.), business trip application documents, out-of-town application documents, overtime application documents, shift application documents, stationing application documents, attendance card replacement documents, regularization application documents, home office application documents, venue reservation application documents (such as conference room reservation application documents, classroom reservation application documents, etc.), item collection application documents (such as office equipment collection application documents, signature collection application documents, transportation collection application documents, etc.), reimbursement application documents, activity application documents (such as competition application documents, party application documents, team building application documents, training application documents, etc.), etc. In the electronic approval scenario, business documents are electronic documents (can be referred to as electronic documents), which are conducive to the circulation of business documents, thereby improving the efficiency of business approval. It can be understood that the business request object refers to a user with business approval needs in entity objects such as enterprises, institutions, and organizations. For example, in a vacation scenario, the business request object can specifically be a user who applies for vacation in enterprise A (for example, user A1); correspondingly, the business approval object refers to a user with business approval authority in entity objects such as enterprises, institutions, and organizations. For example, in a vacation scenario, the business approval object can specifically be the superior of user A1 in the aforementioned enterprise A (for example, user A2).Among them, the business approval object can be specified by the business management object (i.e., the user responsible for managing the business, for example, user A3) in the entity objects such as enterprises, institutions, and organizations when setting the approval process, and the number of business approval objects can be one or more. The number of business approval objects will not be limited here, and the specific approval method adopted will not be limited.

[0089] It should be noted that the terminal devices in the embodiments of the present application can be roughly divided into two terminal types according to their operating methods. For the sake of distinction, they can be referred to as the first terminal type and the second terminal type respectively. Among them, the terminal device with the first terminal type (also referred to as a desktop device or a desktop-oriented terminal device) refers to a terminal device that mainly uses interactive operations such as mouse clicks and keyboard input, and the client running on this type of terminal device can usually open multiple windows at the same time. Therefore, this type of terminal device has the characteristic of interacting with windows as the dimension. The terminal devices with the first terminal type may include laptops, desktop computers, smart computers, and some tablet computers (such as Microsoft's Surface Pro, which can be operated with an external keyboard and mouse), etc.; and the terminal devices with the second terminal type (also referred to as non-desktop devices) refer to terminal devices that mainly use interactive operations such as user hand clicks or slides, and the client running on this type of terminal device can usually only open one window. The terminal devices with the second terminal type may include smart phones, some tablet computers (such as Apple's iPad), mobile Internet devices, wearable devices (such as smart watches, smart bracelets, etc.), smart car-mounted devices, etc. It can be understood that, accordingly, the embodiments of the present application can also divide the clients installed and running on different terminal types into two client types, wherein the client type of the client installed and running on the terminal device having the first terminal type can be referred to as the first client type (i.e., a desktop-oriented client, such as a computer terminal), and the client type of the client installed and running on the terminal device having the second terminal type can be referred to as the second client type (such as a mobile phone terminal). It can be understood that for the two different client types of the same application, there may be certain differences in their interface layout and interaction methods. The method provided in the present application is applicable to all client types. Therefore, all embodiments of the present application do not limit the terminal type of the terminal device involved, and do not limit the client type of the client involved, and the differences in the interface layout and interaction methods of different client types will not be distinguished and described later.

[0090] Taking the client as an instant messaging client as an example, the business server 100 may include multiple servers such as a background server, a data processing server, a data storage server, etc. corresponding to the instant messaging client. Therefore, each terminal device can transmit data with the business server 100 through the instant messaging client. For example, each terminal device can submit the business document filled out by the corresponding business request object to the business server 100 for processing through the instant messaging client it runs, and when the document is submitted successfully, the business server 100 can send relevant approval notification messages to other terminal devices to notify the corresponding business approval object to approve the business document in time.

[0091] It should be noted that in the document submission scenario, some business documents will involve duration calculation when submitted. For ease of understanding, the terminal device 200a, the terminal device 200b and the business server 100 are used as examples for explanation. Assuming that a client B (such as an instant messaging client) with a document processing function is installed and running on the terminal device 200a, the business request object associated with the terminal device 200a (such as user 1) can fill in the corresponding business document C on the client B according to its own business approval requirements. When user 1 fills in the business start and end time D1 on the business document C, the client B will immediately send the business start and end time D1 to the business server 100; further, the business server 100 can automatically calculate the business duration E1 corresponding to the business start and end time D1, and can return the business duration E1 to the client B, and the client B will display the business duration E1 on the business document C. It can be understood that the business server automatically calculates the business duration and fills it into the business document, which can reduce the workload of the user to manually calculate and configure the business duration, thereby improving the efficiency of generating and submitting the business document. Optionally, user 1 can also manually modify the business duration calculated by the business server 100. It can be understood that after user 1 fills in the information required for the business document C, the document can be submitted. Specifically, the client B can send the business document C to the business server 100, and then the business server 100 sends the business document C to the client F (such as an instant messaging client) running on the terminal device 200b. Subsequently, the client F can display the business document C to the associated business approval object (such as user 2) for approval, and can notify user 1 through the business server 100 after the approval is completed (for example, an approval approval notification message can be sent to client B when the business approval is passed, or an approval rejection notification message can be sent to client B when the business approval is not passed), thereby realizing the general process of business approval.

[0092] It is understandable that in the above scenario, the business request object may manually modify the business start and end time. For example, when the aforementioned user 1 finds that the business start and end time D1 previously filled in is incorrect, the business start and end time can be re-filled, for example, the business start and end time D1 can be changed to the business start and end time D2. Similarly, the business server 100 will recalculate the business duration E2 corresponding to the business start and end time D2, and the business server 100 needs to consume a certain amount of calculation time to calculate the business duration. If the business server 100 has not successfully returned the calculated business duration E2 (such as network delays, complex calculations, poor system performance and other factors may cause the calculation of the business duration to be very time-consuming, for example, under normal circumstances, the calculation of the business duration takes within 200ms, but in some cases it may take more than 400ms), user 1 quickly submits the business document C through client B, which may cause the actual submitted business duration (i.e., business duration E1) to be inconsistent with the business duration (i.e., business duration E2) calculated by the business server 100.

[0093] Based on this, in response to the above-mentioned inconsistency in duration, the embodiment of the present application proposes a technical solution to ensure the consistency of duration calculation based on the scenario of too-fast submission of documents, which can ensure that the business duration when the business request object submits the business document is consistent with the business duration calculated by the business server. For ease of understanding and explanation, the embodiment of the present application can refer to the business documents to be submitted and the business documents that have not been successfully submitted as business documents to be submitted (such as the above-mentioned business document C). For ease of distinction, the business involved in the business document to be submitted can be referred to as the target business, which can include but is not limited to leave, business trips, going out, overtime, shift changes, assignments, attendance card replacement, regularization, home office, venue reservations, item collection, reimbursement, application for activities and other businesses, which are not limited here. It can be understood that the business documents to be submitted may be classified according to the target business involved, including but not limited to leave application documents, business trip application documents, out-of-town application documents, overtime application documents, shift transfer application documents, dispatch application documents, attendance card replacement documents, regularization application documents, home office application documents, venue reservation application documents, item collection application documents, reimbursement application documents, activity application documents and other business documents involving business time calculation. The type and content of the business documents to be submitted will not be limited here. It can be understood that the business document to be submitted can be a business document customized by the business request object (that is, the business request object independently adds corresponding content according to business needs), so that the document content can be more in line with actual business needs, thereby improving the document utilization rate; optionally, the business document to be submitted can also be a business document determined by a specified business document template. In an embodiment of the present application, different types of business documents can correspond to different business document templates, that is, different business document templates can be used to indicate different document filling rules (for example, a leave document template can indicate the filling rules for leave application documents). In this way, a blank (or only containing a small amount of information) business document can be quickly generated through the existing business document template. After the business request object supplements the relevant information, a complete business document can be obtained, thereby effectively improving the generation efficiency of business documents. Similarly, according to the aforementioned target business classification, business document templates may include but are not limited to leave document templates, business trip document templates, out-of-office document templates, overtime document templates, shift transfer document templates, stationing document templates, attendance card replacement document templates, regularization document templates, home office document templates, venue reservation document templates, item collection document templates, reimbursement document templates, event application document templates, etc. Among them, the business document template can be a document template set by the business management object according to actual business needs, or it can be a default document template or recommended document template provided by the client, etc. The form of the business document template is not limited here.

[0094] Among them, the business document to be submitted includes the business start and end time and business duration. The business start and end time here can represent the start and end time of the target business (such as the above-mentioned business start and end time D1, business start and end time D2), specifically including the business start time (i.e. the start time of the target business, such as time t1) and the business end time (i.e. the end time of the target business, such as time t2); correspondingly, the business duration can represent the duration of the target business (such as the above-mentioned business duration E1, business duration E2), which can be determined by the corresponding business start and end time. Optionally, the business duration can be further determined by the template data information corresponding to the business document template. It can be understood that the business start and end time can be automatically configured by the client (for example, calling the time acquisition interface on the terminal device to automatically obtain the current terminal time, and determining the business start time or business end time based on the terminal time), or it can be manually configured by the business request object (i.e. the business request object manually fills in or voice inputs the business start time or business end time). There is no restriction on the configuration method of the business start and end time. Similarly, the service duration can be automatically configured by the client (for example, the result obtained by the service server automatically calculating the duration is used as the service duration), or manually configured by the service request object (that is, the service request object manually fills in or voice inputs the specified service duration, or manually modifies the duration returned by the service server). There is no restriction on the configuration method of the service duration. In this way, by providing multiple configuration methods, the generation method of business documents can be enriched, and the automatic configuration method can also improve the generation efficiency of business documents.

[0095] In addition, in the embodiment of the present application, any terminal device associated with the service request object may be referred to as a first terminal. The first terminal here may be Figure 1 Any terminal device in the terminal cluster shown, for example, terminal device 200a; similarly, the terminal device associated with the business approval object can be called a second terminal, where the second terminal can be Figure 1Any terminal device in the terminal cluster shown, for example, terminal device 200b. Among them, clients with document processing functions can be deployed in both the first terminal and the second terminal, and the business request object can submit business documents through the relevant client, and the business approval object can approve the business documents submitted by the business request object through the relevant client. The client here can be any one of the instant messaging client, social client, entertainment client and other clients listed above, and the embodiment of the present application does not limit the type of client. In addition, depending on the different operating modes, the client involved in the embodiment of the present application may include but is not limited to client applications, applets running as subprograms in the client, and web applications opened through a browser, etc., and the operating mode of the client is not limited here. It can be understood that the client is part of the business front end (which can be referred to as the front end), and the business server (for example, the above-mentioned Figure 1 The business server 100 in the example belongs to a part of the business backend (which may be referred to as the backend, business backend, backend, etc.) corresponding to the business frontend, and is used to interact with the client to provide computing and application service support for the client. The business server and the client may be directly or indirectly connected in a wired or wireless manner, which is not limited in the present embodiment of the application.

[0096] In combination with the foregoing, the method provided in the embodiment of the present application is mainly used to solve the problem of inconsistent duration in the document submission scenario. Therefore, the following will take the client on the first terminal (such as the aforementioned client B) as an example to explain the interaction process between the client and the business server (such as the aforementioned business server 100). Specifically, when the first business start and end time (such as the aforementioned business start and end time D1) is displayed in the business document to be submitted (such as the aforementioned business document C), the client can receive the first business duration (such as the aforementioned business duration E1) returned by the business server for the first business start and end time, and configure the business duration on the business document to be submitted to the first business duration; further, the business start and end time in the business document to be submitted is changed from the first business start and end time (such as the aforementioned business start and end time D1) to the second business start and end time (such as the aforementioned business start and end time D2), and the business duration on the business document to be submitted remains as the first business duration. When a business duration is one, in response to the document submission operation for the business document to be submitted, the second business start and end time and the first business duration are sent to the business server, so that when the business server calculates the second business duration corresponding to the second business start and end time (such as the aforementioned business duration E2), the second business duration is compared with the first business duration (such as the aforementioned business duration E1), and when the duration comparison is inconsistent, the second business duration is returned to the client; when receiving the second business duration returned by the business server, the client can update the business duration on the business document to be submitted from the first business duration to the second business duration.

[0097] It is understandable that, optionally, when the durations are compared and consistent, the client can display to the business request object that the business document to be submitted has been submitted successfully.

[0098] It is understandable that the business request object (such as the aforementioned user 1) can choose not to modify the first business start and end time and the corresponding first business duration when the business document to be submitted is configured with the first business start and end time and the corresponding first business duration, and directly submit the business document to be submitted, or it can also modify any one or more data in the business start and end time and the business duration in the business document to be submitted, and then submit the business document to be submitted, for example, the business start and end time in the business document to be submitted can be changed from the first business start and end time to the second business start and end time, or the business duration on the business document to be submitted can be changed from the first business duration to the third business duration, or both the business start and end time and the business duration can be changed. It is understandable that in either case, after the client submits the business document to be submitted, the business server can verify the business duration on the business document to be submitted, that is, the duration verification can be performed each time the business document is submitted, so as to ensure the consistency and accuracy of the business duration on all business documents.

[0099] It can be seen that the embodiment of the present application provides a solution for ensuring the consistency of duration calculation in the document submission scenario. The core of the solution is to perform a secondary check on the business duration on the business document to be submitted, that is, when a business document (such as the aforementioned business document to be submitted) is submitted through the front-end client, the back-end business server can recalculate the corresponding business duration based on the business start and end time (such as the aforementioned second business start and end time) input by the client, and then the business duration (such as the aforementioned second business duration) calculated by the business server at this time can be compared with the business duration (such as the aforementioned first business duration) input by the client, and when the duration comparison is inconsistent, the business duration (such as the aforementioned second business duration) calculated by the business server can be used as a benchmark to correct the business duration on the business document displayed by the aforementioned client, so that the consistency and accuracy of the business duration can be guaranteed when submitting the business document.

[0100] For further understanding, please refer to Figure 2a-2c , Figure 2a-2c 20A and the service server 20B are used as an example to illustrate the embodiment of the present application. The terminal device 20A and the service server 20B are used as the first terminal. The terminal device 20A can be used as the first terminal. Figure 1 Any terminal device in the terminal cluster shown, for example, terminal device 200a; the business server 20B here can interact with the terminal device 20A for data, and the business server 20B can be the above Figure 1 The business server 100 is shown.

[0101] like Figure 2a As shown, user 21a can be used as the aforementioned business request object and has a binding relationship with terminal device 20A. Multiple clients (for example, instant messaging clients, game clients, audio and video clients, etc.) can be installed and run on terminal device 20A for use by user 21a. For example, the multiple clients can include client 21b with a document processing function (for example, it can be an instant messaging client). In this way, when user 21a wants to participate in the target business (such as any of the aforementioned leave, business trips, going out, overtime, etc.), he can use its document processing function by starting client 21b to submit the relevant business documents to the designated business approval object for approval.

[0102] For example, Figure 2aAs shown, interface 201 shows an exemplary business access interface, which can be any interface on client 21b. For example, optionally, the business access interface can be the business main interface of client 21b (such as the first interface displayed after starting client 21b); optionally, the business access interface can also be any business sub-interface other than the business main interface, and any business sub-interface can be entered through the business main interface to perform operations related to the business sub-interface in any business sub-interface. Among them, the business access interface can include a document processing function entrance, and the document processing function on client 21b can be enabled through the document processing function entrance. For example, Figure 2a As shown, when the document processing function entrance 201a is displayed on the interface 201, the client 21b can respond to the access operation (e.g., click operation) to the document processing function entrance 201a, and display one or more business controls associated with the document processing function. The specific number of business controls is not limited here. It can be understood that one business control corresponds to the application entrance of a business (such as the aforementioned leave, business trip, going out, overtime, shift adjustment, assignment, venue reservation, item collection and other businesses).

[0103] It is understood that the one or more business controls mentioned above may be displayed in some form on the business access interface, or may be displayed on other interfaces (such as a business application interface) independent of the business access interface, and this is not limited. Figure 2aThe interface 202 shown can be used as an exemplary business application interface, which can be used to display multiple business controls associated with the document processing function. The multiple business controls can specifically include business controls 202a (such as business controls corresponding to leave, which can also be called leave application controls), business controls 202b (such as business controls corresponding to business trips, which can also be called business trip application controls), business controls 202c (such as business controls corresponding to going out, which can also be called going out application controls), business controls 202d (such as business controls corresponding to overtime, which can also be called overtime application controls), business controls 202e (such as business controls corresponding to shift changes, which can also be called shift change application controls), business controls 202f (such as business controls corresponding to assignments, which can also be called assignment application controls), and business controls 202g (such as the business control corresponding to the attendance card replacement, also known as the card replacement application control), business control 202h (such as the business control corresponding to the regularization, also known as the regularization application control), business control 202i (such as the business control corresponding to the home office, also known as the home office application control), business control 202j (such as the business control corresponding to the venue reservation, also known as the venue reservation application control), business control 202k (such as the business control corresponding to the item collection, also known as the item collection application control), business control 202m (such as the business control corresponding to the reimbursement, also known as the reimbursement application control), and business control 202n (such as the business control corresponding to the application for an event, also known as the event application control), may also include other business controls, which are not listed here one by one.

[0104] It should be understood that the one or more business controls may be displayed in a floating window, a masked window, or a semi-transparent window on the business access interface (eg Figure 2a The business controls may be displayed in any area of ​​the interface 201 shown in the figure. For example, these business controls may be displayed in the middle area of ​​the business access interface; alternatively, they may be displayed using an interface that can change the display size through a trigger operation (such as a drag operation) and is retractable, and the size of the interface is smaller than the business access interface; alternatively, they may be displayed using an interface that is independent of the business access interface (such as the aforementioned business application interface, see Figure 2a The interface 202 shown is displayed, and this embodiment of the present application does not limit this.

[0105] It can be understood that in a feasible implementation, user 21a can generate the required business documents according to his own needs through the business document template associated with any one of the above-mentioned multiple business controls; optionally, user 21a can also define the required business documents by himself without relying on the ready-made business document template, and the generation method of the business document will not be limited here. For ease of understanding, the method of generating business documents based on the business document template is used as an example to illustrate here. Specifically, the client 21b can respond to the selection operation (for example, click operation) of the target business control in the above-mentioned multiple business controls, and output the document display interface associated with the target business corresponding to the target business control, and the document display interface can be used to display and edit related business documents. For example, taking the target business as the leave business as an example, the business control 202a can be used as the target business control, and the client 21b can respond to the selection operation of the business control 202a, and output the interface 203 associated with the leave business, and the interface 203 can be used as an exemplary document display interface.

[0106] It can be understood that there may be many types of leave for leave business, such as annual leave, personal leave, sick leave, adjustment leave, marriage leave, maternity leave, paternity leave, prenatal check-up leave, bereavement leave, etc., which are not limited here. One leave type may correspond to a business document template, and the above-mentioned leave document templates may include annual leave document template, personal leave document template, sick leave document template, adjustment leave document template, marriage leave document template, maternity leave document template, paternity leave document template, prenatal check-up leave document template, bereavement leave document template, etc.; accordingly, leave application documents may include annual leave application document, personal leave application document, sick leave application document, adjustment leave application document, marriage leave application document, maternity leave application document, paternity leave application document, prenatal check-up leave application document, bereavement leave application document, etc. Based on this, after determining the leave type (such as annual leave), the client 21b can request the business server 20B for the template data information corresponding to the business document template (such as annual leave document template) configured for the leave type, and then when receiving the template data information, the template data information can be combined and displayed on the document display interface according to the specified layout format, thereby obtaining a blank (or containing a small amount of information) business document (such as annual leave application document). For example, Figure 2aAs shown, after user 21a determines that the leave type is annual leave, the corresponding business document 21c (i.e., annual leave application document) can be displayed on interface 203. Subsequently, user 21a can fill in the corresponding business start time (such as leave start time), business end time (such as leave end time), business duration (such as leave duration), application reason (such as leave reason), explanation attachment (such as communication record with superior) and other information according to the instructions, so as to obtain a complete business document. It can be understood that some of the information filled in can be set as required items (such as business start time, business end time, business duration, etc.), and some can be set as optional items (such as application reason, explanation attachment, etc.). In actual application, it can be set according to business needs, and there is no restriction here.

[0107] In the embodiment of the present application, the service document 21c can be used as the aforementioned service document to be submitted. It can be understood that after the user 21a fills in the service start and end time (including the service start time and the service end time), the service server 20B can calculate the service duration corresponding to the service start and end time as quickly as possible, and return it to the client 21b for display. Figure 2a As shown, assuming that the business start time in the business document 21c is configured as time 21d (for example, 2023 / 1 / 12 morning), and the business end time in the business document 21c is configured as time 21e (for example, 2023 / 1 / 15 afternoon), the client 21b can send time 21d and time 21e as the first business start and end time to the business server 20B. When the business server 20B receives time 21d and time 21e, it can calculate the duration 21f (for example, 4 days) corresponding to time 21d and time 21e, and then return the duration 21f as the first business duration to the client 21b. Correspondingly, when receiving the duration 21f, the client 21b can configure the business duration on the business document 21c to the duration 21f, and can display the duration 21f on the interface 204. Among them, the specific duration calculation logic executed by the business server 20B can be found in the subsequent Figure 4 It is understood that, when the service server 20B has not successfully returned the duration 21f, the client 21b detects that the service duration on the service receipt 21c is a null value (that is, the service duration is not configured, for example, see interface 203), and the client 21b cannot submit the service receipt 21c.

[0108] Further, optionally, user 21a can directly submit the above-mentioned business document 21c for approval, or, optionally, user 21a can also modify the business start and end time in the business document 21c again, and the client 21b and the business server 20B will also repeat the above-mentioned processing flow accordingly. In order to avoid the problem of inconsistent duration that may occur when submitting a business document, the embodiment of the present application supports the business server to perform a secondary verification of the business duration input by the client. Among them, in the scenario of modifying the business start and end time, user 21a can modify any one or more of the business start time and the business end time in the business document 21c, and the embodiment of the present application does not limit this.

[0109] For example, Figure 2b As shown, assuming that user 21a changes the business start time in business document 21c from the aforementioned time 21d to time 21g (for example, 2023 / 1 / 14 morning), and the business end time is not changed and remains the aforementioned time 21e (for example, 2023 / 1 / 15 afternoon), the client 21b can use time 21g and time 21e as the second business start and end time, and display the second business start and end time on the document display interface (such as interface 205). At this time, the business start and end time in business document 21c is changed from the aforementioned first business start and end time (including time 21d and time 21e) to the second business start and end time (including time 21g and time 21e). Further, if the service duration on the service document 21c still remains the aforementioned first service duration (for example, duration 21f) (that is, the service server 20B is still calculating and has not yet returned a new service duration to the client 21b), the user 21a determines to submit the service document 21c, then the client 21b can respond to the document submission operation for the service document 21c and send the second service start and end time and the first service duration calculated last time to the service server 20B. Optionally, the document display interface may include a document submission control, such as control 21h on interface 205. The client 21b may respond to a confirmation operation (e.g., a click operation) on control 21h and send time 21g, time 21e, and duration 21f to the business server 20B. Accordingly, the business server 20B may calculate a duration 21i (e.g., 2 days) corresponding to time 21g and time 21e, and the duration 21i may be used as a second business duration, and the duration 21i calculated by the business server 20B may be compared with the duration 21f transmitted by the client 21b.

[0110] It can be understood that when the duration comparison is inconsistent (i.e., the duration 21i is inconsistent with the duration 21f), it means that the user 21a submitted the document too quickly. At this time, the service duration on the service document 21c is incorrect and needs to be corrected. Then the service server 20B can return the duration 21i to the client 21b. When receiving the duration 21i returned by the service server 20B, if Figure 2b As shown in the interface 206, the client 21b can update the business duration on the business document 21c from the aforementioned duration 21f to duration 21i. Obviously, the duration 21i at this time is the correct business duration corresponding to time 21g and time 21e. Therefore, when the user 21a submits the business document 21c again, the business document 21c can be submitted successfully, thereby ensuring the consistency of duration calculation in the scenario where the document is submitted too quickly.

[0111] On the contrary, optionally, if the durations are consistent (ie, the duration 21i is consistent with the duration 21f), the business document 21c is successfully submitted, and the business server 20B may return corresponding prompt information to the client 21b to indicate that the business document 21c is successfully submitted.

[0112] Among them, it is understandable that Figure 2a-2b Interface 203, interface 204, interface 205 and interface 206 shown are document display interfaces at different times.

[0113] It can be understood that when the target business is other businesses (such as business trips, outings, overtime, shift changes, assignments, attendance card replacement, regularization, home office, venue reservations, item collection, reimbursement, application for activities, etc.), the specific process of consistency verification of the business duration on the relevant business documents is similar to the duration consistency verification process in the leave scenario illustrated in the above example, and will not be listed one by one here.

[0114] For example, optionally, when the target service is a venue reservation service, the service control 202j (ie, venue reservation application control) shown in the above interface 202 can be used as the target service control, such as Figure 2cAs shown, the client 21b can output an interface 207 associated with the venue reservation service in response to the selection operation on the service control 202j, and the interface 207 can be used as an exemplary document display interface. It can be understood that the venue reservation service can include but is not limited to the reservation of venues such as conference rooms, classrooms, and exhibition halls. One venue can correspond to a business document template. For example, the venue reservation document template can include a conference room reservation document template, a classroom reservation document template, an exhibition hall reservation document template, etc. Correspondingly, the venue reservation application document can include a conference room reservation application document, a classroom reservation application document, an exhibition hall reservation application document, etc. Assuming that user 21a wants to apply for a certain conference room, the client 21b can request the business server 20B for the template data information corresponding to the configured conference room reservation document template, and then, when receiving the template data information, the template data information can be combined and displayed on the document display interface (such as interface 207) according to the specified layout format, thereby obtaining a conference room reservation application document (such as business document 21j). Subsequently, user 21a can fill in the reserved conference room, business start time (such as the scheduled start time), business end time (such as the scheduled end time), business duration (such as the scheduled duration), meeting topic, participants (such as colleagues in the entire department) and other information according to the instructions.

[0115] It can be understood that at this time, the service document 21j can be used as the aforementioned service document to be submitted. After the user 21a fills in the service start and end time (including the service start time and the service end time), the service server 20B can calculate the service duration corresponding to the service start and end time as quickly as possible and return it to the client 21b for display. Figure 2c As shown in the interface 207 in FIG. 207 , assuming that the service start time in the service receipt 21j is configured as time 21k (for example, 2023 / 1 / 12 11:00), and the service end time in the service receipt 21j is configured as time 21m (for example, 2023 / 1 / 12 12:00), the client 21b can send the time 21k and the time 21m as the first service start and end time to the service server 20B. When the service server 20B receives the time 21k and the time 21m, it can calculate the duration 21n (for example, 1 hour) corresponding to the time 21k and the time 21m, and then return the duration 21n as the first service duration to the client 21b. Accordingly, when the client 21b receives the duration 21n, it can configure the service duration on the service receipt 21j as the duration 21n, and can display the duration 21n on the interface 207 .

[0116] Furthermore, it is assumed that user 21a modifies the service start and end time in service document 21j again, such as Figure 2cAs shown in the interface 208, the user 21a changes the business start time in the business document 21j from the aforementioned time 21k to time 21o (for example, 2023 / 1 / 12 10:00), and the business end time from the aforementioned time 21m to time 21p (for example, 2023 / 1 / 12 11:30). Then, the client 21b can use time 21o and time 21p as the second business start and end time. At this time, the business start and end time in the business document 21j is changed from the aforementioned first business start and end time (including time 21k and time 21m) to the second business start and end time (including time 21o and time 21p). Further, if the service duration on the service document 21j still remains the aforementioned first service duration (e.g., duration 21n) (i.e., the service server 20B is still calculating and has not yet returned a new service duration to the client 21b), and the user 21a determines to submit the service document 21j, the client 21b can respond to the document submission operation for the service document 21j (e.g., it can respond to the confirmation operation for the control 21q (i.e., the document submission control)) and send the time 21o, time 21p, and duration 21n to the service server 20B; accordingly, the service server 20B can calculate the duration 21r (e.g., 1.5 hours) corresponding to the time 21o and the time 21p, and the duration 21r can be used as the second service duration, and then the duration 21r calculated by the service server 20B can be compared with the duration 21n transmitted by the aforementioned client 21b. It can be understood that when the duration comparison is inconsistent (i.e., the duration 21r is inconsistent with the duration 21n), it means that the user 21a submitted the document too quickly. At this time, the service duration on the service document 21j is incorrect and needs to be corrected. Then the service server 20B can return the duration 21r to the client 21b. When receiving the duration 21r returned by the service server 20B, if Figure 2c As shown in the interface 209, the client 21b can update the business duration on the business document 21j from the aforementioned duration 21n to duration 21r. Obviously, the duration 21r at this time is the correct business duration corresponding to time 21o and time 21p. Therefore, when the user 21a submits the business document 21j again, the business document 21j can be successfully submitted, thereby ensuring the consistency of duration calculation in the scenario where the document is submitted too quickly.

[0117] Among them, it is understandable that Figure 2c Interface 207, interface 208 and interface 209 shown are document display interfaces at different times.

[0118] It should be noted that the interfaces involved in all embodiments of the present application are not limited to the several exemplary interfaces mentioned; in actual applications, these interfaces may also have other forms of expression, which are not limited to this.

[0119] It can be understood that the interactive operations involved in all embodiments of the present application (such as the aforementioned access operation, selection operation, document submission operation, confirmation operation, and the first-time editing operation and second-time editing operation mentioned later) may include but are not limited to gesture operations, voice signal input operations, etc.; wherein, gesture operations may include but are not limited to: single-click operations, double-click operations (such as clicking the same position in the interface twice in a short time (such as 3 seconds)), long press operations (such as performing continuous pressing operations on any position in the interface), sliding operations (such as fast sliding operations in different directions, sliding operations with preset shapes (such as sliding tracks of "S" shape or "L line"), etc.), drag operations, etc.; voice signal input operations may refer to the operation of collecting voice signals in the physical environment (i.e., the surrounding environment where the business request object is located) through the microphone of the terminal device for indicating the display of a certain interface. The specific form of the interactive operation is not limited here.

[0120] It should be noted that "display" and "output" in all embodiments of the present application can be expressed as a jump switch of the interface, or it can be expressed as opening up a new area in the current interface, such as creating a pop-up window, or displaying a hidden area in the current interface, etc., and there is no limitation here.

[0121] It should be noted that the interfaces and controls shown in all the embodiments of this application are merely some forms of expression for reference. In actual applications, developers can make relevant designs based on product requirements. This application does not limit the specific forms of the interfaces and controls involved.

[0122] It is understandable that in the specific implementation of the present application, when submitting a business document, the business start and end time, business duration, and identity data (such as the name, account name, account identification number (ID), avatar, account level, membership attributes, etc.) of the business request object, personnel information (such as the department, region, superior, etc. of the business request object), and explanatory attachments (such as communication records with superiors, physical condition and other certification materials) and other data related to the business request object may be obtained. When the embodiments in the present application are applied to specific products or technologies, it is necessary to obtain the permission or consent of the business request object, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of the relevant countries and regions. For example, a prompt interface or pop-up window can be displayed, and the prompt interface or pop-up window is used to prompt the business request object that it is currently collecting data such as business start and end time, business duration, identity data, personnel information, explanatory attachments, etc., and only after the business request object issues a confirmation operation on the prompt interface or pop-up window, the relevant steps of data acquisition are started, otherwise it ends.

[0123] As can be seen from the above, by performing a secondary check on the business duration on the business document to be submitted, the consistency and accuracy of the business duration can be guaranteed when submitting the business document. In addition, compared with the prior art method in which manual submission and approval are required multiple times when the business duration is inconsistent, the method provided in the embodiment of the present application ensures the consistency and accuracy of the business duration when submitting the business document, and does not require manual verification of the business duration, so the required business application duration can be reduced, thereby improving the efficiency of business approval.

[0124] It should be noted that the method provided in the embodiment of the present application is applicable to various business scenarios where there is a need to verify the business duration on documents, such as leave, business trips, going out, overtime, shift changes, assignments, attendance card replacement, regularization, home office, venue reservations, item collection, reimbursement, application for activities, etc. The specific business scenarios will not be listed one by one here.

[0125] For example, in the item collection scenario, the target items that can be applied for include, but are not limited to, office equipment, production equipment, signatures, and transportation vehicles configured by the enterprise / institution / organization where the business request object is located. When the business request object wishes to apply for a certain target item (such as an office computer), the relevant information can be filled in on the corresponding business document (i.e., item collection application document), such as the relevant information of the target item applied for, the collection start time (i.e., the business start time), the collection end time (i.e., the business end time), the collection duration (i.e., the business duration), the reason for application, etc. It can be understood that after the collection start time and the collection end time are filled in the item collection application document, the business server will calculate the collection duration corresponding to the collection start time and the collection end time at the fastest speed, and return the collection duration to the client to fill in the item collection application document. If the business request object modifies any one or more of the aforementioned collection start time and collection end time, it will trigger the business server to perform a new round of duration calculation and obtain a new collection duration; if the business request object quickly submits the document before the business server feeds back the new collection duration to the client, then there may be a problem of inconsistent collection durations on both sides. Therefore, the business server will verify the collection duration submitted by the client. If it is found that the collection duration submitted by the client is inconsistent with the collection duration recalculated by the business server, the collection duration submitted by the client needs to be corrected.

[0126] For another example, in a reimbursement scenario, items that can be reimbursed include, but are not limited to, travel expenses, entertainment expenses, office expenses, telephone charges, rental fees, audit fees, consulting fees, water and electricity charges, maintenance fees, fuel charges, freight, etc. When the business request object wishes to apply for reimbursement of a certain expense (such as travel expenses), the relevant information can be filled in on the corresponding business document (i.e., reimbursement application document), such as the type of item for which reimbursement is applied, specific expenditure expenses, the start time of the expenditure (i.e., the business start time), the end time of the expenditure (i.e., the business end time), the duration of the expenditure (i.e., the business duration, for example, accommodation expenses during a business trip can be calculated from the first day of arrival at the accommodation until the last departure), the place of occurrence, etc. It can be understood that after filling in the start time and end time of the expenditure in the reimbursement application document, the business server will calculate the expenditure duration corresponding to the start time and end time of the expenditure as quickly as possible, and return the expenditure duration to the client to fill in the reimbursement application document. If the business request object modifies any one or more of the aforementioned expense expenditure start time and expense expenditure end time, it will trigger the business server to perform a new round of duration calculation to obtain a new expense expenditure duration; if the business request object quickly submits the document before the business server feeds back the new expense expenditure duration to the client, then the expense expenditure duration on both sides may be inconsistent. Therefore, the business server will verify the expense expenditure duration submitted by the client. If it is found that the expense expenditure duration submitted by the client is inconsistent with the expense expenditure duration recalculated by the business server, the expense expenditure duration submitted by the client needs to be corrected.

[0127] The specific process of the client submitting the business document to be submitted and the specific process of the business server verifying the business duration on the business document to be submitted can be seen as follows Figures 3 to 10 The corresponding embodiment.

[0128] For further information, see Figure 3 , Figure 3 This is a flow chart of a data processing method provided in an embodiment of the present application. Figure 1 .like Figure 3 As shown, the method can be executed by a client, and the client can be run on a first terminal. For example, the first terminal can be the above Figure 1 Any terminal device in the terminal cluster shown (eg, terminal device 200a). The method may specifically include the following steps S101 to S103.

[0129] Step S101, when the first service start and end time is displayed in the service document to be submitted, receiving the first service duration returned by the service server for the first service start and end time, and configuring the service duration on the service document to be submitted as the first service duration;

[0130] It can be understood that when the business start and end time in the business document to be submitted is configured as the first business start and end time, the client can display the first business start and end time in the business document to be submitted, and can send the first business start and end time to the business server, so that the business server can calculate the corresponding first business duration as quickly as possible; when the client receives the first business duration returned by the business server for the first business start and end time, the business duration on the business document to be submitted can be configured as the first business duration.

[0131] Among them, the first service start and end time include the first service start time and the first service end time, and the embodiment of the present application does not limit the configuration method of the first service start and end time. Optionally, the first service start and end time can be automatically configured by the client, for example, the client can call the time acquisition interface on the first terminal to obtain the current terminal time (i.e., system time), and can convert the obtained terminal time into the first service start time or the first service end time according to the time scale parameter configured in the service document to be submitted (for example, in days or hours), for example, when configuring the first service start time, assuming that the terminal time obtained by the client is "2023 / 6 / 5 16:34:04", if the time scale parameter configured in the service document to be submitted indicates that it is calculated by hours, then the converted time "2023 / 6 / 5 16:34" can be used as the first service start time; if the time scale configured in the service document to be submitted indicates that it is calculated by days, then the converted time "2023 / 6 / 5 afternoon" can be used as the first service start time. Optionally, the first service start and end time can be manually configured by the service request object. For example, the service request object can input the specified first service start time and first service end time through relevant operations (such as first time editing operations). For example, the service request object can input the corresponding time through certain gesture operations (such as sliding, clicking, etc.), or can input the corresponding time by inputting a specified voice signal. Optionally, the first service start and end time can also be automatically configured by the client + manually modified by the service request object. For example, when the client calls the time acquisition interface to obtain the terminal time, the terminal time can be converted into the initial service start time (or initial service end time) and displayed in the service document to be submitted. Then, the service request object can manually modify the initial service start time (or initial service end time) in the service document to be submitted, thereby modifying the initial service start time (or initial service end time) to the first service start time (or first service end time). It can be seen that the embodiment of the present application provides a variety of service start and end time configuration methods, improves the diversity and flexibility of service start and end time configuration methods, and helps to improve the configuration efficiency of service start and end time, thereby improving the generation efficiency of service documents.

[0132] In one embodiment, the business document to be submitted can be displayed, edited (for example, the content in the business document to be submitted can be supplemented, modified, deleted, etc.) and submitted through the document display interface. An exemplary document display interface can be seen in the above Figure 2a The interface 203 shown in the figure does not limit the specific form of the document display interface in the present embodiment. An implementation method of outputting the document display interface (such as the aforementioned interface 203) on the client can be referred to in the above Figure 2a The description of the specific process of the output interface 203 in the corresponding embodiment will not be repeated here.

[0133] Based on this, when configuring the business start and end time in the business document to be submitted as the first business start and end time, the client can display the first business start and end time in the business document to be submitted on the document display interface, and can configure the business duration on the business document to be submitted as the first business duration corresponding to the first business start and end time. The specific process can be: on the document display interface, the client can respond to the first time editing operation on the business document to be submitted, and display the first business start and end time (including the first business start time and the first business end time) in the business document to be submitted; the first time editing operation here refers to the operation of the business request object configuring (or editing) the business start and end time in the business document to be submitted as the first business start and end time. The first time editing operation includes but is not limited to gesture operations, voice signal input operations, etc. for configuring the first business start and end time. The specific form of the first time editing operation is not limited here. For example, taking the above Figure 2a Taking the business document 21c in the corresponding embodiment as an example, Figure 2a As shown in the interface 203 in FIG. 2 , the client 21b can respond to the first time editing operation on the business document 21c and display the first business start time (such as time 21d) and the first business end time (such as time 21e) configured by the first time editing operation in the business document 21c. Further, the client can send the first business start and end time to the business server, so that the business server returns the first business duration to the client when calculating the first business start and end time corresponding to the first business duration. The specific process of the business server calculating the first business duration and returning it to the client can be referred to in the subsequent Figure 4 It is understood that when the first service duration returned by the service server is not received, the service duration on the service document to be submitted can be displayed as a default duration (for example, the default duration is empty at the initial moment) or the most recently configured service duration on the service document to be submitted.

[0134] Further, upon receiving the first service duration returned by the service server, the client may configure the service duration on the service receipt to be submitted as the first service duration, and may display the first service duration on the receipt display interface. Figure 2a Taking the business document 21c in the corresponding embodiment as an example, Figure 2a As shown in the interface 204 in FIG, after receiving the first service duration (such as the duration 21f corresponding to the time 21d and the time 21e) calculated by the service server 20B, the client 21b can configure the service duration on the service document 21c as the duration 21f, and can display the duration 21f on the interface 204. As can be seen from the above, configuring the service duration on the service document to be submitted as the first service duration automatically calculated by the service server can save the cost and time of manually calculating the service duration, and can improve the configuration efficiency of the service duration while improving the configuration accuracy of the service duration, thereby facilitating the generation efficiency and quality of the service documents.

[0135] Specifically, when the business request object wants to participate in the target business (such as leave business), the client can respond to the target business control corresponding to the target business (such as leave application control, as mentioned above). Figure 2a The business control 202a shown in the middle interface 202 is selected to send a template acquisition request to the business server. The template acquisition request carries the template identifier (also called template id) of the business document template (such as a leave document template) configured by the target business. The template acquisition request is used to instruct the business server to obtain the template data information corresponding to the aforementioned business document template from the business database according to the template identifier, and return the obtained template data information to the client. Among them, the template data information can be understood as the detailed information of the corresponding business document template, which may include the basic template information of the business document template (including template name, template identifier, template icon, template grouping information, etc.), business configuration parameters (i.e., parameters related to duration calculation configured for the target business, such as leave type and time scale parameters configured for leave business), control configuration information (i.e., control name and control type corresponding to the control added in the business document template), and other information. The specific content of the template data information is not limited here. Furthermore, when the client obtains the template data information returned by the business server, it can combine part or all of the information in the template data information into a business document to be submitted according to a certain display format, and can display the business document to be submitted on the document display interface (such as the above Figure 2aThe interface 203 shown in the figure). It can be understood that the business document to be submitted at this time can be a blank business document (i.e., does not contain information related to the business request object) or a business document containing only a small amount of information (such as the name of the business request object), and there is no limitation here. The subsequent business request object can edit the business document to be submitted through the document display interface, such as configuring the business start and end time in the business document to be submitted to be the first business start and end time.

[0136] In an embodiment of the present application, the client can send the first business start and end time to the business server through the applet end for document processing; based on this, the client displays the first business start and end time in the business document to be submitted, and the specific process of sending the first business start and end time to the business server can be: on the document display interface, in response to the first time editing operation on the business document to be submitted, the business start and end time in the business document to be submitted is configured as the first business start and end time (including the first business start time and the first business end time, such as the aforementioned time 21d and time 21e), and the first business start and end time is displayed in the business document to be submitted; further, the client can obtain the template identifier of the business document template corresponding to the business document to be submitted (such as the template identifier of the business document template in the aforementioned Figure 2a In the corresponding embodiment, it can be a template identifier of the annual leave document template), and the template identifier and the first business start and end time are sent to the mini-program end used for document processing, so that the mini-program end sends a first business request to the business server based on the template identifier and the first business start and end time; wherein, the first business request here is used to instruct the business server to obtain the template data information corresponding to the aforementioned business document template from the business database through the template identifier, calculate the first business duration based on the template data information and the first business start and end time, and return the first business duration to the client through the mini-program end.

[0137] Among them, it can be understood that when the mini program end and the business server interact with data, a certain communication protocol (such as TCP (Transmission Control Protocol), UDP (User Data Protocol) and other protocols) can be adopted. There is no restriction on the specific communication protocol adopted here; based on the adopted communication protocol, the mini program end can send data to the business server by request reorganization or direct forwarding. For example, the mini program end can reorganize the received template identifier and the start and end time of the first business into a first business request, and then transmit the first business request to the business server. Optionally, the mini program end can also directly forward the received template identifier and the start and end time of the first business to the business server. The embodiment of the present application does not limit the specific method of data transmission.

[0138] It can be understood that the client and the applet end can be programs that the business front end (can be referred to as the front end) is responsible for at the same time, and the two can be collectively referred to as business clients, that is, interacting with the business server as a whole; optionally, the client and the applet end can be independent programs from each other, or, optionally, the client and the applet end can be integrated into one program, for example, the applet end can be embedded in the client, or the applet end can be directly integrated on the client. Optionally, the client and the applet end can be integrated on the same terminal device, or they can be separately deployed on different terminal devices. The embodiment of the present application does not limit the deployment method of the client and the applet end. The client is mainly responsible for interface interaction with the business request object, and the data stream (such as click stream) generated during the interaction will flow to the applet end, and the applet end is responsible for logical processing of the received data stream. Among them, when the applet end receives the template identifier and the start and end time of the first business sent by the client, the received template identifier and the start and end time of the first business can be packaged into a first request data packet, and the first request data packet is written into the first business request, and then the first business request can be sent to the business server. In addition, the first request data packet may also include other information (such as the template name of the business document template), which is not limited here. It can be understood that the embodiment of the present application can use data encapsulation technology to transmit the template identifier and the start and end time of the first business to the business server in the form of a data packet, which can achieve safe and reliable data transmission and improve data transmission efficiency.

[0139] In addition, it can be understood that when the client, the mini program and the business server collaborate with each other, each part performs its own duties, which can reduce the data processing pressure and data storage burden of each part in the document processing process, and help improve the efficiency of successful document submission.

[0140] Optionally, when the business document to be submitted is not determined by a business document template but is customized by a business request object, the client can directly send the first business start and end time to the mini program end, so that the mini program end packages the received first business start and end time into a first request data packet, and writes the first request data packet into the first business request for sending to the business server.

[0141] It is understandable that the template data information corresponding to all business document templates can be stored in the business database, which is a database managed by the business backend and can interact with the business server. In short, the database can be regarded as an electronic filing cabinet - a place to store electronic files, where users can add, query, update, delete, and other operations on the data in the files. The so-called "database" is a collection of data that is stored together in a certain way, can be shared with multiple users, has as little redundancy as possible, and is independent of the application.

[0142] It should be noted that a business document template corresponds to a unique template identifier, that is, a template identifier is used to uniquely identify a business document template. Therefore, the business server can quickly find the template data information corresponding to the business document template from the business database based on the template identifier of a business document template. For example, assuming that the template identifier of the annual leave document template is "1234567", the business server can quickly obtain the template data information of the annual leave document template from the business database based on "1234567". For the business server, it does not need to store all the template data information, which reduces the burden of data storage. It only needs to obtain the relevant template data information on demand from the business database when performing relevant logical processing. It is flexible and convenient, which can effectively reduce the pressure of data processing and improve the security of data storage. For the client, it does not need to directly transmit the complete template data information, so as to reduce the amount of data transmission between the front and back ends, which helps to improve the overall efficiency of obtaining business time.

[0143] Among them, the template identifier can be represented by one or more of numbers, letters, symbols, etc., and the representation form of the template identifier is not limited here. When setting the relevant business document template, the business server can generate the corresponding template identifier. For example, optionally, the business server can obtain the template setting timestamp when setting the business document template (for example, it can be represented by a Unix timestamp), and generate the corresponding template identifier based on the obtained template setting timestamp; optionally, the business server can randomly generate the template identifier of the business document template; optionally, the business server can assign a corresponding template identifier to each business document template according to certain template identifier generation rules, for example, an unsigned integer can be assigned to each business document template in order from small to large as its template identifier; the generation method of the template identifier will not be limited here.

[0144] Optionally, in some special cases, the business management object is not configured with any business document template, nor is the relevant duration calculation rules (such as holiday configuration, attendance rules, time scales, etc.) set for the business document. In this case, the duration calculation logic will not be so complicated. For example, the business server can directly calculate the corresponding business duration based on the business start time and business end time passed in by the client, without having to obtain the relevant template data information for duration calculation. For example, assuming that the business management object has newly created an enterprise (such as enterprise A) and has not set any duration calculation rules, the duration calculation rules stored in the business database are empty. If during this period a business request object (such as user B in enterprise A) submits a leave application document, applying for personal leave from 10:00 am (i.e. the business start time) to 11:00 am (i.e. the business end time) on the same day, since the business server has not found any relevant duration calculation rules in the business database, the default rule (such as the default submitted business start and end times are both normal working hours) can be used to calculate the time difference between 10:00 and 11:00 (i.e. 1 hour) as the corresponding business duration. Therefore, the duration calculation in this case can be simple and efficient.

[0145] In addition, when displaying the business document to be submitted, the client can receive the document identification (also called document ID) of the business document to be submitted returned by the business server. It can be understood that when the business request object determines to submit the business document to be submitted later, the client can send the document data information including the document identification and template identification corresponding to the business document to be submitted to the business server. After the business document to be submitted is successfully submitted, the business server can also store the document data information corresponding to the business document to be submitted in the business database. Among them, the document data information can be understood as the detailed information of the corresponding business document, which can include the document identification of the business document, the document submission time, the document content (such as the business start time, the business end time, the business duration, the application reason, the description attachment, etc.), the template identification of the business document template corresponding to the business document, and other information. The specific content of the document data information is not limited here.

[0146] It should be noted that a business document corresponds to a unique document identifier, that is, a document identifier is used to uniquely identify a business document. Therefore, the business server can quickly find the document data information corresponding to a business document from the business database based on the document identifier of a successfully submitted business document. For example, Figure 2aIn the corresponding embodiment, assuming that the aforementioned business document 21c has been submitted successfully, and its document identifier is "5432100", the business server 20B can quickly obtain the document data information corresponding to the business document 21c from the business database according to "5432100" for processing. For example, the total length of leave for user 21a in a certain time period (such as half a year) can be counted. For the business server, it does not need to store all the document data information, which reduces the burden of data storage. It only needs to obtain relevant document data information from the business database on demand when performing relevant logical processing. It is flexible and convenient, which can effectively reduce data processing pressure and improve the security of data storage. Among them, the document identifier can be represented by one or more of numbers, letters, symbols, etc., and there is no restriction on the representation form of the document identifier. When generating relevant business documents, the business server may generate a corresponding document identifier. For example, optionally, the business server may obtain a document generation timestamp when the business document is generated (for example, it may be represented by a Unix timestamp), and generate a corresponding document identifier based on the obtained document generation timestamp; optionally, the business server may randomly generate a document identifier for the business document; optionally, the business server may assign a corresponding document identifier to each business document according to certain document identifier generation rules, for example, an unsigned integer may be assigned to each business document in ascending order as its document identifier; the generation method of the document identifier will not be limited here.

[0147] It can be understood that the template identifier and the document identifier represent different identifiers respectively, and the values ​​of the two cannot be the same. Multiple business documents can be generated according to the same business document template, but the document identifier of each business document is unique. For example, 10 personal leave application documents can be submitted according to the personal leave document template. For these 10 personal leave application documents, the template identifier corresponding to each personal leave application document is the same (that is, they are all template identifiers of the personal leave document template), but the document identifier of each personal leave application document is different. In this way, when all template data information and document data information are stored in the same business database, these data can be effectively distinguished by the template identifier and the document identifier, thereby reducing the complexity of data storage in the business database and improving the security of data stored in the business database. In addition, the efficiency of obtaining data in the business database can also be improved.

[0148] Step S102: when the service start and end time in the service document to be submitted is changed from the first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains the first service duration, in response to the document submission operation for the service document to be submitted, the second service start and end time and the first service duration are sent to the service server, so that when the service server calculates the second service duration corresponding to the second service start and end time, the second service duration is compared with the first service duration, and when the duration comparison is inconsistent, the second service duration is returned to the client;

[0149] It can be understood that when the business start and end time in the business document to be submitted changes (for example, from the first business start and end time to the second business start and end time), but the business duration on the business document to be submitted does not change accordingly (that is, it still remains the first business duration corresponding to the first business start and end time), if the business document to be submitted is submitted directly, there may be a problem of inconsistent business duration. Based on this, the embodiment of the present application supports the business server to calculate the second business duration corresponding to the second business start and end time when receiving the second business start and end time and the first business duration sent by the client, and compare the calculated second business duration with the first business duration transmitted by the client to ensure the consistency of the business duration.

[0150] Specifically, on the document display interface, in response to the second time editing operation on the business document to be submitted, the business start and end time in the business document to be submitted is changed from the first business start and end time (including the first business start time and the first business end time) to the second business start and end time (including the second business start time and the second business end time), wherein the change of the business start and end time may include any one or more of the change methods of changing the business start time and changing the business end time, which are not limited here. Therefore, the first business start time and the second business start time may be the same or different, and similarly, the first business end time and the second business end time may be the same or different; the second time editing operation here refers to the operation by the business request object to change the business start and end time in the business document to be submitted. The second time editing operation includes but is not limited to gesture operations, voice signal input operations, etc. for changing the first business start and end time to the second business start and end time. The specific form of the second time editing operation is not limited here. For example, taking the above Figure 2a-2b Taking the business document 21c in the corresponding embodiment as an example, the client 21b can respond to the second time editing operation on the business document 21c and change the first business start time (for example, time 21d) to the second business start time (for example, time 21g), while the first business end time (for example, time 21d) does not change. At this time, the first business end time (for example, time 21d) can be used as the second business end time.

[0151] Furthermore, when the business duration on the business document to be submitted remains at the first business duration, the client can respond to the document submission operation for the business document to be submitted, and send the template identifier of the business document template corresponding to the business document to be submitted (such as the template identifier of the aforementioned annual leave document template), the second business start and end time (including the second business start time and the second business end time, such as the aforementioned time 21g and time 21e) and the first business duration (such as the aforementioned duration 21f) to the mini program end, so that the mini program end sends a second business request to the business server based on the template identifier, the second business start and end time and the first business duration; wherein the document submission operation here refers to the business request object submitting the business document to be submitted The operation of business documents, the document submission operation includes but is not limited to gesture operations and voice signal input operations for submitting business documents to be submitted, and the specific form of the document submission operation is not limited here; wherein, the second business request here is used to instruct the business server to obtain the template data information corresponding to the aforementioned business document template (such as the template data information corresponding to the aforementioned annual leave document template) from the business database through the template identifier, and calculate the second business duration (such as the aforementioned duration 21i) based on the template data information and the second business start and end time, and then the second business duration can be compared with the first business duration, and when the duration comparison is inconsistent, the second business duration is returned to the client through the mini program end. Among them, the business server calculates the second business duration and compares the second business duration with the first business duration. The specific process can be found in the subsequent Figure 4 The corresponding step S203 in the embodiment.

[0152] It can be understood that the client does not need to transmit the complete template data information. Instead, the client sends the template identifier to the business server, and the business server obtains the corresponding template data information from the business database through the template identifier. This method not only reduces the data processing pressure and data storage burden on the business server side, but also reduces the amount of data transmission between the front and back ends, which helps to improve the overall efficiency of business duration verification.

[0153] Optionally, the document display interface may include a document submission control (such as the above Figure 2bThe control 21h shown in the figure, when the business duration on the business document to be submitted remains as the first business duration, the client can respond to the determination operation (for example, a click operation) of the document submission control, and send the template identifier of the business document template corresponding to the business document to be submitted (such as the template identifier of the aforementioned annual leave document template), the second business start and end time (such as the aforementioned time 21g and time 21e) and the first business duration (such as the aforementioned duration 21f) to the mini program end. Correspondingly, the mini program end can package the received template identifier, the second business start and end time, and the first business duration into a second request data packet, and write the second request data packet into the second business request, and then send the second business request to the business server. In addition, the second request data packet can also contain other information (such as the template name of the business document template), which is not limited here. It can be understood that the embodiment of the present application can adopt data encapsulation technology to transmit the template identifier, the second business start and end time, and the first business duration to the business server in the form of a data packet, which can achieve safe and reliable data transmission and improve data transmission efficiency.

[0154] Optionally, the mini program end may also forward the received template identifier, the start and end time of the second service, and the duration of the first service to the service server for processing; the embodiment of the present application does not limit the method of data transmission.

[0155] In addition, it can be understood that the client, mini program and business server each perform their respective duties, which can reduce the data processing pressure and data storage burden of each part of the document processing flow, and improve the efficiency of successful document submission while ensuring consistent business time.

[0156] Optionally, when no business document template and duration calculation rules are configured, the above-mentioned business document to be submitted can be customized by the business request object; the client can send the second business start and end time (including the second business start time and the second business end time) and the first business duration in the business document to be submitted to the business server, and then the business server can directly calculate the corresponding second business duration according to the second business start time and the second business end time (for example, calculate the time difference between the second business start time and the second business end time), without the need to combine relevant template data information to perform duration calculation, which can reduce the complexity of duration calculation.

[0157] Step S103: when receiving the second service duration returned by the service server, the service duration on the service document to be submitted is updated from the first service duration to the second service duration.

[0158] It is understood that, upon receiving the second service duration returned by the service server, the client can change the service duration on the service document to be submitted from the first service duration to the second service duration, and display the second service duration on the document display interface. Figure 2b Taking the business document 21c in the corresponding embodiment as an example, Figure 2b As shown, after receiving the duration 21i returned by the service server, the client 21b can update the service duration on the service receipt 21c from the original duration 21f to the duration 21i, thereby ensuring the consistency and accuracy of the service duration.

[0159] It is understandable that, optionally, in addition to modifying the business start and end time in the business document to be submitted, the business request object (such as the aforementioned user 1) can also modify the business duration on the business document to be submitted. For example, the client can respond to the duration change operation on the business document to be submitted and change the business duration on the business document to be submitted from the first business duration (such as the aforementioned business duration E1) to the third business duration (such as business duration E3); then, when submitting the business document to be submitted, the business server will also verify the business duration submitted by the business request object.

[0160] For example, when the business start and end time in the business document to be submitted remains as the first business start and end time (such as the aforementioned business start and end time D1), and the business duration on the business document to be submitted is changed from the first business duration (such as the aforementioned business duration E1) to the third business duration (such as the aforementioned business duration E3), the client can respond to the document submission operation for the business document to be submitted, and send the first business start and end time and the third business duration to the business server, so that the business server compares the first business duration with the third business duration when calculating the first business duration (such as the aforementioned business duration E1) corresponding to the first business start and end time; when the duration comparison is inconsistent, the first business duration is returned to the client; conversely, optionally, when the duration comparison is consistent, the business server will notify the client that the business document to be submitted has been submitted successfully.

[0161] For another example, when the business start and end time in the business document to be submitted is changed from the first business start and end time (such as the aforementioned business start and end time D1) to the second business start and end time (such as the aforementioned business start and end time D2), and the business duration on the business document to be submitted is changed from the first business duration (such as the aforementioned business duration E1) to the third business duration (such as the aforementioned business duration E3), the client can respond to the document submission operation for the business document to be submitted, and send the second business start and end time and the third business duration to the business server, so that the business server compares the second business duration with the third business duration when calculating the second business duration (such as the aforementioned business duration E2) corresponding to the second business start and end time; when the duration comparison is inconsistent, the second business duration is returned to the client; conversely, optionally, when the duration comparison is consistent, the business server will notify the client that the business document to be submitted has been submitted successfully.

[0162] It is understandable that, optionally, the business request object may also not modify the business start and end time and business duration on the business document to be submitted (i.e., directly submit the business document to be submitted). Then, when submitting the business document to be submitted, the business server will also verify the business duration submitted by the business request object. For example, when the business start and end time in the business document to be submitted is the first business start and end time (such as the aforementioned business start and end time D1), and the business duration on the business document to be submitted is the first business duration (such as the aforementioned business duration E1), the client can respond to the document submission operation for the business document to be submitted, send the first business start and end time and the first business duration to the business server, so that the business server compares the first business duration with the first reference business duration when calculating the first reference business duration (such as business duration E4) corresponding to the first business start and end time; optionally, when the duration comparison is inconsistent, the first reference business duration is returned to the client; conversely, optionally, when the duration comparison is consistent, the business server will notify the client that the business document to be submitted is submitted successfully.

[0163] It is understandable that for business documents that are directly submitted without modifying the business start and end time and business duration, or business documents that are submitted after modifying any one or more of the business start and end time and business duration, the business server can verify the submitted business duration, that is, after calculating the corresponding business duration through the currently submitted business start and end time, the business duration calculated by the business server is compared with the business duration submitted by the client. If the duration comparison is inconsistent, it means that the business request object submitted the document too quickly, and the submitted business duration is incorrect at this time. It is necessary to further use the business duration calculated by the business server as a benchmark to correct the submitted business duration. Optionally, the business request object can also be prompted that the business duration has been updated; if the duration comparison is consistent, it means that the business duration submitted at this time is the same as the business duration calculated by the business server, so the client can directly display that the document has been submitted successfully. In this way, the duration verification is performed for all submitted business documents, which can ensure the accuracy of the business duration on the business document without the need for manual verification of the business duration, which helps to improve the efficiency of business approval.

[0164] As can be seen from the above, the embodiment of the present application provides a solution for ensuring the consistency of duration calculation in the document submission scenario. The core of the solution is to perform a secondary check on the business duration on the business document to be submitted, that is, when a business document (such as the aforementioned business document to be submitted) is submitted through the front-end client, the back-end business server can recalculate the corresponding business duration according to the business start and end time (such as the aforementioned second business start and end time) passed in by the client, and then the business duration (such as the aforementioned second business duration) calculated by the business server at this time can be compared with the business duration (such as the aforementioned first business duration) passed in by the client, and when the duration comparison is inconsistent, the business duration (such as the aforementioned second business duration) calculated by the business server can be used as a benchmark to correct the business duration on the business document displayed by the aforementioned client, so that the consistency and accuracy of the business duration can be guaranteed when submitting the business document. In addition, since the consistency and accuracy of the business duration are guaranteed, and there is no need to manually check the business duration, the required business application duration can be reduced, thereby improving the efficiency of business approval. In addition, the logical integrity of the document submission process can also be enhanced.

[0165] For further information, see Figure 4 , Figure 4 FIG. 2 is a flow chart of a data processing method provided in an embodiment of the present application. Figure 4 As shown, the method can be executed by a business server, for example, the business server can be the above Figure 1 The service server 100 is shown. The method may specifically include the following steps S201 to S203.

[0166] Step S201, when the first service start and end time is displayed in the service document to be submitted, the first service start and end time sent by the client is obtained, the first service duration is calculated according to the first service start and end time, and the first service duration is returned to the client, so that when the client receives the first service duration, the service duration on the service document to be submitted is configured as the first service duration;

[0167] It can be understood that when the first business start and end time is displayed in the business document to be submitted, the client can send the first business start and end time to the business server. When the business server receives the first business start and end time sent by the client, it can calculate the corresponding first business duration through the first business start and end time, and return the first business duration to the client. Correspondingly, when the client receives the first business duration, it can configure the business duration on the business document to be submitted as the first business duration. Among them, the first business start and end time includes the first business start time and the first business end time. When the business duration on the business document to be submitted is configured as the first business start and end time, the first business start and end time can be displayed in the business document to be submitted. The specific configuration method can be found in the above Figure 3 The description of configuring the start and end time of the first service in step S101 of the corresponding embodiment will not be repeated here.

[0168] In one embodiment, data can be exchanged between the client and the business server through a small program end for document processing. The advantage of this is that the business front-end and the business back-end are isolated from each other through the network through the small program end, which can reduce the frequent interference of a large number of interactive operations generated by the business request objects on the business front-end to the business back-end, thereby ensuring the data storage security and normal calculation logic of the business back-end.

[0169] Based on this, optionally, when the mini program side sends the first business request to the business server, the business server can obtain the first business request sent by the mini program side; wherein, the mini program side is called by the client when the first business start and end time is displayed in the business document to be submitted; the first business request is generated based on the first business start and end time when the mini program side receives the first business start and end time sent by the client; it can be understood that when the business document to be submitted is determined by a related business document template (for example, the aforementioned business document 21c can be determined by an annual leave document template), the first business request also carries the business to be submitted. The template identifier of the business document template corresponding to the document, the template identifier is used to uniquely identify the corresponding business document template; that is, when the first business start and end time is displayed in the business document to be submitted, the client can call the mini program end, send the first business start and end time and the template identifier of the corresponding business document template to the mini program end, and when the mini program end receives the first business start and end time and the template identifier, it can package the received first business start and end time and the template identifier into a first request data packet, and write the first request data packet into the first business request, and then send the first business request to the business server. It can be understood that the mini program end is responsible for logically processing the data generated by the client during the interaction process (such as the aforementioned first business start and end time and template identifier), which can reduce the data processing pressure on the client side and ensure the smoothness of the client operation to a certain extent, thereby improving the interactive experience between the business request object and the client.

[0170] In addition, optionally, when the mini program end directly forwards the received template identifier and the first service start and end time to the service server, the service server can obtain the template identifier and the first service start and end time forwarded by the mini program end. The specific method of data transmission is not limited here.

[0171] Among them, the business document template corresponding to the above-mentioned business documents to be submitted can be any one of the document templates such as leave document template, business trip document template, out-of-office document template, overtime document template, shift transfer document template, dispatch document template, attendance card replacement document template, regularization document template, home office document template, venue reservation document template, item collection document template, reimbursement document template, and event application document template, without restriction here.

[0172] Furthermore, the business server can obtain the template identifier from the first business request (specifically, it can be obtained by parsing the first request data packet in the first business request), and obtain the template data information corresponding to the relevant business document template from the business database according to the template identifier (including the template identifier); then, the first business duration can be calculated based on the template data information and the first business start and end time in the first business request, and the first business duration is returned to the mini program end, so that the mini program end returns the first business duration to the client. For example, still using the above Figure 2a Taking the business document 21c in the corresponding embodiment as an example, the business document 21c can be determined by the annual leave document template, and the time 21d and the time 21e can be used as the start and end time of the first business. Then the business server 20B can obtain the template data information M corresponding to the annual leave document template from the business database, and then the duration 21f can be calculated based on the obtained template data information and the time 21d and the time 21e. It can be understood that the template data information corresponding to all business document templates can be stored in the business database, so the client only needs to transmit the relevant template identifier, and the business server can obtain the corresponding template data information from the business database according to the template identifier, thereby reducing the data storage pressure on the client and the business server, saving the data transmission overhead, and improving the security of data storage.

[0173] Among them, the business server and the business database both belong to the business backend, and the business server can exchange data with the business database; optionally, the business database can be deployed on the business server, which makes it easier for the business server to read and write data in the business database, thereby improving data reading efficiency; optionally, the business database can also be deployed on other physical servers independent of the business server, which can separate data storage and data processing, thereby ensuring the stability of the business. The embodiments of the present application do not limit the deployment method of the business backend.

[0174] In an embodiment of the present application, the business server may include a service end (also referred to as an Svr end) and a logic end (also referred to as a Logic end), and the two may interact with the aforementioned business client as a whole. Among them, the service end includes a duration calculation interface, which is used to provide external business duration calculation services, and may include multiple interfaces involved in business duration calculation, such as a calendar reading interface, a time reading interface, a clock-in information reading interface, etc., so as to meet various duration calculation logics; the service end is used to receive the first business request sent by the mini-program end through the duration calculation interface, and transmit the first business request to the logic end; that is, after the mini-program end obtains the first business request, it can call the duration calculation interface of the service end, send the first business request to the service end, and then the service end transmits the first business request to the logic end for processing. Among them, the logic end is used to obtain the template data information corresponding to the aforementioned business document template from the business database according to the template identifier carried in the first business request when receiving the first business request.

[0175] It should be noted that, optionally, the service end and the logic end can be deployed on the same physical server, that is, the business server at this time can be an independent physical server, which is conducive to data interaction between the service end and the logic end; optionally, the service end and the logic end can be deployed on different physical servers, that is, the business server at this time can be a server cluster or distributed system composed of multiple physical servers, which can avoid the direct paralysis of the entire business system in the event of an unexpected accident (such as a power outage on the server), and can better maintain business stability when the business volume is large. The embodiments of the present application do not limit the deployment method of the business server.

[0176] It can be understood that the above template data information may include business configuration parameters, which refers to the collective name of all parameters (or business rules) related to duration calculation configured for the target business. For different businesses, the same or different business configuration parameters can be added to the corresponding business document template. Common business configuration parameters include any one or more of the leave type, time scale parameters, duration calculation parameters, unit conversion parameters, vacation balance, clock-in rules, object clock-in information, overtime rules, card re-stuffing rules, venue opening hours, item collection rules, etc. Different combinations can represent different duration calculation logics, and the specific content of the business configuration parameters is not limited here.

[0177] Among them, the leave type is used to indicate the type of leave applied for by the business request object, including but not limited to annual leave, personal leave, sick leave, adjustment leave, marriage leave, maternity leave, paternity leave, prenatal check-up leave, bereavement leave, etc. The time scale parameter is used to indicate the time unit used when calculating the business duration, for example, it can be set to calculate by day / hour. The duration calculation parameter is used to indicate the date type selected when calculating the business duration. For example, if it is set to calculate by natural day, no national statutory holidays and weekends will be deducted when calculating the business duration; if it is set to calculate by working day, national statutory holidays and weekends will be deducted when calculating the business duration. It can be understood that in this case, when calculating the duration, the relevant interface (such as the calendar reading interface) can be called to determine whether it is a natural day or a working day. The unit conversion parameter is used to indicate the conversion rule between two different time units. For example, if it is set to "1 day = 24 hours", the business hours will be converted to hours according to this rule; if the punch-in rule is configured, it can be calculated according to the working hours. For example, when the punch-in rule indicates that the working hours of a day are 8 hours, the corresponding unit conversion parameter can be set to "1 day = 8 hours". The holiday balance refers to the balance of a certain holiday currently owned by the business request object. For example, as mentioned above Figure 2a As shown in the interface 203, user 21a still has 9 days of annual leave remaining.

[0178] Among them, the punch-in rule (also known as the attendance rule) refers to the rules formulated by the enterprise / institution / organization where the business request object is located for attendance management, which is used to manage the attendance of internal members. It may include punch-in rule types (for example, fixed get off work and off-duty (that is, everyone punches in at the same time), scheduled get off work and off-duty (that is, different personnel punch in according to their own schedules), free get off work and off-duty (no time limit, you can punch in at any time), etc.), scheduled working hours (for example, the scheduled working time is 8:30, the scheduled off-duty time is 17:30, and optionally, a lunch break can be included between the two), added special dates (including dates where punch-in is required (such as designated make-up shift dates) and dates where punch-in is not required), etc. The object punch-in information refers to the information collected when the business request object punches in, which may include the actual punch-in time, punch-in area and other information of the business request object. It can be understood that the object punch-in information can be collected through online punch-in methods (such as punching in through the punch-in function provided by the client) or offline punch-in methods (such as punching in with fingerprints or swiping cards through a punch-in attendance machine). The specific punch-in method is not limited here; among them, for the online punch-in method, after the business request object punches in through the punch-in function provided by the client, the client will directly transmit the object punch-in information obtained at this time to the business database for storage; for the offline punch-in method, the business request object punches in through the punch-in function provided by the client. After the object clocks in or swipes the card through the clock-in machine, the obtained object clock-in information can be exported from the clock-in machine, and then stored in the back-end business database; wherein, optionally, the object clock-in information can be exported from the clock-in machine at a specified export time, and deleted locally on the clock-in machine after the data is successfully exported. For example, assuming that the export time is set to 4 a.m. every day, the object clock-in information stored in the clock-in machine before this time (such as the actual clock-in time at 00:10 a.m.) can be counted as the clock-in data of the previous day, thereby reducing the situation where the clock-in machine counts missing clock-in information to a certain extent.

[0179] Among them, overtime rules refer to the rules formulated by the enterprise / institution / organization where the business request object is located for overtime, which are used to manage the overtime of internal members. For example, different overtime rules can be set according to working days, rest days, and holidays. The calculation methods of overtime rules may include but are not limited to calculation based on approval time (that is, after the overtime application is approved, the overtime time is recorded according to the approval time), calculation based on punch-in time (that is, no approval is required, and the overtime time is automatically calculated based on the actual punch-in time), and calculation based on approval and punch-in time (that is, within the approval period, the overtime time is calculated based on the actual punch-in time). Card-replacement rules refer to the rules formulated by the enterprise / institution / organization where the business request object is located for attendance card-replacement, which are used to manage the card-replacement of internal members, and may include the allowed card-replacement time (for example, card-replacement is only allowed during normal working hours on weekdays), the maximum number of card-replacement times, etc. Venue opening hours are used to indicate the opening hours of public places such as conference rooms and classrooms. For example, the opening hours of a conference room can be set to 8:00-22:00 on weekdays. Item collection rules refer to the usage rules for target items such as office equipment, production equipment, signatures, and transportation vehicles configured by the enterprise / institution / organization to which the business request is directed. They may include the permitted usage time and permitted usage area of ​​the target items. For example, the permitted usage time of a car can be set to working days.

[0180] It can be understood that for the target business, any one or more parameters can be selected from the above-listed parameters according to actual needs, and combined into business configuration parameters associated with the target business. In the embodiment of the present application, when the target business is a business related to holidays or attendance (such as leave, business trips, going out, overtime, shift changes, assignments, attendance card replacement, etc.), the corresponding business configuration parameters can also be called leave and attendance configuration parameters. It can be seen that the embodiment of the present application can support the addition of rich business configuration parameters in the business document template, so that a variety of duration calculation logics can be implemented to meet different business needs.

[0181] Among them, the first service start and end time include the first service start time and the first service end time; the service server calculates the first service duration based on the template data information and the first service start and end time, and returns it to the mini program end. The specific process can be: obtain the service configuration parameters in the template data information through the logic end, and then calculate the duration according to the service configuration parameters, the first service start time and the first service end time to obtain the first service duration; then, when the first service duration is returned to the server end through the logic end, the first service duration can be returned to the mini program end through the server end. For example, still using the above Figure 2aTake the business document 21c in the corresponding embodiment as an example. The business document 21c can be determined by the annual leave document template, and the time 21d and the time 21e can be used as the first business start and end time. When the business server 20B obtains the template data information M corresponding to the annual leave document template from the business database, the business configuration parameters N for the annual leave can be obtained from the template data information M (for example, the time scale parameters, duration calculation parameters, unit conversion parameters configured for the annual leave by the enterprise A where the user 21a is located, and the punch-in rules of the enterprise A, the actual punch-in time of the user 21a, etc.), and then the duration 21f (i.e., the first business duration) can be calculated based on the business configuration parameters N and the time 21d and the time 21e. Among them, different business configuration parameters will correspond to different duration calculation logics, which are not listed here one by one. In addition, the logic end is responsible for logic processing, and the service end provides an external interface, transparently transmits business requests and feedback response information. The two have clear division of labor and cooperate with each other. While maintaining business stability, the pressure on each part in data processing can be reduced, thereby improving the business approval efficiency of the entire system to a certain extent.

[0182] For ease of understanding, the embodiments of the present application will take several different business scenarios as examples to illustrate the specific process of duration calculation.

[0183] In one implementation, when the target business is a leave business, the business document to be submitted is a leave application document, and the business document template corresponding to the business document to be submitted is a leave document template. For the sake of distinction, the present application embodiment may refer to the business configuration parameters contained in the template data information corresponding to the leave document template as the first type of business configuration parameters. The first type of business configuration parameters can be used to represent the duration calculation logic in the leave scenario. For ease of understanding, please refer to Figure 5 , Figure 5 Schematic diagram of a leave request form template provided in the embodiment of the present application. Figure 5As shown, interface 501 is an exemplary template setting interface, on which template data information of the leave document template can be displayed, including template name (such as "AAA"), template icon, template grouping information (such as grouping as "other"), control name corresponding to the added control (such as "leave type"), etc., wherein interface 501 also displays an exemplary first-category business configuration parameter, specifically including leave type (such as parameter 501a), first time scale parameter (such as parameter 501b) and first duration calculation parameter (such as parameter 501c), wherein leave types include annual leave, personal leave, sick leave, adjustment leave, marriage leave, maternity leave, paternity leave, etc.; the first time scale parameter is used to indicate the time unit used when calculating the leave duration (i.e., a type of business duration), such as parameter 501b can be set to be calculated by day or by hour; the first duration calculation parameter is used to indicate the date type selected when calculating the leave duration, such as parameter 501c can be set to be a natural day or a working day. It is understandable that different time scale parameters and duration calculation parameters can be set for different leave types. Therefore, the leave duration can be calculated through information such as leave type, first time scale parameter, first duration calculation parameter, leave start time (i.e., a type of business start time), leave end time (i.e., a type of business end time). In addition, the first type of business configuration parameters may also include other parameters, such as clock-in rules, actual clock-in time of the business request object, etc., which are not limited here.

[0184] Among them, the business configuration parameters in the embodiments of the present application can be configured through the template setting interface exemplified above, or through other interfaces or functions on the client. For example, the punch-in rules can be set through the punch-in rules setting interface on the client, which will not be listed one by one here.

[0185] For example, suppose user X1 needs to take annual leave, and fills in the leave start time T1 (for example, 2023 / 5 / 5 morning) and the leave end time T2 (for example, 2023 / 5 / 9 afternoon) on the corresponding annual leave application document Y1. As shown in interface 501, assuming that the time scale parameter configured for the annual leave indicates calculation by day, and the duration calculation parameter indicates calculation by natural day, the corresponding leave duration can be calculated to be 5 days.

[0186] For another example, suppose user X1 needs to take a personal leave, and fills in the leave start time T3 (for example, 2023 / 6 / 5 10:00) and the leave end time T4 (for example, 2023 / 6 / 5 15:30) on the corresponding personal leave application document Y2. As shown in interface 501, assuming that the time scale parameter configured for the personal leave indicates calculation by hours, and the duration calculation parameter indicates calculation by working days, without considering other parameters (such as punch-in rules, actual punch-in time, etc.), the corresponding leave duration can be calculated as 5.5 hours; optionally, assuming that a punch-in rule is also configured, and the punch-in rule is set with a scheduled working time (for example, 09:00-18:00 on working days 0), which also includes a 2-hour lunch break from 12:00 to 14:00. When calculating the leave duration, it is necessary to consider whether the leave start time T3 and the leave end time T4 include the scheduled working time, and it is also necessary to deduct the lunch break, so as to calculate the corresponding leave duration as 3.5 hours. The leave duration can also be calculated based on the actual clock-in time of user X1, for example, considering whether the leave start time T3 and the leave end time T4 include the actual clock-in time and the actual clock-out time of user X1.

[0187] In one implementation, when the target business is a business trip, the business document to be submitted is a business trip application document, and the business document template corresponding to the business document to be submitted is a business trip document template. For the sake of distinction, the present application embodiment may refer to the business configuration parameters contained in the template data information corresponding to the business trip document template as the second type of business configuration parameters, which can be used to represent the duration calculation logic in the business trip scenario. For ease of understanding, please refer to Figure 6 , Figure 6 Schematic diagram of a business trip document template provided in an embodiment of the present application. Figure 6As shown, interface 601 is an exemplary template setting interface, on which template data information of the business trip document template can be displayed, including template name (such as "BBB"), template icon, template grouping information (such as grouping as "other"), control name corresponding to the added control (such as "business trip"), etc., wherein interface 601 also displays an exemplary second-category business configuration parameter, specifically including a second time scale parameter (such as parameter 601a), a second duration calculation parameter (such as parameter 601b) and a first unit conversion parameter (such as parameter 601c), wherein the second time scale parameter is used to indicate the time unit used when calculating the business trip duration (i.e., a type of business duration), such as parameter 601a can be set to be calculated by day; the second duration calculation parameter is used to indicate the date type selected when calculating the business trip duration, such as parameter 601b can be set to natural day; the first unit conversion parameter is used to indicate the conversion rule between two different time units, such as parameter 601c can be set to "1 day = 24 hours". Based on this, the business trip duration can be calculated through the second time scale parameter, the second duration calculation parameter, the first unit conversion parameter, the business trip start time (i.e., a type of business start time), the business trip end time (i.e., a type of business end time), etc. In addition, the second type of business configuration parameters may also include other parameters, such as punch-in rules, the actual punch-in time of the business request object, etc., which are not limited here.

[0188] For example, suppose user X2 needs to go on a business trip, and fills in the business trip start time T5 (for example, 2023 / 7 / 1 afternoon) and the business trip end time T6 (for example, 2023 / 7 / 5 afternoon) on the corresponding business trip application document Y3. As shown in interface 601, suppose the time scale parameter configured for the business trip service indicates that it is calculated by day, the duration calculation parameter indicates that it is calculated by natural day, and the unit conversion parameter indicates that 1 day is equal to 24 hours. Without considering other parameters (such as punch-in rules, actual punch-in time, etc.), the corresponding business trip duration can be calculated as 4.5 days. When the business trip duration is converted into duration data in hours, it can be calculated that the business trip duration is 4.5*24=108 hours; optionally, assuming that a punch-in rule is also configured, it is also necessary to consider whether the above-mentioned business trip start time T5 and business trip end time T6 include the scheduled working hours (such as 09:00-18:00 on weekdays) when calculating the business trip duration. The business trip duration can also be calculated based on the actual punch-in time of user X2, such as considering whether the business trip start time T5 and business trip end time T6 include the actual work punch-in time and actual leave work punch-in time of user X2.

[0189] In one implementation, when the target service is an outbound service, the service document to be submitted is an outbound application document, and the service document template corresponding to the service document to be submitted is an outbound document template. For the sake of distinction, the service configuration parameters contained in the template data information corresponding to the outbound document template may be referred to as the third-category service configuration parameters in this application embodiment. The third-category service configuration parameters may be used to represent the duration calculation logic in an outbound scenario. For ease of understanding, please refer to Figure 7 , Figure 7 Schematic diagram of an outbound document template provided in the embodiment of the present application. Figure 7 As shown, interface 701 is an exemplary template setting interface, on which template data information of the outgoing document template can be displayed, including template name (such as "CCC"), template icon, template grouping information (such as grouping as "other"), control name corresponding to the added control (such as "outgoing"), etc., wherein interface 701 also displays an exemplary third category of business configuration parameters, specifically including a third time scale parameter (such as parameter 701a), a third duration calculation parameter (such as parameter 701b) and a second unit conversion parameter (such as parameter 701c), wherein the third time scale parameter is used to indicate the time unit used when calculating the outgoing duration (i.e., a type of business duration), such as parameter 701a can be set to calculate in hours; the third duration calculation parameter is used to indicate the date type selected when calculating the outgoing duration, such as parameter 701b can be set to working day; the second unit conversion parameter is used to indicate the conversion rule between two different time units, such as parameter 701c can be set to "1 day = 8 hours". Based on this, the out-of-office duration can be calculated through the third time scale parameter, the third duration calculation parameter, the second unit conversion parameter, the out-of-office start time (i.e., a type of service start time), the out-of-office end time (i.e., a type of service end time), and other information. In addition, the third type of service configuration parameters may also include other parameters, such as clock-in rules, the actual clock-in time of the service request object, etc., which are not limited here.

[0190] For example, suppose user X3 needs to go out, and fills in the out-of-town start time T7 (for example, 2023 / 7 / 3 10:00) and out-of-town end time T8 (for example, 2023 / 7 / 3 10:00) on the corresponding out-of-town application form Y4. 12:00), as shown in interface 701, assuming that the time scale parameter configured for the out-of-office service indicates that it is calculated in hours, the duration calculation parameter indicates that it is calculated in working days, and the unit conversion parameter indicates that 1 day is equal to 8 hours. Without considering other parameters (such as clock-in rules, actual clock-in time, etc.), the corresponding out-of-office duration can be calculated to be 2 hours. When it is necessary to convert the out-of-office duration into duration data in days, it can be calculated that the out-of-office duration is 2÷8=0.25 days; optionally, assuming that a clock-in rule is also configured, then when calculating the out-of-office duration, it is also necessary to consider whether the above-mentioned out-of-office start time T7 and out-of-office end time T8 include the scheduled working hours (such as 08:00-18:00 on working days). The out-of-office duration can also be calculated based on the actual clock-in time of user X3, such as considering whether the out-of-office start time T7 and the out-of-office end time T8 include the actual clock-in time and the actual clock-in time of user X3.

[0191] In one implementation, when the target business is an overtime business, the business document to be submitted is an overtime application document, and the business document template corresponding to the business document to be submitted is an overtime document template. For the sake of distinction, the present application embodiment may refer to the business configuration parameters contained in the template data information corresponding to the overtime document template as the fourth type of business configuration parameters. The fourth type of business configuration parameters can be used to represent the duration calculation logic in the overtime scenario. For ease of understanding, please refer to Figure 8 , Figure 8 Schematic diagram of an overtime document template provided in the embodiment of the present application. Figure 8As shown, interface 801 is an exemplary template setting interface, on which template data information of the overtime document template can be displayed, including template name (such as "DDD"), template icon, template grouping information (such as grouping as "other"), control name corresponding to the added control (such as "overtime"), etc., wherein interface 801 also displays an exemplary fourth category of business configuration parameters, specifically including a fourth time scale parameter (such as parameter 801a), a fourth duration calculation parameter (such as parameter 801b) and a third unit conversion parameter (such as parameter 801c), wherein the fourth time scale parameter is used to indicate the time unit used when calculating the overtime duration (i.e., a type of business duration), such as parameter 801a can be set to calculate in hours; the fourth duration calculation parameter is used to indicate the date type selected when calculating the overtime duration, such as parameter 801b can be set to natural day; the third unit conversion parameter is used to indicate the conversion rule between two different time units, such as parameter 801c can be set to "1 day = 24 hours". Based on this, the overtime duration can be calculated through the fourth time scale parameter, the fourth duration calculation parameter, the third unit conversion parameter, the overtime start time (i.e., a type of business start time), the overtime end time (i.e., a type of business end time), etc. In addition, the fourth type of business configuration parameters may also include other parameters, such as overtime rules, clock-in rules, actual clock-in time of the business request object, etc., which are not limited here.

[0192] For example, assuming that user X4 needs to apply for overtime, and fills in the overtime start time T9 (such as 2023 / 7 / 3 18:00) and the overtime end time T10 (such as 2023 / 7 / 3 22:00) on the corresponding overtime application document Y5, as shown in interface 801, assuming that the time scale parameter configured for the overtime business indicates calculation by hours, the duration calculation parameter indicates calculation by natural days, and the unit conversion parameter indicates that 1 day is equal to 24 hours. Without considering other parameters (such as clock-in rules, actual clock-in time, etc.), the corresponding overtime duration can be calculated to be 4 hours. When the overtime duration needs to be converted into duration data in days, the overtime duration can be calculated to be 4÷24=0.17 days; Optionally, assuming that overtime rules are configured, the specified overtime rule calculation method needs to be used when calculating the overtime hours, which may also involve punch-in rules. For example, when calculating the overtime hours, it is necessary to consider whether the above-mentioned overtime start time T9 and overtime end time T10 include the scheduled working hours (such as 08:00-18:00 on working days). It may also be necessary to calculate the overtime hours based on the actual punch-in time of user X4, such as considering whether the overtime start time T9 and overtime end time T10 include the actual on-duty punch-in time and actual off-duty punch-in time of user X4.

[0193] In one embodiment, when the target service is a venue reservation service (such as booking a conference room), the service document to be submitted is a venue reservation application document (for example, see the above Figure 2c In the corresponding embodiment, the business document 21j) corresponds to the business document to be submitted. The business document template corresponding to the venue reservation document template is a venue reservation document template. For the sake of distinction, the present application embodiment may refer to the business configuration parameters contained in the template data information corresponding to the venue reservation document template as the fifth type of business configuration parameters. The fifth type of business configuration parameters can be used to represent the duration calculation logic in the venue reservation scenario. For ease of understanding, please refer to Fig. 9 , Fig. 9 Schematic diagram of a venue reservation document template provided in an embodiment of the present application. Fig. 9 As shown, interface 901 is an exemplary template setting interface, on which template data information of a venue reservation document template can be displayed, including a template name (such as "EEE"), a template icon, template grouping information (such as grouping as "other"), a control name corresponding to an added control (such as "conference room reservation"), etc., wherein interface 901 also displays an exemplary fifth category of business configuration parameters, specifically including a fifth time scale parameter (such as parameter 901a), a fifth duration calculation parameter (such as parameter 901b) and a fourth unit conversion parameter (such as parameter 901c), wherein the fifth time scale parameter is used to indicate the time unit used when calculating a reservation duration (i.e., a type of business duration), such as parameter 901a can be set to be calculated in hours; the fifth duration calculation parameter is used to indicate the date type selected when calculating the reservation duration, such as parameter 901b can be set to a working day; the fourth unit conversion parameter is used to indicate a conversion rule between two different time units, such as parameter 901c can be set to "1 day = 24 hours". Based on this, the scheduled duration can be calculated through the fifth time scale parameter, the fifth duration calculation parameter, the fourth unit conversion parameter, the scheduled start time (i.e., a type of service start time), the scheduled end time (i.e., a type of service end time), etc. In addition, the fifth type of service configuration parameters may also include other parameters, such as venue opening hours, etc., which are not limited here.

[0194] For example, suppose user X5 needs to book a conference room and fills in the booking start time T11 (e.g., 2023 / 7 / 3 14:00) and booking end time T12 (e.g., 2023 / 7 / 3 14:00) on the corresponding venue booking application form Y6. 15:00), as shown in interface 901, assuming that the time scale parameter configured for conference room reservation indicates calculation in hours, the duration calculation parameter indicates calculation in working days, and the unit conversion parameter indicates that 1 day is equal to 24 hours. Without considering other parameters (such as venue opening hours, etc.), the corresponding scheduled duration can be calculated to be 1 hour. When it is necessary to convert the scheduled duration into duration data in days, the scheduled duration can be calculated to be 1÷24=0.04 days; optionally, assuming that the venue opening hours are also configured, then when calculating the scheduled duration, it is also necessary to consider whether the above-mentioned scheduled start time T11 and scheduled end time T12 include the venue opening hours. For example, assuming that the opening hours of the conference room are 08:00-12:00 and 14:30-18:00 on working days, the time when the conference room is not open (i.e., half an hour between 14:00-14:30) needs to be deducted when calculating the scheduled duration, so that the final scheduled duration is 0.5 hours.

[0195] It can be understood that in some cases, the actual calculated service duration may be a decimal. In this case, the approximate value can be taken as the final calculation result according to the specified counting retention method. The embodiment of the present application does not limit the specific counting retention method used. For example, rounding, up one method, down one method, truncation method, etc. can be used.

[0196] It can be understood that after the logic end calculates the first business duration through the relevant duration calculation logic, the first business duration can be returned to the server; the server can generate a first business response message based on the first business duration, and return the first business response message carrying the first business duration to the mini program end. Among them, the server can package the received first business duration into a first response data packet, write the first response data packet into the first business response information, and then send the first business response information to the mini program end. Correspondingly, the mini program end can parse the first response data packet in the first business response information to obtain the first business duration, and then send the first business duration to the client, so that when the client receives the first business duration, the business duration on the business document to be submitted is configured as the first business duration, and the first business duration is displayed on the document display interface. It can be understood that the embodiment of the present application can adopt data encapsulation technology to transmit the first business duration to the mini program end in the form of a data packet, which can achieve safe and reliable data transmission and improve data transmission efficiency.

[0197] Optionally, the server may also directly return the first service duration to the mini program end, and forward the first service duration to the client through the mini program end; the embodiment of the present application does not limit the specific method of data transmission.

[0198] Optionally, when the business document to be submitted is customized by the business request object (i.e., not dependent on the business document template, such as a start-up company), the mini program end can package the first business start and end time sent by the client into a first request data packet, and write the first request data packet into the first business request, and then send the first business request to the business server for processing. It can be understood that the first business request at this time does not carry any template identifier. If the business server does not query any relevant duration calculation rules in the business database, the corresponding first business duration can be directly calculated based on the first business start time and the first business end time. Optionally, the mini program end can also directly forward the first business start and end time sent by the client to the business server for processing.

[0199] Step S202: when the service start and end time in the service document to be submitted is changed from the first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains the first service duration, the second service start and end time and the first service duration sent by the client are obtained; the second service start and end time and the first service duration are sent when the client responds to the document submission operation for the service document to be submitted;

[0200] It can be understood that if the business start and end time in the business document to be submitted changes (for example, from the first business start and end time to the second business start and end time), but the business duration on the business document to be submitted does not change accordingly (that is, it still remains the first business duration corresponding to the first business start and end time), if the business document to be submitted is submitted directly, there may be a problem of inconsistent business duration. Based on this, the embodiment of the present application supports the business server to verify the first business duration according to the second business start and end time when receiving the second business start and end time and the first business duration sent by the client.

[0201] It can be understood that when the service start and end time in the service document to be submitted is changed from the first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains the first service duration, the client can respond to the document submission operation for the service document to be submitted and send the second service start and end time and the first service duration to the service server. The specific implementation method can refer to the above Figure 3 The step S102 in the corresponding embodiment will not be described in detail here. Accordingly, the service server can obtain the start and end time of the second service and the duration of the first service sent by the client.

[0202] Among them, the business server may include a service end and a logic end; wherein the service end includes a document submission interface, which is used to provide business document submission services to the outside world. Optionally, when it comes to duration calculation (such as calculating the second business duration corresponding to the second business start and end time), the duration calculation interface may be further called. Based on this, the specific process of obtaining the second business start and end time and the first business duration sent by the client may be: the service end receives the second business request sent by the mini-program end for document processing through the document submission interface, and then transmits the second business request to the logic end; further, the logic end obtains the second business start and end time (such as the aforementioned time 21g and time 21e) and the first business duration (such as the aforementioned duration 21f) from the received second business request. Among them, the mini-program end is called when the client responds to the document submission operation for the business document to be submitted; the second business request is generated based on the second business start and end time and the first business duration when the mini-program end receives the second business start and end time and the first business duration sent by the client. The specific implementation method can be found in the above Figure 3 Step S102 in the corresponding embodiment will not be described in detail here.

[0203] Among them, the second service request carries a second request data packet, and when the logic end receives the second service request, it can parse the second request data packet in the second service request to obtain the start and end time of the second service and the duration of the first service. It can be understood that the embodiment of the present application transmits the start and end time of the second service and the duration of the first service from the applet end to the logic end in the form of a data packet, which can achieve secure and reliable data transmission and improve data transmission efficiency.

[0204] Step S203, calculate the second business duration by the start and end time of the second business, compare the second business duration with the first business duration, and when the duration comparison is inconsistent, return the second business duration to the client, so that when the client receives the second business duration, it will update the business duration on the business document to be submitted from the first business duration to the second business duration.

[0205] It can be understood that the business server can verify the first business duration based on the start and end time of the second business. Specifically, the second business duration can be first calculated according to the start and end time of the second business, and then the second business duration can be compared with the first business duration. The correctness of the business duration input by the client is determined by whether the duration comparison is consistent; if correct, the client is notified that the document has been submitted successfully; otherwise, if incorrect, it needs to be corrected.

[0206] It can be understood that, when the business document to be submitted is determined by the relevant business document template, the second business request also carries the template identifier of the business document template corresponding to the business document to be submitted; then the specific process of the business server performing duration verification can be: when the template identifier is obtained from the second business request through the logic end (specifically, it can be obtained by parsing the second request data packet in the second business request), the template data information corresponding to the aforementioned business document template can be obtained from the business database according to the template identifier, and then the second business duration can be calculated based on the template data information and the second business start and end time in the second business request; further, the second business duration is compared with the first business duration by the logic end; optionally, when the duration comparison is inconsistent, the second business duration can be returned to the server end, and then the second business duration is returned to the mini program end through the server end, so that the mini program end returns the second business duration to the client end. Accordingly, when the client receives the second service duration, the service duration on the service document to be submitted can be updated from the first service duration to the second service duration, thereby solving the problem of inconsistent service duration between the front-end and back-end. The specific implementation method of duration update can be found in the above Figure 3 Step S103 in the corresponding embodiment will not be described in detail here.

[0207] From the above, it can be seen that in the embodiment of the present application, the client, mini-program, server and logic ends each perform their respective functions, which can reduce the data processing pressure and data storage burden of each part of the document processing flow and ensure the stability of the entire system. In addition, while ensuring consistent business duration, the efficiency of successful document submission can be improved, and the logical integrity of the bill of lading process can be enhanced.

[0208] Among them, the aforementioned template data information may include business configuration parameters for the target business; the second business start and end time includes the second business start time and the second business end time; then the specific process of calculating the second business duration based on the template data information and the second business start and end time can be: obtain the business configuration parameters in the template data information through the logic end, and then calculate the duration according to the business configuration parameters, the second business start time and the second business end time to obtain the second business duration. It can be understood that the business configuration parameters here are the same as the business configuration parameters used to calculate the first business duration in the above step S201, so the logic end will also calculate the second business duration through the same duration calculation logic, so as to ensure that the second business duration calculated at this time is correct. Its specific implementation method is similar to the specific process of calculating the first business duration described in the above step S201, and will not be repeated here.

[0209] For example, still based on the above Figure 2bTaking the business document 21c in the corresponding embodiment as an example, the business document 21c can be determined by the annual leave document template, time 21g and time 21e can be used as the second business start and end time, and duration 21f can be used as the first business duration. When the business server 20B obtains the template data information M corresponding to the annual leave document template from the business database, the business configuration parameters N for the annual leave can be obtained from the template data information M (for example, it may include the time scale parameters, duration calculation parameters, unit conversion parameters configured for the annual leave by the enterprise A where the user 21a is located, as well as the punch-in rules of the enterprise A, the actual punch-in time of the user 21a, etc.), and then the duration 21i (i.e., the second business duration) can be calculated based on the business configuration parameters N and time 21g and time 21e, and the duration 21i can be compared with the duration 21f later.

[0210] It can be understood that after the logic end calculates the second service duration through the relevant duration calculation logic, the second service duration can be returned to the server; the server can generate a second service response information based on the second service duration, and return the second service response information carrying the second service duration to the mini program end. Among them, the server can package the received second service duration into a second response data packet, write the second response data packet into the second service response information, and then send the second service response information to the mini program end. Correspondingly, the mini program end can parse the second response data packet in the second service response information to obtain the second service duration, and then send the second service duration to the client, so that when the client receives the second service duration, the service duration on the service document to be submitted is updated from the first service duration to the second service duration, and the second service duration is displayed on the document display interface. It can be understood that the embodiment of the present application can adopt data encapsulation technology to transmit the second service duration to the mini program end in the form of a data packet, which can achieve safe and reliable data transmission and improve data transmission efficiency.

[0211] Optionally, the server may also directly return the received second service duration to the mini program, and forward the second service duration to the client through the mini program. The embodiment of the present application does not limit the specific method of data transmission.

[0212] It can be understood that when the duration comparison is inconsistent, the business server can optionally return a first prompt message to the client. The first prompt message can be generated by the logic end based on the second business duration. After the logic end sends the first prompt message to the server, the server can then send the first prompt message to the client through the mini-program end, and finally the client can display the first prompt message on the document display interface. The first prompt message here can be used to indicate that the business duration on the business document to be submitted has been updated. For example, the first prompt message can be displayed as text information such as "The duration has been updated, please resubmit"; or, the first prompt message can be used to instruct the business request object to postpone submission of the business document to be submitted. For example, the first prompt message can be displayed as text information such as "The system is busy, please wait". The embodiment of the present application does not limit the content and form of the first prompt message.

[0213] In addition, optionally, when the duration comparison is consistent, it means that the business duration transmitted by the client at this time is the same as the business duration calculated by the business server, then the business server can return a second prompt message to the client; the second prompt message can be used to indicate that the business document to be submitted is submitted successfully. Among them, the second prompt message can be generated by the logic end. After the logic end sends the second prompt message to the server end, the server end can send the second prompt message to the client end through the mini program end, and finally the client can display the second prompt message on the document display interface. For example, the second prompt message can be displayed as text information such as "Submission successful". The embodiment of the present application does not limit the content and form of the second prompt message. In addition, the business server can write the business document to be submitted into the business database for storage.

[0214] In the embodiment of the present application, when the service duration on the service document to be submitted is updated from the first service duration to the second service duration, for the convenience of distinction, the service document to be submitted after the duration is updated can be referred to as a service document with duration update. It should be noted that the service start and end time in the service document to be submitted is not changed again, that is, the service start and end time in the service document with duration update is still the second service start and end time. It can be understood that the client can resubmit the service document with duration update. For example, when the service request object clicks to submit the document again, the client can respond to the document submission operation for the service document with duration update and send the service document with duration update to the service server. After successful submission, the service document with duration update can be sent to the second terminal through the service server so that the service approval object associated with the second terminal can approve the service document with duration update. Optionally, after the duration update is completed, the client can also automatically send the service document with duration update to the service server without the need for the service request object to actively submit it again, thereby improving the efficiency of document submission.

[0215] It is understandable that, optionally, after receiving the duration update service document, the service duration (i.e., the aforementioned second service duration) on the duration update service document can be verified again, that is, when the service server calculates the second reference service duration corresponding to the second service start and end time, the calculated second reference service duration can be compared with the second service duration submitted by the client. Obviously, if the duration comparison is consistent at this time, the service server can return a successful submission prompt message to the client; the successful submission prompt message is used to indicate that the duration update service document has been successfully submitted. The embodiment of the present application does not limit the content and form of the successful submission prompt message. In addition, the service server can write the duration update service document into the service database for storage. It can be seen that each time the client submits a service document, regardless of whether the service document has been verified for duration before, the service server can verify the currently submitted service duration. In this way, even if the service request object continuously changes the service start and end time or service duration in the same service document, the consistency and accuracy of the duration of the service document that is finally submitted successfully can be guaranteed, thereby improving the document submission process.

[0216] Optionally, considering the performance consumption of the system by the duration check, the embodiment of the present application also provides a method of reducing repeated checks by using a check mark parameter (i.e., a check mark bit). Each business document can be configured with a corresponding check mark parameter to mark whether the corresponding business document has been checked for duration. For example, when the check mark parameter adopts the "01" mark bit, the check mark parameter value of "1" can indicate that the corresponding business document has been checked for duration; conversely, the check mark parameter value of "0" can indicate that the corresponding business document has not been checked for duration. In addition, the check mark parameter can also be in other forms, which are not limited in the embodiment of the present application.

[0217] Specifically, after comparing the second business duration with the first business duration, the business server can obtain the verification mark parameter (such as parameter Z) associated with the business document to be submitted, and configure the parameter value of the verification mark parameter to be a verified parameter value (for example, configure the parameter value of parameter Z to "1"); wherein the verified parameter value is used to indicate that the business duration on the business document to be submitted has been verified; in addition, the business server can also save the business start and end time (i.e., the second business start and end time) in the business document to be submitted at this time. Further, when the business duration on the business document to be submitted is updated from the first business duration to the second business duration, the business document to be submitted after the duration is updated can be used as a duration update business document. It should be noted that at this time, the business start and end time in the duration update business document is still the aforementioned second business start and end time, and the client can resubmit the duration update business document.

[0218] Further, when the received business document is the duration update business document, the business server may compare the business start and end time in the duration update business document with the second business start and end time in the previously saved business document to be submitted. It can be understood that when the time comparison is consistent, it means that the business start and end time submitted at this time is the same as the business start and end time submitted last time, that is, compared with the business start and end time in the business document to be submitted, the business start and end time in the duration update business document has not changed; further, the business server may obtain a check mark parameter associated with the duration update business document (that is, a check mark parameter associated with the aforementioned business document to be submitted, such as the aforementioned parameter Z with a value of "1"). At this time, the parameter value of the check mark parameter is a checked parameter value, indicating that the corresponding business document (that is, the duration update business document) has been checked for duration, so the business server does not need to check the business duration on the duration update business document again, but can directly return a third prompt information to the client based on the check mark parameter with a checked parameter value, where the third prompt information is used to indicate that the duration update business document is submitted successfully. In addition, the business server can write the duration-updated business document into the business database for storage. It can be seen that when it is determined that the business start and end time in the received business document has not changed and the business duration on the business document has been verified, the business server does not need to re-verify the business document, thereby reducing the performance consumption caused by the duration verification and improving the efficiency of document submission.

[0219] As can be seen from the above, in the document submission scenario, the embodiment of the present application can ensure the consistency of the business duration when submitting the business document by verifying the business duration on the business document to be submitted, solve the related problems caused by inconsistent duration (such as the failure to submit the business document successfully), and at the same time, enhance the logical integrity of the bill of lading process. In addition, when the business duration calculated by the business server is inconsistent with the business duration input by the client, the business duration calculated by the business server can be used as a benchmark to correct the business duration on the business document to be submitted. After the subsequent successful submission of the business document to be submitted, the consistency and accuracy of its business duration are guaranteed, and there is no need to manually verify the business duration, so the required business application time can be reduced, thereby improving the efficiency of business approval.

[0220] For further information, see Fig.10 , Fig.10 This is a flow chart of a data processing method provided in an embodiment of the present application. Figure 3 .like Fig.10As shown, the method can be jointly executed by a client, a mini-program, a server (i.e., an Svr), a logic (i.e., a Logic), and a business database, wherein the client is associated with a business request object and can be run on a first terminal, for example, the first terminal can be the above-mentioned Figure 1 Any terminal device in the terminal cluster shown (for example, terminal device 200a); the client and the applet end are both business front ends; the service end and the logic end are both business servers, for example, the business server can be the above Figure 1 The business server 100 shown in the figure can exchange data with the business database, and both the business server and the business database belong to the business backend. The method can specifically include the following steps:

[0221] Step S301, when the business request object fills in the relevant document information of the document to be submitted on the document display interface of the client, the client can display the document information filled in by the business request object on the document display interface, such as the business start time, business end time, business duration (generally calculated by the business backend, and the business request object can also modify it manually), description attachments, related members, departments, etc.;

[0222] Step S302: After the service request object fills in the service start time (i.e., the aforementioned first service start time) and service end time (i.e., the aforementioned first service end time), the duration calculation link is triggered, and the client can call the mini program end to send the first service start time, the first service end time, and the template identifier of the service document template corresponding to the document to be submitted to the mini program end;

[0223] Step S303, when the mini program receives the first service start time, the first service end time and the template identifier sent by the client, it can generate a first service request (i.e., the calculation parameters are passed in the package Req) based on the first service start time, the first service end time and the template identifier, and then call the duration calculation interface of the server to send the first service request to the server; the calculation parameters here include the first service start time, the first service end time and the template identifier;

[0224] Step S304: After receiving the first service request, the server may transparently transmit the first service request carrying the calculation parameters to the logic end for duration calculation;

[0225] Step S305: After receiving the first service request, the logic end may obtain the first service start time, the first service end time and the template identifier from the first service request, and then send a first data read request to the service database based on the template identifier;

[0226] Step S306: After receiving the first data read request, the business database may obtain the template data information corresponding to the document to be submitted from the business database according to the template identifier carried in the first data read request, and return the obtained template data information to the logic end;

[0227] Step S307, after receiving the template data information returned by the service database, the logic end can calculate the corresponding service duration (i.e., the first service duration) according to the template data information (specifically, the service configuration parameters therein), the first service start time, and the first service end time;

[0228] Step S308, the logic end returns the calculated first service duration to the server end;

[0229] Step S309, the server returns the received first service duration to the mini program end. Specifically, the server may generate first service response information based on the first service duration (i.e., assemble Resp to return the first service duration), and then return the first service response information carrying the first service duration to the mini program end;

[0230] Step S310, the mini program end fills the returned first service duration into the client;

[0231] Step S311, after receiving the first service duration, the client may configure the service duration on the service document to be submitted as the first service duration, and may update the interface data associated with the document display interface, so as to display the first service duration to the service request object on the document display interface;

[0232] It is understandable that the business request object can continuously modify the business start time and business end time in the business document to be submitted, that is, loop the above steps S302 to S311; or directly choose to submit the business document to be submitted, which is not limited here.

[0233] Step S312: When the business request object continues to fill in other required document information (such as application reason, description attachments, etc.) on the document display interface, the client may display the document information filled in by the business request object on the document display interface;

[0234] Step S313, when the business request object clicks to submit the document, the client can respond to the document submission operation for the business document to be submitted (for example, respond to the click operation for the document submission control on the document display interface), trigger the document submission link, and call the mini program end to send the document data information of the business document to be submitted (that is, detailed information of the business document to be submitted, such as document ID, template ID, business start time, business end time, business duration, etc.) to the mini program end;

[0235] It can be understood that after the business request object clicks to submit the document, the business backend needs to verify the consistency of the business duration (also known as duration slicing or duration slicing information) to ensure that the business duration submitted by the business request object is consistent with the business duration calculated by the business backend.

[0236] Step S314, after receiving the document data information sent by the client, the mini program end can package and submit the document data information (i.e., package Req to submit the document); wherein, optionally, if the business start and end time in the business document to be submitted has been changed from the aforementioned first business start and end time (i.e., the first business start time and the first business end time) to the second business start and end time (i.e., the second business start time and the second business end time), and the business duration on the business document to be submitted is still maintained as the first business duration, then the document data information received by the mini program end will include the second business start and end time, the first business duration and the template identifier of the business document template corresponding to the document to be submitted. At this time, the mini program end can generate a second business request based on the document data information, and then call the document submission interface of the server end to send the second business request to the server end;

[0237] Step S315, after receiving the second service request, the server may transparently transmit the second service request carrying the second service start and end time, the first service duration and the template identifier to the logic end for logic processing;

[0238] Step S316: After receiving the second service request, the logic end may obtain the second service start and end time, the first service duration, and the template identifier from the second service request, and then send a second data read request to the service database based on the template identifier;

[0239] Step S317: After receiving the second data read request, the business database may obtain the template data information corresponding to the document to be submitted from the business database according to the template identifier carried in the second data read request, and return the obtained template data information to the logic end;

[0240] Step S318, after receiving the template data information returned by the business database, the logic end can recalculate the corresponding business duration (i.e., the second business duration) according to the template data information (specifically, the business configuration parameters therein), the second business start time, and the second business end time, and then verify whether the business duration on the document to be submitted (i.e., the aforementioned first business duration) matches the business duration calculated by the logic end (i.e., the second business duration), that is, compare the business duration input by the client with the business duration calculated by the logic end to ensure the consistency of the business duration;

[0241] Step S319: After the verification is completed, the logic end may return the matching result (or verification result) to the server end;

[0242] Optionally, when the service duration input by the client is inconsistent with the service duration calculated by the logic end, it means that the service request object may click to submit the document too quickly, resulting in incorrect submitted service duration. It is necessary to use the service duration calculated by the logic end as a benchmark to correct the service duration submitted by the service request object, and transmit the corrected service duration (i.e., the aforementioned second service duration) to the server.

[0243] Optionally, when the service duration input by the client is consistent with the service duration calculated by the logic end, it means that the service duration submitted by the service request object is the same as the service duration calculated by the backend, and the logic end can directly return a prompt message of successful submission to the server (i.e., the aforementioned second prompt message);

[0244] Step S320: After receiving the matching result returned by the logic end, the server end may return relevant data according to the matching result group Resp;

[0245] Optionally, when the matching result indicates that the service duration on the document to be submitted does not match the service duration calculated by the logic end (i.e., the service duration input by the client is inconsistent with the service duration calculated by the logic end), the server end may obtain the second service duration returned by the logic end, and may generate the second service response information based on the second service duration (i.e., the second service duration is returned by assembling Resp);

[0246] Optionally, when the matching result indicates that the business duration on the document to be submitted matches the business duration calculated by the logic end (i.e., the business duration input by the client is consistent with the business duration calculated by the logic end), the server end may obtain the second prompt information returned by the logic end, and may package the second prompt information into a third response data packet, and then write the third response data packet into the third business response information (i.e., the second prompt information is returned by the package Resp); wherein the second prompt information is used to indicate that the business document to be submitted is successfully submitted; optionally, the server end may also directly return the second prompt information returned by the logic end to the mini program end, so that the mini program end returns the second prompt information to the client end;

[0247] Step S321, the server may respond to the mini program's call to the document submission interface in step S314 and return a call result to the mini program; wherein the call result may be the aforementioned second business response information or the third business response information;

[0248] Step S322: When the mini program receives the second service response information as the call result returned by the server, the second service duration in the second service response information can be obtained and returned to the client, so that when the client receives the second service duration returned by the mini program, the service duration on the service document to be submitted is updated from the first service duration to the second service duration; in addition, the client can optionally prompt the service request object that the service duration has been updated;

[0249] Optionally, when the mini program receives a call result returned by the server as a third business response message, it can obtain the second prompt message in the third business response message and return the second prompt message to the client, so that when the client receives the second prompt message returned by the mini program, it displays the second prompt message on the document display interface to prompt that the business request object document has been submitted successfully.

[0250] It is understood that the specific implementation of the above steps S301 to S322 can be found in the above Figure 3 and Figure 4 The description in the corresponding embodiment will not be repeated here.

[0251] From the above, it can be seen that in the document submission scenario, the embodiment of the present application can ensure the consistency of the business duration when submitting the business document by verifying the business duration on the submitted business document, thereby solving the related problems caused by inconsistent duration (such as the failure to submit the business document successfully). At the same time, it enhances the logical integrity of the bill of lading process. In addition, since the consistency and accuracy of the business duration on the business document are guaranteed, there is no need for manual verification of the business duration, so the required business application time can be reduced, thereby improving the efficiency of business approval.

[0252] For further information, see Fig.11 , Fig.11 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. Figure 1 .like Fig.11 As shown, the data processing device 1 can be applied to a client, for example, the client can be the above-mentioned Figure 2a-2c The client 21b in the corresponding embodiment. It should be understood that the data processing device 1 can be a computer program (including program code) running on a computer device (for example, the terminal device 20A where the client 21b is located). For example, the data processing device 1 can be an application software; it can be understood that the data processing device 1 can be used to execute the corresponding steps of the method provided in the embodiment of the present application. Fig.11 As shown, the data processing device 1 may include: a duration configuration module 11, a document submission module 12, and a duration update module 13;

[0253] The duration configuration module 11 is used to receive the first service duration returned by the service server for the first service start and end time when the first service start and end time is displayed in the service document to be submitted, and configure the service duration on the service document to be submitted as the first service duration;

[0254] The document submission module 12 is used for, when the business start and end time in the business document to be submitted is changed from the first business start and end time to the second business start and end time, and the business duration on the business document to be submitted remains the first business duration, in response to the document submission operation for the business document to be submitted, sending the second business start and end time and the first business duration to the business server, so that when the business server calculates the second business duration corresponding to the second business start and end time, it compares the second business duration with the first business duration, and when the duration comparison is inconsistent, returns the second business duration to the client;

[0255] The duration updating module 13 is used to update the service duration on the service document to be submitted from the first service duration to the second service duration when receiving the second service duration returned by the service server.

[0256] The duration configuration module 11 may include: a first editing unit 111, a duration configuration unit 112;

[0257] The first editing unit 111 is used to display the first service start and end time in the service document to be submitted in response to the first time editing operation on the service document to be submitted on the document display interface, and send the first service start and end time to the service server, so that the service server returns the first service duration to the client when calculating the first service start and end time corresponding to the first service start and end time;

[0258] The duration configuration unit 112 is used to configure the service duration on the service document to be submitted as the first service duration when receiving the first service duration returned by the service server, and display the first service duration on the document display interface.

[0259] The specific functional implementation of the first editing unit 111 and the duration configuration unit 112 can be found in the above Figure 3 The description of step S101 in the corresponding embodiment will not be repeated here.

[0260] The document display interface is determined by the business document template corresponding to the business document to be submitted;

[0261] The first editing unit 111 may include: a configuration display subunit 1111 and a data sending subunit 1112;

[0262] The configuration display subunit 1111 is used to configure the business start and end time in the business document to be submitted as the first business start and end time on the document display interface in response to the first time editing operation on the business document to be submitted, and display the first business start and end time in the business document to be submitted;

[0263] The data sending sub-unit 1112 is used to obtain the template identifier of the business document template, and send the template identifier and the first business start and end time to the mini-program end used for document processing, so that the mini-program end sends a first business request to the business server based on the template identifier and the first business start and end time; the first business request is used to instruct the business server to calculate the first business duration based on the template data information and the first business start and end time when obtaining the template data information corresponding to the business document template from the business database through the template identifier, and return the first business duration to the client through the mini-program end.

[0264] The specific functional implementation of the configuration display subunit 1111 and the data sending subunit 1112 can be found in the above Figure 3 The description of step S101 in the corresponding embodiment will not be repeated here.

[0265] The document submission module 12 may include: a second editing unit 121, a document submission unit 122;

[0266] The second editing unit 121 is used to change the business start and end time in the business document to be submitted from the first business start and end time to the second business start and end time on the document display interface in response to the second time editing operation on the business document to be submitted;

[0267] The document submission unit 122 is used to send the template identifier of the business document template, the second business start and end time, and the first business duration to the mini-program end in response to the document submission operation for the business document to be submitted when the business duration on the business document to be submitted remains at the first business duration, so that the mini-program end sends a second business request to the business server based on the template identifier, the second business start and end time, and the first business duration; the second business request is used to instruct the business server to calculate the second business duration based on the template data information and the second business start and end time when obtaining the template data information corresponding to the business document template from the business database through the template identifier, compare the second business duration with the first business duration, and when the duration comparison is inconsistent, return the second business duration to the client through the mini-program end.

[0268] The specific functional implementation of the second editing unit 121 and the document submission unit 122 can be found in the above Figure 3 The description of step S102 in the corresponding embodiment will not be repeated here.

[0269] The specific functional implementation of the duration configuration module 11, the document submission module 12, and the duration update module 13 can be found in the above Figure 3 The description of step S101 to step S103 in the corresponding embodiment will not be repeated here. It should be understood that the description of the beneficial effects obtained by adopting the same method will not be repeated.

[0270] For further information, see Fig.12 , Fig.12 A second structural diagram of a data processing device provided in an embodiment of the present application. Fig.12 As shown, the data processing device 2 can be applied to a business server. For example, the business server can be the above-mentioned Figure 2a-2c The business server 20B in the corresponding embodiment. It should be understood that the data processing device 2 can be a computer program (including program code) running on a computer device (for example, the aforementioned business server 20B), for example, the data processing device 2 can be an application software; it can be understood that the data processing device 2 can be used to execute the corresponding steps of the method provided in the embodiment of the present application. Fig.12 As shown, the data processing device 2 may include: a duration calculation module 21, a document acquisition module 22, and a duration comparison module 23;

[0271] The duration calculation module 21 is used to obtain the first service start and end time sent by the client when the first service start and end time is displayed in the service document to be submitted, calculate the first service duration by the first service start and end time, and return the first service duration to the client, so that the client configures the service duration on the service document to be submitted as the first service duration when receiving the first service duration;

[0272] The document acquisition module 22 is used to acquire the second business start and end time and the first business duration sent by the client when the business start and end time in the business document to be submitted is changed from the first business start and end time to the second business start and end time, and the business duration on the business document to be submitted remains the first business duration; the second business start and end time and the first business duration are sent by the client when responding to the document submission operation for the business document to be submitted;

[0273] The duration comparison module 23 is used to calculate the second business duration through the start and end time of the second business, compare the second business duration with the first business duration, and when the duration comparison is inconsistent, return the second business duration to the client, so that when the client receives the second business duration, it will update the business duration on the business document to be submitted from the first business duration to the second business duration.

[0274] The duration calculation module 21 may include: a first acquisition unit 211, a second acquisition unit 212, and a first calculation unit 213;

[0275] The first acquisition unit 211 is used to acquire a first business request sent by the mini program end for document processing; the mini program end is called by the client when the first business start and end time is displayed in the business document to be submitted; the first business request is generated based on the first business start and end time when the mini program end receives the first business start and end time sent by the client; the first business request carries a template identifier of a business document template corresponding to the business document to be submitted;

[0276] The second acquisition unit 212 is used to acquire the template identifier from the first business request, and acquire the template data information corresponding to the business document template from the business database according to the template identifier;

[0277] The first calculation unit 213 is used to calculate the first service duration based on the template data information and the first service start and end time in the first service request, and return the first service duration to the mini program end, so that the mini program end returns the first service duration to the client.

[0278] The specific functional implementation of the first acquisition unit 211, the second acquisition unit 212, and the first calculation unit 213 can be found in the above Figure 4 The description of step S201 in the corresponding embodiment will not be repeated here.

[0279] Among them, the business server includes a service end and a logic end; the service end includes a duration calculation interface; the service end is used to receive the first business request sent by the mini-program end through the duration calculation interface, and transmit the first business request to the logic end; the logic end is used to obtain template data information corresponding to the business document template from the business database according to the template identifier carried in the first business request when receiving the first business request; the template data information includes business configuration parameters; the first business start and end time includes the first business start time and the first business end time;

[0280] The first calculation unit 213 may include: a duration calculation subunit 2131 and a duration return subunit 2132;

[0281] The duration calculation subunit 2131 is used to obtain the service configuration parameters in the template data information through the logic end, and perform duration calculation according to the service configuration parameters, the first service start time and the first service end time to obtain the first service duration;

[0282] The duration return subunit 2132 is used to return the first service duration to the server through the logic end, and the server generates first service response information based on the first service duration, and returns the first service response information carrying the first service duration to the mini program end.

[0283] The specific functional implementation of the duration calculation subunit 2131 and the duration return subunit 2132 can be found in the above Figure 4 The description of step S201 in the corresponding embodiment will not be repeated here.

[0284] Among them, the business server includes the server side and the logic side; the server side includes the document submission interface;

[0285] The document acquisition module 22 may include: a request receiving unit 221, a third acquisition unit 222;

[0286] The request receiving unit 221 is used for receiving, by the server side through the document submission interface, a second business request sent by the mini program side for document processing, and transmitting the second business request to the logic side; the mini program side is called when the client side responds to the document submission operation for the business document to be submitted; the second business request is generated based on the second business start and end time and the first business duration when the mini program side receives the second business start and end time and the first business duration sent by the client side;

[0287] The third acquisition unit 222 is configured to acquire, by the logic end, the second service start and end time and the first service duration from the received second service request.

[0288] The specific functional implementation of the request receiving unit 221 and the third obtaining unit 222 can be found in the above Figure 4 The description of step S202 in the corresponding embodiment will not be repeated here.

[0289] The second business request carries a template identifier of a business document template corresponding to the business document to be submitted;

[0290] The duration comparison module 23 may include: a second calculation unit 231, a duration comparison unit 232, and a duration return unit 233;

[0291] The second calculation unit 231 is used to obtain the template identifier from the second service request through the logic end, obtain the template data information corresponding to the service document template from the service database according to the template identifier, and calculate the second service duration based on the template data information and the second service start and end time in the second service request;

[0292] The duration comparison unit 232 is used to compare the second service duration with the first service duration by the logic end, and when the duration comparison is inconsistent, return the second service duration to the server end;

[0293] The duration returning unit 233 is used for the server to generate second service response information based on the second service duration, and return the second service response information carrying the second service duration to the mini program end, so that the mini program end returns the second service duration to the client end.

[0294] The template data information includes the service configuration parameters; the second service start and end time includes the second service start time and the second service end time;

[0295] The second calculation unit 231 is specifically configured to obtain the service configuration parameters in the template data information through the logic end, and perform duration calculation according to the service configuration parameters, the second service start time and the second service end time to obtain the second service duration.

[0296] The specific functional implementation of the second calculation unit 231, the duration comparison unit 232, and the duration return unit 233 can be found in the above Figure 4 The description of step S203 in the corresponding embodiment will not be repeated here.

[0297] The data processing device 2 may further include: a first prompting module 24;

[0298] The first prompt module 24 is used to return a first prompt message to the client when the duration comparison is inconsistent.

[0299] The data processing device 2 may further include: a second prompting module 25;

[0300] The second prompt module 25 is used to return a second prompt message to the client when the duration comparison is consistent; the second prompt message is used to indicate that the business document to be submitted is submitted successfully.

[0301] The data processing device 2 may further include: a parameter configuration module 26, a third prompt module 27;

[0302] The parameter configuration module 26 is used to obtain a verification mark parameter associated with the business document to be submitted after comparing the second business duration with the first business duration, configure the parameter value of the verification mark parameter to a verified parameter value, and save the second business start and end time in the business document to be submitted; the verified parameter value is used to indicate that the business duration on the business document to be submitted has been verified;

[0303] The third prompt module 27 is used to use the business document to be submitted after the updated duration as a duration update business document when the business duration on the business document to be submitted is updated from the first business duration to the second business duration; when the received business document is a duration update business document, the business start and end time in the duration update business document is compared with the saved second business start and end time, and when the time comparison is consistent, based on the verification mark parameter with the verified parameter value, a third prompt message is returned to the client; the third prompt message is used to indicate that the duration update business document is submitted successfully.

[0304] Among them, the business document template corresponding to the business document to be submitted includes any one of the leave document template, business trip document template, out-of-office document template and overtime document template; the template data information corresponding to the leave document template includes the first type of business configuration parameters; the first type of business configuration parameters include the leave type, the first time scale parameter and the first duration calculation parameter; the template data information corresponding to the business trip document template includes the second type of business configuration parameters; the second type of business configuration parameters include the second time scale parameter, the second duration calculation parameter and the first unit conversion parameter; the template data information corresponding to the out-of-office document template includes the third type of business configuration parameters; the third type of business configuration parameters include the third time scale parameter, the third duration calculation parameter and the second unit conversion parameter; the template data information corresponding to the overtime document template includes the fourth type of business configuration parameters; the fourth type of business configuration parameters include the fourth time scale parameter, the fourth duration calculation parameter and the third unit conversion parameter.

[0305] The specific functional implementation of the duration calculation module 21, the document acquisition module 22, the duration comparison module 23, the first prompt module 24, the second prompt module 25, the parameter configuration module 26, and the third prompt module 27 can be found in the above Figure 4 The description of steps S201 to S203 in the corresponding embodiment will not be repeated here. It should be understood that the description of the beneficial effects obtained by adopting the same method will not be repeated.

[0306] For further information, see Fig.13 , Fig.13 Schematic diagram of the structure of a computer device provided in an embodiment of the present application. Fig.13As shown, the computer device 1000 can be a terminal device or a server, which will not be limited here. For ease of understanding, this application takes the computer device as a server as an example. The computer device 1000 may include: a processor 1001, a network interface 1004 and a memory 1005. In addition, the computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. Among them, the user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or it may be a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 1005 may optionally also be at least one storage device located away from the aforementioned processor 1001. As Fig.13 As shown, the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a device control application program.

[0307] In such Fig.13 In the computer device 1000 shown in the figure, the network interface 1004 can provide a network communication function; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to execute the above Figure 3 , Figure 4 , Fig.10 The description of the data processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here.

[0308] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the data processing device 1 or the data processing device 2 mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the above-mentioned Figure 3 , Figure 4 , Fig.10The description of the data processing method in the corresponding embodiment will therefore not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application. As an example, computer instructions can be deployed on a computing device for execution, or executed on multiple computing devices located in one location, or, executed on multiple computing devices distributed in multiple locations and interconnected by a communication network, without limitation here.

[0309] The computer-readable storage medium may be the data processing device provided in any of the aforementioned embodiments or the internal storage unit of the computer device, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. equipped on the computer device. Further, the computer-readable storage medium may also include both the internal storage unit of the computer device and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

[0310] In addition, it should be noted that: the embodiment of the present application also provides a computer program product or a computer program, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. The processor of the 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 above Figure 3 , Figure 4 , Fig.10 The method provided by the corresponding embodiment will therefore not be described in detail here. In addition, the description of the beneficial effects of adopting the same method will not be described in detail. For technical details not disclosed in the computer program product or computer program embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0311] For further information, see Fig.14 , Fig.14 Schematic diagram of a data processing system provided in an embodiment of the present application. Fig.14As shown, the data processing system 3 may include a business client 1a and a business server 2a. There is a communication connection between the business client 1a and the business server 2a. The two can exchange data through the communication connection. The communication connection does not limit the connection method and can be directly or indirectly connected by wired or wireless means. The embodiment of the present application does not limit this. Among them, the business client 1a may include a client 31 and a mini program end 32; the client 31 may be the above-mentioned Figure 2a-2c The client described in the corresponding embodiment (or the above Fig.10 The client described in the corresponding embodiment) can be integrated in the above Figure 1 Any terminal device in the terminal cluster shown in the figure will not be described in detail here; the applet terminal 32 can be the above Fig.10 The mini program end described in the corresponding embodiment will not be described in detail here. Figure 2a-2c The service server described in the corresponding embodiment may be the above-mentioned Figure 1 The business server 100 shown in the figure will not be described in detail here; the business server 2a may include a service end 33 and a logic end 34; the service end 33 may be the above-mentioned Fig.10 The server described in the corresponding embodiment will not be described in detail here; the logic end 34 can be the above Fig.10 The logical ends described in the corresponding embodiments will not be further described here.

[0312] In the embodiment of the present application, the client 31 is used to send the second business start and end time and the first business duration to the mini program end 32 in response to the document submission operation for the business document to be submitted, when the business start and end time in the business document to be submitted is changed from the first business start and end time to the second business start and end time, and the business duration on the business document to be submitted is maintained as the first business duration corresponding to the first business start and end time; the first business duration is calculated by the logic end 34 based on the first business start and end time;

[0313] The mini program end 32 is used to send the received second service start and end time and the first service duration to the logic end 34 through the server end 33;

[0314] The logic end 34 is used to calculate the second service duration by using the start and end time of the second service, compare the second service duration with the first service duration, and when the durations are inconsistent, return the second service duration to the mini program end 32 through the service end 33, so that the mini program end 32 returns the second service duration to the client end 31;

[0315] The client 31 is used for updating the service duration on the service document to be submitted from the first service duration to the second service duration when receiving the second service duration.

[0316] The specific operations performed by the client 31, the applet end 32, the server end 33 and the logic end 34 can be found in the above Figure 3 , Figure 4 or Fig.10 The relevant descriptions in the corresponding embodiments will not be repeated here; in addition, the descriptions of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the data processing system embodiments involved in this application, please refer to the description of the method embodiments of this application.

[0317] The terms "first", "second", etc. in the description, claims, and drawings of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, device, product, or equipment that includes a series of steps or units is not limited to the listed steps or modules, but optionally includes steps or modules that are not listed, or optionally includes other step units inherent to these processes, methods, devices, products, or equipment.

[0318] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0319] It should be noted that, for the above-mentioned various method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0320] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0321] The modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0322] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0323] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A data processing method, characterized in that: The method is executed by a service server and includes: When the first service start and end time is displayed in the service document to be submitted, the first service start and end time sent by the client is obtained, a first service duration is calculated according to the first service start and end time, and the first service duration is returned to the client, so that when the client receives the first service duration, the service duration on the service document to be submitted is configured as the first service duration; When the service start and end time in the service document to be submitted is changed from the first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains the first service duration, acquiring the second service start and end time and the first service duration sent by the client; the second service start and end time and the first service duration are sent when the client responds to a document submission operation for the service document to be submitted; A second business duration is calculated by using the start and end time of the second business, and the second business duration is compared with the first business duration. When the durations are inconsistent, the second business duration is returned to the client, so that when the client receives the second business duration, it updates the business duration on the business document to be submitted from the first business duration to the second business duration.

2. The method according to claim 1, characterized in that When the first service start and end time is displayed in the service document to be submitted, obtaining the first service start and end time sent by the client, calculating the first service duration according to the first service start and end time, and returning the first service duration to the client, includes: Acquire a first business request sent by a mini-program end for document processing; the mini-program end is called by a client when a first business start and end time is displayed in a business document to be submitted; the first business request is generated based on the first business start and end time when the mini-program end receives the first business start and end time sent by the client; the first business request carries a template identifier of a business document template corresponding to the business document to be submitted; Acquire the template identifier from the first service request, and acquire template data information corresponding to the service document template from a service database according to the template identifier; The first service duration is calculated based on the template data information and the first service start and end time in the first service request, and the first service duration is returned to the mini program end, so that the mini program end returns the first service duration to the client.

3. The method according to claim 2, characterized in that The business server includes a service end and a logic end; the service end includes a duration calculation interface; the service end is used to receive a first business request sent by the mini program end through the duration calculation interface, and transmit the first business request to the logic end; The logic end is used to obtain template data information corresponding to the business document template from a business database according to the template identifier carried in the first business request when the first business request is received; The template data information includes service configuration parameters; the first service start and end time includes a first service start time and a first service end time; The calculating the first service duration based on the template data information and the first service start and end time in the first service request, and returning the first service duration to the mini program end, includes: Acquire the service configuration parameter in the template data information through the logic end, calculate the duration according to the service configuration parameter, the first service start time and the first service end time, and obtain the first service duration; When the first service duration is returned to the server end through the logic end, the server end generates first service response information based on the first service duration, and returns the first service response information carrying the first service duration to the mini program end.

4. The method according to claim 1, characterized in that The business server includes a service end and a logic end; the service end includes a document submission interface; The obtaining the start and end time of the second service and the duration of the first service sent by the client includes: The server receives the second service request sent by the mini program end for document processing through the document submission interface, and transmits the second service request to the logic end; the mini program end is called when the client responds to the document submission operation for the business document to be submitted; the second service request is generated based on the second service start and end time and the first service duration when the mini program end receives the second service start and end time and the first service duration sent by the client; The logic end obtains the start and end time of the second service and the duration of the first service from the received second service request.

5. The method according to claim 4, characterized in that The second business request carries a template identifier of a business document template corresponding to the business document to be submitted; The step of calculating the second service duration by using the start and end time of the second service, comparing the second service duration with the first service duration, and returning the second service duration to the client when the durations are inconsistent includes: When the template identifier is obtained from the second service request through the logic end, template data information corresponding to the service document template is obtained from the service database according to the template identifier, and the second service duration is calculated based on the template data information and the start and end time of the second service in the second service request; The logic end compares the second service duration with the first service duration, and returns the second service duration to the server when the durations are inconsistent; The server generates second service response information based on the second service duration, and returns the second service response information carrying the second service duration to the mini program end, so that the mini program end returns the second service duration to the client end.

6. The method according to claim 5, characterized in that The template data information includes service configuration parameters; the second service start and end time includes a second service start time and a second service end time; The calculating the second service duration based on the template data information and the second service start and end time in the second service request includes: The service configuration parameters in the template data information are obtained through the logic end, and the duration is calculated according to the service configuration parameters, the second service start time and the second service end time to obtain the second service duration.

7. The method according to claim 1, characterized in that Also includes: After comparing the second service duration with the first service duration, obtaining a verification mark parameter associated with the service document to be submitted, configuring a parameter value of the verification mark parameter as a verified parameter value, and saving the second service start and end time in the service document to be submitted; The verified parameter value is used to indicate that the service duration on the service document to be submitted has been verified; When the service duration on the service document to be submitted is updated from the first service duration to the second service duration, the service document to be submitted after the duration is updated is used as the service document with updated duration; When the received service document is the duration update service document, comparing the service start and end time in the duration update service document with the saved second service start and end time, and when the time comparison is consistent, returning third prompt information to the client based on the verification mark parameter with the verified parameter value; The third prompt information is used to indicate that the duration update service document is submitted successfully.

8. The method according to claim 2, characterized in that: The business document template corresponding to the business document to be submitted includes any one of a leave document template, a business trip document template, an out-of-office document template and an overtime document template; the template data information corresponding to the leave document template includes a first type of business configuration parameters; the first type of business configuration parameters includes a leave type, a first time scale parameter and a first duration calculation parameter; the template data information corresponding to the business trip document template includes a second type of business configuration parameters; the second type of business configuration parameters includes a second time scale parameter, a second duration calculation parameter and a first unit conversion parameter; the template data information corresponding to the out-of-office document template includes a third type of business configuration parameters; the third type of business configuration parameters includes a third time scale parameter, a third duration calculation parameter and a second unit conversion parameter; the template data information corresponding to the overtime document template includes a fourth type of business configuration parameters; the fourth type of business configuration parameters includes a fourth time scale parameter, a fourth duration calculation parameter and a third unit conversion parameter.

9. A data processing device, characterized in that: include: a duration calculation module, configured to obtain the first service start and end time sent by the client when the first service start and end time is displayed in the service document to be submitted, calculate the first service duration by using the first service start and end time, and return the first service duration to the client, so that the client configures the service duration on the service document to be submitted as the first service duration when receiving the first service duration; a document acquisition module, configured to acquire the second service start and end time and the first service duration sent by the client when the service start and end time in the service document to be submitted is changed from the first service start and end time to the second service start and end time, and the service duration on the service document to be submitted remains the first service duration; the second service start and end time and the first service duration are sent by the client when responding to a document submission operation for the service document to be submitted; The duration comparison module is used to calculate the second business duration through the start and end time of the second business, compare the second business duration with the first business duration, and when the duration comparison is inconsistent, return the second business duration to the client, so that when the client receives the second business duration, the business duration on the business document to be submitted is updated from the first business duration to the second business duration.

10. A data processing system, characterized in that: The data processing system includes a client, a mini-program, a server, and a logic terminal; The client is used for sending the second business start and end time and the first business duration to the mini program end in response to a document submission operation for the business document to be submitted, when the business start and end time in the business document to be submitted is changed from the first business start and end time to the second business start and end time, and the business duration on the business document to be submitted remains the first business duration corresponding to the first business start and end time; the first business duration is calculated by the logic end based on the first business start and end time; The mini program end is used to send the received start and end time of the second service and the duration of the first service to the logic end through the server end; The logic end is used to calculate the second service duration according to the start and end time of the second service, compare the second service duration with the first service duration, and when the durations are inconsistent, return the second service duration to the mini program end through the server end, so that the mini program end returns the second service duration to the client end; The client is used for updating the service duration on the service document to be submitted from the first service duration to the second service duration upon receiving the second service duration.

11. A computer device, characterized in that: include: Processor and memory; The processor is connected to the memory, wherein the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method according to any one of claims 1 to 8.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 8.

13. A computer program product, characterized in that The computer program product comprises computer instructions, which are stored in a computer-readable storage medium. The computer instructions are suitable for being read and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 8.

Images