Page editing locking method, system, device and computer readable storage medium

Abstract

A page editing locking method, system, device and computer readable storage medium. The method comprises: a client loading a page, the page comprising a business form; the client, in response to an editing request for the business form, acquiring an editing locking enabling parameter corresponding to a current process node; if the editing locking enabling parameter indicates that locking is enabled, the client sending a form identifier of the business form to a server; the server detecting a locking record based on the form identifier and returning a corresponding instruction according to whether the locking record exists, and the client enabling or maintaining an editing state according to the instruction. Through the present application, a more intelligent and adaptive page editing locking function for business requirements is realized.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a page editing locking method, system, device, and computer-readable storage medium. Background Technology

[0002] Existing technologies typically set a global, static edit lock switch for business forms. This means that the locking function must either be fully enabled or fully disabled throughout the entire process, severely impacting the flexibility and collaboration efficiency of the business process. Summary of the Invention

[0003] This application provides a page editing locking method, system, device, and computer-readable storage medium, which can solve the technical problem of the rigid page editing locking mechanism in the prior art.

[0004] In a first aspect, embodiments of this application provide a page editing locking method, the page editing locking method comprising:

[0005] The client loads a page, which includes a business form;

[0006] In response to an edit request for the business form, the client obtains the edit lock enable parameter corresponding to the current process node;

[0007] If the edit lock enable parameter indicates that locking is not enabled, the client enables the editing function of the business form to allow the user to perform editing operations on the business form;

[0008] If the edit lock enable parameter indicates that locking is enabled, the client sends the form identifier of the business form to the server;

[0009] The server receives the form identifier and checks whether there is a lock record corresponding to the form identifier;

[0010] If the lock record does not exist, the server creates and stores the lock record corresponding to the form identifier, and returns a first instruction to the client;

[0011] In response to the first instruction, the client enables the editing function of the business form, allowing the user to perform editing operations on the business form;

[0012] If the lock record exists, the server returns a second instruction to the client;

[0013] The client responds to the second instruction by maintaining the business form in an uneditable state.

[0014] In conjunction with the first aspect, in one implementation, the form identifier of the business form sent by the client to the server if the edit lock enable parameter indicates that locking is enabled includes:

[0015] If the edit lock enable parameter indicates that locking is enabled, the client establishes a two-way communication connection with the server and sends the form identifier of the business form to the server based on the two-way communication connection.

[0016] In conjunction with the first aspect, in one implementation, after the server establishes and stores the lock record corresponding to the form identifier, the method further includes:

[0017] If the server detects that the bidirectional communication connection is interrupted, it deletes the lock record corresponding to the form identifier.

[0018] In conjunction with the first aspect, in one implementation, after the server establishes and stores the lock record corresponding to the form identifier, the method further includes:

[0019] In response to the edit exit request, the client terminates its bidirectional communication connection with the server.

[0020] In conjunction with the first aspect, in one implementation, after the client and server establish a bidirectional communication connection, the method further includes:

[0021] The server periodically sends probe packets to the client;

[0022] If the server detects a timeout in the client's response, it determines that the bidirectional communication connection is interrupted.

[0023] In conjunction with the first aspect, in one embodiment, the page editing locking method further includes:

[0024] If the edit lock enable parameter indicates that locking is enabled, the client sends the form identifier of the business form and the user identity information that triggered the edit request to the server;

[0025] If the lock record does not exist, the server creates and stores the lock record corresponding to the form identifier and returns a first instruction to the client, wherein the lock record includes the user identity information;

[0026] If the lock record exists, the server extracts the user identification information from the lock record and returns it to the client along with the second instruction; the client responds to the second instruction by maintaining the uneditable state of the business form and displaying a lock prompt including the user identification information.

[0027] In conjunction with the first aspect, in one implementation, the lock record is stored in a local cache on the server.

[0028] Secondly, embodiments of this application provide a page editing locking system, which includes a client and a server, wherein:

