Security and secrecy service ledger full life cycle resume maintenance system based on process driving

Abstract

The invention provides a security and secrecy service ledger full life cycle resume maintenance system based on process driving, and belongs to the field of information security and service and process management. Comprising the following modules: a business process module, a ledger module, a resume module, an authorization management module, an organization management module, a log auditing module, a system management module and a security and secrecy business database. According to the system, a process-driven mode is adopted, through an automatic resume updating mechanism, full-life-cycle automatic resume maintenance management of a service ledger from creation, modification, auditing to archiving is achieved, the accuracy, integrity, confidentiality and traceability of ledger information in the full life cycle are comprehensively guaranteed, and the service ledger management efficiency is improved. Therefore, the efficiency and the accuracy of business ledger management are improved, human errors and leakage risks are reduced, the management efficiency is remarkably improved, the information security protection capability is enhanced, and the method has wide application prospects and important practical values.

Description

Technical Field

[0001] The present invention belongs to the field of information security and business and process management, and in particular relates to a process-driven secure and confidential business ledger full life cycle history maintenance system. Background Art

[0002] Traditional security and confidentiality business ledger management usually relies on manual operations, which are inefficient, error-prone, information scattered, opaque processes, difficult to trace, and data security risks, and can no longer meet the needs of modern information security management. Therefore, there is an urgent need for an efficient, secure and traceable confidentiality business ledger and resume management system. Summary of the invention

[0003] In order to solve the above technical problems, the present invention provides a process-driven secure and confidential business account full life cycle history maintenance system, including the following modules:

[0004] The business process module is used to define the business approval process for security and confidentiality management and realize the automatic flow of the approval process; automatically add and update the corresponding security and confidentiality business ledger according to the preset process nodes, and automatically trigger the recording operation of the resume information;

[0005] The ledger module can realize the addition, query, maintenance, import, export and verification of corresponding security and confidentiality business ledger information according to the access control strategy, and save the ledger information created or changed through business process push;

[0006] The resume module records the information changes of the corresponding security and confidentiality business ledgers caused by process drive or user operation, summarizes and traces the resume information of the corresponding ledger, performs query operations on the resume information, and can generate formatted electronic documents from the resume information;

[0007] The authorization management module is used to authorize menus and interface components in the system. The authorization dimensions are roles, departments, users, positions, and groups, and the union of multiple dimensions is taken; the ledger permission labels are set to specify the corresponding roles, users, departments, or to filter, display, and control the scope of ledger data according to the set ledger fields;

[0008] Organization management module, used to implement organization management, department user management, role management, user management, group management, position management, and user relationship management;

[0009] The log audit module is used to record the operation information of users and administrators, designate administrators to view classified logs, support log archiving, and export system logs;

[0010] System management module is used to manage the basic configuration of the system, including system configuration, menus, system parameters, data dictionary, online users, scheduled tasks, codes, and confidentiality levels;

[0011] The secure and confidential business database stores the corresponding data of the secure and confidential business processes, ledgers, and resumes in the database for system use.

[0012] Beneficial effects:

[0013] The present invention provides a process-driven full-life cycle history maintenance system for security and confidentiality business ledgers. Through process-driven business approval, it realizes the automated update and refined management of security and confidentiality business ledgers, and automatically records the history of the ledgers, ensuring that the entire life cycle of ledger management is traceable, enhancing information security and transparency, improving compliance management, and being able to effectively reduce management costs and significantly improve the efficiency of enterprise security and confidentiality management. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a structural block diagram of a process-driven secure and confidential business account full life cycle history maintenance system of the present invention;

[0015] Figure 2 It is a flowchart of the whole life cycle history management method of the security and confidentiality business account of the present invention;

[0016] Figure 3 A schematic diagram of the process of updating the secure and confidential business ledger and resume of the business process in the present invention. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention 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 invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0018] Embodiment 1

[0019] like Figure 1 As shown, an embodiment of the present invention provides a process-driven security and confidentiality business account full life cycle history maintenance system, including the following modules:

[0020] The business process module is used to define the business approval process for security and confidentiality management and realize the automatic flow of the approval process; automatically add and update the corresponding security and confidentiality business ledger according to the preset process nodes, and automatically trigger the recording operation of the resume information;

[0021] The ledger module, based on the access control policy, implements the addition, query, maintenance, import, export and verification of corresponding security and confidentiality business ledger information, and saves the ledger information created or changed through business process push;

[0022] The resume module records the information changes of the corresponding security and confidentiality business ledgers caused by process drive or user operation, summarizes and traces the resume information of the corresponding ledger, performs query operations on the resume information, and can generate formatted electronic documents from the resume information;

[0023] The authorization management module is used to authorize menus and interface components in the system. The authorization dimensions are roles, departments, users, positions, and groups, and the union of multiple dimensions is taken; the ledger permission labels are set to specify the corresponding roles, users, departments, or to filter, display, and control the scope of ledger data according to the set ledger fields;

