CN113742295B - Service data management method and device and document tag management method and device - Google Patents
Service data management method and device and document tag management method and device Download PDFInfo
- Publication number
- CN113742295B CN113742295B CN202111055543.XA CN202111055543A CN113742295B CN 113742295 B CN113742295 B CN 113742295B CN 202111055543 A CN202111055543 A CN 202111055543A CN 113742295 B CN113742295 B CN 113742295B
- Authority
- CN
- China
- Prior art keywords
- service
- service data
- additional information
- document
- information
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 106
- 238000007726 management method Methods 0.000 title claims description 26
- 238000013523 data management Methods 0.000 title claims description 9
- 238000012545 processing Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 9
- 238000012163 sequencing technique Methods 0.000 claims description 6
- 238000002372 labelling Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 238000012550 audit Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 2
- 108010093488 His-His-His-His-His-His Proteins 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/168—Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Bioethics (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Document Processing Apparatus (AREA)
Abstract
The invention provides a method and a device for managing service data, and a method and a device for managing document labels, wherein the method for managing the service data comprises the following steps: acquiring service data and additional information of the service data; generating an identification of the service data based on the additional information; and synchronously displaying the identifiers when the service data is displayed, so that the identifiers are synchronously displayed when the service data is displayed, and the efficiency of checking the identifiers of the service data is improved.
Description
Technical Field
The present invention relates to the field of information processing technologies, and in particular, to a method and an apparatus for managing service data, a method and an apparatus for managing document tags, an electronic device, and a storage medium.
Background
Currently, in a related application scene of a document, when a secret document file containing a secret mark is stored in a cloud, if the secret document needs to be opened through a client, related attribute information of the secret document needs to be checked in a designated dialog box. Or when the document is in the process of approval circulation, the relevant information needs to be checked at a designated position to know the approval result. In these application scenarios, custom single document tags are typically manually entered in corresponding documents according to specific requirements.
The defects or shortcomings of the single document labels in the application scenes include that the user-defined single document labels are manually input into corresponding documents according to specific requirements in each application scene, and the problem of low document state viewing efficiency exists.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a business data management method and device, a document label management method and device, electronic equipment and storage medium.
The invention provides a business data management method, which comprises the following steps:
acquiring service data and additional information of the service data;
Generating an identification of the service data based on the additional information;
And synchronously displaying the identification when the service data is displayed.
According to the method for managing service data provided by the invention, before the service data and the additional information of the service data are acquired, the method further comprises the following steps:
Determining a service node where the service data is currently located, wherein the service node is a node in a preset service flow;
And in the service node where the service node is currently located, taking the service information of the service node aiming at the service data as the additional information of the service data.
According to the method for managing service data provided by the invention, in the currently located service nodes, service information of the currently located service nodes aiming at the service data is used as additional information of the service data, and the method comprises the following steps:
and in the service node where the service node is currently located, taking the first service information representing the service node where the service node is currently located as the additional information of the service data.
According to the method for managing service data provided by the invention, in the service node where the service node is currently located, first service information representing the service node where the service node is currently located is used as additional information of the service data, and the method comprises the following steps:
Acquiring first service information representing the service node where the service node is currently located;
Judging whether the service data has additional information conforming to a first condition, wherein the additional information conforming to the first condition is service information representing a first node, and the first node is a service node belonging to the same service flow as the service node in which the first node is currently located;
And when the additional information meeting the first condition exists in the service data, replacing the additional information meeting the first condition by using the first service information.
According to the method for managing service data provided by the invention, in the currently located service nodes, service information of the currently located service nodes aiming at the service data is used as additional information of the service data, and the method further comprises the following steps:
And in the service node where the service node is currently located, taking second service information generated by the service node where the service node is currently located operating the service data as additional information of the service data.
According to the method for managing service data provided by the present invention, in the currently located service node, second service information generated by the operation of the currently located service node on the service data is used as additional information of the service data, and the method comprises the following steps:
determining the operation of the service node currently located on the service data as a first operation, and recording second service information generated by the first operation;
Judging whether the service data has additional information conforming to a second condition, wherein the additional information conforming to the second condition is service information generated by any service node executing a second operation on the service data, and the second operation and the first operation are preset operations of the same type;
And when the additional information meeting the second condition exists in the service data, replacing the additional information meeting the second condition by using the second service information.
According to the method for managing service data provided by the invention, the generating the identifier of the service data based on the additional information comprises the following steps:
And taking the additional information as the identification of the service data.
According to the method for managing service data provided by the invention, the generating the identifier of the service data based on the additional information comprises the following steps:
Determining a category of the additional information;
and selecting one piece of additional information from the additional information belonging to the same category as the identification of the service data.
According to the method for managing service data provided by the invention, after determining the category of the additional information, the method further comprises the following steps:
determining a plurality of additional information belonging to the same category;
Sorting the plurality of additional information according to the time sequence of adding the plurality of additional information to the same category;
and generating a service processing flow chart of the service data based on the sequencing result.
The invention provides a management method of a document tag, which is used for a cloud server and comprises the following steps:
Acquiring a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server;
generating a document tag of the target document based on the target attribute information;
and synchronously displaying the document labels when the target document is displayed.
The invention provides a service data management device, which comprises:
the first acquisition module is used for acquiring service data and additional information of the service data;
the first generation module is used for generating the identification of the service data based on the additional information;
And the first display module is used for synchronously displaying the identification when the service data are displayed.
The invention provides a document label management device, which comprises:
The second acquisition module is used for acquiring a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server;
the second generation module is used for generating a document tag of the target document based on the target attribute information;
And the second display module is used for synchronously displaying the document labels when the target document is displayed.
The invention also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and running on the processor, wherein the processor executes the program to realize the steps of the method for managing business data or the method for managing document labels.
The present invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method of managing business data or the method of managing document tags as described in any one of the above.
The method and the device for managing the service data acquire the service data and the additional information of the service data; based on the additional information, the identification of the service data is generated, so that the identification is synchronously displayed when the service data is displayed, and the efficiency of checking the identification of the service data is improved.
According to the method and the device for managing the document tag, the document tag of the target document is automatically generated by acquiring and analyzing the target attribute information, and the automatically generated document tag is displayed, so that the state of the target document can be checked on the premise that the target document is not opened, and the efficiency of checking the state of the document is improved.
Drawings
In order to more clearly illustrate the invention or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of a method for managing service data according to an embodiment of the present invention;
FIG. 2 is a second flow chart of a method for managing service data according to an embodiment of the present invention;
FIG. 3 is a third flow chart of a method for managing service data according to an embodiment of the present invention;
FIG. 4 is a schematic flow chart of a document tag management method according to an embodiment of the present invention;
FIG. 5 is a second flowchart of a document tag management method according to an embodiment of the present invention;
FIG. 6 is a third flowchart of a method for managing document tags according to an embodiment of the present invention;
FIG. 7 is an exemplary diagram of generating a status tag in a method for managing document tags provided by an embodiment of the present invention;
FIG. 8 is an exemplary diagram of generating approval tags in a method for managing document tags provided by an embodiment of the present invention;
FIG. 9 is a schematic diagram of generating a security label in the document label management method according to the embodiment of the present invention;
FIG. 10 is a schematic diagram showing status tags and approval tags in a document tag management method according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a service data management device according to an embodiment of the present invention;
FIG. 12 is a schematic diagram of a document tag management apparatus according to an embodiment of the present invention;
Fig. 13 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, 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.
The figures are merely examples and are not drawn to scale. As used herein, the term "preferred" and similar terms are used as a table approximation, not as a table degree, and are intended to illustrate inherent deviations in measured or calculated values that would be recognized by one of ordinary skill in the art. It should be noted that in this specification, the expressions "first", "second", "third", etc. are used only to distinguish one feature from another feature, and do not denote any limitation of the features, particularly do not denote any order of precedence.
It will be further understood that terms such as "comprises," "comprising," "includes," "including," and/or "having," are intended to be inclusive and not to open ended as defined in the specification, and to exclude the presence of other features, elements, components, and/or groups thereof. Furthermore, when describing embodiments of the application, use of "may" means "one or more embodiments of the application. Also, the term "exemplary" is intended to refer to an example or illustration.
Unless otherwise defined, all terms (including engineering and technical terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present application pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
In order to solve the problems in the prior art, embodiments of the present invention provide a method and an apparatus for managing service data, a method and an apparatus for managing document tags, an electronic device, and a storage medium.
First, terms related to one or more embodiments of the present invention will be explained.
The mark density refers to identifying the target density.
Secret determination refers to determining a secret level based on the relevant secret terms or secret identification.
The embodiment of the invention provides a service data management method, referring to fig. 1, comprising the following steps 101 to 103:
And 101, acquiring service data and additional information of the service data.
Wherein, the service data is the data generated in the process of processing the service. The business has corresponding business processes, which include a plurality of business nodes, such as processing documents, including document encryption processes, document approval processes, and the like.
Correspondingly, before step 101, the method further comprises: and determining the service node where the service data is currently located, and taking the service information of the service node aiming at the service data as the additional information of the service data.
Wherein the service information may include a plurality of kinds, for example, information including service nodes, such as service node names; as another example, traffic information, such as a level of confidentiality, approval results, etc., generated by performing a traffic operation in a traffic node.
Through step 101, the service data and the additional information thereof can be obtained, so that the additional information can be processed in the subsequent step, and the service data can be managed.
Step 102, generating the identification of the service data based on the additional information.
Specifically, in one specific application scenario, step 102 includes: and taking the additional information as the identification of the service data.
For example, the generated additional information is information of a secret scale, and the secret scale can be directly used as an identifier of the service data and displayed below, on the side of or in other designated areas of the service data; or when the mouse pointer is moved to the area of the service data, the identification of the service data is popped up.
For another example, the object associated with the additional information is used as an identifier of the service data. The object may be a plurality of multimedia data, such as icons, text, etc., associated with additional information.
In another specific application, step 102 includes: determining a category of the additional information; and selecting one piece of additional information from the additional information belonging to the same category as the identification of the service data.
It should be noted that, the type of the additional information may be first service information indicating different service nodes in the same service flow, or may be second service information generated by executing the same type of service operation in the service nodes.
In addition, the selection manner of selecting an additional information from the additional information belonging to the same category may include various selection manners, for example, the selection manner may be based on the sequence of service nodes, and the additional information associated with the last service node is selected from the additional information of the same category as the identifier of the service data;
The additional information related to the last operation logic can be selected from the additional information of the same category as the identification of the service data according to the logic sequence of the operation;
The time sequence of the operation can also be that the additional information associated with the last operation time is selected from the additional information of the same category as the identification of the service data.
And step 103, synchronously displaying the identification when the service data are displayed.
Specifically, the manner of display may include a variety of:
For example, synchronous display is performed in the surrounding area of the service data, for example, the lower side, the right side and the like of the service data;
the synchronous display can also be performed for the designated association area of the service data, for example, other areas located in the same line with the service data.
The display of the mark can also be performed in the form of a pop-up box for a secondary display box corresponding to the service data under the condition of selecting the service data.
Through step 103, synchronous display of the identification and the service data is realized.
The business data management method provided by the embodiment of the invention acquires the business data and the additional information of the business data; based on the additional information, the identification of the service data is generated, so that the identification is synchronously displayed when the service data is displayed, and the efficiency of checking the identification of the service data is improved. Further, the additional information is service information of the service node where the service data is currently located for the service data, and the service data is synchronously displayed with an identifier generated according to the additional information, so that information related to the service data can be quickly obtained through the identifier, for example, node information of the service node where the service data is located can be quickly obtained, and service operations executed by the service node can be also obtained.
Further, before step 101, referring to fig. 2, the method further includes:
step 201, determining a service node where the service data is currently located.
Wherein, each business corresponds to a preset business flow, and different business flows can mutually jump. Each business process comprises at least one business node, and the current business node is a node in the preset business process.
For example, for a document's encryption-decryption-issuance business, it includes three business processes: a labeling process, a secret setting process and a issuing process. Different business processes can jump according to the actual demands of the business.
For different service nodes, the service information corresponding to the service data is also different. Therefore, the current service node where the service data is located needs to be determined first.
Step 202, in the service node where the service node is currently located, service information of the service node aiming at the service data is used as additional information of the service data.
In particular, the service information includes two kinds, one kind of service information representing information of a service node, such as a name of the service node. Correspondingly, the execution method comprises the following steps: and in the service node where the service node is currently located, taking the first service information representing the service node where the service node is currently located as the additional information of the service data.
Another type of service information is service information generated by performing a service operation in a service node, such as a level of encryption. Correspondingly, the execution method comprises the following steps: and in the service node where the service node is currently located, taking second service information generated by the service node where the service node is currently located operating the service data as additional information of the service data.
In an embodiment, for the first service information, the step 202 includes:
Step 221, obtaining first service information representing the service node currently located.
Wherein the first service information may include a plurality of kinds. For example, nodes such as a label, a secret, a sign, a change state and the like in a document label flow, and business nodes such as a submitting audit, a cancelling application, a passing approval, a rejecting approval and the like in a document approval flow. Further, information of the node, such as a name of the node, may be used as the first service information.
Step 222, judging whether the service data has additional information meeting the first condition.
The additional information meeting the first condition is service information representing a first node, and the first node is a service node belonging to the same service flow as the service node where the first node is currently located.
Step 223, when the service data has additional information meeting the first condition, replacing the additional information meeting the first condition with the first service information.
For example, the current traffic includes traffic nodes A, B and C, the current traffic node being node B. If the service data exists in the service information of the first node a, the service information of the first node B should be used instead of the service information of the node a.
The updating of the first service information of the current service node is achieved by steps 221-223.
Of course, in yet another embodiment, the service data may be associated with a plurality of additional information, and the plurality of additional information may be service information respectively belonging to a plurality of nodes of the same service flow. Further, the plurality of additional information may be ordered according to a time order in which the association with the service data is established.
In an embodiment, for the second service information, the step 202 includes:
Step 224, determining the operation of the service node currently located on the service data as a first operation, and recording second service information generated by the first operation.
Specifically, the second service information is service information generated by operating service data in the service node, for example, a document security level used in the document encryption in the encryption node, an audit label used in the audit node for auditing the document, and the like.
Step 225, judging whether the service data has additional information meeting a second condition.
The additional information meeting the second condition is service information generated by any service node executing a second operation on the service data, wherein the second operation and the first operation are the same type of preset operation.
And step 226, when the additional information meeting the second condition exists in the service data, replacing the additional information meeting the second condition by using the second service information.
For example, the additional information is service information generated by any service node performing the same type of operation D, E, F on the service data. If the operation of the service node currently located on the service data is a first operation E, recording second service information generated by the first operation E; and the additional information meeting the second condition is the service information generated by any service node executing the second operation D on the service data, the service information generated by the first operation E should be used to replace the service information generated by the second operation D.
The update of the second service information of the current service node is achieved through steps 224-226.
Of course, in yet another embodiment, the service data may be associated with a plurality of additional information, and the plurality of additional information may be service information generated by performing a plurality of operations of the same type on the service data, respectively. Further, the plurality of additional information may be ordered according to a time order in which the association with the service data is established.
Further, referring to fig. 3, a plurality of additional information may be associated with the service data, and the plurality of additional information may be service information respectively belonging to a plurality of nodes of the same service flow; or may be associated with a plurality of additional information for the service data, where the plurality of additional information may be service information generated by performing a plurality of operations of the same type on the service data, respectively, and in this embodiment, after determining the category of the additional information, the method further includes:
step 301, determining a plurality of pieces of additional information belonging to the same category.
Step 302, sorting the plurality of additional information according to the time sequence of adding the plurality of additional information to the same category.
Step 303, generating a service processing flow chart of the service data based on the sequencing result.
The service processing flow chart can display the information of the service nodes through which the service data passes, the executed service operations and the like.
Through steps 301 to 303, a service processing flow chart of the service data can be further displayed, so that the service processing flow of the service data can be conveniently and intuitively checked.
The embodiment of the invention also discloses a method for managing the document labels, which is used for the cloud server and comprises the following steps:
step 401, obtaining a target document and target attribute information of the target document.
Wherein the target document includes: and the target document and/or the document created in the cloud server are/is sent by the client.
For example, the generated target attribute information is information of a document approval result, and the approval result can be directly used as the identification of the target document and displayed below, on the side of or in other designated areas of the target document; or pop up the identity of the target document when the mouse pointer is moved to the region of the target document.
Step 402, generating a document tag of the target document based on the target attribute information.
Specifically, in one specific application scenario, step 402 includes: and taking the target attribute information as a document tag of the target document.
The document label can be in the format of pictures, characters and the like.
Specifically, in another specific application scenario, step 402 includes: determining the category of the target attribute information; and selecting target attribute information from target attribute information belonging to the same category as a document tag of the target document.
It should be noted that, the category of the target attribute information may be first attribute information indicating different service nodes in the same service flow, or may be second attribute information generated by executing the same type of service operation in the service nodes.
The selection manner of selecting the target attribute information from the target attribute information belonging to the same category may include various selection manners, and reference is made to the foregoing embodiment, and the selection manner of selecting the additional information from the additional information belonging to the same category is not listed here.
Step 403, synchronously displaying the document tag when the target document is displayed.
Specifically, the display modes of the document tag may include various modes:
for example, synchronous display is performed in a surrounding area of the target document, such as the lower side, the right side, etc. of the target document;
The synchronous display can also be performed in a designated association area of the target document, for example, other areas which are positioned in the same line as the target document.
And a secondary display frame corresponding to the target document can be also used for displaying the document label in the form of a pop-up frame under the condition that the target document is selected.
According to the document tag management method provided by the embodiment of the invention, the document tag of the target document is automatically generated by acquiring and analyzing the target attribute information, and the automatically generated document tag is displayed, so that the state of the target document can be checked on the premise that the target document is not opened, and the efficiency of checking the state of the document is improved.
Specifically, before step 401, referring to fig. 5, the method further includes:
step 501, determining a service node where the target document is currently located, where the service node is a node in a preset service flow.
For example, for a document's encryption-decryption-issuance business, it includes three business processes: a labeling process, a secret setting process and a issuing process. Different business processes can jump according to the actual demands of the business.
For different service nodes, the service information corresponding to the service data is also different. Therefore, the current service node where the service data is located needs to be determined first.
Step 502, in the service node where the service node is currently located, the attribute information of the service node aiming at the target document is used as the target attribute information of the target document.
Specifically, the attribute information of the target document includes two kinds:
The attribute information represents information of the service node, such as a name of the service node. Correspondingly, the execution method comprises the following steps: and in the service node where the current service node is located, taking the first attribute information representing the current service node as the target attribute information of the target document.
Another attribute information is service information generated by performing a service operation in the service node, such as a level of confidentiality. Correspondingly, the execution method comprises the following steps: and in the service node where the service node is currently located, second attribute information which is generated by the service node where the service node is currently located by operating the target document is used as target attribute information of the service data.
Specifically, for attribute information of a first type of target document, the method includes:
step 521, obtaining first attribute information representing the service node where the service node is currently located.
The first attribute information may include various kinds of business information, such as encryption, issuing, status change, etc. in the document encryption process, and business information, such as submission and verification, cancellation of application, approval passing, approval refusal, etc. in the document approval process.
Step 522, determining whether the target document has target attribute information meeting the first condition.
The target attribute information meeting the first condition is attribute information representing a first node, and the first node is a service node belonging to the same service flow as the service node where the first node is currently located.
Step 523, when the target document has target attribute information conforming to a first condition, replacing the target attribute information conforming to the first condition by using the first attribute information.
Through steps 521-523, the updating of the first attribute information of the target document of the current service node is realized.
Specifically, for attribute information of the second target document, the method includes:
Step 524, determining the operation of the service node currently located on the target document as a first operation, and recording second attribute information generated by the first operation.
And 525, judging whether the target document has target attribute information meeting a second condition.
The target attribute information meeting the second condition is attribute information generated by any service node executing a second operation on the target document, wherein the second operation and the first operation are the same type of preset operation.
And 526, replacing the additional information meeting the second condition by using the second attribute information when the additional information meeting the second condition exists in the service data.
The updating of the second attribute information of the target document of the current service node is achieved through steps 524-526.
Optionally, after the determining the category of the target attribute information, referring to fig. 6, the method further includes:
step 601, determining a plurality of target attribute information belonging to the same category.
Step 602, sorting the plurality of target attribute information according to the time sequence of adding the plurality of target attribute information to the same category.
And 603, generating a business processing flow chart of the target document based on the sequencing result.
The service processing flow chart can display the information of the service nodes through which the service data passes, the executed service operations and the like.
The security attribute information is information that abstractly describes the security of the current document.
Through steps 601-603, a business processing flow chart of business data can be further displayed, so that the business processing flow of the target document can be conveniently and intuitively checked.
Referring to fig. 7, fig. 7 is an exemplary diagram of generating a status tag in a document tag management method according to an embodiment of the present invention. As shown in fig. 7, generating a status tag includes:
In step 701, a target document is acquired.
Step 702, judging whether the target document contains the attribute information of the security level; if yes, go to step 704, if no, go to step 703.
Step 703, no label is displayed.
Step 704, judging whether the target document is in a confidential state; if yes, go to step 705, if no, go to step 706.
Step 705, the document tag displays "label".
In this example, generating a document tag of a target document based on target attribute information includes: and taking the target attribute information as a document tag of the target document.
In this example, the document label is the name of a node such as a label, a sign, a change state and the like in the document label process.
The generation method of the attribute information of the target document may refer to the following procedure:
Determining a service node where the target document is currently located, wherein the service node is a node in a preset service flow;
and in the service node where the service node is currently located, taking the service information of the service node aiming at the service data as the attribute information of the target document.
Step 706, judging whether the target document is in a fixed-density state; if yes, go to step 707, if no, go to step 708.
Step 707, the document tag displays "secret".
Step 708, judging whether the target document is in a signed state; if yes, go to step 709, if no, go to step 710.
In step 709, the document tag displays "issue".
Step 710, judging whether the target document is in a changed state; if yes, go to step 711, if no, end.
Step 711, the document tag displays "change".
Based on the above embodiments, by generating and displaying the document tag of the target document based on the target attribute information, the object of viewing the attribute information of the target document without opening the target document is achieved.
Based on the above embodiments, fig. 8 is an exemplary diagram of generating approval tags in a document tag management method according to an embodiment of the present invention. As shown in fig. 8, generating an approval tag includes:
In step 801, a target document is acquired.
Step 802, judging whether the target document is submitted for auditing; if yes, go to step 804, if not, go to step 803.
Step 803, no label is displayed.
Step 804, judging whether the target document is cancelled to submit for auditing; if yes, go to step 805, if no, go to step 806.
In step 805, the document tag displays "cancel application".
In this example, the document label is the name of a node such as submitting and checking, canceling an application, passing an approval, rejecting an approval, and the like in the document approval process.
Step 806, judging whether the target document passes the examination; if yes, go to step 807, if no, go to step 808.
The document tag displays "audit passed" step 807.
In step 808, the document tag displays "approval reject".
Based on the above embodiment, the aim of checking the approval attribute of the target document on the premise of not opening the target document is achieved by generating and displaying the approval label of the target document based on the target attribute information.
For example, based on the above embodiments, an example of generating a security label may be described in connection with a specific application scenario.
Based on the above embodiments, fig. 9 is a schematic diagram of generating a security label in a document label management method according to an embodiment of the present invention.
For example, as shown in fig. 9, if the current status tag of the target document displayed at the front end of the cloud server is a secret; meanwhile, the security attribute information loaded into the target document includes a document name AAAAAA, a company name BBBBBB, a drafting person ccccc, a drafting time DDDDDD, a security type EEEEEE, an awareness range FFFFFF, and an awareness description HHHHHH. And under the condition that the secret foundation and the decryption condition are not considered specifically, the secret attribute information loaded into the target document is analyzed, so that the secret label of the target document, specifically, the core secret or the common secret, can be generated, and the corresponding display is carried out at the secret label corresponding to the secret in fig. 9.
For example, based on the above embodiment, the display situations of the status tag and the approval tag may be correspondingly described in connection with a specific application scenario.
Based on the above embodiments, fig. 10 is a schematic display diagram of status tags and approval tags in a document tag management method according to an embodiment of the present invention.
For example, as shown in fig. 10, if the document name is ABC, the document state is a fixed-density state, the applicant is mm, the application type is a fixed-density application, and the document with the application time XX-YY-ZZ is a target document; the document label management method provided by the invention is applied to process the target document, and the document label which is approved and approved can be generated and displayed in the document label area corresponding to the target document.
If the document name is QQQ, the document state is the issuing state, the application is nn, the application type is a security change application, and the document with the application time of UU-VV-WW is a target document; the document label management method provided by the invention is applied to process the target document, and can generate and display the document label corresponding to the target document, issue and approve the rejected document label.
If the document name is KJY, the document state is a fixed-density state, the application person is ll, the application type is a security level change application, and the document with the application time of RR-SS-TT is a target document; the document label management method provided by the invention is applied to process the target document, and the document label which is refused by approval and approval can be generated and displayed in the document label area corresponding to the target document.
Based on the above embodiments, fig. 11 is a management apparatus for service data provided according to an embodiment of the present invention, including:
a first obtaining module 1110, configured to obtain service data and additional information of the service data;
A first generating module 1120, configured to generate an identifier of the service data based on the additional information;
and the first display module 1130 is configured to synchronously display the identifier when the service data is displayed.
Optionally, the apparatus further comprises:
the first service node determining module is used for determining a service node where the service data are currently located, wherein the service node is a node in a preset service flow;
and the first additional information determining module is used for taking the service information of the current service node aiming at the service data as the additional information of the service data in the current service node.
Optionally, the additional information determining module is specifically configured to: and in the service node where the service node is currently located, taking the first service information representing the service node where the service node is currently located as the additional information of the service data.
Optionally, the additional information determining module is specifically configured to:
Acquiring first service information representing the service node where the service node is currently located;
Judging whether the service data has additional information conforming to a first condition, wherein the additional information conforming to the first condition is service information representing a first node, and the first node is a service node belonging to the same service flow as the service node in which the first node is currently located;
And when the additional information meeting the first condition exists in the service data, replacing the additional information meeting the first condition by using the first service information.
Optionally, the additional information determining module is specifically configured to: and in the service node where the service node is currently located, taking second service information generated by the service node where the service node is currently located operating the service data as additional information of the service data.
Optionally, the additional information determining module is specifically configured to:
determining the operation of the service node currently located on the service data as a first operation, and recording second service information generated by the first operation;
Judging whether the service data has additional information conforming to a second condition, wherein the additional information conforming to the second condition is service information generated by any service node executing a second operation on the service data, and the second operation and the first operation are preset operations of the same type;
And when the additional information meeting the second condition exists in the service data, replacing the additional information meeting the second condition by using the second service information.
Optionally, the first generating module 1120 is specifically configured to: and taking the additional information as the identification of the service data.
Optionally, the first generating module 1120 is specifically configured to: determining a category of the additional information; and selecting one piece of additional information from the additional information belonging to the same category as the identification of the service data.
Optionally, the device further comprises a business process processing module, configured to:
determining a plurality of additional information belonging to the same category;
Sorting the plurality of additional information according to the time sequence of adding the plurality of additional information to the same category;
and generating a service processing flow chart of the service data based on the sequencing result.
The management device of the service data provided by the embodiment of the invention acquires the service data and the additional information of the service data; based on the additional information, the identification of the service data is generated, so that the identification is synchronously displayed when the service data is displayed, and the efficiency of checking the identification of the service data is improved.
The embodiment of the invention discloses a document tag management device, which is shown in FIG. 12 and comprises:
a second obtaining module 1210, configured to obtain a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server;
A second generating module 1220, configured to generate a document tag of the target document based on the target attribute information;
And a second display module 1230 for synchronously displaying the document tag when the target document is displayed.
Optionally, the apparatus further comprises:
the second service node determining module is used for determining a service node where the target document is currently located, wherein the service node is a node in a preset service flow;
And the target attribute information determining module is used for taking the attribute information of the service node which is currently located aiming at the target document as the target attribute information of the target document in the service node which is currently located.
Optionally, the target attribute information determining module is specifically configured to: and in the service node where the current service node is located, taking the first attribute information representing the current service node as the target attribute information of the target document.
Optionally, the target attribute information determining module is specifically configured to:
Acquiring first attribute information representing the current service node;
Judging whether the target document has target attribute information meeting a first condition, wherein the target attribute information meeting the first condition is attribute information representing a first node, and the first node is a service node belonging to the same service flow as the service node where the first node is currently located;
and when the target document has the target attribute information meeting the first condition, replacing the target attribute information meeting the first condition by using the first attribute information.
Optionally, the target attribute information determining module is specifically configured to: and in the service node where the service node is currently located, second attribute information which is generated by the service node where the service node is currently located by operating the target document is used as target attribute information of the service data.
Optionally, the target attribute information determining module is specifically configured to:
determining the operation of the current service node on the target document as a first operation, and recording second attribute information generated by the first operation;
Judging whether the target document has target attribute information meeting a second condition, wherein the target attribute information meeting the second condition is attribute information generated by any service node executing a second operation on the target document, and the second operation and the first operation are preset operations of the same type;
And when the additional information meeting the second condition exists in the service data, replacing the additional information meeting the second condition by using the second attribute information.
Optionally, the second generating module 1220 is specifically configured to: and taking the target attribute information as a document tag of the target document.
Optionally, the second generating module 1220 is specifically configured to: determining the category of the target attribute information; and selecting target attribute information from target attribute information belonging to the same category as a document tag of the target document.
Optionally, the device further comprises a business process processing module, configured to:
determining a plurality of target attribute information belonging to the same category;
Sorting the plurality of target attribute information according to the time sequence of adding the plurality of target attribute information to the same category;
And generating a business processing flow chart of the target document based on the sequencing result.
According to the document tag management device provided by the embodiment of the invention, the document tag of the target document is automatically generated by acquiring and analyzing the target attribute information, and the automatically generated document tag is displayed, so that the state of the target document can be checked on the premise that the target document is not opened, and the efficiency of checking the state of the document is improved.
Fig. 13 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention. As shown in fig. 13, the electronic device may include: processor 1310, communication interface Communications Interface 1320, memory 1330 and communication bus 1340, wherein processor 1310, communication interface 1320, memory 1330 communicate with each other via communication bus 1340. Processor 1310 may invoke logic instructions in memory 1330 to perform a method of managing traffic data, including: acquiring service data and additional information of the service data; generating an identification of the service data based on the additional information; and synchronously displaying the identification when the service data is displayed.
Or executing a document tag management method for a cloud server, wherein the method comprises the following steps:
Acquiring a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server; generating a document tag of the target document based on the target attribute information; and synchronously displaying the document labels when the target document is displayed.
Further, the logic instructions in the memory 1330 can be implemented in the form of software functional units and can be stored in a computer readable storage medium when sold or used as a stand alone product. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In another aspect, the present invention also provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform a method of managing business data provided by the above methods, comprising: acquiring service data and additional information of the service data; generating an identification of the service data based on the additional information; and synchronously displaying the identification when the service data is displayed.
Or executing a document tag management method for a cloud server, wherein the method comprises the following steps:
Acquiring a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server; generating a document tag of the target document based on the target attribute information; and synchronously displaying the document labels when the target document is displayed.
In yet another aspect, the present invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, is implemented to perform a method of managing business data, comprising: acquiring service data and additional information of the service data; generating an identification of the service data based on the additional information; and synchronously displaying the identification when the service data is displayed.
Or executing a document tag management method for a cloud server, wherein the method comprises the following steps:
Acquiring a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server; generating a document tag of the target document based on the target attribute information; and synchronously displaying the document labels when the target document is displayed.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (12)
1. A method for managing service data, comprising:
acquiring service data and additional information of the service data;
Generating an identification of the service data based on the additional information;
Synchronously displaying the identification when the service data is displayed;
the generating the identification of the service data based on the additional information includes:
Determining a category of the additional information in the case that the service data is associated with a plurality of additional information belonging to the same category; the type of the additional information is first service information representing different service nodes in the same service flow or second service information generated by executing the same type of service operation in the service nodes; the plurality of additional information belonging to the same category is service information of a plurality of service nodes respectively belonging to the same service flow, or the plurality of additional information belonging to the same category is service information generated by respectively executing a plurality of same type operations on service data; the plurality of additional information belonging to the same category are sequenced according to the time of establishing association with the service data;
Selecting an additional information from the additional information belonging to the same category as the identification of the service data;
The selection mode for selecting one piece of additional information from the additional information belonging to the same category comprises a sequence based on the service node, a logic sequence based on operation or a time sequence based on operation.
2. The method of claim 1, further comprising, prior to said obtaining the service data and the additional information of the service data:
Determining a service node where the service data is currently located, wherein the service node is a node in a preset service flow, and the preset service flow at least comprises one of the following steps: a labeling process, a secret setting process, a issuing process and a document approval process;
And in the service node where the service node is currently located, taking the service information of the service node aiming at the service data as the additional information of the service data.
3. The method according to claim 2, wherein said regarding, among the service nodes currently located, service information of the service node currently located for the service data as additional information of the service data includes:
and in the service node where the service node is currently located, taking the first service information representing the service node where the service node is currently located as the additional information of the service data.
4. A method according to claim 3, wherein said providing, in said service node at which said service node is currently located, first service information representing said service node at which said service node is currently located as additional information of said service data comprises:
Acquiring first service information representing the service node where the service node is currently located;
Judging whether the service data has additional information conforming to a first condition, wherein the additional information conforming to the first condition is service information representing a first node, and the first node is a service node belonging to the same service flow as the service node in which the first node is currently located;
And when the additional information meeting the first condition exists in the service data, replacing the additional information meeting the first condition by using the first service information.
5. The method according to claim 2, wherein, in the service node where the service node is currently located, service information of the service node for the service data is used as additional information of the service data, and further comprising:
And in the service node where the service node is currently located, taking second service information generated by the service node where the service node is currently located operating the service data as additional information of the service data.
6. The method according to claim 5, wherein said second service information generated by said service node currently located operating said service data in said service node currently located is used as additional information of said service data, comprising:
determining the operation of the service node currently located on the service data as a first operation, and recording second service information generated by the first operation;
Judging whether the service data has additional information conforming to a second condition, wherein the additional information conforming to the second condition is service information generated by any service node executing a second operation on the service data, and the second operation and the first operation are preset operations of the same type;
And when the additional information meeting the second condition exists in the service data, replacing the additional information meeting the second condition by using the second service information.
7. The method of claim 1, further comprising, after said determining the category of the additional information:
determining a plurality of additional information belonging to the same category;
Sorting the plurality of additional information according to the time sequence of adding the plurality of additional information to the same category;
and generating a service processing flow chart of the service data based on the sequencing result.
8. A method for managing document tags, the method being used for a cloud server, the method comprising:
Acquiring a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server;
generating a document tag of the target document based on the target attribute information;
synchronously displaying the document tags when the target document is displayed;
the generating the document tag of the target document based on the target attribute information includes:
Determining the category of the target attribute information under the condition that the service data are associated with a plurality of target attribute information belonging to the same category; the category of the target attribute information is first attribute information representing different service nodes in the same service flow or second attribute information generated by executing the same type of service operation in the service nodes; the plurality of target attribute information belonging to the same category are attribute information of a plurality of service nodes respectively belonging to the same service flow, or the plurality of target attribute information belonging to the same category are attribute information generated by respectively executing a plurality of same type operations on service data; the target attribute information belonging to the same category is sequenced according to the time of establishing association with the service data;
Selecting target attribute information from target attribute information belonging to the same category as a document tag of the target document;
The selection mode for selecting the target attribute information from the target attribute information belonging to the same category comprises a sequence based on the service node, a logic sequence based on operation or a time sequence based on operation.
9. A service data management apparatus, comprising:
the first acquisition module is used for acquiring service data and additional information of the service data;
the first generation module is used for generating the identification of the service data based on the additional information;
The first display module is used for synchronously displaying the identifiers when the service data are displayed;
The first generation module is specifically configured to:
Determining a category of the additional information in the case that the service data is associated with a plurality of additional information belonging to the same category; the type of the additional information is first service information representing different service nodes in the same service flow or second service information generated by executing the same type of service operation in the service nodes; the plurality of additional information belonging to the same category is service information of a plurality of service nodes respectively belonging to the same service flow, or the plurality of additional information belonging to the same category is service information generated by respectively executing a plurality of same type operations on service data; the plurality of additional information belonging to the same category are sequenced according to the time of establishing association with the service data;
Selecting an additional information from the additional information belonging to the same category as the identification of the service data;
The selection mode for selecting one piece of additional information from the additional information belonging to the same category comprises a sequence based on the service node, a logic sequence based on operation or a time sequence based on operation.
10. A document tag management apparatus, comprising:
The second acquisition module is used for acquiring a target document and target attribute information of the target document; wherein the target document includes: the target document sent by the client and/or the target document created in the cloud server;
the second generation module is used for generating a document tag of the target document based on the target attribute information;
The second display module is used for synchronously displaying the document labels when the target document is displayed;
the second generating module is specifically configured to:
Determining the category of the target attribute information under the condition that the service data are associated with a plurality of target attribute information belonging to the same category; the category of the target attribute information is first attribute information representing different service nodes in the same service flow or second attribute information generated by executing the same type of service operation in the service nodes; the plurality of target attribute information belonging to the same category are attribute information of a plurality of service nodes respectively belonging to the same service flow, or the plurality of target attribute information belonging to the same category are attribute information generated by respectively executing a plurality of same type operations on service data; the target attribute information belonging to the same category is sequenced according to the time of establishing association with the service data;
Selecting target attribute information from target attribute information belonging to the same category as a document tag of the target document;
The selection mode for selecting the target attribute information from the target attribute information belonging to the same category comprises a sequence based on the service node, a logic sequence based on operation or a time sequence based on operation.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of managing business data according to any one of claims 1 to 7 or the method of managing document tags according to claim 8 when the program is executed by the processor.
12. A non-transitory computer readable storage medium having stored thereon a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method of managing business data according to any one of claims 1 to 7 or the method of managing document tags according to claim 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111055543.XA CN113742295B (en) | 2021-09-09 | 2021-09-09 | Service data management method and device and document tag management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111055543.XA CN113742295B (en) | 2021-09-09 | 2021-09-09 | Service data management method and device and document tag management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113742295A CN113742295A (en) | 2021-12-03 |
| CN113742295B true CN113742295B (en) | 2024-06-21 |
Family
ID=78737567
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111055543.XA Active CN113742295B (en) | 2021-09-09 | 2021-09-09 | Service data management method and device and document tag management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113742295B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112632947A (en) * | 2020-12-25 | 2021-04-09 | 中国工商银行股份有限公司 | Online document processing method, online document processing device and electronic equipment |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106446611A (en) * | 2016-08-31 | 2017-02-22 | 北京北信源软件股份有限公司 | Security-level information generation and reading methods and apparatuses |
| RU2647643C1 (en) * | 2017-01-25 | 2018-03-16 | Акционерное общество "Кросс технолоджис" | System for establishing a confidentiality mark in an electronic document, accounting and control of work with confidential electronic documents |
| CN107180195A (en) * | 2017-05-18 | 2017-09-19 | 北京计算机技术及应用研究所 | Electronic document Life cycle safety protecting method based on safety label |
| CN109558101B (en) * | 2018-10-16 | 2022-09-09 | 平安科技（深圳）有限公司 | Financial information dynamic display method and device, storage medium and server |
| CN111324629B (en) * | 2020-02-19 | 2023-08-15 | 望海康信(北京)科技股份公司 | Service data processing method and device, electronic equipment and computer storage medium |
-
2021
- 2021-09-09 CN CN202111055543.XA patent/CN113742295B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112632947A (en) * | 2020-12-25 | 2021-04-09 | 中国工商银行股份有限公司 | Online document processing method, online document processing device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113742295A (en) | 2021-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2019100577A1 (en) | Automated test management method and apparatus, terminal device, and storage medium | |
| US20090241165A1 (en) | Compliance policy management systems and methods | |
| US20230153447A1 (en) | Automatic generation of security labels to apply encryption | |
| CN112116325A (en) | Examination and approval form control method and device, electronic equipment and readable storage medium | |
| US9053450B2 (en) | Automated business process modeling | |
| Wrona et al. | Assisted content-based labelling and classification of documents | |
| US10223389B2 (en) | System and method for analyzing complex metadata | |
| CN114444131A (en) | Document auditing method and computer storage medium | |
| US8631389B2 (en) | Methods and apparatus for authentication of configuration items via configuration item change analysis | |
| CN113742295B (en) | Service data management method and device and document tag management method and device | |
| US20210342900A1 (en) | Methods for customized rule engines for automated medical bill review and devices thereof | |
| CN116302079A (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN111428265A (en) | Statement quality inspection method, device, equipment and storage medium based on federal learning | |
| CN116400913A (en) | Business process generation method and device | |
| CN111090787A (en) | Message processing method, device, system and storage medium | |
| CN113220285B (en) | Security event response scenario generation method, system, device and storage medium | |
| CN112765641B (en) | Efficient desensitization method and device | |
| CN107122381A (en) | Document generating method and device and data analysing method and device | |
| CN108280182B (en) | Examination and approval method and system for flexibly applying internal lists | |
| JP4832132B2 (en) | Access control device, access control simulation method, and access control simulation program | |
| US11436339B1 (en) | Systems, methods, and user interfaces for intelligent and expedited generation of cybersecurity artifacts using cybersecurity control data objects | |
| CN116485336B (en) | Management method, management system and electronic equipment for one-page display work whole process | |
| JP6515439B2 (en) | Authority management apparatus, authority management method, and authority management system | |
| CN111414151B (en) | Page generation method and device for process application, electronic equipment and storage medium | |
| JP2008250782A (en) | Material management device, method, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |