Business record processing method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to the technical field of big data, and particularly discloses a business record processing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: receiving a service record maintenance request for any sub-service system in a service system; under the condition that the maintenance record annotation pre-configured by the service system indicates to intercept the service record maintenance request, determining the type of intercepted data aiming at the interception processing logic configured by the service record maintenance request based on the maintenance record annotation; according to the type of the intercepted data, intercepting a maintenance record formed by triggering the service record maintenance request; storing the maintenance record in a maintenance record table of the service system; the maintenance record table is used for responding to the maintenance record query operation of any business record and returning the maintenance record meeting the query condition corresponding to the maintenance record query operation. By adopting the method, the beneficial effect of efficiently and uniformly processing the business records of each sub-business system can be achieved.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a business record processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of Internet technology, more and more business organizations implement different business functions by deploying multiple sub-business systems.

[0003] At present, the business systems of large business organizations deploy a large number of sub-business systems. Each sub-business system implements the basic function of business records according to its own business. Since the basic function of business records needs to be coupled to the normal business logic of each business subsystem, a large amount of code workload will be generated, resulting in high business complexity. In addition, in actual applications, the same business processing logic exists in different sub-business systems. When the basic function of business records is coupled to the normal business logic of each business subsystem, redundant business processing work will be generated, reducing development efficiency.

[0004] Therefore, there is a problem in the traditional technology that the business records of each sub-business system cannot be processed in a unified and efficient manner. Summary of the invention

[0005] Based on this, it is necessary to provide a business record processing method, apparatus, computer equipment, computer-readable storage medium and computer program product that can efficiently and uniformly process the business records of each sub-business system in response to the above technical problems.

[0006] A business record processing method, comprising:

[0007] Receiving a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any sub-business system;

[0008] In the case where the maintenance record annotation preconfigured in the business system indicates interception of the business record maintenance request, determining the interception data category based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation;

[0009] According to the intercepted data category, intercept the maintenance record generated by the business record maintenance request trigger;

[0010] The maintenance records are stored in the maintenance record table of the business system; the maintenance record table is used to respond to the maintenance record query operation of any business record and return the maintenance records that meet the query conditions corresponding to the maintenance record query operation.

[0011] In an exemplary embodiment, according to the intercepted data category, intercepting the maintenance record triggered by the service record maintenance request includes:

[0012] According to the intercepted data category, the first identifier, the second identifier, the business record attribute before maintenance and the business record attribute after maintenance associated with the business record maintenance request are obtained; the first identifier is the account identifier of the user account bound to the business system; the second identifier is the account identifier of the user account that initiated the business record maintenance request;

[0013] A maintenance record is generated according to the first identifier, the second identifier, the business record attribute before maintenance, and the business record attribute after maintenance.

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

[0015] Display the maintenance record query page of any sub-business system; the maintenance record query page is used to receive the maintenance record query operation for any business record of any sub-business system;

[0016] In response to the maintenance record query operation, a maintenance record list of any business record of the sub-business system is displayed on the maintenance record query page; the maintenance record list of any business record includes multiple maintenance records of the business record.

[0017] In an exemplary embodiment, any maintenance record of any business record includes a maintenance operation time for the business record, and a maintenance record query page of any sub-business system includes a time range setting control. After the step of displaying a maintenance record list of any business record of the sub-business system, the method further includes:

[0018] In response to a setting operation on a time range setting control, obtaining the time range set by the setting operation;

[0019] Filter out maintenance records whose maintenance operation time is within the time range from the maintenance record list of business records;

[0020] The maintenance records are displayed in the maintenance record query page of the sub-business system.

[0021] In an exemplary embodiment, in response to a maintenance record query operation, a maintenance record list of any business record of a sub-business system is displayed on a maintenance record query page, including:

[0022] In response to the maintenance record query operation, obtaining a business record identifier corresponding to the business record queried by the maintenance record query operation;

[0023] The business record identifier is passed into the pre-written business record query interface, and each maintenance record of the business record is obtained based on the business record identifier by calling the business record query interface;

[0024] The maintenance records of the business records are displayed in the maintenance record query page in the form of a list.

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

[0026] Determine the cut-off point configuration information and enhanced configuration information; the cut-off point configuration information is used to intercept any business record maintenance request of any sub-business system in the business system; the enhanced configuration information is used to execute corresponding interception processing logic for any intercepted business record maintenance request;

[0027] Generate maintenance record annotations for business system preconfiguration based on the cut-off point configuration information and enhanced configuration information.

[0028] A business record processing device, comprising:

[0029] A receiving module, used to receive a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any sub-business system;

[0030] A determination module, configured to determine the intercepted data category based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation, when the maintenance record annotation preconfigured in the business system indicates interception of the business record maintenance request;

[0031] An interception module, used to intercept the maintenance record generated by the business record maintenance request trigger according to the interception data category;

[0032] The storage module is used to store the maintenance records in the maintenance record table of the business system; the maintenance record table is used to respond to the maintenance record query operation of any business record and return the maintenance records that meet the query conditions corresponding to the maintenance record query operation.

[0033] In an exemplary embodiment, an interception module is used to obtain a first identifier, a second identifier, a business record attribute before maintenance, and a business record attribute after maintenance associated with a business record maintenance request according to an interception data category; the first identifier is an account identifier of a user account bound to a business system; the second identifier is an account identifier of a user account that initiates a business record maintenance request; and a maintenance record is generated based on the first identifier, the second identifier, the business record attribute before maintenance, and the business record attribute after maintenance.

[0034] In an exemplary embodiment, the device also includes: a display module, used to display a maintenance record query page of any sub-business system; the maintenance record query page is used to receive a maintenance record query operation for any business record of any sub-business system; in response to the maintenance record query operation, a maintenance record list of any business record of the sub-business system is displayed in the maintenance record query page; the maintenance record list of any business record includes multiple maintenance records of the business record.

[0035] In an exemplary embodiment, any maintenance record of any business record includes a maintenance operation time for the business record, and a maintenance record query page of any sub-business system includes a time range setting control. The display module is also used to respond to a setting operation for the time range setting control, obtain the time range set by the setting operation; filter out maintenance records whose maintenance operation time is within the time range in the maintenance record list of the business record; and display the maintenance record in the maintenance record query page of the sub-business system.

[0036] In an exemplary embodiment, the display device is also used to: respond to a maintenance record query operation, obtain a business record identifier corresponding to the business record queried by the maintenance record query operation; pass the business record identifier into a pre-written business record query interface, and obtain each maintenance record of the business record based on the business record identifier by calling the business record query interface; and display each maintenance record of the business record in the form of a list on the maintenance record query page.

[0037] In an exemplary embodiment, the device also includes: a generation module for determining the cut-off point configuration information and enhanced configuration information; the cut-off point configuration information is used to intercept any business record maintenance request of any sub-business system in the business system; the enhanced configuration information is used to execute corresponding interception processing logic for any intercepted business record maintenance request; based on the cut-off point configuration information and the enhanced configuration information, a maintenance record annotation pre-configured for the business system is generated.

[0038] A computer device includes 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.

[0039] A computer-readable storage medium stores a computer program, which implements the steps of the above method when executed by a processor.

[0040] A computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0041] The above-mentioned business record processing method, apparatus, computer equipment, computer-readable storage medium and computer program product receive a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any sub-business system; when the maintenance record annotation pre-configured in the business system indicates intercepting the business record maintenance request, the interception data category is determined based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation; according to the interception data category, the maintenance record triggered by the business record maintenance request is intercepted; the maintenance record is stored in the maintenance record table of the business system; the maintenance record table is used In response to the maintenance record query operation of any business record, the maintenance record that meets the query conditions corresponding to the maintenance record query operation is returned; in this way, the changes in the business records of each sub-business system in the business system can be recorded only through the pre-configured maintenance record annotations, thereby achieving unified maintenance of the maintenance records of each business record in different sub-business systems with zero intrusion and low coupling to the code of each sub-business system. Since each sub-business system does not need to implement the relevant functions of the business record according to its own business, it can reduce the workload of code and reduce the complexity of code, thereby achieving the beneficial effect of efficiently and uniformly processing the business records of each sub-business system. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions 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 related drawings can be obtained based on these drawings without paying creative work.

[0043] Figure 1 An application environment diagram of a business record processing method in an embodiment;

[0044] Figure 2 A schematic diagram of a flow chart of a business record processing method in an embodiment;

[0045] Figure 3 A schematic diagram of a maintenance record processing method in one embodiment;

[0046] Figure 4 A schematic diagram of a maintenance record generation method in one embodiment;

[0047] Figure 5 A schematic diagram of a maintenance record query page in one embodiment;

[0048] Figure 6is a schematic diagram of a page displaying business records in one embodiment;

[0049] Figure 7 A schematic diagram of a method for intercepting a service record maintenance request in one embodiment;

[0050] Figure 8 is a flow chart of a business record processing method in another embodiment;

[0051] Fig. 9 is a structural block diagram of a service record processing device in one embodiment;

[0052] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. It should be noted that in the embodiments of the present application, certain software, groups, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0054] 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. The acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with relevant provisions of national laws and regulations.

[0055] The service record processing method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The server 104 receives a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when any business record of any sub-business system is maintained; when the maintenance record annotation pre-configured in the business system indicates interception of the business record maintenance request, the server 104 determines the interception data category based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation; the server 104 intercepts the maintenance record triggered by the business record maintenance request according to the interception data category; the server 104 stores the maintenance record in the maintenance record table of the business system; the maintenance record table is used to respond to the maintenance record query operation of any business record, and return the maintenance record that meets the query conditions corresponding to the maintenance record query operation to the terminal 102. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0056] In an exemplary embodiment, Figure 2 As shown, a business record processing method is provided, which is applied to Figure 1 The server 104 in the example is used as an example to illustrate, including the following steps 202 to 208. Among them:

[0057] Step 202, receiving a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any sub-business system.

[0058] Among them, the business system may refer to the computer system deployed by the business organization to conduct business and realize business functions.

[0059] Among them, the sub-business system can be a sub-system in the business system used to implement different business functions. In actual applications, the sub-business system can be a sub-system such as role, position, organization, user, and application management. The role corresponds to a set of operation functions bound to the user account, the position is a set of roles, and the organization is a processing organization bound to the role and position. Through roles, positions, and organizations, the user's permissions in business functions are managed to achieve the function of isolating the permissions of each user.

[0060] The business record maintenance request may refer to a request triggered when a user account maintains a business record stored in a sub-business system. For example, the business record maintenance request may be a request triggered when a user account deletes or modifies a business attribute in a business record stored in a sub-business system. In actual applications, the business record maintenance types may include adding, modifying, deleting, disabling, enabling, deregistering, authorizing, and changing passwords.

[0061] Optionally, the user account maintains any business record in any sub-business system, and the server receives a business record maintenance request triggered by the maintenance operation.

[0062] Step 204 , when the maintenance record annotation preconfigured in the business system indicates interception of the business record maintenance request, determine the interception data category based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation.

[0063] Among them, the maintenance record annotation is pre-configured according to actual needs, and it can be used to uniformly intercept the maintenance records generated by maintaining the business records of all sub-business systems in the business system, thereby supporting the function of viewing the maintenance records of all sub-business systems.

[0064] The interception processing logic may be a processing logic corresponding to a method executed on the intercepted business record maintenance request after the business record maintenance request is intercepted.

[0065] The intercepted data category may refer to the data category that needs to be intercepted.

[0066] Optionally, when a maintenance record annotation preconfigured in the business system indicates interception of a business record maintenance request, the server determines an interception data category for the business record maintenance request based on the interception processing logic configured for the business record maintenance request in the maintenance record annotation.

[0067] Step 206: intercept the maintenance record triggered by the business record maintenance request according to the intercept data category.

[0068] The maintenance record triggered by the business record maintenance request may be a maintenance record generated by corresponding maintenance operation data when the user account maintains the business record.

[0069] Optionally, the server intercepts the maintenance record triggered by the business record maintenance request according to the intercepted data category.

[0070] Step 208, store the maintenance record in the maintenance record table of the business system; the maintenance record table is used to respond to the maintenance record query operation of any business record and return the maintenance records that meet the query conditions corresponding to the maintenance record query operation.

[0071] The maintenance record table may be a data table in the business system storing all maintenance records of each business record of each sub-business system.

[0072] The maintenance record query operation may be an operation corresponding to when a user queries the maintenance record of a business record.

[0073] The query condition may be a maintenance record query condition set for any business record according to actual needs of the user account. For example, the query condition may be a time range or a maintenance operation type.

[0074] Optionally, the server stores the maintenance record in the maintenance record table of the business system. When a user account subsequently queries the maintenance record of a business record, the server queries the maintenance record table for the maintenance record that meets the query conditions entered by the user account and displays them on the page.

[0075] In order to facilitate the understanding of those skilled in the art, Figure 3 An exemplary process is provided for simultaneously processing maintenance records of different sub-business systems, wherein process 1 is triggered by a business record maintenance request in sub-business system 1, process 2 is triggered by a business record maintenance request in sub-business system 2, and process 3 is triggered by a business record maintenance request in sub-business system 3.

[0076] In the above-mentioned business record processing method, a business record maintenance request for any sub-business system in the business system is received; the business record maintenance request is a request triggered when maintaining any business record of any sub-business system; when the maintenance record annotation pre-configured in the business system indicates intercepting the business record maintenance request, the interception data category is determined based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation; according to the interception data category, the maintenance record triggered by the business record maintenance request is intercepted; the maintenance record is stored in the maintenance record table of the business system; the maintenance record table is used to respond to the maintenance record query operation of any business record and return the maintenance record that meets the query condition corresponding to the maintenance record query operation; in this way, only through the pre-configured maintenance record annotation, the maintenance status of the business records of each sub-business system in the business system can be recorded, and the maintenance records of each business record in different sub-business systems are uniformly maintained under the condition of zero intrusion and low coupling to the code of each sub-business system. Since each sub-business system does not need to implement the relevant functions of the business record according to its own business, the code workload and code complexity can be reduced, thereby achieving the beneficial effect of efficiently and uniformly processing the business records of each sub-business system.

[0077] In an exemplary embodiment, Figure 4 As shown, step 206 includes steps 402 to 404 .

[0078] in:

[0079] Step 402, according to the intercepted data category, obtain the first identifier, the second identifier, the business record attributes before maintenance and the business record attributes after maintenance associated with the business record maintenance request; the first identifier is the account identifier of the user account bound to the business system; the second identifier is the account identifier of the user account that initiates the business record maintenance request.

