A method and apparatus for managing page history maintenance records.

Abstract

This invention discloses a method and apparatus for managing page history maintenance records, relating to the field of financial information service technology. One specific implementation of the method includes: responding to a monitored query operation targeting a target page, determining whether the target page meets preset conditions; if the target page meets the preset conditions, obtaining the history maintenance record corresponding to the target page, and retrieving the historical value of a target field in the target page from the history maintenance record; responding to a monitored submission operation targeting the target page, obtaining the current value of the target field; comparing the current value with the historical value, and if the comparison result indicates that the current value and the historical value are different, saving the current value to the history maintenance record. This implementation stores the history maintenance record in the front-end system, independent of various back-end service systems, reducing the coupling between the front-end and back-end systems, reducing development workload, and saving development costs.

Description

Technical Field

[0001] This invention relates to the field of financial information service technology, and in particular to a method and apparatus for managing page history maintenance records. Background Technology

[0002] For business operations in application systems that require maintenance, it is necessary to query historical maintenance records to trace other related issues during maintenance.

[0003] In related technologies, the historical maintenance records of a page are generally stored in the backend service system, and then the frontend system calls the query function provided by the backend service system to retrieve the historical maintenance records. However, when multiple business functions depend on multiple different backend service systems, the requirements for the query functions provided by different backend service systems are different. The frontend system needs to repeatedly develop query pages, and if the backend system does not support querying, a query interface also needs to be developed, resulting in a large workload and high cost. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a method and apparatus for managing page history maintenance records, which stores the history maintenance records in the front-end system without relying on various back-end service systems, thereby reducing the coupling between the front-end and back-end systems, reducing development workload, and saving development costs.

[0005] To achieve the above objectives, according to one aspect of the present invention, a method for managing page history maintenance records is provided, comprising:

[0006] In response to the detection of a query operation targeting a target page, determine whether the target page meets preset conditions;

[0007] If the target page meets the preset conditions, obtain the historical maintenance record corresponding to the target page, and obtain the historical value of the target field in the target page from the historical maintenance record;

[0008] In response to a detected submission operation to the target page, the current value of the target field is obtained;

[0009] The current value is compared with the historical value. If the comparison result indicates that the current value is different from the historical value, the current value is saved to the historical maintenance record.

[0010] Optionally, after saving the current value to the historical maintenance record, the process includes: using the current value as the historical value of the target field.

[0011] Optionally, the preset condition is that the URL address of the target page exists in the registration configuration file.

[0012] Optionally, before determining whether the target page meets the preset conditions, the process includes:

[0013] Register and configure multiple page URLs, and save these multiple page URLs in the registration configuration file.

[0014] Optionally, before determining whether the URL address of the target page exists in the registration configuration file, the method further includes:

[0015] The registration configuration includes HTML element blocks in the main page and its subpages corresponding to the page URL address, wherein the HTML element blocks include multiple preset fields, and the target field is one or more of the multiple preset fields.

[0016] Optionally, after comparing the current value with the historical value, the method further includes:

[0017] If the comparison result indicates that the current value is the same as the historical value, the current value is not saved.

[0018] Optionally, before retrieving the historical value of the target field from the historical maintenance record, the following steps are included:

[0019] It is determined that a historical value for the target field exists in the historical maintenance record;

[0020] If the target field does not have a historical value in the historical maintenance record, the current value is saved to the historical maintenance record.

[0021] Optionally, the method further includes:

[0022] After obtaining the historical value of the target field in the target page from the historical maintenance record, a scheduled task is started to monitor the target page and obtain the field value of the target field. Based on the historical value and the field value, it is determined whether the value of the target field has been modified. If it has been modified, the field value is saved in the historical maintenance record.

[0023] Optionally, before obtaining the historical value of the target field in the target page from the historical maintenance record, the process includes: constructing a behavior analysis function and declaring a global variable and a local variable;

[0024] Comparing the current value with the historical value includes:

[0025] The historical value is assigned to the global variable; the current value is assigned to the local variable; the behavior analysis function is used to compare the historical value in the global variable and the current value in the local variable to obtain the comparison result.

