Protocol text management method and device, storage medium and computer equipment

Abstract

The invention provides a protocol text management method and device, a storage medium and computer equipment, and the method comprises the steps: displaying a protocol editing interface corresponding to a preset rich text editor in response to a triggering operation of a newly added protocol control or a modified protocol control displayed in a protocol text management interface; in response to an editing completion operation triggered in the rich text editor, obtaining a target protocol text corresponding to the current protocol version based on the protocol information edited in the protocol editing interface and the edited protocol format; transmitting the target protocol text to a protocol database; the protocol database is used for responding to a protocol content request of the user side and returning the target protocol text to the user side; wherein the user side is used for responding to the triggering operation of the protocol text to be browsed and displaying the target protocol text in the edited protocol format, and the effect of reducing the cost of managing the protocol text can be achieved.

Description

Technical Field

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

[0002] With the increase in applications, many applications need to notify users to read the corresponding privacy agreements, laws and regulations, and other agreements. In the modern management background, the management of text content such as laws and regulations and user agreements is an essential function. As user privacy policies and platform terms become increasingly complex, the platform needs a flexible way to update and manage these agreements to ensure that the text content displayed when users visit always meets the latest legal and business requirements.

[0003] In the related art, the agreement content is manually entered and updated through the backend management end, and the front end obtains and displays the agreement through the interface.

[0004] However, during the implementation process, the relevant technology at least has the problem of high cost of protocol text management. Summary of the invention

[0005] Based on this, the purpose of this application is to solve at least one of the above-mentioned technical defects, especially the technical defect of protocol text management cost in the prior art. This application provides a protocol text management method, device, storage medium and computer equipment.

[0006] In a first aspect, the present application provides a protocol text management method, the method comprising:

[0007] In response to a triggering operation of adding a new protocol control or modifying a protocol control displayed in the protocol text management interface, a protocol editing interface corresponding to a preset rich text editor is displayed;

[0008] In response to an edit completion operation triggered in the rich text editor, based on the protocol information edited in the protocol editing interface and the edited protocol format, a target protocol text corresponding to the current protocol version is obtained;

[0009] The target protocol text is transmitted to the protocol database; the protocol database is used to respond to the protocol content request of the user terminal and return the target protocol text to the user terminal;

[0010] The user terminal is used to display the target protocol text in the edited protocol format in response to a triggering operation of the protocol text to be browsed.

[0011] In one of the embodiments, in response to an edit completion operation triggered in a rich text editor, based on the protocol information edited in the protocol editing interface and the edited protocol format, a target protocol text corresponding to the current protocol version is obtained, including:

[0012] In response to a triggering operation of a protocol saving control displayed in a rich text editor, a selection window for a protocol saving type is displayed;

[0013] In response to a selection operation on a target saving type in a selection window, the target protocol text is saved in the target saving type; wherein the target saving type is used to indicate whether to remind the user that the protocol version has been updated.

[0014] In one embodiment, the method further comprises:

[0015] In response to a triggering operation of a protocol type window in a protocol editing interface, displaying a protocol type list;

[0016] In response to a selection operation of a protocol type in the protocol type list, determining the protocol type of the currently edited protocol;

[0017] In response to a text input operation of the agreement content in the agreement editing interface, acquiring the agreement text content;

[0018] Based on the protocol type and the protocol text content, the protocol information edited in the protocol editing interface is obtained.

[0019] In one embodiment, the method further comprises:

[0020] In response to the operation of opening the protocol text management interface, displaying the historical protocol texts corresponding to the various historical protocol versions in the protocol text management interface;

[0021] In response to the cancel selection operation on the historical protocol text, the selected historical protocol text is canceled.

[0022] In one embodiment, in response to the operation of opening the protocol text management interface, displaying the historical protocol texts corresponding to each historical protocol version in the protocol text management interface, further comprising:

[0023] In response to the operation of opening the protocol text management interface, the historical protocol version identifier, protocol type, and protocol modification time corresponding to each historical protocol version are displayed in the protocol text management interface.

[0024] In one embodiment, the method further comprises:

[0025] In response to the installation operation of the rich text editor, obtaining the rich text editor;

[0026] In response to a selection operation on the rich text editor, the rich text editor is used as a preset rich text editor for protocol text management.

[0027] In a second aspect, the present application provides a protocol text management system, the system comprising:

[0028] The backend management terminal is used to implement the above-mentioned protocol text management method;

[0029] Database, used to store the protocol text transmitted by the backend management end;

[0030] The user end is used to respond to the trigger operation of the protocol text to be browsed, send a protocol content request to the database, obtain the target protocol text returned by the database, and display the target protocol text in the edited protocol format determined when editing by the background management end.

[0031] In a third aspect, the present application provides a protocol text management device, the device comprising:

[0032] An editing response module, used to respond to a triggering operation of adding a new protocol control or modifying a protocol control displayed in the protocol text management interface, and display a protocol editing interface corresponding to a preset rich text editor;

[0033] A protocol determination module, for obtaining a target protocol text corresponding to the current protocol version based on the protocol information edited in the protocol editing interface and the edited protocol format in response to an edit completion operation triggered in the rich text editor;

[0034] The protocol transmission module is used to transmit the target protocol text to the protocol database; the protocol database is used to return the target protocol text to the user end in response to the protocol content request of the user end;

[0035] The user terminal is used to display the target protocol text in the edited protocol format in response to a triggering operation of the protocol text to be browsed.

[0036] In a fourth aspect, the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0037] In a fifth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the above method when the computer program is executed by a processor.

[0038] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0039] The protocol text management method, device, storage medium and computer equipment provided by the present application display a protocol text management interface on the back-end management end, and can display a new protocol control or a modified protocol control on the protocol text management interface, so that it is convenient for users to modify or add protocol texts on the back-end management end, and it is convenient to manage multiple protocol texts or trace the historical versions of protocol texts. And by completing the editing of the protocol content with a rich text editor, it is convenient for the front end to obtain the rich text content and directly display the protocol text in the edited protocol format, ensuring that the displayed protocol text format is consistent with the format of the back-end management end, thereby reducing the cost of protocol text management. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] 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 labor.

[0041] Figure 1 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 1 ;

[0042] Figure 2 A schematic diagram of a protocol editing interface provided in an embodiment of the present application Figure 1 ;

[0043] Figure 3 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 2 ;

[0044] Figure 4 A schematic diagram of a protocol editing interface provided in an embodiment of the present application Figure 2 ;

[0045] Figure 5 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 3 ;

[0046] Figure 6 A schematic diagram of a protocol text management interface provided in an embodiment of the present application;

[0047] Figure 7 A schematic diagram of the structure of a protocol text management system provided in an embodiment of the present application;

[0048] Figure 8 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 4 ;

[0049] Fig. 9 A schematic diagram of the structure of a protocol text management device provided in an embodiment of the present application;

[0050] Fig.10 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] 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.

[0052] With the increase in applications, many applications need to notify users to read the corresponding privacy agreements, laws and regulations, and other agreements. In the modern management background, the management of text content such as laws and regulations and user agreements is an essential function. As user privacy policies and platform terms become increasingly complex, the platform needs a flexible way to update and manage these agreements to ensure that the text content displayed when users visit always meets the latest legal and business requirements.

[0053] In the related art, the agreement content is manually entered and updated through the backend management end, and the frontend obtains and displays the agreement through the interface. However, many systems lack a version management mechanism for updating the agreement content, making it difficult to notify users that the agreement has been updated, or it is not easy to configure different versions of the agreement content. In addition, when displaying content, the frontend component needs to do a lot of formatting work, which makes the backend configuration content inconsistent with the frontend display content.

[0054] At the same time, many software systems lack protocol version management, making it difficult to trace historical versions or remind users of protocol updates. The rich text content configured in the background is often not fully restored when displayed on the front end due to differences in devices, browsers, etc., affecting the user experience. The front-end team needs to customize the corresponding pages or components according to the display requirements of different protocols, which has high maintenance costs. When there are adjustments to laws, regulations or activity rules, technical personnel must be relied upon for development or modification, which is not flexible enough to meet frequent business needs.

[0055] That is, during the implementation process, the relevant technology at least has the problem of high cost of protocol text management.

[0056] Based on this, the present application provides a protocol text management method, device, storage medium and computer equipment. By displaying a protocol text management interface on the back-end management end, and displaying a new protocol control or a modified protocol control on the protocol text management interface, it is convenient for users to modify or add protocol texts on the back-end management end, and it is convenient to manage multiple protocol texts or trace the historical versions of protocol texts. And by completing the editing of the protocol content with a rich text editor, it is convenient for the front end to obtain the rich text content and directly display the protocol text in the edited protocol format, ensuring that the displayed protocol text format is consistent with the format of the back-end management end, thereby reducing the cost of protocol text management.