[0029] The client is used to load a page, which includes a business form; in response to an editing request for the business form, it obtains the editing lock enable parameter corresponding to the current process node; if the editing lock enable parameter indicates that locking is enabled, it sends the form identifier of the business form to the server; if the editing lock enable parameter indicates that locking is not enabled, it enables the editing function of the business form to allow the user to perform editing operations on the business form.

[0030] The server receives the form identifier and checks whether a lock record corresponding to the form identifier exists. If the lock record does not exist, it creates and stores the lock record corresponding to the form identifier and returns a first instruction to the client. If the lock record exists, it returns a second instruction to the client.

[0031] The client is configured to, in response to the first instruction, enable the editing function of the business form to allow the user to perform editing operations on the business form; and, in response to the second instruction, maintain the business form in a non-editable state.

[0032] Thirdly, embodiments of this application provide a page editing locking device, which includes a processor, a memory, and a page editing locking program stored in the memory and executable by the processor, wherein when the page editing locking program is executed by the processor, it implements the steps of the page editing locking method as described in the first aspect.

[0033] Fourthly, embodiments of this application provide a computer-readable storage medium storing a page editing locking program, wherein when the page editing locking program is executed by a processor, it implements the steps of the page editing locking method as described in the first aspect.

[0034] The beneficial effects of the technical solutions provided in this application include:

[0035] It improves the flexibility and efficiency of business processes: by dynamically obtaining the editing lock enable parameter based on the current process node, it achieves fine-grained control over page editing lock. This overcomes the limitations of existing technologies where the locking function is either all on or all off due to a global static switch, allowing editing lock to be flexibly enabled or disabled as needed at different business stages. As a result, users can process business forms more efficiently in collaborative workflows, avoiding unnecessary locking conflicts or waiting, and improving overall work efficiency.

[0036] This ensures the accuracy and real-time nature of lockout control: the server detects lockout records based on form identifiers and returns corresponding instructions based on the existence of lockout records, allowing the client to enable or maintain an editing state accordingly. This mechanism ensures that only the currently locked user can edit the form, while other users are promptly notified and remain in an uneditable state, reducing data conflicts and the risk of accidental operations, and further optimizing the collaboration experience.

[0037] In summary, the embodiments of this application effectively solve the problems of low flexibility and collaboration efficiency caused by global static switches in the prior art through parameterized configuration and dynamic locking management at the process node level, and realize a more intelligent page editing locking function that adapts to business needs. Attached Figure Description

[0038] Figure 1 This is a flowchart illustrating one embodiment of the page editing locking method of this application;

[0039] Figure 2 This is a schematic diagram of the architecture of an embodiment of the page editing locking system of this application;

[0040] Figure 3 This is a schematic diagram of the hardware structure of the page editing locking device involved in the embodiments of this application. Detailed Implementation

[0041] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0043] Firstly, embodiments of this application provide a page editing locking method.

[0044] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating one embodiment of the page editing locking method for this application. Figure 1 As shown, page editing locking methods include:

[0045] Step S10: The client loads a page, which includes a business form;

[0046] Step S20: In response to the edit request for the business form, the client obtains the edit lock enable parameter corresponding to the current process node;

[0047] In this embodiment, it is assumed that a business process involves process nodes including node A, node B, node C, and node D. Node A requires collaboration from multiple people, so the edit lock enable parameter for node A is set to disabled. Nodes B, C, and D only require processing by specific personnel, so the edit lock enable parameter for nodes B, C, and D is set to enabled. The edit lock enable parameter for each node is configured according to the business scenario and business requirements.

[0048] Taking this business process based on a business system as an example, assume the client loads the relevant page through a browser and displays the corresponding business form on the page. If an edit request for the business form is received triggered by a user action, the client responds to the edit request and retrieves the edit lock enable parameters corresponding to the current process node based on the configured information.

[0049] Step S30: If the edit lock enable parameter indicates that the lock is not enabled, the client enables the editing function of the business form to allow the user to perform editing operations on the business form;

