A method for implementing collaborative editing in low-code forms

Abstract

The present invention discloses a method for realizing collaborative editing in a low-code form, which belongs to the field of collaborative editing and includes the following steps: S1, a user logs in to a low-code platform through an identity authentication system; S2, a user creates a new form on the low-code platform or selects an existing form for editing; S3, when a user starts editing a form, the low-code platform records the user's editing operation and pushes the editing operation to all other users who are viewing or editing the same form in real time; S4, the low-code platform monitors concurrent editing operations, detects possible editing conflicts, and provides a conflict resolution mechanism; S5, the low-code platform maintains a version history record for each form; S6, when a user performs an editing operation, a notification is sent to the relevant user. The method for realizing collaborative editing by this method has many improvements in improving collaboration efficiency, refining authority management, optimizing user experience, promoting feedback loops, conflict resolution mechanisms, and effective notification mechanisms.

Description

Technical Field

[0001] The present invention belongs to the field of collaborative editing, and more specifically, particularly relates to a method for realizing collaborative editing in a low-code form. Background Art

[0002] In existing low-code platforms, the collaborative editing function of forms often has some shortcomings, which limit the efficiency and experience of users in the collaborative process, as follows:

[0003] Imperfect real-time synchronization mechanism: When multiple users edit the same form at the same time, the existing low-code platform may not be able to effectively push the editing operations to other users in real time; this causes the user interface to not be updated in time, resulting in data inconsistency problems; the lack of an effective concurrent editing monitoring mechanism makes it difficult to detect and resolve editing conflicts, which may cause changes between users to overwrite each other, affecting data accuracy;

[0004] Lack of version control function: Many low-code platforms do not have a complete version history function, and users cannot easily go back to previous versions to view or restore historical status. There is a lack of detailed editing operation records, including operation type, operation content, operation time, and user information of the operation, which makes it difficult for users to track the change history of the form;

[0005] Unclear conflict resolution mechanism: When editing conflicts occur, existing low-code platforms may not have clear conflict resolution strategies, such as weighted algorithms that calculate the weight value of each user to determine the final editing output; lack of consideration of manual weighting, and inability to flexibly adjust weight distribution according to actual conditions, affecting the rationality of editing results;

[0006] In summary, we propose a method to realize collaborative editing in low-code forms, which is used to solve the shortcomings of existing technologies in the collaborative editing of low-code forms, such as real-time synchronization, version control, permission management, feedback mechanism, user experience, conflict resolution and notification mechanism. Summary of the invention

[0007] The purpose of the present invention is to solve the shortcomings existing in the prior art, and proposes a method for realizing collaborative editing in a low-code form. The method for realizing collaborative editing has many improvements, such as improving collaboration efficiency, enhancing version control capabilities, refining permission management, optimizing user experience, promoting feedback loops, conflict resolution mechanisms, and effective notification mechanisms. These effects work together to greatly enhance the capabilities of the low-code platform in form collaborative editing, and provide users with a more efficient, secure, and friendly working environment.

[0008] To achieve the above object, the present invention provides the following technical solutions:

[0009] A method for implementing collaborative editing in a low-code form includes the following steps:

[0010] S1. The user logs in to the low-code platform through the authentication system;

[0011] S2. The user creates a new form on the low-code platform or selects an existing form for editing. The low-code platform initializes the form structure, including fields, layout, and initial data.

[0012] S3. When a user starts editing a form, the low-code platform records the user's editing operations and pushes the editing operations to all other users who are viewing or editing the same form in real time. The user interface that receives the editing operations is automatically updated to reflect the latest form status;

[0013] S4. The low-code platform monitors concurrent editing operations, detects possible editing conflicts, and provides conflict resolution mechanisms, including locking fields and prompting users to manually merge changes to ensure data consistency;

[0014] S5. The low-code platform maintains a version history for each form, recording the timestamp and editor information of each editing operation. Users can go back to the previous version at any time to view or restore the historical status;

[0015] S6. When a user performs an editing operation, a notification is sent to relevant users, and the relevant users make suggestions on the editing through the feedback function provided by the system.