[0057] In an exemplary embodiment, Figure 1 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 1 ,like Figure 1 As shown, this embodiment uses the method applied to a terminal as an example for illustration. It is understandable that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes S101 to S103. Among them:

[0058] S101. In response to a triggering operation of adding a new protocol control or modifying a protocol control displayed in a protocol text management interface, a protocol editing interface corresponding to a preset rich text editor is displayed.

[0059] Among them, the protocol text management interface can be an interface in the protocol management system. The new protocol control can be a control for adding a new protocol. The modify protocol control can be a control for modifying historical protocols. The rich text editor can be a tool for rich text editing. For example, the rich text editor can be the TinyMCE editor. TinyMCE is an HTML editor that complies with the LGPL license agreement and is web interface-oriented. As an example, this application mainly uses the TinyMCE editor as a rich text editor to implement the editing of the protocol text in this application. The protocol editing interface may refer to the interface provided by the rich text editor, which can be used to implement the editing of rich text. For example, Figure 2 A schematic diagram of a protocol editing interface provided in an embodiment of the present application Figure 1 ,like Figure 2 As shown, the protocol editing interface may include a protocol title area, a protocol type area, and a protocol content area.

[0060] Exemplarily, the backend management terminal may display the protocol text management interface in response to the user's operation of opening the protocol text management interface, and may display new protocol controls and modified protocol controls on the protocol text management interface, wherein each historical protocol text may correspond to a modified protocol control, and triggering the modified protocol corresponding to the historical protocol text means modifying the historical protocol text.

[0061] The back-end management end can respond to the trigger operation of the newly added protocol control, trigger the instruction of the newly added protocol text, and display the protocol editing interface corresponding to the TinyMCE editor used to add the newly added protocol text. Users can use the protocol editing interface to implement the operation of adding new protocol content, and can generate a new version of the protocol text based on the newly added protocol content.

[0062] The backend management end can also respond to the trigger operation of modifying the protocol control for a certain historical protocol text, and display the protocol content of the historical protocol text in the protocol editing interface corresponding to the TinyMCE editor. The user can modify the protocol content and generate a new version of the protocol text with the modified protocol content.

[0063] In this way, the present application can not only have the function of adding new protocol texts, but also realize the management of historical protocol texts, which is conducive to improving the efficiency of protocol text management.

[0064] As an example, the TinyMCE rich text editor can be integrated into the backend management end, allowing operators to configure the content of the agreement according to their needs, whether it is laws and regulations or activity rules descriptions. The rich text editor supports the insertion of text, pictures, tables, links and other content, and can use CSS styles to customize the content.

[0065] S102: In response to an editing completion operation triggered in the rich text editor, a target protocol text corresponding to the current protocol version is obtained based on the protocol information edited in the protocol editing interface and the edited protocol format.

[0066] The editing completion operation may be an operation that is triggered by the user to complete the editing. For example, the user triggers the save operation, which can be considered as the editing completion. The protocol information may refer to the protocol content entered or modified by the user. The protocol format may refer to the format or form of the protocol content in the rich text editor, such as the format of paragraphs, image positions, etc. The current protocol version may refer to the newly generated protocol version, which may be the new protocol version obtained after the current editing is completed.

[0067] Exemplarily, the backend management end can obtain the input or edited protocol information content and determine the protocol format of the protocol text in response to the editing operation in the rich text editor. The backend management end can respond to the operation of saving the protocol triggered in the rich text editor, save the protocol text content in the protocol format based on the protocol information content and the determined protocol format, obtain the target protocol text, and the backend management end can generate a new version identifier for the target protocol text, that is, the version identifier corresponding to the target protocol text.

[0068] In this way, the target protocol text with a new version identifier can be generated through the determined protocol information and protocol format, which can facilitate the management of protocol texts of various versions and facilitate the front-end to directly display the protocol text according to the protocol format, ensuring that the protocol content configured in the background is highly consistent with the front-end display effect, thereby reducing development workload and maintenance costs.

[0069] S103, transmitting the target protocol text to the protocol database; the protocol database is used to respond to the protocol content request of the user end and return the target protocol text to the user end.