[0050] In this embodiment, assuming the current process node is node A, and the edit lock enable parameter corresponding to node A is disabled, that is, the edit lock enable parameter indicates that locking is not enabled, that is, the current business form has shared attributes, then the client directly enables the editing function of the business form to allow the user to perform editing operations on the business form.

[0051] Step S40: If the edit lock enable parameter indicates that locking is enabled, the client sends the form identifier of the business form to the server.

[0052] Step S50: The server receives the form identifier and checks whether there is a lock record corresponding to the form identifier;

[0053] Step S60: If the lock record does not exist, the server creates and stores the lock record corresponding to the form identifier, and returns a first instruction to the client;

[0054] Step S70: In response to the first instruction, the client enables the editing function of the business form to allow the user to perform editing operations on the business form;

[0055] Step S80: If the lock record exists, the server returns a second instruction to the client;

[0056] In step S90, the client responds to the second instruction by maintaining the business form in an uneditable state.

[0057] In this embodiment, assuming the current process node is node C, and the edit lock enable parameter corresponding to node C is enabled (i.e., the edit lock enable parameter indicates that locking is enabled), it is necessary to verify whether the business form has been locked. For example:

[0058] The client sends the form identifier of the business form to the server. For the server, each time a form identifier is received, it checks whether there is a lock record corresponding to the currently received form identifier. If it does not exist, it creates a lock record corresponding to the currently received form identifier and returns the first instruction to the client. If it exists, it returns the second instruction to the client.

[0059] It's easy to understand that if no lock record exists, it means the business form is not currently being edited on other clients, but the client that sent the form identifier has an editing need. In this case, a new lock record is created corresponding to the currently received form identifier, and a first instruction is returned to the client. The client then responds to the first instruction to enable the business form's editing function, allowing the user to perform editing operations on the business form. If a lock record exists, it means the business form has already been edited on other clients, and the current process node has independent edit attributes. In this case, a second instruction is returned to the client, allowing the client to respond to the second instruction and maintain the business form's uneditable state.

[0060] This embodiment improves the flexibility and collaboration efficiency of business processes: by dynamically obtaining the edit lock enable parameter based on the current process node, fine-grained control of page edit lock is achieved. This overcomes the limitations of existing technologies where the lock function is either fully enabled or fully disabled due to a global static switch, allowing for flexible enabling or disabling of edit lock as needed at different business stages. As a result, users can process business forms more efficiently in collaborative workflows, avoiding unnecessary lock conflicts or waiting, and improving overall work efficiency. The accuracy and real-time nature of lock control are ensured: the server detects lock records based on form identifiers and returns corresponding instructions based on the existence of lock records, allowing the client to enable or maintain the edit state accordingly. This mechanism ensures that only the currently locked user can edit the form; other users are promptly notified and remain in an uneditable state, reducing data conflicts and the risk of misoperation, further optimizing the collaboration experience.

[0061] In summary, the embodiments of this application effectively solve the problems of low flexibility and collaboration efficiency caused by global static switches in the prior art through parameterized configuration and dynamic locking management at the process node level, and realize a more intelligent page editing locking function that adapts to business needs.

[0062] Further, in one embodiment, step S30 includes:

[0063] If the edit lock enable parameter indicates that locking is enabled, the client establishes a two-way communication connection with the server and sends the form identifier of the business form to the server based on the two-way communication connection.

[0064] In this embodiment, a WebSocket connection is used as an example for bidirectional communication. Other connection methods can also be used, but this is only for illustrative purposes and does not constitute a limitation on the specific method of bidirectional communication connection.

[0065] Furthermore, in one embodiment, after the server establishes and stores the lock record corresponding to the form identifier, the method further includes:

[0066] If the server detects that the bidirectional communication connection is interrupted, it deletes the lock record corresponding to the form identifier.