[0016] Preferably, in step S1, the low-code platform assigns corresponding permissions based on user roles to ensure that only authorized users can access and edit specific forms;

[0017] The low-code platform's authentication system receives the user's login request and extracts the username and password. The low-code platform searches the user database for a record that matches the provided username.

[0018] If a matching record is found, the system checks whether the encrypted password stored in the database matches the password provided by the user. If the passwords match, authentication succeeds; otherwise, authentication fails.

[0019] If the username or password verification fails, the system will display an error message to the user, prompting them that the credentials they entered are incorrect. The user will then re-enter the credentials or reset the password through real-time verification.

[0020] Preferably, in step S2, the user creates a new form on the low-code platform, specifically:

[0021] Users can select a template that meets their needs, or start from a blank template;

[0022] The low-code platform initializes the empty form structure, including fields, layout, and initial data. Users then layout and enter fields based on this.

[0023] The low-code platform provides a real-time preview function, allowing users to instantly view the appearance and layout of the form. Users can save the form as a draft at any time during the design process for subsequent editing;

[0024] After the form is created, the low-code platform prompts the user to set access permissions for the form;

[0025] Preferably, the user selects an existing form to edit, specifically:

[0026] Users browse or search the existing list of forms on the low-code platform’s interface;

[0027] The low-code platform loads the structural information of the selected form from the database, including fields, layout, and initial data, and displays the form structural information on the editing interface;

[0028] The low-code platform provides a real-time preview function, allowing users to instantly view the appearance and layout of the form. Users can save the form as a draft at any time during the design process for subsequent editing;

[0029] After the form is created, the low-code platform prompts the user to set access permissions for the form and sends notifications to relevant users to inform them that the form has been updated and prompt them to make corresponding adjustments and tests.

[0030] Preferably, step S3 specifically comprises:

[0031] S31. The first user logs in to the low-code platform and opens a form for editing;

[0032] S32. The low-code platform detects the editing operation of the first user and records the operation in the system;

[0033] S33. The low-code platform pushes the editing operation of the first user to all other users who are viewing or editing the same form in real time;

[0034] S34, the interfaces of other users are automatically updated to reflect the changes made by the first user;

[0035] S35. If one of the other users performs an editing operation, the operation will be recorded by the low-code platform and pushed to other users except the user in real time;

[0036] S36. Continue S32-S35 until all users have completed editing the form.

[0037] Preferably, in step S4, if several users edit the same content of the same form at the same time, a weighted algorithm is used to calculate the weight value of each user, and the user edit with the highest weight value is used as the final edit output, and the output is pushed to all other users who are viewing or editing the same form. The weighted algorithm calculates the weight value of each user, specifically:

[0038] 1) Define weight factors, including editing time (T), user level (P), matching degree (M) and manual weighting (U), where user level (P) includes administrators and users, and matching degree (M) refers to the matching degree between user edited content and actual needs, which is obtained through manual comparison;

[0039] 2) Determine the weight value and assign a weight coefficient to each weight factor;

[0040] 3) Calculate the total weight and output the total weight.

[0041] Preferably, the total weight calculation formula is:

[0042] W total =(wT×T+wP×P+wM×M)+ ;

[0043] Where W total is the total weight of the user, wT is the weight coefficient of the editing time, wP is the weight coefficient of the permission level, and wM is the weight coefficient of the matching degree;

[0044] In the above formula, the total weight also takes into account manual weighting, which is a real-time or preset score given by several people to a certain modification. U is the manual weighting coefficient, n is the number of manual weightings, is an artificially weighted average;

[0045] Among them, the editing time reflects the main contribution of the user who edits the form to the form, and the value range of wT is 0.5-1; the administrator weight coefficient in the weight coefficient of the permission level is 0.3, and the user weight coefficient is 0.2; the value range of each item of the manual weight coefficient is 0.2-0.5.

[0046] Preferably, step S5 is specifically:

[0047] S51. When a user creates or edits a form on the low-code platform, the low-code platform automatically initializes the version of the form;