[0070] The user terminal is used to display the target protocol text in the edited protocol format in response to a triggering operation of the protocol text to be browsed.

[0071] The protocol database may be a storage system integrated on the server. The user end may refer to the front end. Before browsing some web pages or applications, the user end needs to understand the protocols related to the web pages or applications, such as privacy agreements, laws and regulations, etc.

[0072] Exemplarily, the backend management end may transfer the newly generated target protocol text to the protocol database, and manage the protocol text through the protocol database.

[0073] The user end can respond to the trigger operation of browsing the protocol text to send a protocol content request to the protocol database, and the protocol database can send the target protocol text to the user end in response to the protocol content request. The target protocol text is the latest version of the protocol text. After the user end obtains the target protocol text from the protocol database, it can directly display the target protocol text in the protocol format edited in the rich text editor so that the user can understand the relevant protocol content. In this way, it is conducive to ensuring that the protocol content configured in the background is highly consistent with the front-end display effect, reducing development workload and maintenance costs, and can effectively realize the display of the target protocol text.

[0074] Optionally, the user terminal can trigger an instruction to browse the agreement text when entering the associated website or application. That is, when the user needs to browse certain websites or applications, he needs to browse the relevant privacy agreements or laws and regulations and other agreement texts in advance to ensure privacy security or legality.

[0075] Alternatively, the user terminal may display a related control for viewing the protocol text, and the user terminal may display the target protocol text in response to a trigger operation on the control for viewing the protocol text.

[0076] As an example, this application configures legal regulations and agreement texts through the TinyMCE editor, creates, modifies and manages the texts in the background, and the front end can directly read the rich text content returned by the interface through the H5 component or page for display. This solution provides a flexible protocol version update mechanism while maintaining a high degree of content consistency.

[0077] In this embodiment, by displaying a protocol text management interface on the backend management end, and displaying a new protocol control or a modified protocol control on the protocol text management interface, it is convenient for users to modify or add protocol texts on the backend management end, and it is convenient to manage multiple protocol texts or trace the historical versions of protocol texts. And by completing the editing of the protocol content with a rich text editor, it is convenient for the front end to obtain the rich text content and directly display the protocol text in the edited protocol format, ensuring that the displayed protocol text format is consistent with the format of the backend management end, thereby reducing the cost of protocol text management.

[0078] In an exemplary embodiment, Figure 3 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 2 ,like Figure 3 As shown, in Figure 1 On the basis of the present invention, the steps in the protocol text management method are described in detail. In step S102, in response to the editing completion operation triggered in the rich text editor, based on the protocol information edited in the protocol editing interface and the edited protocol format, the target protocol text corresponding to the current protocol version is obtained, including S301 to S302, wherein:

[0079] S301, in response to a triggering operation of a protocol saving control displayed in a rich text editor, displaying a selection window for a protocol saving type;

[0080] S302. In response to a selection operation on a target saving type in a selection window, save the target protocol text in the target saving type; wherein the target saving type is used to indicate whether to remind the user that the protocol version has been updated.

[0081] The protocol save control may refer to a control for saving the edited protocol content after the editing of the protocol content is completed. The protocol save type may refer to a method of saving the protocol, for example, it may be to save the protocol directly or to save the protocol conditionally; saving the protocol conditionally may be used to update the protocol version and remind the user to confirm the updated protocol content. The selection window may refer to a window for selecting the protocol save type.

[0082] Exemplarily, the backend management end can trigger an instruction to save the agreement text in response to a trigger operation of the agreement save control in the TinyMCE editor, and display a selection window for the agreement save type that can be selected. The user can select the type to be saved, for example, the user can choose to save only the agreement text, or choose to save the agreement and update the version. When choosing to save the agreement and update the version, the user end needs to agree to the updated target agreement text again.

[0083] The backend management end may respond to the user's selection operation on the save type in the selection window, take the selected save type as the target selection type, and save the target protocol text according to the target save type.

[0084] Optionally, Figure 4 A schematic diagram of a protocol editing interface provided in an embodiment of the present application Figure 2 ,like Figure 4 As shown, after triggering the "Confirm Save" control, the background management end can display the save type controls of "Save Agreement Only" and "Save Agreement and Update Version".

[0085] Administrators can choose whether to force users to update the agreement. If reminders are enabled, users will see an update prompt the next time they log in and will be asked to read the new agreement.