[0067] In this embodiment, it is assumed that client x has established a bidirectional communication connection with the server, and the server has established and stored a lock record corresponding to the form identifier of business form 1, preventing other clients from obtaining editing permissions for business form 1. If client x fails, relevant personnel will be unable to continue editing business form 1 on client x, and a different client will be needed to continue the editing work. However, due to the existence of the lock record, other clients cannot intervene. Therefore, considering that if client x fails, its WebSocket connection with the server will be immediately interrupted due to the underlying TCP connection failure, when the server detects the bidirectional communication connection interruption, it deletes the lock record corresponding to the form identifier, which is equivalent to unlocking the business form 1.

[0068] In existing technologies, unlocking a locked page requires the front-end to call an unlock API or wait for the lock to automatically time out. In scenarios such as abnormal page closure, user-initiated browser closure, or power outage, the unlock API cannot be called normally, leading to a deadlock. The embodiments in this application avoid this deadlock scenario.

[0069] Furthermore, in one embodiment, after the server establishes and stores the lock record corresponding to the form identifier, the method further includes:

[0070] In response to the edit exit request, the client terminates its bidirectional communication connection with the server.

[0071] In this embodiment, when the user on the client side finishes editing, an editing exit request is triggered through a related operation (such as closing the page). It is then considered that the locking state of the business form needs to be released, and the bidirectional communication connection with the server is actively disconnected so that the server can detect the interruption of the bidirectional communication connection and delete the locked record corresponding to the form identifier.

[0072] Furthermore, in one embodiment, after the client and server establish a bidirectional communication connection, the method further includes:

[0073] The server periodically sends probe packets to the client; if the server detects that the client's response has timed out, it determines that the bidirectional communication connection is interrupted.

[0074] In this embodiment, based on the keep-alive mechanism, the server periodically sends heartbeat packets to the client via a bidirectional communication connection, and the client automatically replies with a response packet upon receiving them. Assuming the client experiences a severe network failure and crashes without actively triggering an edit / exit request, if the server sends heartbeat packets three times consecutively without receiving any response, the server's heartbeat detector will determine that the bidirectional communication connection has failed, actively mark it as interrupted, and invoke cleanup logic to delete the corresponding lock record.

[0075] Furthermore, in one embodiment, the page editing locking method further includes:

[0076] If the edit lock enable parameter indicates that locking is enabled, the client sends the form identifier of the business form and the user identity information that triggered the edit request to the server;

[0077] If the lock record does not exist, the server creates and stores the lock record corresponding to the form identifier and returns a first instruction to the client, wherein the lock record includes the user identity information;

[0078] If the lock record exists, the server extracts the user identification information from the lock record and returns it to the client along with the second instruction; the client responds to the second instruction by maintaining the uneditable state of the business form and displaying a lock prompt including the user identification information.

[0079] In this embodiment, for each client, if it is determined that the edit lock enable parameter corresponding to the current process node indicates that the lock is enabled, in addition to sending the form identifier of the business form to the server, the client also sends the user identity information (e.g., name) that triggered the edit request to the server.

[0080] For example, in one scenario, client 1 sends form identifier 1 of business form 1 and user identity information "Zhang San" to the server. The server detects that no lock record exists corresponding to form identifier 1. The server then creates and stores a lock record corresponding to form identifier 1, including the information "Zhang San," and returns a first instruction to client 1. Client 1 responds to this first instruction to enable the editing function of business form 1, allowing the user to perform editing operations on business form 1. Subsequently, client 2 sends form identifier 1 of business form 1 and user identity information (e.g., Li Si) to the server. This time, a lock record exists corresponding to form identifier 1. The server extracts the user identity information "Zhang San" from the lock record and returns it to the client along with a second instruction. The client responds to the second instruction, keeping business form 1 in an uneditable state and displaying a lock prompt including "Zhang San," such as "The current form is being edited by Zhang San, please try again later."

[0081] Furthermore, in one embodiment, the lock record is stored in a local cache on the server.