[0024] Organization management module, used to implement organization management, department user management, role management, user management, group management, position management, and user relationship management;

[0025] The log audit module is used to record the operation information of users and administrators, designate administrators to view classified logs, support log archiving, and export system logs;

[0026] System management module is used to manage the basic configuration of the system, including system configuration, menus, system parameters, data dictionary, online users, scheduled tasks, codes, and confidentiality levels;

[0027] The secure and confidential business database stores the corresponding data of the secure and confidential business processes, ledgers, and resumes in the database for system use.

[0028] In one embodiment, the business process module automatically adds and updates the corresponding security and confidentiality business ledger according to the preset process nodes, and automatically triggers the recording operation of the history information.

[0029] The overall management process of the system coordination process, ledger and resume in the embodiment of the present invention includes generating SQL queries, processing ledger data (new or updated), and recording resume information. The pseudo code is as follows:

[0030] / / Initialize the collection used to store SQL query statements

[0031] define get data sql collection as List <string>;

[0032] / / Traverse the executable script information and generate SQL query statements for each configuration item

[0033] for (config in executable script information) {

[0034] / / Multi-threaded calls to improve processing efficiency

[0035] sqlQuery = query data sql method (config.operation type, config);

[0036] / / Add the generated SQL query statement to the collection

[0037] Get data sql collection.add(sqlQuery);

[0038] }

[0039] / / Initialize the collection used to store resume data

[0040] define resume data collection as List <record>;

[0041] / / Traverse the executable script information again and process the ledger data

[0042] for (config in executable script information) {

[0043] if (config.operation type == "add new account") {

[0044] / / Call the new ledger method to process the new data and obtain the resume information

[0045] recordList = Add new record method (database structure definition column set, query data sql, config);

[0046] } else if (config.operation type == "update ledger") {

[0047] / / Call the update ledger method to process the update data and obtain the resume information

[0048] recordList = update ledger method (database structure definition column set, query data sql, config);

[0049] }

[0050] / / Add the acquired resume information to the collection

[0051] Record data collection.addAll(recordList);

[0052] }

[0053] / / Traverse the resume data set and insert the resume information into the database

[0054] for (record in record data set) {

[0055] / / Encapsulate necessary information of resume data, such as process ID, operation time, etc.

[0056] preparedData = encapsulate record data (record);

[0057] / / Perform database insert operation

[0058] InsertIntoDatabase(preparedData);

[0059] }

[0060] Among them, SQL queries are dynamically generated according to the operation type and executable script information. The main technical methods are as follows:

[0061] / / Method parameters: operation type (add, update), executable script information

[0062] define query data sql method (operation type, executable script information) {

[0063] / / Initialize the SELECT and FROM parts of the SQL statement

[0064] define select statement string as String;

[0065] define from statement string as String;

[0066] / / Get detailed information about the executable script

[0067] define executable script details = get detailed information based on executable script ID (executable script information.configuration ID);

[0068] / / Get the structure definition column information of the ledger library

[0069] define ledger library structure definition column information = Get the ledger library structure definition (executable script information) from the cache;

[0070] / / Concatenate SQL statements according to the operation type

[0071] if (operation type == "add") {

[0072] / / Traverse the ledger library structure definition column information and executable script details, and splice SELECT and FROM statements

[0073] for (column in ledger library structure definition column information) {

[0074] for (detail in executable script details) {

[0075] if (column.column name == detail.configuration data) {

[0076] select statement string += "SELECT " + column.column name + " ";

[0077] from statement string += "FROM " + column. table name + " ";

[0078] / / ... you may also need to connect other conditions or statements

[0079] }

[0080] }

[0081] }

[0082] } else if (operation type == "update") {

[0083] / / Similarly, concatenate SELECT and FROM statements for update operations, taking into account the comparison of new and old values

[0084] / / ...

[0085] }

[0086] / / Return the concatenated SQL query statement

[0087] return select statement string + from statement string; / / You may also need to add other parts, such as WHERE conditions

[0088] }

[0089] The business process module specifically includes the following steps:

[0090] Step S11: Process configuration, which implements the configuration of the association between the approval process and the approval form through the process engine, and specifies the approval node to automatically add and update the ledger information;

[0091] Step S12: Account addition and update. During the process flow, after reaching the node set in step S11, the system automatically adds or updates the specified account information to the account module according to the business logic;

[0092] Among them, the pseudo code for processing the addition of ledger data, generating and returning historical information is as follows:

[0093] / / Method parameters: library structure definition column set, query data sql, executable script information