[0026] According to another aspect of the present invention, a management device for page history maintenance records is provided, comprising:

[0027] The judgment module, in response to the monitoring of a query operation for the target page, determines whether the target page meets preset conditions;

[0028] The first acquisition module, when the target page meets the preset conditions, acquires the historical maintenance record corresponding to the target page, and acquires the historical value of the target field in the target page from the historical maintenance record;

[0029] The second acquisition module, in response to detecting a submission operation for the target page, acquires the current value of the target field;

[0030] The determination module compares the current value with the historical value. If the comparison result indicates that the current value is different from the historical value, the current value is saved to the historical maintenance record.

[0031] Optionally, the determining module is further configured to: after saving the current value to the historical maintenance record, use the current value as the historical value of the target field.

[0032] Optionally, the preset condition is that the URL address of the target page exists in the registration configuration file.

[0033] Optionally, the judgment module is further configured to: register and configure multiple page URL addresses before judging whether the target page meets the preset conditions, and save the multiple page URL addresses in the registration configuration file.

[0034] Optionally, the determination module is further configured to: before determining whether the URL address of the target page exists in the registration configuration file, register the configuration of the HTML element block in the main page and its subpages corresponding to the page URL address, wherein the HTML element block includes multiple preset fields, and the target field is one or more of the multiple preset fields.

[0035] Optionally, the determining module is further configured to: after comparing the current value with the historical value, if the comparison result indicates that the current value is the same as the historical value, not save the current value.

[0036] Optionally, the first acquisition module is further configured to: determine that a historical value of the target field exists in the historical maintenance record before acquiring the historical value of the target field from the historical maintenance record; and save the current value to the historical maintenance record if a historical value of the target field does not exist in the historical maintenance record.

[0037] Optionally, the device further includes a monitoring module, configured to: after obtaining the historical value of the target field in the target page from the historical maintenance record, start a scheduled task to monitor the target page, obtain the field value of the target field, determine whether the value of the target field has been modified based on the historical value and the field value, and if the modification exists, save the field value in the historical maintenance record.

[0038] Optionally, the first acquisition module is further configured to: before acquiring the historical value of the target field in the target page from the historical maintenance record, construct a behavior analysis function and declare a global variable and a local variable;

[0039] The determining module is further configured to: assign the historical value to the global variable; assign the current value to the local variable; and use the behavior analysis function to compare the historical value in the global variable and the current value in the local variable to obtain a comparison result.

[0040] According to another aspect of the present invention, an electronic device is provided, comprising:

[0041] One or more processors;

[0042] Storage device for storing one or more programs.

[0043] When the one or more programs are executed by the one or more processors, the one or more processors implement the page history maintenance record management method provided by the present invention.

[0044] According to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the page history maintenance record management method provided by the present invention.

[0045] According to another aspect of the present invention, a computer program product is provided, including a computer program that, when executed by a processor, implements the page history maintenance record management method provided by the present invention.

[0046] One embodiment of the above invention has the following advantages or beneficial effects: By monitoring the operation behavior on the target page, judging whether the target page meets the preset conditions, and if the target page meets the preset conditions, comparing the historical value of the target field obtained from the historical maintenance record during the query operation with the current value of the target field obtained during the submission operation, obtaining the comparison result, and saving the current value to the historical maintenance record if the current value is inconsistent with the historical value, thereby updating the historical maintenance record. This method is applied to the front end, and the front end saves the historical maintenance record, thereby reducing the communication cost between the front end and the back end service system, reducing redundant R&D workload, freeing up R&D manpower, reducing the coupling between the front end and the back end system, providing basic data for the front end to implement the monitoring function, and overcoming the defects of related technologies, such as the need for the front end system to repeatedly develop the query and maintenance record page, the lack of effective monitoring methods in the front end system, the need for the back end service system to manually develop the query and maintenance record function, and the high degree of dependence and coupling between the front end and the back end.

[0047] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0048] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0049] Figure 1 This is a schematic diagram of the main process of a page history maintenance record management method according to an embodiment of the present invention;

[0050] Figure 2 This is a schematic diagram of the main process of another page history maintenance record management method according to an embodiment of the present invention;