[0086] In this embodiment, in response to the triggering operation of the protocol save control that can be displayed in the rich text editor, a selection window for the protocol save type is displayed; in this way, the selection of the save type can be provided, and the user end can be forced to confirm the updated protocol text through the background management end, thereby facilitating support for version control and update reminders, helping the platform to operate in compliance, and at the same time protecting the user's right to know.

[0087] In an exemplary embodiment, Figure 5 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 3 ,like Figure 5 As shown, in Figure 1 Based on the above, other steps in the protocol text management method are described in detail. The method also includes S501 to S504, wherein:

[0088] S501. In response to a triggering operation of a protocol type window in a protocol editing interface, display a protocol type list.

[0089] S502: In response to a selection operation on a protocol type in the protocol type list, determine the protocol type of the currently edited protocol.

[0090] S503: In response to the text input operation of the agreement content in the agreement editing interface, the agreement text content is obtained.

[0091] S504: Based on the protocol type and the protocol text content, obtain the protocol information edited in the protocol editing interface.

[0092] For example, Figure 2 As shown, the user can click on the protocol type area in the protocol editing interface, and the backend management end can respond to the triggering operation of the protocol type window in the protocol type area in the protocol editing interface to display a protocol type list, and the protocol type list can display multiple protocol types, for example, it can include service agreements, privacy agreements, and logout agreements. The backend management end can respond to the user's selection operation on the protocol type in the protocol type list, determine the protocol type to which the currently edited protocol text belongs, and can save it with the selected protocol type.

[0093] The backend management terminal may also determine the input or edited protocol text content in response to the text input or editing operation for the protocol content in the protocol content area included in the protocol editing interface. The backend management terminal may generate an updated protocol text according to the above-determined protocol type and protocol text content. The backend management terminal may display the protocol type and creation time of the newly generated protocol text in the protocol text management interface.

[0094] In this embodiment, through the above steps S501 to S504, the protocol information edited by the user can be effectively determined, which is conducive to the effective management of the protocol text, so that the purpose of reducing the management of the protocol text can be achieved through this application.

[0095] In an exemplary embodiment, the method further comprises:

[0096] In response to the operation of opening the protocol text management interface, displaying the historical protocol texts corresponding to the various historical protocol versions in the protocol text management interface;

[0097] In response to the cancel selection operation on the historical protocol text, the selected historical protocol text is canceled.

[0098] The historical protocol text may refer to the protocol text created historically. The historical protocol version may refer to the version corresponding to the protocol text created historically. The cancel selection operation may refer to the operation corresponding to the cancel function. The backend management terminal may be provided with a cancel function for the historical protocol text. For example, a cancel function may be provided for each historical version of the protocol text. In this way, each historical protocol text can be effectively canceled.

[0099] Exemplarily, the backend management terminal may display the protocol text management interface in response to the user's operation of opening the protocol text management; for example, the backend management terminal may display the protocol text management interface in response to the user's click operation on the protocol text management software system. And the historical protocol text corresponding to each historical protocol version may be displayed in the protocol text management interface, for example, the historical protocol text corresponding to multiple historical protocol versions may be displayed in the form of a list, and the historical protocol text may be displayed in reverse order of creation time.

[0100] The backend management terminal can display a cancellation function for each historical protocol text in the protocol text management interface, and the backend management terminal can respond to the selection operation of the cancellation control corresponding to the historical protocol text and cancel the selected historical protocol text. In this way, the historical protocol text that is no longer needed can be cancelled, thereby ensuring the validity of the historical protocol text.

[0101] Optionally, the backend management terminal can save the historical versions of each agreement, and the administrator can trace back the content of the historical versions, or invalidate the agreements that are no longer applicable.

[0102] In this embodiment, by responding to the operation of opening the protocol text management interface, the historical protocol texts corresponding to each historical protocol version can be displayed in the protocol text management interface, which is beneficial for users to manage the historical protocol texts, and by responding to the cancellation selection operation of the historical protocol text, the selected historical protocol text can be invalidated, ensuring the timely cancellation of the historical protocol text, which is beneficial to reducing the cost of protocol text management.

[0103] Optionally, in response to the operation of opening the protocol text management interface, displaying historical protocol texts corresponding to each historical protocol version in the protocol text management interface, further comprising:

[0104] In response to the operation of opening the protocol text management interface, the historical protocol version identifier, protocol type, and protocol modification time corresponding to each historical protocol version are displayed in the protocol text management interface.