[0094] define new ledger method (library structure definition column set, query data sql, executable script information) {

[0095] / / Get the data set according to the query data sql

[0096] define data collection = execute query (query data sql);

[0097] / / Initialize the INSERT statement

[0098] define insert statement as String;

[0099] / / Initialize the history information collection

[0100] define resume information collection as List <record>;

[0101] / / Traverse the library structure to define the column set and data set, splice the INSERT statement and generate the resume information

[0102] for (column in library structure definition column set) {

[0103] for (data in data set) {

[0104] if (data.containsKey(column.column name)) {

[0105] / / Concatenate INSERT statements

[0106] insert statement += "INSERT INTO ... VALUES (...); ";

[0107] / / Call the resume generation method to generate resume information and add it to the collection

[0108] Resume information = generate resume method (column, null, data [column. column name], "new");

[0109] Resume information collection.add(resume information);

[0110] } else {

[0111] / / Handle the situation where the column has a default value or needs to generate an encoding

[0112] / / ...

[0113] }

[0114] }

[0115] }

[0116] / / Execute the INSERT statement to insert data into the database

[0117] Execute database operations (insert statements);

[0118] / / Return the resume information collection

[0119] return resume information collection;

[0120] }

[0121] Among them, processing update ledger data, generating and returning resume information is similar to the method of adding a new ledger. The main difference is that the UPDATE statement is spliced, and the update condition needs to be obtained to locate the data row to be updated. The pseudo code is as follows:

[0122] / / ... (the parts similar to the new ledger method are omitted)

[0123] / / Get the update condition and splice it into the WHERE part of the UPDATE statement

[0124] define update condition = get update condition based on executable script information (executable script information);

[0125] update statement += "WHERE " + update condition;

[0126] / / Execute the UPDATE statement to update the data in the database

[0127] Execute database operations (update statements);

[0128] / / Return the resume information collection

[0129] return resume information collection;

[0130] }

[0131] Step S13: History update. During the process flow, after reaching the node set in step S11, after completing the operation of step S12 at the same time, the history information of the specified ledger is synchronously updated to the history module.

[0132] Among them, the resume object is generated according to the ledger column configuration information, the previous value of the data, the next value of the data, and the operation type. The pseudo code is as follows:

[0133] / / Method parameters: ledger column configuration information, data before value, data after value, operation type

[0134] define Generate history method (ledger column configuration information, data before value, data after value, operation type) {

[0135] / / Initialize the resume object

[0136] define Resume object as Record;

[0137] / / Encapsulate the basic information of the resume object, such as table name, field name, operation type, etc.

[0138] Resume object. Table name = ledger column configuration information. Table name;

[0139] Resume object.Field name = ledger column configuration information.Column name;

[0140] Resume object.operation type = operation type;

[0141] / / Parse the data before and after values ​​and convert them into a readable format (such as converting codes into Chinese characters)

[0142] / / ...

[0143] / / Encapsulate the before and after values ​​of the parsed data into the resume object

[0144] Resume object.previous data value = previous data value after parsing;

[0145] Resume object.Data value = parsed data value;

[0146] / / Return the resume object

[0147] return resume object;

[0148] }

[0149] In one embodiment, the above-mentioned ledger module implements the addition, query, maintenance, import, export and verification of corresponding security and confidentiality business ledger information according to the access control policy, and saves the ledger information created or changed through business process push, specifically including:

[0150] Step S21: The ledger is added. The corresponding ledger record is automatically created through process approval or manually entered by a user with access rights. When the ledger information is created, a unique identifier for the ledger record is generated synchronously. This identifier will serve as the unique identifier for the entire life cycle management process of the ledger;

[0151] Step S22: Update of ledger information. Changes to corresponding ledger records can be achieved through process approval. When initiating process approval, a specified ledger record is selected and distinguished by the unique identifier in step S21. After approval, the information is automatically updated to the corresponding ledger at the specified process node, or the ledger information is manually maintained by a user with access rights and updated after saving.

[0152] Step S23: querying the ledger information. Users with access rights can query the ledger. The query conditions are specified by the ledger module.

[0153] Step S24: Exporting ledger information. Users with access rights can export the ledger information to export the ledger records within the user's query range to form an electronic spreadsheet file, which specifically includes:

[0154] Export of ledger information Users with corresponding access control permissions can export existing security and confidentiality business ledgers. In the ledger module, select the export operation, and you can select all fields in the ledger or select some fields in the ledger for export. You can revoke the selected fields. When the selection is complete, select Export, and the system will automatically export the ledger list file to the local computer.

[0155] Step S25: Importing ledger information. Users with access rights can import ledgers and upload existing ledger electronic spreadsheet files. The system automatically matches the fields in the specified header, or the user specifies the header to match the ledger fields. This can verify the length of the data and enable the addition or update (overwrite) of ledgers. Specifically, it includes:

[0156] Step S251: After entering the ledger module, select the import function, select the excel list file of the ledger historical data to be imported and upload it to the system. After uploading, the system will automatically list the business data table in the ledger module. After selecting the business data table, the field list in the table will be displayed. At the same time, the system will list the column names in the excel file in the interface to facilitate the correspondence between the ledger data table fields and the excel list;