[0048] S52. Whenever a user edits a form, the low-code platform will capture the operation and record it, including the operation type, operation content, operation time, and user information of the user who performed the operation. Each edit operation will generate a new version and save it to the version history;

[0049] S53. If the user needs to restore to a historical version, the low-code platform will replace the current form status with the status of the historical version selected by the user. The restore operation will generate a new version and record the timestamp of the restore operation and the user information who performed the operation.

[0050] S54. When a form is restored to a historical version, the low-code platform will send a notification to all users related to the form. The notification content includes the time of the restoration operation, the user who performed the operation, and the restored version information.

[0051] Preferably, the low-code platform also provides a centralized feedback management interface, allowing administrators or form owners to view and manage all feedback. Administrators filter feedback based on its importance and urgency. Administrators can reply to feedback or assign feedback to other users for processing. Each feedback has a clear status including unprocessed, in progress, and resolved, and its progress can be tracked in the system. Administrators or assigned users are responsible for updating the status of feedback and notifying the original submitter upon completion.

[0052] Technical effects and advantages of the present invention: The present invention provides a method for realizing collaborative editing in a low-code form. Compared with the prior art, the present invention has the following advantages:

[0053] The real-time synchronization mechanism ensures that when multiple users edit the same form at the same time, all users' interfaces can be updated in time to reflect the latest form status. The weighted algorithm is used to resolve editing conflicts, ensuring the rationality of the final output, avoiding changes between users from overwriting each other, and further improving the smoothness of the collaboration process.

[0054] A weighted algorithm is used to calculate the weight value of each user, and the user edit with the highest weight value is used as the final edit output. Multiple factors such as editing time, user level, matching degree and manual weighting are taken into consideration to ensure the fairness and rationality of the editing results. Through manual weighting, the weight distribution can be flexibly adjusted according to actual conditions, further enhancing the adaptability and effectiveness of the conflict resolution mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 A flow chart of a method for implementing collaborative editing in a low-code form of the present invention;

[0056] Figure 2 This is a flow chart of step S3 in an embodiment of the present invention. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention is further described in detail below in conjunction with specific embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0058] The present invention provides a method for implementing collaborative editing in a low-code form. The method for implementing collaborative editing has many beneficial effects, such as improving collaboration efficiency, enhancing version control capabilities, refined permission management, optimizing user experience, promoting feedback loops, conflict resolution mechanisms, and effective notification mechanisms. The multiple effects work together to greatly enhance the capabilities of the low-code platform in form collaborative editing, and provide users with a more efficient, secure, and friendly working environment.

[0059] like Figure 1 As shown, a method for implementing collaborative editing in a low-code form includes the following steps:

[0060] S1. The user logs in to the low-code platform through the authentication system; in step S1, the low-code platform assigns corresponding permissions based on the user role to ensure that only authorized users can access and edit specific forms;

[0061] The low-code platform's authentication system receives the user's login request and extracts the username and password. The low-code platform searches the user database for a record that matches the provided username.

[0062] If a matching record is found, the system checks whether the encrypted password stored in the database matches the password provided by the user. If the passwords match, authentication succeeds; otherwise, authentication fails.

[0063] If the username or password verification fails, the system will display an error message to the user, prompting them that the credentials they entered are incorrect. The user will then re-enter the credentials or reset the password through real-time verification.

[0064] S2. The user creates a new form on the low-code platform or selects an existing form for editing. The low-code platform initializes the form structure, including fields, layout, and initial data. In step S2, the user creates a new form on the low-code platform, specifically:

[0065] Users can select a template that meets their needs, or start from a blank template;

[0066] The low-code platform initializes the empty form structure, including fields, layout, and initial data. Users then layout and enter fields based on this.

[0067] The low-code platform provides a real-time preview function, allowing users to instantly view the appearance and layout of the form. Users can save the form as a draft at any time during the design process for subsequent editing;

[0068] After the form is created, the low-code platform prompts the user to set access permissions for the form;

[0069] The user selects an existing form to edit, specifically:

[0070] Users browse or search the existing list of forms on the low-code platform’s interface;

[0071] The low-code platform loads the structural information of the selected form from the database, including fields, layout, and initial data, and displays the form structural information on the editing interface;

[0072] The low-code platform provides a real-time preview function, allowing users to instantly view the appearance and layout of the form. Users can save the form as a draft at any time during the design process for subsequent editing;

[0073] After the form is created, the low-code platform prompts the user to set access permissions for the form and sends notifications to relevant users to inform them that the form has been updated and prompt them to make corresponding adjustments and tests.

[0074] S3. When a user starts editing a form, the low-code platform records the user's editing operation and pushes the editing operation to all other users who are viewing or editing the same form in real time. The user interface that receives the editing operation is automatically updated to reflect the latest form status. Step S3 is specifically as follows:

[0075] S31. The first user logs in to the low-code platform and opens a form for editing;

[0076] S32. The low-code platform detects the editing operation of the first user and records the operation in the system;

[0077] S33. The low-code platform pushes the editing operation of the first user to all other users who are viewing or editing the same form in real time;

[0078] S34, the interfaces of other users are automatically updated to reflect the changes made by the first user;

[0079] S35. If one of the other users performs an editing operation, the operation will be recorded by the low-code platform and pushed to other users except the user in real time;

[0080] S36. Continue S32-S35 until all users have completed editing the form.

[0081] S4. The low-code platform monitors concurrent editing operations, detects possible editing conflicts, and provides conflict resolution mechanisms, including locking fields and prompting users to manually merge changes to ensure data consistency; in step S4, if several users edit the same content of the same form at the same time, a weighted algorithm is used to calculate the weight value of each user, and the user edit with the highest weight value is used as the final editing output, and the output is pushed to all other users who are viewing or editing the same form. The weighted algorithm calculates the weight value of each user, specifically:

[0082] 1) Define weight factors, including editing time (T), user level (P), matching degree (M) and manual weighting (U), where user level (P) includes administrators and users, and matching degree (M) refers to the matching degree between user edited content and actual needs, which is obtained through manual comparison;

[0083] 2) Determine the weight value and assign a weight coefficient to each weight factor;

[0084] 3) Calculate the total weight and output the total weight.

[0085] It should be noted that the total weight calculation formula is:

[0086] W total =(wT×T+wP×P+wM×M)+ ;

[0087] Where W total is the total weight of the user, wT is the weight coefficient of the editing time, wP is the weight coefficient of the permission level, and wM is the weight coefficient of the matching degree;

[0088] In the above formula, the total weight also takes into account manual weighting, which is a real-time or preset score given by several people to a certain modification. U is the manual weighting coefficient, n is the number of manual weightings, is an artificially weighted average;

[0089] As an option: Manual weighting for several people to score a modification in real time or preset scoring. The scoring groups include: Preset review team: review members are pre-specified during the system setting phase based on the project attributes of the form, including business managers (weight 35%), technical experts (30%) and key user representatives (35%). Review members must access the system through a two-level authentication system (digital certificate + dynamic password).

[0090] Dynamic designation mechanism: When a form editing conflict occurs, the system automatically recommends reviewers in related fields based on the knowledge graph, requiring participants to have performed ≥20 operations on similar forms in the past 6 months and the conflict rate must be <5%.

[0091] Hierarchical supplementary rules: When the response rate of the preset members is insufficient, the system will fill in the order of the same project team members → department coordination nodes → platform management experts, ensuring that at least 3 people participate in the scoring of each modification;

[0092] Objective scoring implementation method, specifically:

[0093] Multi-dimensional quantitative evaluation matrix: The system provides a scoring template that includes business fit (0-5 points), grammatical standardization (0-3 points), and logical integrity (0-2 points). The scoring items are intelligently associated with the form field metadata;

[0094] Differentiated display mode: Visual analysis of different dimensions of the same modified content by role:

[0095] Business Roles: Highlight business process impact diagrams;

[0096] Technical role: Display heat map of data structure changes;

