CN117851160A - Log recording system and method for business data stream change process - Google Patents

Log recording system and method for business data stream change process Download PDF

Info

Publication number
CN117851160A
CN117851160A CN202311712640.0A CN202311712640A CN117851160A CN 117851160 A CN117851160 A CN 117851160A CN 202311712640 A CN202311712640 A CN 202311712640A CN 117851160 A CN117851160 A CN 117851160A
Authority
CN
China
Prior art keywords
flow
layer
file
module
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311712640.0A
Other languages
Chinese (zh)
Inventor
黄卫坚
葛海波
汪浩博
张�杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tianyi Cloud Technology Co Ltd
Original Assignee
Tianyi Cloud Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tianyi Cloud Technology Co Ltd filed Critical Tianyi Cloud Technology Co Ltd
Priority to CN202311712640.0A priority Critical patent/CN117851160A/en
Publication of CN117851160A publication Critical patent/CN117851160A/en
Pending legal-status Critical Current

Links

Abstract

The invention provides a business data flow change process log recording system and a method thereof, belonging to the technical field of data log processing, wherein the business data flow change process log recording system comprises an access layer, an interface layer, a service layer and a resource layer, wherein the access layer is used for processing user requests, the interface layer defines a public interface of the system, so that a user or other systems can interact with the system, the service layer is used for processing business logic, including verification, processing, storage and the like of data, and the resource layer is used for being responsible for actual data storage and management; in the invention, the flow submitting form data is extracted into PDF format file snapshots and is related to the flow history track, and software development of form data storage, analysis and display is realized based on different types of flow forms in different vertical fields, so that universal PDF file resource reading and writing are made.

Description