[0157] Step S252: Match the correspondence of the fields. The column names in the Excel file are used as the source fields, and the fields in the system data table are used as the target fields. One-to-one correspondence can be achieved through manual selection. Only the source fields that have been added to the correspondence will be imported into the ledger database. The system can realize the automatic correspondence function. The system can automatically select the fields whose source field names in each column of the Excel file are consistent with the target field names in the ledger data table for one-to-one correspondence, and automatically form a correspondence relationship. In the correspondence matching process, the operation of removing the correspondence or resetting the correspondence can be manually selected to adjust the correspondence relationship.

[0158] Step S253: After completing the corresponding relationship matching, you can check the length of the corresponding field. Select the length verification function, and the system will automatically verify whether the data length of the source field matches the target field length. If they are consistent, it will prompt that the data can be imported into the database. If the source data length exceeds the limit, the name of the source field that exceeds the limit will be automatically prompted, and the import operation will be performed after modification and confirmation;

[0159] Step S254: You can choose to add or overwrite the import mode to operate. The adding operation is to add new ledger data, and the overwriting operation is to overwrite and update the existing ledger information. When the adding operation is selected, the unique identifier of the ledger is required to be clearly stated in the source data. The system will verify its uniqueness. If the field value is unique, the system will automatically add the ledger information to the database; if the field value is not unique during import, the system will automatically prompt that the import of non-unique data fails, and the import operation needs to be performed after modification and confirmation; when the overwriting operation is selected, the system will match the value of the unique identifier in the data source with the same ledger entry in the ledger data, and update the value of the corresponding target field according to the source field value in the data source; after the import operation is completed, the corresponding source data in Excel will be saved to the ledger data;

[0160] Step S255: Users with corresponding access control rights can export existing security and confidentiality business ledgers. In the ledger module, select the export operation, and select all fields in the ledger or select some fields in the ledger for export. The selected fields can be revoked. When the selection is complete, select Export, and the system will automatically export the ledger list file to the local computer.

[0161] Step S26: System integration, through which the addition of a ledger or the update of a corresponding ledger record is realized; while the ledger information is established, the system synchronously generates a unique identifier for the ledger record; wherein, system integration specifically includes:

[0162] System integration includes interface integration with other systems using at least one of the following methods: HTTP, WebService, DBlink, and API;

[0163] Step S27: Ledger verification. Users with access rights can verify the ledger. After selecting the corresponding ledger, initiate the verification. Modify the corresponding ledger field information and fill in the verification reason before saving. The system automatically pushes it to the reviewer. After the review is passed, the system automatically modifies the corresponding field information. If it fails, the information remains unchanged.

[0164] In one embodiment, the above-mentioned history module records the information changes of the corresponding security and confidentiality business ledger caused by process drive or user operation, summarizes and traces the history information of the corresponding ledger, performs query operations on the history information, and can generate a formatted electronic document from the history information, specifically including the following steps:

[0165] Step S31: History query, select the corresponding account to view its full life cycle history information, the recorded information includes operation date, operation time, operation type, operation source, operator, operation content, content before modification, content after modification, reviewer, related processes, and remarks. You can specify the operation date, operation type, operation source, operator, and related processes for conditional query;

[0166] Step S32: Process viewing, the corresponding approval process of the changed ledger data can be viewed in the resume information. The system uses anti-tampering technology to save all the information of the approval process. When viewing, the specific process form, flow process and approval information will be displayed;

[0167] Step S33: Resume generation. When performing resume summary and tracing, you can select a specified account to generate an electronic version of the account's resume record. After selecting to generate a resume, the system automatically generates PDF, OFD, XPS, and GD format files for the full life cycle resume information of the account, and implements document tamper-proofing through digital signatures.

[0168] In one embodiment, the account permission tag is set in the authorization management module, specifically including the following steps:

[0169] Step S41: The permission label of the ledger is to identify and classify the ledger information that each system role can access and obtain, so as to avoid the situation where the scope of knowledge of the ledger information is expanded. The corresponding permission label of the ledger-role is established in the system so that each role has a basis to rely on when accessing the ledger data;

[0170] Step S42: Select the corresponding role, and formulate the ledger module that the role can access, and describe the permission label in words to illustrate the access relationship between the role and the ledger; then maintain the access rights of the user attributes corresponding to the role, and specify the user access rights as "myself" or "all", that is, only the user's own ledger or all ledger information can be accessed. If "myself" is selected, the user field to which the corresponding ledger belongs can be specified as the judgment condition, supporting multiple field matching, that is, if any one of two or more user identification fields exists, access rights are granted; supporting partial matching of user values, that is, if at least one of the multiple user values ​​contained in the specified field matches the current user value, access rights are granted;

[0171] Step S43: Maintain the role's access rights to the department attributes corresponding to the ledger information, and specify the role's permission label for the department attributes to which the ledger belongs; the access rights can be specified as "this department" or "all", that is, the role can only access the ledger of the department to which it belongs or the ledger information of all departments; if "this department" is selected, the corresponding ledger department field can be specified as the judgment condition, and multiple field matching is supported, that is, access rights are granted if any one of two or more department identification fields exists; cascading parent departments is supported, that is, access rights to the parent department ledger can be granted;