[0051] Figure 3 This is a schematic diagram of the main process of another page history maintenance record management method according to an embodiment of the present invention;

[0052] Figure 4 This is a flowchart illustrating a method for managing page history maintenance records according to an embodiment of the present invention;

[0053] Figure 5 This is a schematic diagram of the main modules of the page history maintenance record management device according to an embodiment of the present invention;

[0054] Figure 6 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0055] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0056] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0057] It should be noted that the acquisition, storage, use, and processing of data in this application comply with the relevant provisions of national laws and regulations and do not violate public order and good morals.

[0058] Figure 1 This is a schematic diagram of the main flow of a page history maintenance record management method according to an embodiment of the present invention, as shown below. Figure 1 As shown, the method includes the following steps:

[0059] Step S101: In response to the detection of a query operation for the target page, determine whether the target page meets the preset conditions;

[0060] Step S102: If the target page meets the preset conditions, obtain the historical maintenance record corresponding to the target page, and obtain the historical value of the target field in the target page from the historical maintenance record;

[0061] Step S103: In response to the detected submission operation for the target page, obtain the current value of the target field;

[0062] Step S104: Compare the current value with the historical value. If the comparison result indicates that the current value is different from the historical value, save the current value to the historical maintenance record.

[0063] In this embodiment of the invention, the method is applied to a front-end system to monitor page behavior. In related technologies, after a front-end page is displayed, it can receive query operations performed by the user on the page, obtain the corresponding query results, and display them on the front-end page. The user can then perform operations on the information on the page, such as adding, modifying, or deleting. After the user submits the operation, the front-end system stores the submitted page data in the back-end service system, allowing the back-end service system to save the page data. In this embodiment of the invention, the page data that needs to be saved is stored in the historical maintenance records of the front-end system database according to business requirements. Subsequent queries of these historical maintenance records can be performed without relying on the back-end service system.

[0064] In this embodiment of the invention, the page that needs to save the historical maintenance record can be a maintenance transaction page, such as the "Merchant MCC Code Blacklist Maintenance" transaction for retail loans. The business functions of this transaction include adding, modifying, deleting, and querying maintenance flow, all of which are maintenance operations. The historical maintenance record saves the data corresponding to each maintenance operation.

[0065] When a query operation targeting a target page is detected, the registration configuration file is referenced to determine if the target page meets preset conditions. These preset conditions can include the existence of the target page's URL (Uniform Resource Locator) address in the registration configuration file. If the target page's URL address exists in the registration configuration file, the historical maintenance record of that target page is retrieved, and then the historical value of the target field in the target page is obtained from the historical maintenance record. The historical value of the target field can be the last stored value of the target field. The historical maintenance record is stored in the front-end system's database, cache, or memory, and can also be stored in the back-end service system's database.

[0066] In this embodiment of the invention, the preset condition can be that the URL address of the target page exists in the registration configuration file. That is, if the URL address of the target page exists in the registration configuration file or the URL address of the target page matches the URL address in the registration configuration file, it means that the URL address of the target page has been registered, and the target page is determined to meet the preset condition.

[0067] In this embodiment of the invention, the preset condition can also be that the target page has a preset identifier. That is, a preset identifier can be added in advance for the page that needs to be maintained. If the page has the preset identifier, the preset condition is met. Alternatively, the preset condition can also be that the page identifier of the target page exists in the registration configuration file.

[0068] In this embodiment of the invention, before determining whether a target page meets preset conditions, the process includes: registering and configuring multiple page URL addresses, and storing these multiple page URL addresses in a registration configuration file. It also includes: registering and configuring HTML element blocks in the main page and its subpages corresponding to the page URL addresses, wherein the HTML element blocks include multiple preset fields, and the target field is one or more of these preset fields. In other words, multiple page URL addresses are pre-registered and configured, and HTML element blocks in each page are configured. These HTML element blocks include multiple preset fields and are stored in the registration configuration file. By referencing the registration configuration file, the determination of whether the target page meets the preset conditions is made. That is, the registration configuration file includes the URL addresses of the pages that need to be maintained and the fields in the pages whose values ​​need to be stored. By referencing the registration configuration file when the page is displayed, effective monitoring of pages that need to save historical maintenance records can be achieved.