[0082] In this embodiment, all form lock records are stored in a local server cache. Since the access speed of the local cache is in the nanosecond range, far exceeding any network request, the lock / unlock operation is extremely fast. At the same time, the system architecture is simplified, eliminating the need to deploy, maintain, and monitor additional caching middleware, thus reducing operational costs. Furthermore, as long as the business service itself is functioning normally, the edit and lock functions are available, which aligns with the inherent requirements of the business logic and provides higher service reliability.

[0083] Secondly, embodiments of this application also provide a page editing locking system.

[0084] In one embodiment, reference is made to Figure 2 , Figure 2 This is a schematic diagram of the architecture of an embodiment of the page editing locking system for this application. Figure 2 As shown, the page editing locking system includes:

[0085] Client 10 is used to load a page, the page including a business form; in response to an editing request for the business form, it obtains the editing lock enable parameter corresponding to the current process node; if the editing lock enable parameter indicates that locking is enabled, it sends the form identifier of the business form to server 20; if the editing lock enable parameter indicates that locking is not enabled, it enables the editing function of the business form to allow the user to perform editing operations on the business form.

[0086] Server 20 is used to receive the form identifier and detect whether there is a lock record corresponding to the form identifier; if there is no lock record, it creates and stores the lock record corresponding to the form identifier and returns a first instruction to the client 10; if there is a lock record, it returns a second instruction to the client 10.

[0087] Client 10 is configured to, in response to the first instruction, enable the editing function of the business form to allow the user to perform editing operations on the business form; and in response to the second instruction, maintain the business form in an uneditable state.

[0088] Furthermore, in one embodiment, client 10 is used for:

[0089] If the edit lock enable parameter indicates that locking is enabled, a two-way communication connection is established with server 20, and the form identifier of the business form is sent to server 20 based on the two-way communication connection.

[0090] Furthermore, in one embodiment, the server 20 is used for:

[0091] If the bidirectional communication connection is detected to be interrupted, delete the lock record corresponding to the form identifier.

[0092] Furthermore, in one embodiment, client 10 is used for:

[0093] In response to the edit exit request, the bidirectional communication connection with the server 20 is terminated.

[0094] Furthermore, in one embodiment, the server 20 is used for:

[0095] Periodically send probe packets to client 10; if a timeout is detected in the response from client 10, determine that the bidirectional communication connection is interrupted.

[0096] Furthermore, in one embodiment, the client 10 is configured to send the form identifier of the business form and the user identity identifier information that triggered the editing request to the server 20 if the edit lock enable parameter indicates that locking is enabled;

[0097] Server 20 is configured to create and store a lock record corresponding to the form identifier if the lock record does not exist, and return a first instruction to client 10, wherein the lock record includes the user identity information; if the lock record exists, the server extracts the user identity information from the lock record and returns it to client 10 along with a second instruction; in response to the second instruction, client 10 maintains the uneditable state of the business form and displays a lock prompt including the user identity information.

[0098] Furthermore, in one embodiment, the lock record is stored in a local cache on the server.

[0099] The embodiments of the above-mentioned page editing locking system refer to the various embodiments of the first aspect, and will not be described in detail here.

[0100] Thirdly, embodiments of this application provide a page editing locking device, which can be a personal computer (PC), laptop computer, server, or other device with data processing capabilities.

[0101] Reference Figure 3 , Figure 3 This is a schematic diagram of the hardware structure of the page editing locking device involved in the embodiments of this application. In the embodiments of this application, the page editing locking device may include a processor, a memory, a communication interface, and a communication bus.

[0102] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0103] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting internal components of the page editing lock device, as well as interfaces used for interconnecting the page editing lock device with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0104] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0105] The processor can be a general-purpose processor, which can call a page editing locking program stored in memory and execute the page editing locking method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the page editing locking program is called can be referred to in the various embodiments of the page editing locking method of this application, and will not be repeated here.

[0106] Those skilled in the art will understand that Figure 3 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0107] Fourthly, embodiments of this application also provide a computer-readable storage medium.

[0108] The present application provides a computer-readable storage medium storing a page editing locking program, wherein when the page editing locking program is executed by a processor, it implements the steps of the page editing locking method as described above.