[0172] Step S44: Maintain the role's settings for additional conditions specified for ledger information, including field name, field value, and matching rules, that is, when the specified additional condition field is equal to or contains the specified value, the role is granted access rights.

[0173] Step S45: After saving the permission tag settings, the role's permission tag configuration is completed. The ledger permission tag configuration can be performed for various roles in the system to ensure that all roles have complete access to ledger data.

[0174] In one embodiment, the above-mentioned organization management module is used to implement organization management, department user management, role management, user management, group management, position management, and user relationship management;

[0175] In one embodiment, the log audit module is used to record the operation information of users and administrators, designate administrators to view classified logs, support log archiving, and export system logs;

[0176] In one embodiment, the system management module is used to perform basic configuration management of the system, and to manage system configuration, menus, system parameters, data dictionaries, online users, scheduled tasks, codes, and confidentiality levels.

[0177] In one embodiment, the above-mentioned security and confidentiality business database stores the security and confidentiality business processes, ledgers, and history corresponding data in the database for system use.

[0178] Embodiment 2

[0179] Reference Figure 2 and Figure 3 , establish the business process through the process engine in the system, set which nodes in the process are used to add or update the ledger and record the history information after the process is established, and simultaneously establish a business ledger module in the system to enable the storage and use of ledger information and realize the data update function. In the embodiment of the present invention, a complete life cycle history management process of a secure and confidential business ledger is as follows:

[0180] Step 1: After establishing the ledger, you can set data permission tags for the ledger to control data filtering. The specific steps include:

[0181] Step 1.1: The permission label of the ledger is used to identify and classify the ledger information that each system role can access and obtain, so as to avoid the expansion of the scope of knowledge of the ledger information. The system should establish corresponding permission identification of the ledger-role so that each role has a basis for accessing the ledger data.

[0182] Step 1.2: Select the corresponding role and define the ledger module that the role can access. Describe the permission label in words to explain the access relationship between the role and the ledger. Then maintain the access rights of the user attributes corresponding to the role. You can specify the user access rights as "myself" or "all", that is, you can only access the user's own ledger or all ledger information. If you select "myself", you can specify the user field to which the corresponding ledger belongs as the judgment condition. It supports multiple field matching, that is, if any one of two or more user identification fields exists, access rights are granted; it supports partial matching of user values, that is, if at least one of the multiple user values ​​contained in the specified field matches the current user value, access rights are granted.

[0183] Step 1.3: Maintain the role's access rights to the department attributes corresponding to the ledger information. You can specify the role's permission label for the department attributes of the ledger. You can specify the access rights as "this department" or "all", that is, you can only access the ledger of the department to which the role belongs or the ledger information of all departments. If you select "this department", you can specify the corresponding ledger department field as the judgment condition. It supports multiple field matching, that is, if there is any one of two or more department identification fields, access rights are granted; it supports cascading parent departments, that is, access rights to the parent department ledger can be granted.

[0184] Step 1.4: Maintain the settings of additional conditions specified by the role for ledger information, including field name, field value, and matching rules. That is, when the specified additional condition field is equal to or contains the specified value, the role is granted access rights.

[0185] Step 1.5: After saving the permission tag settings, the permission tag configuration of the role is completed. The ledger permission tag configuration can be performed for various roles in the system to ensure that all roles have complete access to ledger data.

[0186] Step 2: When the process flows to the set node, the system will automatically maintain (create or update) the confidential business ledger information according to the corresponding data in the process and simultaneously record the history information of the changed ledger. At the same time, the system operation log will be recorded in the system. The specific steps include:

[0187] Step 2.1: The process flows to the setting node. The system will add or update the specified security and confidentiality business ledger according to the operation type. If it is an addition operation, the unique identifier of the ledger will be automatically verified, and a new unique identifier will be created according to the coding rules. At the same time, new ledger information will be created and written into the database. The data information generally includes: unique identifier, time information, ownership information, business information, confidentiality information, and validity information.

[0188] Step 2.2: If it is an update operation, the unique identifier of the ledger will be automatically verified, and the unique identifier of the corresponding ledger will be found based on the corresponding data information in the process. The ledger information will be updated and written into the database. The data information generally includes: time information, ownership information, business information, confidentiality information, and validity information.