[0105] The historical protocol version identifier may refer to the protocol version number, version title, and other identifying information. The protocol modification time may include the protocol creation time, the time when the protocol was last modified, and so on.

[0106] For example, Figure 6 A schematic diagram of a protocol text management interface provided in an embodiment of the present application. The backend management terminal can display the protocol text management interface in response to the user's operation of opening the protocol text management, and can display the historical protocol version identifier, protocol type, protocol modification time and other information corresponding to each historical protocol version in the protocol text management interface. For example, each historical protocol text is displayed in the form of a list, then the version identifier, protocol type, protocol modification time and other information of a historical protocol text can be displayed in the same row, such as Figure 6 shown.

[0107] Optionally, each time the administrator saves or modifies the content of the agreement, the backend management terminal can automatically generate a new agreement version number and record the update time.

[0108] In this embodiment, by responding to the operation of opening the protocol text management interface, the historical protocol version identifier, protocol type, and protocol modification time corresponding to each historical protocol version can be displayed in the protocol text management interface, which helps users to better understand the relevant information of the historical version protocol, and is conducive to the management of historical protocol texts, thereby reducing the management cost of the protocol text.

[0109] In an exemplary embodiment, the method further comprises:

[0110] In response to the installation operation of the rich text editor, obtaining the rich text editor;

[0111] In response to a selection operation on the rich text editor, the rich text editor is used as a preset rich text editor for protocol text management.

[0112] The rich text editor may be a TinyMCE editor.

[0113] Exemplarily, the backend management terminal can install the rich text editor in response to the installation operation for the rich text editor. For example, the TinyMCE editor can be installed using the npm or yarn package management tool. The terminal can reference the rich text editor as the editor of the protocol text in response to the selection operation of the rich text editor. For example, in a page or component that needs to use a rich text editor, the TinyMCE editor can be used in combination with the API provided by it to easily complete the editing and saving of rich text content.

[0114] Optionally, the backend management terminal may also respond to the following content: using TinyMCE configuration items to set parameters such as the appearance, function, and language of the editor.

[0115] In an exemplary embodiment, Figure 7 A schematic diagram of the structure of a protocol text management system provided in an embodiment of the present application, such as Figure 7 As shown, the protocol text management system includes:

[0116] The backend management terminal 710 is used to implement the above-mentioned protocol text management method;

[0117] Database 720, used to store the protocol text transmitted by the backend management terminal;

[0118] The user terminal 730 is used to respond to the trigger operation of the protocol text to be browsed, send a protocol content request to the database, obtain the target protocol text returned by the database, and display the target protocol text in the edited protocol format determined when editing by the backend management terminal.

[0119] For example, Figure 8 A schematic diagram of a protocol text management method provided in an embodiment of the present application Figure 4 ;like Figure 8 As shown, the method is applied to a protocol text management system, and the method includes:

[0120] S801, rich text protocol copy configuration; the backend management end can configure the protocol content through the TinyMCE rich text editor.

[0121] S802, save the agreement text; update the agreement version number; the backend management end can save the agreement text through the backend API interface.

[0122] S803. After updating the protocol text, the backend management terminal may simultaneously update the version protocol number.

[0123] S804, determine whether to prompt the user that the agreement has been updated; the backend management terminal can determine whether the user is prompted that the agreement has been updated when saving, that is, determine the selected agreement saving type.

[0124] S805, storing in database; the backend management end can store the agreement text in the database through the backend API interface.

[0125] S806, requesting protocol content; the user end may request the protocol text through the H5 page.

[0126] S807. Return the rich text content of the protocol; the backend API interface can return the protocol text to the user end.

[0127] S808. Display the agreement text; wherein, the user end can display the agreement text through the front-end rich text display component.

[0128] Optionally, the specific limitations of the protocol text management method executed by the protocol text management system provided in the embodiment of the present application can be found in the above limitations on the protocol text management method, which will not be repeated here.

[0129] Optionally, the system and method provided in the embodiment of the present application have rich text editing and display consistency: through the TinyMCE rich text editor, the text content configured in the background is ensured to be highly consistent with the front-end display effect, reducing development workload and maintenance costs; it has protocol version management and reminder functions: the system supports version control and update reminders to help the platform operate in compliance while protecting the user's right to know; it realizes componentized design: the front-end protocol display is implemented in a componentized manner, which is suitable for a variety of business scenarios, and there is no need for the front-end team to manually configure the display logic; it has cross-platform compatibility: the component can be compatible with display on both mobile (H5) and desktop browsers, and ensure the consistency of the text format.