[0080] The first identifier may be an account identifier of a user account bound to the business system, for example, a tenant id (ptid).

[0081] The second identifier may be an identifier of a user account that triggers a business record maintenance operation and initiates a business record maintenance request, for example, a user id.

[0082] Among them, the business record attributes can be the various business attributes recorded in the business record, the business record attributes before maintenance can be the attribute values ​​corresponding to the various business attributes before the business record is maintained, and the business record attributes after maintenance can be the attribute values ​​corresponding to the various business attributes after the business record maintenance is completed.

[0083] Optionally, the server determines that the interception data category for the business record maintenance request includes a first identifier (e.g., tenant ID), a second identifier (e.g., user ID), business record attributes before maintenance, and business record attributes after maintenance based on the interception processing logic set for the business record maintenance request according to the maintenance record annotation.

[0084] Step 404: Generate a maintenance record according to the first identifier, the second identifier, the business record attributes before maintenance, and the business record attributes after maintenance.

[0085] Optionally, the server generates a maintenance record according to the first identifier, the second identifier, the business record attributes before maintenance, and the business record attributes after maintenance.

[0086] In this embodiment, the first identifier, the second identifier, the business record attributes before maintenance and the business record attributes after maintenance associated with the business record maintenance request are obtained according to the interception data category; the first identifier is the account identifier of the user account bound to the business system; the second identifier is the account identifier of the user account that initiates the business record maintenance request; a maintenance record is generated according to the first identifier, the second identifier, the business record attributes before maintenance and the business record attributes after maintenance; in this way, it is possible to determine that the key data in the maintenance operation data is generated as a maintenance record according to the interception data category configured for the business record maintenance request according to the maintenance record annotation, so that the maintenance operation data of different sub-business systems can be flexibly classified and recorded according to the maintenance operation data recording requirements of different sub-business systems, thereby achieving the beneficial effect of improving the efficiency and flexibility of maintenance record generation.

[0087] In an exemplary embodiment, the method also includes: displaying a maintenance record query page of any sub-business system; the maintenance record query page is used to receive a maintenance record query operation for any business record of any sub-business system; in response to the maintenance record query operation, displaying a maintenance record list of any business record of the sub-business system in the maintenance record query page; the maintenance record list of any business record includes multiple maintenance records of the business record.

[0088] The maintenance record query page of any sub-business system may be a page for querying maintenance records of business records in any sub-business system.

[0089] The maintenance record list may be a list formed by multiple maintenance records.

[0090] Optionally, the server displays a maintenance record query page of the sub-business system. When a user queries the maintenance record of a business record of the sub-business system, the server responds to the query operation by displaying a maintenance record list of the business record of the sub-business system on the maintenance record query page of the sub-business system. At this time, all maintenance records of the business record are displayed.

[0091] In actual applications, it is necessary to pre-write a display interface for maintenance records to display maintenance records on the maintenance record query page of each sub-business system.

[0092] In order to facilitate the understanding of those skilled in the art, Figure 5 A schematic diagram is provided by way of example in which a maintenance record list is displayed in a maintenance record query page. The maintenance record list in the figure includes a maintenance record, which includes a maintenance operation time "20xx-xx-xx-day x hour x minute x second", a business record field "ddd" targeted by the maintenance operation, and a maintenance operation type "new".

[0093] In actual applications, it is necessary to predetermine the changed attributes that each sub-business system needs to display in the maintenance record query page. For example, for the user sub-business system, the changed attributes that need to be displayed may be user attribute information such as user name and login key.

[0094] In this embodiment, a maintenance record query page of any sub-business system is displayed; the maintenance record query page is used to receive a maintenance record query operation for any business record of any sub-business system; in response to the maintenance record query operation, a maintenance record list of any business record of the sub-business system is displayed in the maintenance record query page; in this way, maintenance record viewing of business records in multiple sub-business systems can be supported, which can achieve the beneficial effect of improving the convenience of viewing maintenance records.

[0095] In an exemplary embodiment, any maintenance record of any business record includes a maintenance operation time for the business record, and a maintenance record query page of any sub-business system includes a time range setting control. After the step of displaying a maintenance record list of any business record of the sub-business system, the method further includes: in response to a setting operation for the time range setting control, obtaining the time range set by the setting operation; filtering out maintenance records whose maintenance operation time is within the time range in the maintenance record list of the business record; and displaying the maintenance record in the maintenance record query page of the sub-business system.

[0096] The maintenance operation time may be the operation time corresponding to when the user account maintains the business record.

[0097] The time range setting control may be a button or an input box for setting the time range.

[0098] The setting operation may be an operation corresponding to setting a time range.

[0099] Among them, the time range can be the time range set by the setting operation, for example, the time range from 0:00 on February 3, 2019 to can be 0:00 on March 2, 2019.