[0097] User role: presents the operation path simulation animation;

[0098] Blind review mode: The anonymous scoring mechanism is activated in strategic-level forms (when the confidentiality level is marked ≥ L3), and the system automatically desensitizes the editor's identity and sensitive content before distributing review tasks;

[0099] Preset scoring rules:

[0100] Industry rule base matching degree R, using the NLP engine to calculate the semantic similarity between the modified content and the preset standard document (the preset score is activated when the cosine similarity is ≥ 0.72);

[0101] Compliance verification deduction items: Automatically mark content that violates SDK constraints, and deduct 30% of the basic score for each violation.

[0102] Among them, the editing time reflects the main contribution of the user who edits the form to the form, and the value range of wT is 0.5-1; the administrator weight coefficient in the weight coefficient of the permission level is 0.3, and the user weight coefficient is 0.2; the value range of each item of the manual weight coefficient is 0.2-0.5.

[0103] For example, if the data of three users are as follows:

[0104] Administrator (UserA): Editing time T A =15 hours; Clearance Level P A=9 (the highest level is 10); matching degree M A =8 (out of 10 points); artificial weighting coefficient U A1 =4,U A2 =5, U A3 =4, U A4 =3;

[0105] Ordinary user 1 (UserB): editing time T B =10 hours; Clearance Level P B =6; matching degree M B =7; artificial weighting coefficient U B1 =3, U B2 =4, U B3 =3, U B4 =2;

[0106] Ordinary user 2 (UserC): editing time T C =12 hours; Clearance Level P C =7; matching degree M C =9; artificial weighting coefficient U C1 =4,U C2 =3, U C3 =5, U C4 =2;

[0107] According to the weighted calculation formula:

[0108] ;

[0109] ;

[0110] ;

[0111] By comparing the total weights of the three users, we can see that the administrator UserA has the highest total weight (15.3), followed by the ordinary user UserC (12.45), and finally the ordinary user UserB (10.35). Therefore, when the above three users edit at the same time, the administrator (UserA)'s edit is used as the output result.

[0112] S5. The low-code platform maintains a version history for each form, recording the timestamp and editor information of each editing operation. Users can go back to the previous version at any time to view or restore the historical status; Step S5 is specifically as follows:

[0113] S51. When a user creates or edits a form on the low-code platform, the low-code platform automatically initializes the version of the form;

[0114] S52. Whenever a user edits a form, the low-code platform will capture the operation and record it, including the operation type, operation content, operation time, and user information of the user who performed the operation. Each edit operation will generate a new version and save it to the version history;

[0115] S53. If the user needs to restore to a historical version, the low-code platform will replace the current form status with the status of the historical version selected by the user. The restore operation will generate a new version and record the timestamp of the restore operation and the user information who performed the operation.

[0116] S54. When a form is restored to a historical version, the low-code platform will send a notification to all users related to the form. The notification content includes the time of the restoration operation, the user who performed the operation, and the restored version information.

[0117] S6. When a user performs an editing operation, a notification is sent to relevant users, and the relevant users make suggestions on the editing through the feedback function provided by the system;

[0118] It should be noted that the low-code platform also provides a centralized feedback management interface, allowing administrators or form owners to view and manage all feedback. Administrators can filter feedback based on its importance and urgency. Administrators can reply to feedback or assign feedback to other users for processing. Each feedback has a clear status, including unprocessed, in progress, and resolved, and its progress can be tracked in the system. Administrators or designated users are responsible for updating the status of feedback and notifying the original submitter upon completion.

[0119] In summary, the beneficial effects of the collaborative editing method include:

[0120] Improve collaboration efficiency: The real-time synchronization mechanism ensures that when multiple users edit the same form at the same time, the interfaces of all users can be updated in time to reflect the latest form status, reducing data inconsistencies caused by delays and improving the efficiency of team collaboration. The weighted algorithm is used to resolve editing conflicts, ensuring the rationality of the final output, avoiding the overwriting of changes between users, and further improving the smoothness of the collaboration process.