[0130] In this embodiment, it has efficient version management: the system has version control and update prompt functions to ensure compliance and user notification after the protocol is updated. It has consistent text display: the rich text content configured in the background can be used directly on the front end without additional formatting processing, ensuring consistent display on different terminals and browsers. It has a flexible componentized design: compared with solutions that require manual configuration, the componentized design of the present invention improves reusability, so that the protocol display function can be seamlessly applied to multiple business scenarios. It is operationally convenient: operators can directly configure and update the protocol content through the background, which greatly improves work efficiency without relying on technical developers.

[0131] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0132] The following is a description of the protocol text management device provided in an embodiment of the present application. The protocol text management device and the above-mentioned protocol text management method have the same inventive concept, and the implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above-mentioned method. Therefore, the specific limitations in one or more protocol text management device embodiments provided below can refer to the limitations on the protocol text management method above. The protocol text management device described below and the protocol text management method described above can be referenced to each other, and will not be repeated here.

[0133] In an exemplary embodiment, Fig. 9 A schematic diagram of the structure of a protocol text management device provided in an embodiment of the present application, such as Fig. 9 As shown, the protocol text management device 90 includes: an editing response module 910, a protocol determination module 920, and a protocol transmission module 930, wherein:

[0134] The editing response module 910 is used to display a protocol editing interface corresponding to a preset rich text editor in response to a triggering operation of adding a new protocol control or modifying a protocol control displayed in the protocol text management interface.

[0135] The protocol determination module 920 is used to obtain the target protocol text corresponding to the current protocol version based on the protocol information edited in the protocol editing interface and the edited protocol format in response to the editing completion operation triggered in the rich text editor.

[0136] The protocol transmission module 930 is used to transmit the target protocol text to the protocol database; the protocol database is used to return the target protocol text to the user end in response to the protocol content request of the user end.

[0137] The user terminal is used to display the target protocol text in the edited protocol format in response to a triggering operation of the protocol text to be browsed.

[0138] In an exemplary embodiment, the protocol determination module is used to display a selection window for the protocol save type in response to a trigger operation of a protocol save control displayed in a rich text editor; in response to a selection operation of a target save type in the selection window, save the target protocol text with the target save type; wherein the target save type is used to indicate whether to remind the user that the protocol version has been updated.

[0139] In an exemplary embodiment, the device further includes a type window module, a type determination module, a text content module, and a protocol information module.

[0140] The type window module is used to display the protocol type list in response to the trigger operation of the protocol type window in the protocol editing interface. The type determination module is used to determine the protocol type of the currently edited protocol in response to the selection operation of the protocol type in the protocol type list. The text content module is used to obtain the protocol text content in response to the text input operation of the protocol content in the protocol editing interface. The text content module is used to obtain the protocol information edited in the protocol editing interface based on the protocol type and the protocol text content.

[0141] In an exemplary embodiment, the apparatus further includes a history protocol module and an invalidation processing module.

[0142] The historical protocol module is used to respond to the operation of opening the protocol text management interface and display the historical protocol texts corresponding to each historical protocol version in the protocol text management interface. The cancellation processing module is used to respond to the cancellation selection operation of the historical protocol text and cancel the selected historical protocol text.

[0143] In an exemplary embodiment, the historical protocol module is used to respond to the operation of opening the protocol text management interface and display the historical protocol version identifier, protocol type, and protocol modification time corresponding to each historical protocol version in the protocol text management interface.

[0144] In an exemplary embodiment, the apparatus further includes an editor installation module and an editor selection module.

[0145] The editor installation module is used to obtain the rich text editor in response to the installation operation of the rich text editor. The editor selection module is used to use the rich text editor as a preset rich text editor for protocol text management in response to the selection operation of the rich text editor.

[0146] In an exemplary embodiment, the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by one or more processors, the one or more processors execute the steps of the protocol text management method in any one of the above embodiments.

[0147] In an exemplary embodiment, the present application also provides a computer device having a computer program stored therein, wherein when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the protocol text management method as described in any one of the above embodiments.

[0148] In an exemplary embodiment, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the protocol text management method in any of the above embodiments.