[0100] Optionally, after the server displays the maintenance record list of a business record of the sub-business system, the server obtains the time range set by the user account in response to the setting operation of the time range setting control in the maintenance record query page of the user account, and the server filters out the maintenance records whose maintenance operation time is within the time range in the maintenance record list of the business record, and displays the maintenance records in the maintenance record query page of the sub-business system.

[0101] In order to facilitate the understanding of those skilled in the art, Figure 6 An exemplary schematic diagram of a page displaying a business record is provided. Taking the role sub-business system as an example, a business record is displayed on the page. The business record includes attribute information such as serial number, role name, role change, subsystem, whether subordinate organizations are allowed to use, role creation organization, and role business definition. The business record also includes a maintenance record viewing control. By clicking the maintenance record viewing control, all maintenance records of the business record can be queried. The page also includes input boxes for entering information such as role name, subsystem to which the role belongs, and whether subordinate organizations are allowed to use. By entering relevant information of the role sub-business system in each input box, the business record can be queried.

[0102] In this embodiment, in response to a maintenance record query operation, after displaying the maintenance record list of any business record of the sub-business system on the maintenance record query page, it is also possible to respond to a setting operation for a time range setting control to obtain the time range set by the setting operation, filter out maintenance records whose maintenance operation time is within the time range in the maintenance record list of the business records, and display the maintenance records on the maintenance record query page of the sub-business system, which enables filtering of each maintenance record in the maintenance record list according to the time range, thereby achieving the beneficial effect of improving the efficiency of viewing maintenance records.

[0103] In an exemplary embodiment, in response to a maintenance record query operation, a maintenance record list of any business record of the sub-business system is displayed on a maintenance record query page, including: in response to the maintenance record query operation, obtaining a business record identifier corresponding to the business record queried by the maintenance record query operation; passing the business record identifier into a pre-written business record query interface, and obtaining each maintenance record of the business record based on the business record identifier by calling the business record query interface; and displaying each maintenance record of the business record in the form of a list on the maintenance record query page.

[0104] The business record identifier may be an identifier of each business record. In actual applications, the business record identifier may be a primary key ID set based on the sub-business system to which the business record belongs.

[0105] The pre-written business record query interface may be a pre-written interface for querying maintenance records of business records.

[0106] Optionally, the server responds to the maintenance record query operation of the user account and obtains the business record identifier corresponding to the business record queried by the user account. The server passes the business record identifier into a pre-written business record query interface, and obtains each maintenance record of the business record based on the business record identifier by calling the business record query interface. The server then displays each maintenance record of the business record in the form of a list on the maintenance record query page.

[0107] In actual applications, it is necessary to pre-write a business record query interface. Later, based on the maintenance record primary key id of the business record of the sub-business system (corresponding to the primary key corresponding to a maintenance record in the maintenance record in which the business record of the current sub-business system has changed), the data of a single maintenance record can be queried and returned to the front-end page. Since the primary key id of the business record maintained by the maintenance record is also stored when a maintenance record is stored, all maintenance records of the current business record can be queried based on the primary key id. Each maintenance record corresponds to an operation time. When querying a maintenance record, you only need to pass in the maintenance operation time to find out the specific maintenance operation data of the maintenance record, such as the parameters before and after the operation, and display it on the maintenance record query page of the sub-business system.

[0108] In this embodiment, by responding to a maintenance record query operation, a business record identifier corresponding to the business record queried by the maintenance record query operation is obtained; the business record identifier is passed into a pre-written business record query interface, and the business record query interface is called to obtain each maintenance record of the business record based on the business record identifier; each maintenance record of the business record is displayed in the form of a list on the maintenance record query page. In this way, the business record identifier can be passed into a pre-written business record query interface, and the business record query interface is called to quickly obtain all maintenance records corresponding to the corresponding business record in the maintenance record list based on the business record identifier, and display them on the maintenance record query page, thereby achieving the beneficial effect of quickly querying all maintenance records of the business record.

[0109] In an exemplary embodiment, the method also includes: determining the cut-off point configuration information and enhanced configuration information; the cut-off point configuration information is used to intercept any business record maintenance request of any sub-business system in the business system; the enhanced configuration information is used to execute corresponding interception processing logic for any intercepted business record maintenance request; based on the cut-off point configuration information and the enhanced configuration information, generating a maintenance record annotation pre-configured for the business system.

[0110] The cut-point configuration information may be information configured with methods that need to be intercepted for each sub-business system.

[0111] The enhanced configuration information may be configured with the processing method to be executed after each method that needs to be intercepted is intercepted.

[0112] Optionally, the server first determines the cut-off point configuration information and the enhanced configuration information, and then generates a maintenance record annotation pre-configured for the business system according to the cut-off point configuration information and the enhanced configuration information.