[0069] In this embodiment of the invention, after comparing the current value with the historical value, the method further includes: if the comparison result indicates that the current value is the same as the historical value, the current value is not saved. That is, if the current value is the same as the historical value, it means that the value of the target field has not been modified, and therefore there is no need to update the historical maintenance record.

[0070] In embodiments of the present invention, such as Figure 2 As shown, when the target page meets preset conditions, the method includes:

[0071] Step S201: Obtain the historical maintenance records corresponding to the target page;

[0072] Step S202: Determine whether there is a historical value of the target field in the target page in the historical maintenance record; if yes, proceed to step S203; if no, proceed to step S204.

[0073] Step S203: Obtain the historical value of the target field from the historical maintenance records;

[0074] Step S204: Save the current value to the historical maintenance record.

[0075] In this embodiment of the invention, if the target page meets the preset conditions, such as the existence of a URL address in the registration configuration file that is the same as the URL address of the target page, then the historical maintenance record of the target page is obtained, and it is determined whether there is a historical value of the target field in the historical maintenance record. If it does not exist, the current value is saved to the historical maintenance record, and the current value will be used as the historical value next time. If it exists, the historical value of the target field is directly obtained from the historical maintenance record and compared with the current value.

[0076] In this embodiment of the invention, the method further includes: after obtaining the historical value of the target field in the target page from the historical maintenance record, starting a scheduled task to monitor the target page, obtaining the field value of the target field, and determining whether the value of the target field has been modified based on the historical value and the field value. If the value has been modified, the field value is saved in the historical maintenance record.

[0077] In this embodiment of the invention, when the target page is displayed, a scheduled task is initiated to periodically analyze page behavior on the target page. Specifically, this involves periodically retrieving the field value of a target field on the target page and determining whether the field value is the same as its historical value (i.e., whether it has been modified). If no modification is found, no action is taken. If a modification is found, the field value is saved to the historical maintenance record, along with the modification time. The query time of the scheduled task can be used as the modification time. The execution interval of the scheduled task can be customized. Monitoring the target page through scheduled tasks allows for timely acquisition of operations performed on the target page, facilitating subsequent business analysis based on the monitoring results.

[0078] In this embodiment of the invention, before obtaining the historical value of the target field in the target page from the historical maintenance record, the process includes: constructing a behavior analysis function, declaring a global variable and a local variable; such as Figure 3 As shown, the current value is compared with historical values, including:

[0079] Step S301: Assign the historical value to the global variable;

[0080] Step S302: Assign the current value to a local variable;

[0081] Step S303: Use a behavior analysis function to compare the historical values ​​in the global variables with the current values ​​in the local variables to obtain the comparison results.

[0082] In this embodiment of the invention, in the behavior analysis function, global variables are used to cache historical values, and local variables are used to cache current values. The behavior analysis function can be used to determine whether the URL address of the target page exists in the registration configuration file; that is, to determine whether there is a URL address in the registration configuration file that is the same as the URL address of the target page. If they are different, no processing is performed; if they are the same, the current value of the target field in the target page is assigned to the local variable. The value of the global variable is retrieved. If the global variable does not exist (i.e., the target field does not have a historical value), the current value of the local variable is assigned to the global variable. If the global variable exists (i.e., the target field has a historical value), the values ​​in the global variable and the local variable are compared; that is, it is determined whether the historical value in all variables and the current value in the local variable are the same. If they are the same, no processing is performed; if they are different, the current value is saved to the historical maintenance record.

[0083] Figure 4This is a flowchart illustrating a method for managing page history maintenance records according to an embodiment of the present invention. The user opens the current page, performs a query and submit operation, and simultaneously starts a scheduled task to monitor the current page; a page behavior analysis function is called to analyze the page behavior; a registration configuration file is read, which includes URLs of multiple pages and multiple preset fields in HTML element blocks; it is determined whether the URL of the current page has been registered; if not, the process ends; if so, the current value of the target field is obtained and cached in a local variable; it is determined whether the global variable is empty; if so, the current value in the local variable is assigned to the global variable; if not, it is determined whether the current value in the local variable is consistent with the historical value in the global variable; if so, the process ends; if not, the current value is saved to the history maintenance record so that the history maintenance record can be applied to user behavior analysis scenarios.