[0149] Indicatively, Fig.10 As shown, Fig.10 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. The computer device 1000 may be provided as a server. Fig.10 The computer device 1000 includes a processing component 1002, which further includes one or more processors, and a memory resource represented by a memory 1001 for storing instructions executable by the processing component 1002, such as an application. The application stored in the memory 1001 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1002 is configured to execute instructions to perform the text recognition method of any of the above embodiments.

[0150] The computer device 1000 may further include a power supply component 1003 configured to perform power management of the computer device 1000, a wired or wireless network interface 1004 configured to connect the computer device 1000 to a network, and an input / output (I / O) interface 1005. The computer device 1000 may operate based on an operating system stored in the memory 1001, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, Free BSD TM, or the like.

[0151] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0152] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0153] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0154] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can refer to each other.

[0155] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A protocol text management method, characterized in that: The method comprises: In response to a triggering operation of adding a new protocol control or modifying a protocol control displayed in the protocol text management interface, a protocol editing interface corresponding to a preset rich text editor is displayed; In response to an edit completion operation triggered in the rich text editor, based on the protocol information edited in the protocol editing interface and the edited protocol format, a target protocol text corresponding to the current protocol version is obtained; The target protocol text is transmitted to a protocol database; the protocol database is used to return the target protocol text to the user terminal in response to a protocol content request from the user terminal; The user terminal is used to display the target protocol text in the edited protocol format in response to a triggering operation of the protocol text to be browsed.

2. The method according to claim 1, characterized in that: The step of obtaining, in response to an edit completion operation triggered in the rich text editor, a target protocol text corresponding to the current protocol version based on the protocol information edited in the protocol editing interface and the edited protocol format, includes: In response to a triggering operation of a protocol saving control displayed in the rich text editor, a selection window for a protocol saving type is displayed; In response to a selection operation of a target saving type in the selection window, the target protocol text is saved in the target saving type; wherein the target saving type is used to indicate whether to remind the user that the protocol version has been updated.

3. The method according to claim 1, characterized in that: The method further comprises: In response to a triggering operation of a protocol type window in the protocol editing interface, displaying a protocol type list; In response to a selection operation of a protocol type in the protocol type list, determining the protocol type of the currently edited protocol; In response to a text input operation of the agreement content in the agreement editing interface, acquiring the agreement text content; Based on the protocol type and the protocol text content, the protocol information edited in the protocol editing interface is obtained.

4. The method according to claim 1, characterized in that: The method further comprises: In response to the operation of opening the protocol text management interface, displaying the historical protocol texts corresponding to the various historical protocol versions in the protocol text management interface; In response to the cancel selection operation on the historical protocol text, the selected historical protocol text is canceled.

5. The method according to claim 4, characterized in that In response to the operation of opening the protocol text management interface, displaying the historical protocol texts corresponding to each historical protocol version in the protocol text management interface, further comprising: In response to the operation of opening the protocol text management interface, the historical protocol version identifier, protocol type, and protocol modification time corresponding to each historical protocol version are displayed in the protocol text management interface.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: In response to the installation operation of the rich text editor, obtaining the rich text editor; In response to a selection operation on the rich text editor, the rich text editor is used as a preset rich text editor for the protocol text management.

7. A protocol text management system, characterized in that: The system comprises: A backend management terminal, used to implement the protocol text management method according to any one of claims 1 to 6; A database, used to store the protocol text transmitted by the background management end; The user end is used to respond to the trigger operation of the protocol text to be browsed, send a protocol content request to the database, obtain the target protocol text returned by the database, and display the target protocol text in the edited protocol format determined when editing by the background management end.

8. A protocol text management device, characterized in that: The device comprises: An editing response module, used to respond to a triggering operation of adding a new protocol control or modifying a protocol control displayed in the protocol text management interface, and display a protocol editing interface corresponding to a preset rich text editor; A protocol determination module, configured to obtain a target protocol text corresponding to the current protocol version based on the protocol information edited in the protocol editing interface and the edited protocol format in response to an edit completion operation triggered in the rich text editor; A protocol transmission module, used to transmit the target protocol text to a protocol database; the protocol database is used to return the target protocol text to the user terminal in response to a protocol content request from the user terminal; The user terminal is used to display the target protocol text in the edited protocol format in response to a triggering operation of the protocol text to be browsed.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images