[0121] Enhanced version control capabilities: Maintain a detailed version history for each form, including the timestamp and editor information of each editing operation, so that users can go back to the previous version at any time to view or restore the historical status, which helps to track the change history of the form and ensure the traceability and auditability of the data; provide the function of restoring to the historical version, allowing users to undo erroneous changes when necessary, increasing the flexibility and security of operations.

[0122] Refined permission management: Assign corresponding permissions according to user roles to ensure that only authorized users can access and edit specific forms, enhance data security, prevent unauthorized access and modification, and provide a field-level locking mechanism to further refine permission control and reduce the possibility of editing conflicts.

[0123] Optimize user experience: Provide real-time preview function, allowing users to instantly view the appearance and layout of the form, so as to make more informed decisions during the design process, improve the intuitiveness and satisfaction of the design; prompt users to set the access rights of the form, and send notifications to relevant users after the form is created, to ensure that all relevant personnel are aware of the latest status of the form, which is convenient for subsequent adjustments and testing.

[0124] Promote feedback loop: When users perform editing operations, notifications are sent to relevant users, and their suggestions are collected through the feedback function provided by the system, establishing an effective feedback loop that helps to continuously improve the design and content of the form; the centralized feedback management interface allows administrators or form owners to view and manage all feedback, filter and process them according to importance and urgency, and ensure that each feedback is properly addressed.

[0125] Conflict resolution mechanism: A weighted algorithm is used to calculate the weight of each user, and the user edit with the highest weight value is used as the final edit output. This method takes into account multiple factors such as editing time, user level, matching degree, and manual weighting to ensure the fairness and rationality of the editing results; through manual weighting, the weight distribution can be flexibly adjusted according to actual conditions, further enhancing the adaptability and effectiveness of the conflict resolution mechanism.

[0126] Notification mechanism: When a form is restored to a historical version, notifications are sent to all users related to the form in a timely manner, ensuring that all users can keep up to date with the latest status of the form and avoiding work confusion caused by information lags. The notification content includes the time of the restoration operation, the user who performed the operation, and the restored version information, providing detailed contextual information to facilitate users to understand and track changes in the form.

[0127] Finally, it should be noted that the above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for implementing collaborative editing in a low-code form, characterized in that: The steps include: S1. The user logs in to the low-code platform through the authentication system; S2. The user creates a new form on the low-code platform or selects an existing form for editing. The low-code platform initializes the form structure, including fields, layout, and initial data. S3. When a user starts editing a form, the low-code platform records the user's editing operations and pushes the editing operations to all other users who are viewing or editing the same form in real time. The user interface that receives the editing operations is automatically updated to reflect the latest form status; S4. The low-code platform monitors concurrent editing operations, detects editing conflicts, and provides conflict resolution mechanisms, including locking fields and prompting users to manually merge changes to ensure data consistency; in step S4, if several users edit the same content of the same form at the same time, a weighted algorithm is used to calculate the weight value of each user, and the user edit with the highest weight value is used as the final editing output, and the output is pushed to all other users who are viewing or editing the same form. The weighted algorithm calculates the weight value of each user, specifically: 1) Define weight factors, including editing time T, user level P, matching degree M, and manual weighting U, where user level P includes administrators and users, and matching degree M is the matching degree between the user's editing content and actual needs, and the matching degree between the user's editing content and actual needs is obtained by manual comparison; 2) Determine the weight value and assign a weight coefficient to each weight factor; 3) Calculate the total weight and output the total weight; The total weight calculation formula is: Where W total is the total weight of the user, wT is the weight coefficient of the editing time, wP is the weight coefficient of the permission level, and wM is the weight coefficient of the matching degree; in the above formula, the total weight also takes into account manual weighting, which is a real-time or preset score given by several people to a certain modification, U is the manual weighting coefficient, n is the number of manual weightings, It is the average value of manual weighting; the editing time reflects the contribution of the user who edited the form to the form, and the value range of wT is 0.5-1; the administrator weight coefficient of the authority level weight coefficient is 0.3, and the user weight coefficient is 0.2; the value range of each manual weight coefficient is 0.2-0.5; S5. The low-code platform maintains a version history for each form, recording the timestamp and editor information of each editing operation. Users can go back to the previous version at any time to view or restore the historical status; S6. When a user performs an editing operation, a notification is sent to relevant users, and the relevant users make suggestions for the editing through the feedback function provided by the system.