Log recording system and method for business data stream change process
Technical Field
The invention belongs to the technical field of data log processing, and particularly relates to a business data stream flow process log recording system and a business data stream flow process log recording method.
Background
In recent years, with the rapid development of PC internet and mobile internet technologies, various industrial digital transformation changes to bremsstrahlung, and the cooperation of office demands should be transported for acceleration. Because government document approval and business processing are both performed in flow form, workflow technology becomes an essential part in collaborative office systems.
However, in the current business process circulation process of each business, due to the diversity and complex data structure of the business process forms, the system only records the historical track and approval opinion of the process at each process node, and does not record the change record of the form data. The process form is caused to be started to be ended, the node where the form data is modified cannot be distinguished, and the requirements of process instance history track tracking or history step backtracking cannot be met. Therefore, a method for backtracking the record change of the workflow form is required to be provided, so as to solve the problems of the history track of the workflow form instance and the backtracking of the history data.
Disclosure of Invention
The invention aims to provide a business data flow change process log recording system and a business data flow change process log recording method, and aims to solve the problems that in the prior art, the history track of a workflow form example is final and the history data backtracking is large.
In order to achieve the above purpose, the present invention provides the following technical solutions:
a business data stream change process logging system, comprising: the system comprises an access layer, an interface layer, a service layer and a resource layer, wherein the access layer is used for being responsible for processing user requests, the interface layer defines a public interface of the system so that a user or other systems can interact with the system, the service layer is used for processing business logic, including verification, processing, storage and the like of data, and the resource layer is used for being responsible for actual data storage and management.
As a preferable scheme of the invention, a web terminal and a PC terminal are arranged in the access layer.
As a preferred aspect of the present invention, the interface layer API Gateway Nginx is load balanced.
As a preferable scheme of the invention, a business service module and a service management module are arranged in the service layer.
As a preferable scheme of the invention, the business service module is internally provided with a user module, a login module, a flow module, an approval module, a file module and a historical data module.
As a preferable scheme of the invention, the service management module is internally provided with a monitoring alarm unit, a log management unit, a permission management unit, an access limiting unit and a timing task unit.
As a preferable scheme of the invention, a database, a cache module and a file storage module are arranged in the resource layer.
A business data flow change process log recording method comprises the following steps:
s101, when a flow node submits a node action, automatically constructing a PDF format file of a snapshot of a current flow table by a system;
s102, recording resource codes of snapshot files and current flow track codes by a flow instance;
s103, when the user tracks the history track of the process instance, the user associates the history track with the corresponding snapshot file of the process form through process track coding and loads the snapshot file out for backtracking.
As a preferable scheme of the invention, the method also comprises a flow form task forward flow, which comprises the following specific steps:
step 1: processing the flow node task and submitting the node task
Step 2: construction of node form pdf snapshot file
Step 3: generating file resource codes and current flow node track numbers
Step 4: recording the track number of the flow node by the flow instance
Step 5: recording the relation between pdf snapshot and file resource codes, and repeating the steps until the task processing of the flow node is finished.
As a preferable scheme of the invention, the invention also comprises a flow form task backtracking flow, and the specific steps are as follows:
step 1: the process instance backtracking starts, and the node track number of the process instance is obtained
Step 2: associating corresponding file resource codes through flow node track codes
Step 3: and (3) exporting the corresponding pdf snapshot file corresponding to the corresponding file resource codes, loading the pdf snapshot file out for backtracking, and ending the backtracking of the flow form task.
A further embodiment of the present application provides a storage medium having a computer program stored therein, wherein the computer program is arranged to implement the method of any of the above when run.
Yet another embodiment of the present application provides an electronic device comprising a memory having a computer program stored therein and a processor configured to run the computer program to implement the method described in any of the above.
Compared with the prior art, the invention has the beneficial effects that:
1. in the invention, the flow submitting form data is extracted into PDF format file snapshots and is related to the flow history track, and software development of form data storage, analysis and display is realized based on different types of flow forms in different vertical fields, so that universal PDF file resource reading and writing are made.
2. In the invention, by providing a standard development mode, an API call interface and other remote call modes, the service core code is not required to be modified basically, and the development workload of software is reduced greatly.
3. According to the invention, the process of each data change is recorded by recording the flow path track information, and the snapshot information is stored by pdf, so that the history track inquiry function is realized. The method thoroughly solves the problems that the change of data of each node cannot be checked in the conventional flow and the historical data cannot be traced back.
4. The invention has wide applicability, provides standardized and universal capability access, and is suitable for services in different vertical fields.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate the invention and together with the embodiments of the invention, serve to explain the invention. In the drawings:
FIG. 1 is a block flow diagram of a business data stream change process logging system and method according to the present invention;
FIG. 2 is a system block diagram of a business data stream change process logging system and method thereof according to the present invention;
FIG. 3 is a block diagram illustrating a backtracking process in a business data flow change process log recording system and method according to the present invention;
FIG. 4 is a block diagram of a business data stream change process logging system and method according to the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Example 1
Referring to fig. 1-4, the present invention provides the following technical solutions:
a business data stream change process logging system, comprising: the system comprises an access layer, an interface layer, a service layer and a resource layer, wherein the access layer is used for processing user requests, the interface layer defines a public interface of the system, so that a user or other systems can interact with the system, the service layer is used for processing business logic, including verification, processing, storage and the like of data, and the resource layer is used for being responsible for actual data storage and management.
In a specific embodiment of the present invention,
a business data stream flow process logging system comprising four levels: an access layer, an interface layer, a service layer, and a resource layer. Each layer has its specific roles and functions.
Access layer:
the function is as follows: the access layer is the portal for a user or client application to interact with the traffic data stream. It is responsible for receiving and validating requests from clients and ensuring that the requests meet the security and rights requirements of the system.
The functions are as follows: the access layer typically has authentication, authorization, request filtering, and session management functions. It verifies the identity of the user and manages the user's session, ensuring that only authorized users can access the protected traffic data stream.
Interface layer:
the function is as follows: the interface layer is responsible for processing requests from the access layer, converting them into formats for use within the system, and routing them to the corresponding service layer for processing. It is also responsible for converting the response results from the service layer back to the format desired by the client and returning them to the client.
The functions are as follows: the interface layer has the functions of request analysis, protocol conversion, routing and the like. The method analyzes the request of the client, converts the request into a data structure used in the system, and routes the request to a corresponding service layer for processing according to the type and the target of the request.
Service layer:
the function is as follows: the service layer is the core of the service data flow and is responsible for processing specific service logic and data operation. The method executes corresponding operations, such as data inquiry, updating, deleting and the like, according to the request parameters transmitted by the interface layer, and generates a response result to return to the interface layer.
The functions are as follows: the service layer has the functions of business logic processing, data processing, response generation and the like. The method executes corresponding business logic and data processing operation according to the request parameters transferred by the interface layer, generates a response result and returns the response result to the interface layer.
Resource layer:
the function is as follows: the resource layer is responsible for storing and managing the actual traffic data. Which may be a database, file system, or other type of storage medium.
The functions are as follows: the resource layer has the functions of data storage and maintenance. It is responsible for storing business data, ensuring data integrity and consistency, and providing data access and manipulation capabilities to support the service layer to perform corresponding business logic and data processing operations.
Access layer: this layer is mainly responsible for handling user requests including authentication, authorization of user identity, routing of requests, etc. It ensures that only authorized users can access the system while routing requests to the correct location. When new traffic data flow changes, the access layer will capture these changes and pass them on to other layers for processing.
Interface layer: this layer is responsible for defining the common interface of the system so that a user or other system can interact with the system. It receives the request from the access layer and performs a preliminary processing on it before passing it to the service layer. The interface layer is also responsible for returning the service layer's response to the user or other system.
Service layer: this layer is the core of the business data stream flow process logging system. It is responsible for handling business logic including authentication, processing, and storage of data, etc. When the request transmitted by the interface layer reaches the service layer, the service layer performs corresponding processing according to the type and the content of the request. For example, if the request is to obtain a log of the flow of a certain type of traffic data, the service layer will obtain the corresponding data from the resource layer and return to the interface layer.
Resource layer: this is the bottom layer of the business data stream flow process logging system, responsible for the actual data storage and management. The resource layer contains all service data including service data stream logs, user information, authority information and the like. The resource layer realizes the persistence and the safety management of the data through the interaction with the access layer and the service layer.
Such a layered design allows for a clear system architecture and ease of maintenance and expansion. Defining the responsibilities and interaction modes of each layer helps to ensure availability and stability of the system when implementing a business data stream flow logging system.
The invention extracts the flow submitting form data into PDF format file snapshot and associates the PDF format file snapshot with the flow history track, and originally, software development of form data storage, analysis and display is realized based on different types of flow forms in different vertical fields, so that universal PDF file resource reading and writing are made; by providing a standard development mode, an API call interface and other remote call modes, the service core code is not required to be modified basically, and the development workload of software is reduced greatly; and recording the process of each data change by recording flow path information, and storing snapshot information by pdf to realize a history path inquiry function. The method thoroughly solves the problems that the change of data of each node cannot be checked and the historical data cannot be traced back in the conventional process; the method has wide applicability, provides standardized and universal capability access, and is suitable for services in different vertical fields.
Specifically, a web terminal and a PC terminal are arranged in the access layer.
Specifically, the interface layer is API Gateway Nginx load balancing.
API Gateway Nginx load balancing uses Nginx as a reverse proxy server to process requests from clients and forward those requests onto the back-end server. In this way, API Gateway Nginx can achieve load balancing and high availability, thereby improving the performance and reliability of the system.
In API Gateway Nginx load balancing, nmginx receives requests from clients as reverse proxy servers and forwards the requests to the back-end servers according to configured load balancing policies. Common load balancing strategies include polling, random, weighted polling, weighted random, and the like. By these strategies, nmginx can ensure that the load of each server is approximately equal, thereby improving the performance and reliability of the system.
Specifically, a business service module and a service management module are arranged in the service layer.
Specifically, a user module, a login module, a flow module, an approval module, a file module and a historical data module are arranged in the business service module.
Specifically, a monitoring alarm unit, a log management unit, a permission management unit, an access limiting unit and a timing task unit are arranged in the service management module.
In the service management module, the functions of the respective units are as follows:
1. monitoring and alarming unit: this unit is responsible for monitoring the operating state of the system, and if an abnormality or failure occurs, it will issue an alarm notification in time so that an administrator or developer can quickly find and solve the problem.
2. Log management unit: this unit is responsible for recording all activities of the system including user behavior, system events, applications, etc. These logs can be used for troubleshooting, problem localization, auditing, compliance checking, and the like.
3. Rights management unit: this unit is responsible for managing the access rights of the system, including user authentication and authorization. It can ensure that only users with the proper rights can access the system or perform certain operations.
4. An access restriction unit: this unit is responsible for restricting the user's access to the system and various policies, such as IP address restrictions, time period restrictions, etc., may be set to prevent unauthorized access.
5. A timed task unit: this unit is responsible for performing predetermined tasks, such as periodically backing up data, cleaning up log files, updating the system, etc., at specific time intervals.
The units cooperate together to enable the service management module to effectively manage and maintain the system, ensuring that it operates stably, safely and efficiently.
Specifically, a database, a cache module and a file storage module are arranged in the resource layer.
Specifically, the method for recording the business data stream change process log is characterized by comprising the following steps:
s101, when a flow node submits a node action, automatically constructing a PDF format file of a snapshot of a current flow table by a system;
s102, recording resource codes of snapshot files and current flow track codes by a flow instance;
s103, when the user tracks the history track of the process instance, the user associates the history track with the corresponding snapshot file of the process form through process track coding and loads the snapshot file out for backtracking.
In this embodiment: in the invention, the workflow in each vertical field has a certain common place. In a workflow system, a business process is defined as individual nodes of the process according to model rules defined by a process engine. When the flow instance operates, the flow flows to each node of the flow, the associated flow forms are submitted through operations such as executing actions, the next approval node of the flow is guided, and meanwhile, the state of the flow instance is modified, so that the flow circulation of the flow is achieved. Each time the flow example is circulated, the information of the current node is written into a flow history track data table or a change log is recorded, and the information of the next node is written into a current step table. After the flow instance is circulated for a plurality of times, the actual running track of the flow instance can be tracked according to the record of the history track table and the user operation log;
because the history track table of the flow only records the flow circulation record and the approval opinion, in order to trace back the record change of the flow form data at different flow nodes, a set of flow data change log table needs to be introduced, and a unique primary key number field of the flow log is added in the log table for being related to the flow track. When the flow node executes action submission, a flow data form snapshot at the current submission is constructed, stored in a PDF or picture format file, and the resource primary key number of the snapshot is recorded in a flow form single track table. Simultaneously, the current flow track resource primary key number is also written into the flow form log table together. When the flow history track is tracked in the subsequent flow example, form snapshot files in a flow form data change table can be associated through the flow track numbers, form data submitted by the current flow can be intuitively reproduced in a PDF file mode, and therefore accurate monitoring can be achieved on service data;
by the method, record changing conditions of form data at different nodes of the process can be quickly and intuitively traced back for different types of process forms, and the requirements of each vertical field on process data monitoring and tracing can be basically met.
Specifically, in the present invention, the forward flow of the flow chart task is as follows:
step 1: processing the flow node task and submitting the node task
Step 2: construction of node form pdf snapshot file
Step 3: generating file resource codes and current flow node track numbers
Step 4: recording the track number of the flow node by the flow instance
Step 5: recording the relation between pdf snapshot and file resource codes, and repeating the steps until the task processing of the flow node is finished.
Specifically, in the invention, the process of backtracking the task of the flow form is as follows:
step 1: the process instance backtracking starts, and the node track number of the process instance is obtained
Step 2: associating corresponding file resource codes through flow node track codes
Step 3: and (3) exporting the corresponding pdf snapshot file corresponding to the corresponding file resource codes, loading the pdf snapshot file out for backtracking, and ending the backtracking of the flow form task.
Specifically, the method for constructing the flow form data snapshot in the invention comprises the following steps:
1. setting a set of flow table Shan Rizhi table, and adding a flow track number field in the log table for being related to the flow track;
2. when a flow node executes action submission, constructing a flow form snapshot at the current submission, storing the snapshot in a PDF format file, and recording a resource code of the snapshot and a current flow track number in a flow form log table;
3. form snapshot files in the flow form log list are associated through the flow track numbers, and form data submitted by the flow at the time are intuitively reproduced in a PDF file mode.
The invention extracts the flow submitting form data into PDF format file snapshot and associates the PDF format file snapshot with the flow history track, and originally, software development of form data storage, analysis and display is realized based on different types of flow forms in different vertical fields, so that universal PDF file resource reading and writing are made; by providing a standard development mode, an API call interface and other remote call modes, the service core code is not required to be modified basically, and the development workload of software is reduced greatly; and recording the process of each data change by recording flow path information, and storing snapshot information by pdf to realize a history path inquiry function. The method thoroughly solves the problems that the change of data of each node cannot be checked and the historical data cannot be traced back in the conventional process; the method has wide applicability, provides standardized and universal capability access, and is suitable for services in different vertical fields.
The embodiment of the invention also provides a storage medium, in which a computer program is stored, wherein the computer program is configured to implement the steps in any of the method embodiments described above when run.
Specifically, in the present embodiment, the above-described storage medium may be configured to store a computer program for executing the steps of:
s101, when a flow node submits a node action, automatically constructing a PDF format file of a snapshot of a current flow table by a system;
s102, recording resource codes of snapshot files and current flow track codes by a flow instance;
s103, when the user tracks the history track of the process instance, the user associates the history track with the corresponding snapshot file of the process form through process track coding and loads the snapshot file out for backtracking.
Specifically, in the present embodiment, the storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.
Compared with the prior art, the method has the advantages that the flow submitting form data are extracted into PDF format file snapshots and are related to flow history tracks, and software development of form data storage, analysis and display is realized based on different types of flow forms in different vertical fields originally, so that universal PDF file resource reading and writing are made; by providing a standard development mode, an API call interface and other remote call modes, the service core code is not required to be modified basically, and the development workload of software is reduced greatly; and recording the process of each data change by recording flow path information, and storing snapshot information by pdf to realize a history path inquiry function. The method thoroughly solves the problems that the change of data of each node cannot be checked and the historical data cannot be traced back in the conventional process; the method has wide applicability, provides standardized and universal capability access, and is suitable for services in different vertical fields.
The embodiment of the invention also provides an electronic device comprising a memory, in which a computer program is stored, and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
Specifically, the electronic device may further include a transmission device and an input/output device, where the transmission device is connected to the processor, and the input/output device is connected to the processor.
Specifically, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
s101, when a flow node submits a node action, automatically constructing a PDF format file of a snapshot of a current flow table by a system;
s102, recording resource codes of snapshot files and current flow track codes by a flow instance;
s103, when the user tracks the history track of the process instance, the user associates the history track with the corresponding snapshot file of the process form through process track coding and loads the snapshot file out for backtracking.
Compared with the prior art, the method has the advantages that the flow submitting form data are extracted into PDF format file snapshots and are related to flow history tracks, and software development of form data storage, analysis and display is realized based on different types of flow forms in different vertical fields originally, so that universal PDF file resource reading and writing are made; by providing a standard development mode, an API call interface and other remote call modes, the service core code is not required to be modified basically, and the development workload of software is reduced greatly; and recording the process of each data change by recording flow path information, and storing snapshot information by pdf to realize a history path inquiry function. The method thoroughly solves the problems that the change of data of each node cannot be checked and the historical data cannot be traced back in the conventional process; the method has wide applicability, provides standardized and universal capability access, and is suitable for services in different vertical fields.
It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present invention is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present invention. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present invention.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, such as the above-described division of units, merely a division of logic functions, and there may be additional manners of dividing in actual implementation, such as multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, or may be in electrical or other forms.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present invention may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a memory, comprising several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the above-mentioned method of the various embodiments of the present invention. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Finally, it should be noted that: the foregoing description is only a preferred embodiment of the present invention, and the present invention is not limited thereto, but it is to be understood that modifications and equivalents of some of the technical features described in the foregoing embodiments may be made by those skilled in the art, although the present invention has been described in detail with reference to the foregoing embodiments. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A business data stream change process logging system, comprising: the system comprises an access layer, an interface layer, a service layer and a resource layer, wherein the access layer is used for being responsible for processing user requests, the interface layer defines a public interface of the system so that a user or other systems can interact with the system, the service layer is used for processing business logic, including verification, processing, storage and the like of data, and the resource layer is used for being responsible for actual data storage and management.
2. The system of claim 1, wherein the access layer is provided with a web side and a PC side.
3. The traffic data stream flow logging system of claim 2, wherein said interface layer API Gateway Nginx is load balanced.
4. A business data stream flow logging system as claimed in claim 3, wherein a business service module and a service management module are provided within the service layer.
5. The system of claim 4, wherein the business service module is provided with a user module, a login module, a flow module, an approval module, a file module, and a history data module.
6. The system according to claim 5, wherein the service management module is provided with a monitoring alarm unit, a log management unit, a right management unit, an access limiting unit and a timing task unit; and a database, a cache module and a file storage module are arranged in the resource layer.
7. A method of logging changes to a traffic data stream according to any one of claims 1 to 6, comprising the steps of:
s101, when a flow node submits a node action, automatically constructing a PDF format file of a snapshot of a current flow table by a system;
s102, recording resource codes of snapshot files and current flow track codes by a flow instance;
s103, when the user tracks the history track of the process instance, the user associates the history track with the corresponding snapshot file of the process form through process track coding and loads the snapshot file out for backtracking.
8. The method of claim 7, further comprising:
the forward flow of the flow form task comprises the following specific steps:
step 1: processing the flow node task and submitting the node task
Step 2: construction of node form pdf snapshot file
Step 3: generating file resource codes and current flow node track numbers
Step 4: recording the track number of the flow node by the flow instance
Step 5: recording the relation between pdf snapshot and file resource codes, and repeating the steps until the task processing of the flow node is finished.
The process form task backtracking process comprises the following specific steps:
step 1: the process instance backtracking starts, and the node track number of the process instance is obtained
Step 2: associating corresponding file resource codes through flow node track codes
Step 3: and (3) exporting the corresponding pdf snapshot file corresponding to the corresponding file resource codes, loading the pdf snapshot file out for backtracking, and ending the backtracking of the flow form task.
9. A storage medium having a computer program stored therein, wherein the computer program is arranged to implement the method of any of claims 1 to 6 when run.
10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to run the computer program to implement the method of any of the claims 1 to 6.
CN202311712640.0A 2023-12-13 2023-12-13 Log recording system and method for business data stream change process Pending CN117851160A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311712640.0A CN117851160A (en) 2023-12-13 2023-12-13 Log recording system and method for business data stream change process

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311712640.0A CN117851160A (en) 2023-12-13 2023-12-13 Log recording system and method for business data stream change process