[0109] The method implemented when the page editing locking procedure is executed can be referred to in various embodiments of the page editing locking method of this application, and will not be repeated here.

[0110] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0111] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0112] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0113] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0114] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0115] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0116] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A page editing locking method, characterized in that, The page editing locking method includes: The client loads a page, which includes a business form; In response to an edit request for the business form, the client obtains the edit lock enable parameter corresponding to the current process node; If the edit lock enable parameter indicates that locking is not enabled, the client enables the editing function of the business form to allow the user to perform editing operations on the business form; If the edit lock enable parameter indicates that locking is enabled, the client sends the form identifier of the business form to the server; The server receives the form identifier and checks whether there is a lock record corresponding to the form identifier; If the lock record does not exist, the server creates and stores the lock record corresponding to the form identifier, and returns a first instruction to the client; In response to the first instruction, the client enables the editing function of the business form, allowing the user to perform editing operations on the business form; If the lock record exists, the server returns a second instruction to the client; The client responds to the second instruction by maintaining the business form in an uneditable state.

2. The page editing locking method as described in claim 1, characterized in that, If the edit lock enable parameter indicates that locking is enabled, the form identifier of the business form sent by the client to the server includes: If the edit lock enable parameter indicates that locking is enabled, the client establishes a two-way communication connection with the server and sends the form identifier of the business form to the server based on the two-way communication connection.

3. The page editing locking method as described in claim 2, characterized in that, After the server establishes and stores the lock record corresponding to the form identifier, the process also includes: If the server detects that the bidirectional communication connection is interrupted, it deletes the lock record corresponding to the form identifier.

4. The page editing locking method as described in claim 3, characterized in that, After the server establishes and stores the lock record corresponding to the form identifier, the process also includes: In response to the edit exit request, the client terminates its bidirectional communication connection with the server.

5. The page editing locking method as described in claim 3, characterized in that, After the client and server establish a two-way communication connection, the following is also included: The server periodically sends probe packets to the client; If the server detects a timeout in the client's response, it determines that the bidirectional communication connection is interrupted.

6. The page editing locking method as described in claim 1, characterized in that, The page editing locking method also includes: If the edit lock enable parameter indicates that locking is enabled, the client sends the form identifier of the business form and the user identity information that triggered the edit request to the server; If the lock record does not exist, the server creates and stores the lock record corresponding to the form identifier, and returns a first instruction to the client, wherein the lock record includes the user identity information; If the lock record exists, the server extracts the user identification information from the lock record and returns it to the client along with the second instruction; the client responds to the second instruction by maintaining the uneditable state of the business form and displaying a lock prompt including the user identification information.

7. The page editing locking method as described in claim 1, characterized in that, The lock record is stored in the server's local cache.

8. A page editing locking system, characterized in that, The page editing locking system includes a client and a server, wherein: The client is used to load a page, which includes a business form; in response to an editing request for the business form, it obtains the editing lock enable parameter corresponding to the current process node; if the editing lock enable parameter indicates that locking is enabled, it sends the form identifier of the business form to the server; if the editing lock enable parameter indicates that locking is not enabled, it enables the editing function of the business form to allow the user to perform editing operations on the business form. The server receives the form identifier and checks whether a lock record corresponding to the form identifier exists. If the lock record does not exist, it creates and stores the lock record corresponding to the form identifier and returns a first instruction to the client. If the lock record exists, it returns a second instruction to the client. The client is configured to, in response to the first instruction, enable the editing function of the business form to allow the user to perform editing operations on the business form; and, in response to the second instruction, maintain the business form in a non-editable state.

9. A page editing locking device, characterized in that, The page editing locking device includes a processor, a memory, and a page editing locking program stored in the memory and executable by the processor, wherein when the page editing locking program is executed by the processor, it implements the steps of the page editing locking method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a page editing locking program, wherein when the page editing locking program is executed by a processor, it implements the steps of the page editing locking method as described in any one of claims 1 to 7.

Images