[0113] The following is an exemplary method for configuring the maintenance record annotation in the present application. The method is implemented based on aspect-oriented programming technology. The aspect-oriented programming technology realizes the unified maintenance of program functions through pre-compilation and dynamic proxy during operation, and can enhance the existing methods without modifying the source code. The method first needs to configure the aspect annotation, which is used for aspect identification and interception processing methods, so that the server knows which methods of which classes need to add interception processing logic, thereby realizing the addition of maintenance records for each sub-business system; secondly, it is necessary to configure the aspect processing logic, and obtain the point-cut configuration information and enhanced configuration information by configuring the point-cut and enhancement parts. For the point-cut configuration information, since the aspect annotation has been configured, all methods with the added aspect annotation need to be intercepted. The point-cut configuration information is the information that configures which methods need to be intercepted. For the enhanced configuration information, it is used to replace the intercepted method. By obtaining the tenant id (ptid) of the sub-business system, the user account id (user id) that triggers the maintenance operation, the pre-operation data of the current business record, and the post-operation data of the current business record are stored in a special maintenance record storage table.

[0114] In actual applications, after obtaining the pre-configured maintenance record annotation, it is necessary to add the pre-configured maintenance record annotation in the add, modify, delete, and authorization interfaces of each sub-business system. The important attributes of the pre-configured maintenance record annotation are: the name of the sub-business system, the maintenance record-related configuration of the sub-business system, and the maintenance operation type.

[0115] For the name of the sub-business system, you need to configure the mapping relationship between the sub-business system and the identification number in the configuration file for maintaining record annotations. For example, set the identification number of the role sub-business system to 1, the identification number of the position sub-business system to 2, the identification number of the organization sub-business system to 3, the identification number of the user sub-business system to 4, and the identification number of the application management sub-business system to 5.

[0116] For the maintenance record-related configuration of the sub-business system, it is necessary to configure the fields required to be displayed in each sub-business system in the configuration file of the maintenance record annotation. For example, for the role sub-business system, it is necessary to configure fields such as the role name, role business definition, and the subsystem to which the role belongs. For the position sub-business system, it is necessary to configure fields such as the position name, position business definition, and position organization type.

[0117] For maintenance operation types, you need to configure the mapping relationship between maintenance operation types and identification numbers in the configuration file of the maintenance record annotation. For example, set the identification number of the new operation to 1, the identification number of the modification operation to 2, the identification number of the deletion operation to 3, the identification number of the disable operation to 4, the identification number of the enable operation to 5, the identification number of the logout operation to 6, the identification number of the authorization operation to 7, and the identification number corresponding to the modification of the login key operation to 8.

[0118] In order to facilitate the understanding of those skilled in the art, Figure 7 A method is exemplarily provided for intercepting business record maintenance requests based on preconfigured maintenance record annotations and generating maintenance records to be stored in a maintenance record table, wherein, when a business record maintenance request is received, it is determined whether information for the business record maintenance request is configured in the maintenance record annotation. If so, the first identifier associated with the business record maintenance request, namely the tenant identifier ptid, the second identifier, namely the user identifier userid, and the system id of the sub-business system are obtained according to the interception data category for the business record maintenance request configured in the maintenance record annotation, and a maintenance record is generated and inserted into the maintenance record table of the business system.

[0119] In this embodiment, by determining the cut-off point configuration information and the enhanced configuration information; the cut-off point configuration information is used to intercept any business record maintenance request of any sub-business system in the business system; the enhanced configuration information is used to execute the corresponding interception processing logic for any intercepted business record maintenance request; according to the cut-off point configuration information and the enhanced configuration information, a maintenance record annotation pre-configured for the business system is generated; in this way, according to the business implementation of each sub-business system, the requests required to be intercepted for each sub-business system can be pre-configured in the maintenance record annotation, without the need to write different codes for each sub-business system, and the business record maintenance requests of each sub-business system in the business system can be uniformly intercepted while reducing the code workload and code complexity, which can achieve the beneficial effect of efficiently and uniformly processing the maintenance records of each sub-business system, and if it is necessary to expand to other sub-business systems in the future, only a small amount of configuration needs to be added to the original maintenance record annotation to support the maintenance record storage and subsequent maintenance record query of other sub-business systems, thereby achieving the beneficial effect of improving the scalability of the unified storage function of maintenance records.

[0120] In another exemplary embodiment, Figure 8 As shown, a business record processing method is provided, which is applied to Figure 1 The server 104 in the example is used as an example to illustrate, including the following steps 802 to 812. Among them:

[0121] Step 802, receiving a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any sub-business system.

[0122] Step 804 , when the maintenance record annotation preconfigured in the business system indicates interception of the business record maintenance request, determine the interception data category based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation.

[0123] Step 806: intercept the maintenance record triggered by the business record maintenance request according to the intercept data category.

[0124] Step 808, store the maintenance record in the maintenance record table of the business system; the maintenance record table is used to respond to the maintenance record query operation of any business record and return the maintenance records that meet the query conditions corresponding to the maintenance record query operation.

[0125] Step 810, displaying a maintenance record query page of any sub-business system; the maintenance record query page is used to receive a maintenance record query operation for any business record of any sub-business system.