2. According to the method for implementing collaborative editing in a low-code form according to claim 1, it is characterized in that: In step S1, the low-code platform assigns corresponding permissions based on user roles to ensure that only authorized users can access and edit the forms corresponding to their permissions; The low-code platform's authentication system receives the user's login request and extracts the username and password. The low-code platform searches the user database for a record that matches the provided username. If a matching record is found, the system checks whether the encrypted password stored in the database matches the password provided by the user. If the passwords match, authentication succeeds; otherwise, authentication fails. If the username or password verification fails, the system will display an error message to the user, prompting them that the credentials they entered are incorrect. The user will then re-enter the credentials or reset the password through real-time verification.

3. According to the method for implementing collaborative editing in a low-code form according to claim 1, it is characterized in that: In step S2, the user creates a new form on the low-code platform, specifically: Users can select a template that meets their needs, or start from a blank template; The low-code platform initializes the blank template structure, including fields, layout, and initial data. Users then layout and input fields based on this. The low-code platform provides a real-time preview function, allowing users to instantly view the appearance and layout of the form. Users can save the form as a draft at any time during the design process for subsequent editing; After the form is created, the low-code platform prompts the user to set access permissions for the form.

4. The method for implementing collaborative editing in a low-code form according to claim 3, characterized in that: The user selects an existing form to edit, specifically: Users browse or search the existing list of forms on the low-code platform’s interface; The low-code platform loads the structural information of the selected form from the database, including fields, layout, and initial data, and displays the form structural information on the editing interface; The low-code platform provides a real-time preview function, allowing users to instantly view the appearance and layout of the form. Users can save the form as a draft at any time during the design process for subsequent editing; After the form is created, the low-code platform prompts the user to set access permissions for the form and sends notifications to relevant users to inform them that the form has been updated and prompt them to make corresponding adjustments and tests.

5. The method for implementing collaborative editing in a low-code form according to claim 1, characterized in that: Step S3 is specifically as follows: S31. The first user logs in to the low-code platform and opens a form for editing; S32. The low-code platform detects the editing operation of the first user and records the operation in the system; S33. The low-code platform pushes the editing operation of the first user to all other users who are viewing or editing the same form in real time; S34, the interfaces of other users are automatically updated to reflect the changes made by the first user; S35. If one of the other users performs an editing operation, the operation will be recorded by the low-code platform and pushed to other users except the user in real time; S36. Continue S32-S35 until all users have completed editing the form.

6. A method for implementing collaborative editing in a low-code form according to claim 1, characterized in that: Step S5 is specifically as follows: S51. When a user creates or edits a form on the low-code platform, the low-code platform automatically initializes the version of the form; S52. Whenever a user edits a form, the low-code platform will capture the operation and record it, including the operation type, operation content, operation time, and user information of the user who performed the operation. Each edit operation will generate a new version and save it to the version history; S53. If the user needs to restore to a historical version, the low-code platform will replace the current form status with the status of the historical version selected by the user. The restore operation will generate a new version and record the timestamp of the restore operation and the user information who performed the operation. S54. When a form is restored to a historical version, the low-code platform will send a notification to all users related to the form. The notification content includes the time of the restoration operation, the user who performed the operation, and the restored version information.

7. The method for implementing collaborative editing in a low-code form according to claim 1, characterized in that: The low-code platform also provides a centralized feedback management interface that allows administrators or form owners to view and manage all feedback. Administrators can filter feedback based on its importance and urgency. Administrators can reply to feedback or assign feedback to other users for processing. Each feedback has a clear status, including unprocessed, in progress, and resolved, and its progress can be tracked in the system. Administrators or assigned users are responsible for updating the status of feedback and notifying the original submitter upon completion.

Images