[0189] Step 2.3: When performing step 2.1 or step 2.2, the history information generated by this operation will be synchronously recorded in the database, and the fields include: unique ID of the ledger, operation date, operation time, operation type, operation source, operator, operation content, content before modification, content after modification, reviewer, related processes, and remarks. The history is associated with the ledger information through the unique ID of the ledger, and the changes in the history of the entire life cycle of the ledger can be recorded accordingly. The operation date refers to the date on which the ledger is added or updated; the operation time refers to the hours, minutes, and seconds of the operation; the operation types include edit and add, edit refers to the update operation of the corresponding ledger, and add refers to the add operation of the corresponding ledger; the operation source includes two types: ledger or process, which respectively refer to manual addition or update in the ledger and automatic update through the process; the operator refers to the user who manually adds or updates the ledger, and the operator is not recorded in the automatic maintenance of the process; the operation content field refers to the added or updated ledger field; the content before modification refers to the value of the field of the corresponding ledger before the ledger field is added or updated manually or automatically by the process; the content after modification refers to the value of the field of the corresponding ledger after the ledger field is added or updated manually or automatically by the process; the reviewer refers to the user who manually adds, updates or verifies the ledger, and the process update does not record the reviewer information; the related process refers to the corresponding process information of the user ledger, and clicking the process can display the form and approval information of the process; the remarks field can record the name of this ledger or the corresponding process, and can also record other text information.

[0190] Step 2.4: When performing step 2.1 or step 2.2, the log information generated by this operation will be synchronously recorded in the system log. The log information includes: operator, operator IP, operation time, module name, log content, operation type, operation result, log type, and source.

[0191] Step 3: Users with corresponding ledger access control permissions can access the specified ledger module in the system according to the corresponding access control permissions, and can query or maintain ledger information. The scope of the queried ledger information is displayed according to the permission tag of the role to which the user belongs. The user cannot view the ledger information beyond the permission tag. The user can perform history query and trace the ledger within the scope of the permission tag, view the full life cycle history records of the corresponding ledger, and export the electronic file archive of the ledger history. The specific steps include:

[0192] Step 3.1: Select the corresponding account, click the history information in the account list, and the history display interface will pop up. You can query the history information by conditions, including operation date, operation time, operation type, operator, operation content, content before modification, content after modification, reviewer, related processes, and notes. According to the operation content, you can accurately locate the history information that needs to be queried, improving the efficiency of review and tracing.

[0193] Step 3.2: Export the electronic file of the record of the ledger. Click on the record export button. The system will automatically generate a layout electronic file based on the record information of the current ledger and export it to the local computer. The information in the electronic file includes record information, process forms, flow charts, and approval information. The layout electronic file formats include PDF, OFD, XPS, and GD formats, and digital signatures are used to prevent document tampering.

[0194] Step 3.3: You can select the ledgers within the specified range to batch export the resume information. Selecting batch export of resumes will export the resume information of the selected ledgers together. The information content contained in the exported electronic format file is consistent with that in step 3.2.

[0195] Step 4: When managing the security and confidentiality business ledger, users can import and export data in the ledger to meet relevant management requirements. Users with corresponding access control permissions can access the specified security and confidentiality business ledger module. If the ledger is initialized, historical data can be imported by importing an Excel list file. The specific steps are as follows:

[0196] Step 4.1: After entering the ledger module, select the import function, select the excel list file of the ledger historical data to be imported and upload it to the system. After uploading, the system will automatically list the business data table in the ledger module. After selecting the business data table, the field list in the table will be displayed. At the same time, the system will list the column names in the excel file in the interface to facilitate the correspondence between the ledger data table fields and the excel list.

[0197] Step 4.2: Match the correspondence of the fields. Use the column names in the Excel file as the source fields and the fields in the system data table as the target fields. One-to-one correspondence can be achieved through manual selection. Only the source fields that have been added to the correspondence will be imported into the ledger database. The system can realize the automatic correspondence function. The system can automatically select the fields with the same source field names in each column of the Excel file and the same target field names in the ledger data table for one-to-one correspondence, and automatically form a correspondence. In the correspondence matching process, you can manually select to remove the correspondence or reset the correspondence to adjust the correspondence.

[0198] Step 4.3: After completing the corresponding relationship matching, you can check the length of the corresponding field. Select the length verification function, and the system will automatically verify whether the data length of the source field matches the length of the target field. If they are consistent, it will prompt that the database can be imported. If the source data length exceeds the limit, the name of the source field that exceeds the limit will be automatically prompted, and the import operation needs to be modified and confirmed.

[0199] Step 4.4: You can choose to add or overwrite the import method. Adding means adding new ledger data, and overwriting means overwriting and updating the existing ledger information. When adding, the source data is required to clearly identify the unique identifier of the ledger. The system will verify its uniqueness. If the field value is unique, the system will automatically add the ledger information to the database. If the field value is not unique during import, the system will automatically prompt that the import of non-unique data has failed, and the modification needs to be confirmed before the import operation can be performed. When overwriting is selected, the system will match the value of the unique identifier in the data source with the same ledger entry in the ledger data, and update the value of the corresponding target field according to the source field value in the data source. After the import operation is completed, the corresponding source data in Excel will be saved in the ledger data.

[0200] Step 4.5: Users with corresponding access control permissions can export existing security and confidentiality business ledgers. Select the export operation in the ledger module. You can select all fields in the ledger or select some fields in the ledger for export. You can revoke the selected fields. When the selection is complete, select Export, and the system will automatically export the ledger list file to the local computer.< / record> < / record> < / string>