[0126] Step 812, in response to the maintenance record query operation, a maintenance record list of any business record of the sub-business system is displayed in the maintenance record query page; the maintenance record list of any business record includes multiple maintenance records of the business record.

[0127] It should be noted that the specific limitations of the above steps can refer to the specific limitations of a business record processing method above.

[0128] 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 does not have a strict order restriction, 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 to be 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.

[0129] Based on the same inventive concept, the embodiment of the present application also provides a business record processing device for implementing the business record processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more business record processing device embodiments provided below can refer to the limitations on the business record processing method above, and will not be repeated here.

[0130] In an exemplary embodiment, Fig. 9 As shown, a business record processing device is provided, including: a receiving module 902, a determining module 904, an intercepting module 906 and a storing module 909, wherein:

[0131] A receiving module 902 is used to receive a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any sub-business system;

[0132] A determination module 904, configured to determine the interception data category based on the interception processing logic configured for the business record maintenance request according to the maintenance record annotation, when the maintenance record annotation preconfigured in the business system indicates interception of the business record maintenance request;

[0133] An interception module 906 is used to intercept the maintenance record generated by the business record maintenance request according to the interception data category;

[0134] The storage module 908 is used to store the maintenance record in the maintenance record table of the business system; the maintenance record table is used to respond to the maintenance record query operation of any business record and return the maintenance record that meets the query conditions corresponding to the maintenance record query operation.

[0135] In an exemplary embodiment, the interception module 906 is used to obtain a first identifier, a second identifier, a business record attribute before maintenance, and a business record attribute after maintenance associated with a business record maintenance request according to the interception data category; the first identifier is the account identifier of a user account bound to the business system; the second identifier is the account identifier of the user account that initiates the business record maintenance request; and a maintenance record is generated based on the first identifier, the second identifier, the business record attribute before maintenance, and the business record attribute after maintenance.

[0136] In an exemplary embodiment, the device also includes: a display module, used to display a maintenance record query page of any sub-business system; the maintenance record query page is used to receive a maintenance record query operation for any business record of any sub-business system; in response to the maintenance record query operation, a maintenance record list of any business record of the sub-business system is displayed in the maintenance record query page; the maintenance record list of any business record includes multiple maintenance records of the business record.

[0137] In an exemplary embodiment, any maintenance record of any business record includes a maintenance operation time for the business record, and a maintenance record query page of any sub-business system includes a time range setting control. The display module is also used to respond to a setting operation for the time range setting control, obtain the time range set by the setting operation; filter out maintenance records whose maintenance operation time is within the time range in the maintenance record list of the business record; and display the maintenance record in the maintenance record query page of the sub-business system.

[0138] In an exemplary embodiment, the display device is also used to: respond to a maintenance record query operation, obtain a business record identifier corresponding to the business record queried by the maintenance record query operation; pass the business record identifier into a pre-written business record query interface, and obtain each maintenance record of the business record based on the business record identifier by calling the business record query interface; and display each maintenance record of the business record in the form of a list on the maintenance record query page.

[0139] In an exemplary embodiment, the device also includes: a generation module for determining the cut-off point configuration information and enhanced configuration information; the cut-off point configuration information is used to intercept any business record maintenance request of any sub-business system in the business system; the enhanced configuration information is used to execute corresponding interception processing logic for any intercepted business record maintenance request; based on the cut-off point configuration information and the enhanced configuration information, a maintenance record annotation pre-configured for the business system is generated.

[0140] Each module in the above-mentioned business record processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0141] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.10As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store business record processing data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a business record processing method is implemented.

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

[0143] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the above-mentioned business record processing method. The steps of the business record processing method here may be the steps of the business record processing method in each of the above-mentioned embodiments.

[0144] In one embodiment, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a processor, the processor executes the steps of the above-mentioned business record processing method. The steps of the business record processing method here can be the steps of the business record processing method in each of the above-mentioned embodiments.

[0145] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, causes the processor to execute the steps of the above-mentioned business record processing method. The steps of the business record processing method here may be the steps of the business record processing method in each of the above-mentioned embodiments.

[0146] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0147] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0148] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A business record processing method, characterized in that: The method comprises: Receiving a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any of the sub-business systems; In the case where the maintenance record annotation preconfigured in the business system indicates interception of the business record maintenance request, determining the interception data category based on the interception processing logic configured for the business record maintenance request by the maintenance record annotation; According to the intercepted data category, intercepting the maintenance record triggered by the business record maintenance request; The maintenance record is stored in the maintenance record table of the business system; the maintenance record table is used to respond to a maintenance record query operation of any of the business records and return maintenance records that meet the query conditions corresponding to the maintenance record query operation.

2. The method according to claim 1, characterized in that The step of intercepting the maintenance record triggered by the business record maintenance request according to the intercepted data category includes: According to the intercepted data category, obtaining a first identifier, a second identifier, a business record attribute before maintenance, and a business record attribute after maintenance associated with the business record maintenance request; the first identifier is an account identifier of a user account bound to the business system; the second identifier is an account identifier of a user account that initiates the business record maintenance request; The maintenance record is generated according to the first identifier, the second identifier, the business record attributes before maintenance, and the business record attributes after maintenance.