[0084] The page history maintenance record management method of this invention monitors the operation behavior of the target page, calls the registration configuration file and behavior analysis function, and judges whether the target page meets the preset conditions through the registration configuration file. If the target page meets the preset conditions, the behavior analysis function compares the historical value of the target field obtained from the history maintenance record of the front end during the query operation with the current value of the target field obtained during the submission operation, and obtains the comparison result. If the current value is inconsistent with the historical value, the current value is saved to update the history maintenance record. Scheduled tasks are used to monitor the behavior of the target page in a timely manner to obtain the modification status of the target field. This method is applied to the front end, and the front end saves the history maintenance record, thereby reducing the communication cost between the front end and the back end service system, reducing redundant R&D workload, freeing up R&D manpower, reducing the coupling between the front end and the back end system, and providing basic data for the front end to implement monitoring functions. It overcomes the defects of related technologies, such as the need for the front end system to repeatedly develop the query maintenance record page, the lack of effective monitoring methods in the front end system, the need for the back end service system to manually develop the query maintenance record function, and the high degree of dependence and coupling between the front end and the back end.

[0085] According to another aspect of the embodiments of the present invention, such as Figure 5 As shown, a page history maintenance record management device 500 is provided, comprising:

[0086] The judgment module 501, in response to the monitoring of a query operation for the target page, determines whether the target page meets the preset conditions;

[0087] The first acquisition module 502, when the target page meets the preset conditions, acquires the historical maintenance record corresponding to the target page, and acquires the historical value of the target field in the target page from the historical maintenance record;

[0088] The second acquisition module 503, in response to the monitored submission operation to the target page, acquires the current value of the target field;

[0089] The determination module 504 compares the current value with the historical value. If the comparison result indicates that the current value is different from the historical value, the current value is saved to the historical maintenance record.

[0090] In this embodiment of the invention, the determining module 504 is further configured to: after saving the current value to the historical maintenance record, use the current value as the historical value of the target field.

[0091] In this embodiment of the invention, the preset condition is that the URL address of the target page exists in the registration configuration file.

[0092] In this embodiment of the invention, the judgment module 501 is further configured to: register and configure multiple page URL addresses before judging whether the target page meets the preset conditions, and save the multiple page URL addresses in the registration configuration file.

[0093] In this embodiment of the invention, the judgment module 501 is further configured to: before judging whether the URL address of the target page exists in the registration configuration file, register the HTML element block in the main page and its subpages corresponding to the page URL address, wherein the HTML element block includes multiple preset fields, and the target field is one or more of the multiple preset fields.

[0094] In this embodiment of the invention, the determining module 504 is further configured to: after comparing the current value with the historical value, if the comparison result indicates that the current value is the same as the historical value, not save the current value.

[0095] In this embodiment of the invention, the first acquisition module 502 is further configured to: determine that a historical value of the target field exists in the historical maintenance record before acquiring the historical value of the target field from the historical maintenance record; and save the current value to the historical maintenance record if a historical value of the target field does not exist in the historical maintenance record.

[0096] In this embodiment of the invention, the device further includes a monitoring module, which is used to: after obtaining the historical value of the target field in the target page from the historical maintenance record, start a scheduled task to monitor the target page, obtain the field value of the target field, and determine whether the value of the target field has been modified based on the historical value and the field value. If the value has been modified, the field value is saved in the historical maintenance record.

[0097] In this embodiment of the invention, the first acquisition module 502 is further configured to: before acquiring the historical value of the target field in the target page from the historical maintenance record, construct a behavior analysis function and declare a global variable and a local variable;

[0098] The determination module 504 is further used to: assign historical values ​​to global variables; assign current values ​​to local variables; and use behavioral analysis functions to compare the historical values ​​in global variables and the current values ​​in local variables to obtain comparison results.

[0099] According to another aspect of the present invention, an electronic device is provided, comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the page history maintenance record management method provided by the present invention.