Claims

1. A process-driven, secure and confidential business account life cycle history maintenance system, characterized in that: Includes the following modules: The business process module is used to define the business approval process for security and confidentiality management and realize the automatic flow of the approval process; automatically add and update the corresponding security and confidentiality business ledger according to the preset process nodes, and automatically trigger the recording operation of the resume information; The ledger module, based on the access control policy, implements the addition, query, maintenance, import, export and verification of corresponding security and confidentiality business ledger information, and saves the ledger information created or changed through business process push; The resume module records the information changes of the corresponding security and confidentiality business ledgers caused by process drive or user operation, summarizes and traces the resume information of the corresponding ledger, performs query operations on the resume information, and can generate formatted electronic documents from the resume information; The authorization management module is used to authorize menus and interface components in the system. The authorization dimensions are roles, departments, users, positions, and groups, taking the union of multiple dimensions; Set ledger permission tags, specify corresponding roles, users, departments, or implement filtering, display and scope control of ledger data based on set ledger fields; Organization management module, used to implement organization management, department user management, role management, user management, group management, position management, and user relationship management; The log audit module is used to record the operation information of users and administrators, designate administrators to view classified logs, support log archiving, and export system logs; System management module is used to manage the basic configuration of the system, including system configuration, menus, system parameters, data dictionary, online users, scheduled tasks, codes, and confidentiality levels; The secure and confidential business database stores the corresponding data of the secure and confidential business processes, ledgers, and resumes in the database for system use.

2. According to the process-driven security and confidentiality business account full life cycle history maintenance system of claim 1, it is characterized by: The business process module automatically adds and updates the corresponding security and confidentiality business ledger according to the preset process nodes, and automatically triggers the recording operation of the resume information, specifically including the following steps: Step S11: Process configuration, which implements the configuration of the association between the approval process and the approval form through the process engine, and specifies the approval node to automatically add and update the ledger information; Step S12: Account addition and update. During the process flow, after reaching the node set in step S11, the system automatically adds or updates the specified account information to the account module according to the business logic; Step S13: History update. During the process flow, after reaching the node set in step S11, after completing the operation of step S12 at the same time, the history information of the specified ledger is synchronously updated to the history module.

3. According to the process-driven security and confidentiality business account full life cycle history maintenance system of claim 1, it is characterized by: The ledger module implements the addition, query, maintenance, import, export and verification of corresponding security and confidentiality business ledger information according to the access control policy, and saves the ledger information created or changed through business process push, specifically including: Step S21: The ledger is added. The corresponding ledger record is automatically created through process approval or manually entered by a user with access rights. When the ledger information is created, a unique identifier for the ledger record is generated synchronously. This identifier will serve as the unique identifier for the entire life cycle management process of the ledger; Step S22: Update of ledger information. Changes to corresponding ledger records can be achieved through process approval. When initiating process approval, a specified ledger record is selected and distinguished by the unique identifier in step S21. After approval, the information is automatically updated to the corresponding ledger at the specified process node, or the ledger information is manually maintained by a user with access rights and updated after saving. Step S23: querying the ledger information. Users with access rights can query the ledger. The query conditions are specified by the ledger module. Step S24: Exporting ledger information: users with access rights can export the ledger information to export the ledger records within the user's query range and form an electronic spreadsheet file; Step S25: Importing ledger information. Users with access rights can import ledgers and upload existing ledger electronic spreadsheet files. The system automatically matches the fields in the specified header, or the user can specify the header to match the ledger fields. This can verify the length of the data and enable the addition or update of ledgers. Step S26: System integration, through which the addition of a ledger or the update of a corresponding ledger record is realized; while the ledger information is established, the system synchronously generates a unique identifier for the ledger record; Step S27: Ledger verification. Users with access rights can verify the ledger. After selecting the corresponding ledger, initiate the verification. Modify the corresponding ledger field information and fill in the verification reason before saving. The system automatically pushes it to the reviewer. After the review is passed, the system automatically modifies the corresponding field information. If it fails, the information remains unchanged.

4. The process-driven security and confidentiality business account full life cycle history maintenance system according to claim 3 is characterized in that: Step S24: Exporting ledger information: A user with access rights can export the ledger to export the ledger records within the user's query range to form an electronic spreadsheet file, specifically including: The export of ledger information can be performed by users with corresponding access control permissions to export existing security and confidentiality business ledgers. In the ledger module, select the export operation, you can select all fields in the ledger, or select some fields in the ledger for export. You can revoke the selected fields. When the selection is completed, select Export, and the system will automatically export the ledger list file to the local computer.