3. The method according to claim 1, characterized in that: The method further comprises: Displaying a maintenance record query page of any of the sub-business systems; the maintenance record query page is used to receive a maintenance record query operation for any of the business records of any of the sub-business systems; In response to the maintenance record query operation, a maintenance record list of any business record of the sub-business system is displayed in the maintenance record query page; the maintenance record list of any business record includes multiple maintenance records of the business record.

4. The method according to claim 3, characterized in that Any maintenance record of any of the business records includes a maintenance operation time for the business record, and a maintenance record query page of any of the sub-business systems includes a time range setting control. After the step of displaying a maintenance record list of any of the business records of the sub-business system, the method further includes: In response to a setting operation on the time range setting control, obtaining the time range set by the setting operation; Filter out maintenance records whose maintenance operation time is within the time range from the maintenance record list of the business record; The maintenance record is displayed on a maintenance record query page of the sub-business system.

5. The method according to claim 3, characterized in that: In response to the maintenance record query operation, displaying a maintenance record list of any of the business records of the sub-business system on the maintenance record query page includes: In response to the maintenance record query operation, obtaining a business record identifier corresponding to the business record queried by the maintenance record query operation; The business record identifier is passed into a pre-written business record query interface, and each maintenance record of the business record is acquired based on the business record identifier by calling the business record query interface; The maintenance records of the business records are displayed in the maintenance record query page in the form of a list.

6. The method according to claim 1, characterized in that The method further comprises: Determine the cut-off point configuration information and the enhanced configuration information; the cut-off point configuration information is used to intercept any of the business record maintenance requests of any of the sub-business systems in the business system; the enhanced configuration information is used to execute the corresponding interception processing logic for any of the intercepted business record maintenance requests; A maintenance record annotation pre-configured for the business system is generated according to the cut-point configuration information and the enhanced configuration information.

7. A business record processing device, characterized in that: The device comprises: A receiving module, used to receive a business record maintenance request for any sub-business system in the business system; the business record maintenance request is a request triggered when maintaining any business record of any of the sub-business systems; a determination module, configured to determine the interception data category based on the interception processing logic configured for the business record maintenance request by the maintenance record annotation when the maintenance record annotation preconfigured by the business system indicates interception of the business record maintenance request; An interception module, configured to intercept the maintenance record generated by the business record maintenance request according to the interception data category; A storage module is used to store the maintenance record in the maintenance record table of the business system; the maintenance record table is used to respond to a maintenance record query operation of any business record and return maintenance records that meet the query conditions corresponding to the maintenance record query operation.

8. The device according to claim 7, characterized in that The interception module is used to obtain a first identifier, a second identifier, a business record attribute before maintenance, and a business record attribute after maintenance associated with the business record maintenance request according to the interception data category; the first identifier is an account identifier of a user account bound to the business system; the second identifier is an account identifier of a user account that initiates the business record maintenance request; The maintenance record is generated according to the first identifier, the second identifier, the business record attributes before maintenance, and the business record attributes after maintenance.

9. The device according to claim 7, characterized in that The device also includes: a display module, used to display a maintenance record query page of any of the sub-business systems; the maintenance record query page is used to receive a maintenance record query operation for any of the business records of any of the sub-business systems; in response to the maintenance record query operation, a maintenance record list of any of the business records of the sub-business system is displayed in the maintenance record query page; the maintenance record list of any of the business records includes multiple maintenance records of the business record.

10. The device according to claim 9, characterized in that Any maintenance record of any of the business records includes the maintenance operation time for the business record, and the maintenance record query page of any of the sub-business systems includes a time range setting control. The display module is also used to respond to a setting operation for the time range setting control, obtain the time range set by the setting operation; filter out maintenance records whose maintenance operation time is within the time range in the maintenance record list of the business record; and display the maintenance record in the maintenance record query page of the sub-business system.

11. The device according to claim 9, characterized in that The display device is also used to: in response to the maintenance record query operation, obtain the business record identifier corresponding to the business record queried by the maintenance record query operation; pass the business record identifier into a pre-written business record query interface, and obtain each maintenance record of the business record based on the business record identifier by calling the business record query interface; and display each maintenance record of the business record in the form of a list on the maintenance record query page.

12. The device according to claim 7, characterized in that The device also includes: a generation module, used to determine the cut-off point configuration information and the enhanced configuration information; the cut-off point configuration information is used to intercept any business record maintenance request of any sub-business system in the business system; the enhanced configuration information is used to execute corresponding interception processing logic for any intercepted business record maintenance request; based on the cut-off point configuration information and the enhanced configuration information, generate the maintenance record annotation pre-configured for the business system.

13. 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.

14. 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.

15. A computer program product comprising a computer program, 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