Publications (1)

Publication Number Publication Date
CN117851160A true CN117851160A (en) 2024-04-09

Family

ID=90531279

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311712640.0A Pending CN117851160A (en) 2023-12-13 2023-12-13 Log recording system and method for business data stream change process

Country Status (1)

Country Link
CN (1) CN117851160A (en)

Similar Documents

Publication Publication Date Title
US11157629B2 (en) Identity risk and cyber access risk engine
RU2586866C2 (en) Differentiation of set of features of participant of leased medium and user
CN108615148B (en) A kind of preposition method of commerce of secured assets and system based on block chain technology
CN111400112B (en) Writing method and device of storage system of distributed cluster and readable storage medium
CN102947797A (en) Online service access controls using scale out directory features
CN115210741A (en) Partially ordered block chain
CN111327613B (en) Distributed service authority control method and device and computer readable storage medium
EP3646226A1 (en) Access control manager configuration based on log files mining
US20210352077A1 (en) Low trust privileged access management
CN102307114A (en) Management method of network
CN110474901B (en) Public block chain network system
Xu et al. Microchain: A light hierarchical consensus protocol for iot systems
JP7192196B2 (en) Network transaction verification method and system based on multiple nodes, and storage medium
CN109617929B (en) Node and user interactive authentication method and system in block chain network mode
CN113162950A (en) Mobile application secondary authority authentication and management system based on i country network
CN114930773A (en) Dormant account identifier
CN117851160A (en) Log recording system and method for business data stream change process
KR100542383B1 (en) System for controlling database access based on 3-Tier structure and Method thereof
CN110572279A (en) Security management system for privileged account
Al-Lawati et al. The impact of cloud computing IT departments: A case study of Oman's financial institutions
CN115426175A (en) Instance incubation system and method based on user isolation
Wadhwa et al. Empirical analysis on consensus algorithms of blockchain
CN108304731A (en) A kind of method, system and information processing platform that management business data calls
CN112395591A (en) Encryption method and system
CN114547704B (en) Data processing method and device based on distributed account book

Legal Events

Date Code Title Description
PB01 Publication
SE01 Entry into force of request for substantive examination