5. The process-driven security and confidentiality business account full life cycle history maintenance system according to claim 3 is characterized in that: Step S25: Importing ledger information. Users with access rights can import the ledger and upload an existing ledger electronic spreadsheet file. The system automatically matches the fields in the specified header, or the user specifies the header to match the ledger field. This can verify the length of the data and add or update the ledger. Specifically, it includes: Step S251: After entering the ledger module, select the import function, select the excel list file of the ledger historical data to be imported and upload it to the system. After uploading, the system will automatically list the business data table in the ledger module. After selecting the business data table, the field list in the table will be displayed. At the same time, the system will list the column names in the excel file in the interface to facilitate the correspondence between the ledger data table fields and the excel list; Step S252: Match the correspondence of the fields. The column names in the Excel file are used as the source fields, and the fields in the system data table are used as the target fields. One-to-one correspondence can be achieved through manual selection. Only the source fields that have been added to the correspondence will be imported into the ledger database. The system can realize the automatic correspondence function. The system can automatically select the fields whose source field names in each column of the Excel file are consistent with the target field names in the ledger data table for one-to-one correspondence, and automatically form a correspondence relationship. In the correspondence matching process, the operation of removing the correspondence or resetting the correspondence can be manually selected to adjust the correspondence relationship. Step S253: After completing the matching relationship, you can check the length of the corresponding field. Select the length verification function. The system will automatically verify whether the data length of the source field matches the length of the target field. If they match, it will prompt that the data can be imported into the database. If the source data length exceeds the limit, the name of the source field that exceeds the limit will be automatically prompted. You need to modify and confirm before importing. Step S254: You can choose to add or overwrite the import mode to operate. The adding operation is to add new ledger data, and the overwriting operation is to overwrite and update the existing ledger information. When the adding operation is selected, the unique identifier of the ledger is required to be clearly stated in the source data. The system will verify its uniqueness. If the field value is unique, the system will automatically add the ledger information to the database; if the field value is not unique during import, the system will automatically prompt that the import of non-unique data fails, and the import operation needs to be performed after modification and confirmation; when the overwriting operation is selected, the system will match the value of the unique identifier in the data source with the same ledger entry in the ledger data, and update the value of the corresponding target field according to the source field value in the data source; after the import operation is completed, the corresponding source data in Excel will be saved to the ledger data; Step S255: Users with corresponding access control permissions can export existing security and confidentiality business ledgers. Select the export operation in the ledger module. You can select all fields in the ledger or select some fields in the ledger for export. You can revoke the selected fields. When the selection is complete, select Export, and the system will automatically export the ledger list file to the local computer.

6. The process-driven security and confidentiality business account full life cycle history maintenance system according to claim 3 is characterized in that: The system integration in step S26 specifically includes: The system integration includes interface integration with other systems using at least one of HTTP, WebService, DBlink, and API.

7. The process-driven security and confidentiality business account full life cycle history maintenance system according to claim 1 is characterized in that: The history module records the information changes of the corresponding security and confidentiality business ledgers caused by process drive or user operation, summarizes and traces the history information of the corresponding ledgers, performs query operations on the history information, and can generate a formatted electronic document from the history information, specifically including the following steps: Step S31: History query. Select the corresponding account to view its full life cycle history information. The recorded information includes operation date, operation time, operation type, operation source, operator, operation content, content before modification, content after modification, reviewer, related processes, and remarks. You can specify the operation date, operation type, operation source, operator, and related processes for conditional query; Step S32: Process viewing, the corresponding approval process of the changed ledger data can be viewed in the resume information. The system uses anti-tampering technology to save all the information of the approval process. When viewing, the specific process form, flow process and approval information will be displayed; Step S33: Resume generation. When performing resume summary and tracing, you can select a specified ledger to generate an electronic resume record for the ledger. After selecting to generate a resume, the system automatically generates a PDF, OFD, XPS, or GD format file for the entire life cycle resume information of the ledger and exports it, and uses digital signatures to prevent document tampering.

8. The process-driven secure and confidential business account life cycle history maintenance system according to claim 1 is characterized in that: The authorization management module sets the ledger permission label, which specifically includes the following steps: Step S41: The permission label of the ledger is to identify and classify the ledger information that each system role can access and obtain, so as to avoid the situation where the scope of knowledge of the ledger information is expanded. The corresponding permission label of the ledger-role is established in the system so that each role has a basis to rely on when accessing the ledger data; Step S42: Select the corresponding role, and formulate the ledger module that the role can access, and give a text description to the permission label to illustrate the access relationship between the role and the ledger; Maintain the access rights of user attributes corresponding to the role; Step S43: Maintain the role's access rights to the department attributes corresponding to the ledger information, and specify the role's authority label for the department attributes to which the ledger belongs; Step S44: Maintain the settings of additional conditions specified by the role for the ledger information, including field name, field value and matching rule, that is, when the specified additional condition field is equal to or contains the specified value, the role is granted access rights; Step S45: After saving the permission tag settings, the role's permission tag configuration is completed. The ledger permission tag configuration can be performed for various roles in the system to ensure that all roles have complete access to ledger data.

Images