[0100] According to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the page history maintenance record management method provided by the present invention.

[0101] According to another aspect of the present invention, a computer program product is provided, including a computer program that, when executed by a processor, implements the page history maintenance record management method provided by the present invention.

[0102] Figure 6 An exemplary system architecture 600 is shown, which can be applied to the page history maintenance record management method or page history maintenance record management device according to embodiments of the present invention.

[0103] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing communication links between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0104] Users can use terminal devices 601, 602, and 603 to interact with server 605 via network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0105] Terminal devices 601, 602, and 603 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0106] Server 605 can be a server that provides various services, such as a backend management server that supports shopping websites browsed by users using terminal devices 601, 602, and 603 (for example only). The backend management server can analyze and process data such as received product information query requests, and feed back the processing results (such as target push information, product information - for example only) to the terminal devices.

[0107] It should be noted that the page history maintenance record management method provided in the embodiments of the present invention is generally executed by terminal devices 601, 602, and 603, and correspondingly, the page history maintenance record management device is generally set in terminal devices 601, 602, and 603.

[0108] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0109] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing a terminal device of the present invention. Figure 7 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0110] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0111] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0112] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this invention.

[0113] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0114] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0115] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a judgment module, a first acquisition module, a second acquisition module, and a determination module. The names of these modules do not necessarily limit the module itself; for example, the judgment module can also be described as "a module that, in response to monitoring a query operation for a target page, determines whether the target page meets preset conditions."

[0116] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to include: in response to monitoring a query operation for a target page, determining whether the target page meets preset conditions; if the target page meets the preset conditions, obtaining a historical maintenance record corresponding to the target page, and obtaining a historical value of a target field in the target page from the historical maintenance record; in response to monitoring a submission operation for the target page, obtaining the current value of the target field; comparing the current value with the historical value, and if the comparison result indicates that the current value and the historical value are different, saving the current value to the historical maintenance record.

[0117] According to the technical solution of this embodiment of the invention, the method for managing historical maintenance records of a page monitors the operation behavior of the target page, calls the registration configuration file and behavior analysis function, judges whether the target page meets preset conditions through the registration configuration file, and if the target page meets the preset conditions, uses the behavior analysis function to compare the historical value of the target field obtained from the historical maintenance record of the front end during the query operation with the current value of the target field obtained during the submission operation, obtains the comparison result, and saves the current value when the current value is inconsistent with the historical value, thereby updating the historical maintenance record. Scheduled tasks are used to monitor the behavior of the target page periodically to obtain the modification status of the target field in a timely manner. This method is applied to the front end, where the front end saves historical maintenance records, thereby reducing the communication cost between the front end and the back end service system, reducing redundant R&D workload, freeing up R&D manpower, reducing the coupling between the front end and the back end system, providing basic data for the front end to implement monitoring functions, and overcoming the defects of related technologies where the front end system needs to repeatedly develop a query maintenance record page, the front end system lacks effective monitoring methods, the back end service system needs manpower to develop a query maintenance record function, and the front end and back end have high dependence and high coupling.

[0118] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A management method of a page history maintenance record, characterized by, The method comprises the following steps: in response to monitoring a query operation for a target page, judging whether the target page meets a preset condition; in the case where the target page meets the preset condition, obtaining a historical maintenance record corresponding to the target page, and obtaining a historical value of a target field in the target page from the historical maintenance record; in response to monitoring a submission operation for the target page, obtaining a current value of the target field; comparing the current value with the historical value, and in the case where the comparison result indicates that the current value is different from the historical value, saving the current value into the historical maintenance record; wherein, after obtaining the historical value of the target field in the target page from the historical maintenance record, the method further comprises starting a timing task to monitor the target page, obtaining a field value of the target field, judging whether the value of the target field is modified according to the historical value and the field value, and in the case where the value is modified, saving the field value in the historical maintenance record; before obtaining the historical value of the target field in the target page from the historical maintenance record, the method comprises constructing a behavior analysis function, declaring a global variable and a local variable; comparing the current value with the historical value comprises: assigning the historical value to the global variable; assigning the current value to the local variable; using the behavior analysis function to compare the historical value in the global variable with the current value in the local variable to obtain a comparison result.

2. The method of claim 1, wherein, after saving the current value into the historical maintenance record, the method comprises: taking the current value as the historical value of the target field.

3. The method of claim 1, wherein, The preset condition is that the URL address of the target page exists in a registration configuration file.

4. The method of claim 3, wherein, Before judging whether the target page meets the preset condition, the method comprises: registering configuration of a plurality of page URL addresses, and saving the plurality of page URL addresses in the registration configuration file.

5. The method of claim 4, wherein, Before judging whether the target page meets the preset condition, the method further comprises: registering configuration of an html element block in a main page and a sub-page corresponding to the page URL address, wherein the html element block comprises a plurality of preset fields, and the target field is one or more of the plurality of preset fields.

6. The method of claim 1, wherein, After comparing the current value with the historical value, the method further comprises: in the case where the comparison result indicates that the current value is the same as the historical value, not saving the current value.

7. The method of claim 1, wherein, Before obtaining the historical value of the target field from the historical maintenance record, the method comprises: determining that the historical maintenance record contains the historical value of the target field; in the case where the historical maintenance record does not contain the historical value of the target field, saving the current value into the historical maintenance record.

8. A management apparatus for maintaining a record of a page history, characterized by comprising: The method comprises the following steps: a judging module, in response to monitoring a query operation for a target page, judging whether the target page meets a preset condition; a first obtaining module, in the case where the target page meets the preset condition, obtaining a historical maintenance record corresponding to the target page, and obtaining a historical value of a target field in the target page from the historical maintenance record; The second obtaining module obtains the current value of the target field in response to monitoring a submission operation for the target page; The determining module compares the current value with the historical value, and saves the current value into the historical maintenance record in a case where the comparison result indicates that the current value is different from the historical value; The apparatus further includes a monitoring module configured to: after obtaining the historical value of the target field in the target page from the historical maintenance record, start a timing task to monitor the target page, obtain a field value of the target field, and determine whether the value of the target field is modified according to the historical value and the field value, and save the field value in the historical maintenance record in a case where the value is modified; The first obtaining module is further configured to: before obtaining the historical value of the target field in the target page from the historical maintenance record, construct a behavior analysis function, and declare a global variable and a local variable; The determining module is further configured to: assign the historical value to the global variable, assign the current value to the local variable, and compare the historical value in the global variable with the current value in the local variable by using the behavior analysis function to obtain a comparison result.

9. The apparatus of claim 8, wherein, The determining module is further configured to: after saving the current value into the historical maintenance record, take the current value as the historical value of the target field.

10. The apparatus of claim 8, wherein, The preset condition is that the URL address of the target page exists in a registration configuration file.

11. The apparatus of claim 10, wherein, The judging module is further configured to: before judging whether the target page meets the preset condition, register a plurality of page URL addresses, and save the plurality of page URL addresses in the registration configuration file.

12. The apparatus of claim 11, wherein, The judging module is further configured to: before judging whether the URL address of the target page exists in the registration configuration file, register an html element block in a main page and a sub-page corresponding to the page URL address, wherein the html element block includes a plurality of preset fields, and the target field is one or more of the plurality of preset fields.

13. The apparatus of claim 8, wherein, The determining module is further configured to: after comparing the current value with the historical value, in a case where the comparison result indicates that the current value is the same as the historical value, do not save the current value.

14. The apparatus of claim 8, wherein, The first obtaining module is further configured to: before obtaining the historical value of the target field from the historical maintenance record, determine that the historical value of the target field exists in the historical maintenance record, and save the current value into the historical maintenance record in a case where the historical value of the target field does not exist in the historical maintenance record.

15. An electronic device, comprising: One or more processors; a storage device for storing one or more programs, The one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method according to any one of claims 1-7. The program, when executed by the processor, implements the method according to any one of claims 1-7.

16. A computer readable medium having stored thereon a computer program, characterized in that, The computer program, when executed by the processor, implements the method according to any one of claims 1-7.

17. A computer program product comprising a computer program, characterized in that, ​

Images