CN111414591B - Workflow management method and device - Google Patents
Workflow management method and device Download PDFInfo
- Publication number
- CN111414591B CN111414591B CN202010135732.7A CN202010135732A CN111414591B CN 111414591 B CN111414591 B CN 111414591B CN 202010135732 A CN202010135732 A CN 202010135732A CN 111414591 B CN111414591 B CN 111414591B
- Authority
- CN
- China
- Prior art keywords
- workflow
- user
- service
- view
- data
- 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
- 238000007726 management method Methods 0.000 title abstract description 77
- 230000006978 adaptation Effects 0.000 claims abstract description 55
- 238000000034 method Methods 0.000 claims abstract description 55
- 238000013507 mapping Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 10
- 230000000977 initiatory effect Effects 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 6
- 230000008569 process Effects 0.000 abstract description 25
- 238000013506 data mapping Methods 0.000 abstract description 6
- 230000004069 differentiation Effects 0.000 abstract description 5
- 230000008447 perception Effects 0.000 abstract 1
- 238000012552 review Methods 0.000 description 24
- 238000012545 processing Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 14
- 230000000694 effects Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 13
- 238000013461 design Methods 0.000 description 11
- 238000012550 audit Methods 0.000 description 9
- 239000007858 starting material Substances 0.000 description 9
- 239000003999 initiator Substances 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000001914 filtration Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 238000007792 addition Methods 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/248—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The invention discloses a workflow management method and device, and relates to the technical field of computers. One embodiment of the method comprises the following steps: constructing a user authority service table of a service system in a service data table space; constructing a user right adaptation table crossing the table space; and constructing a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table. According to the embodiment, the workflow data table space is constructed, layering, differentiation and independent management are carried out on the workflow data table space, the relevance between a business process and business data can be decoupled, and the read-write authority and the safety of the data are enhanced; the user identity authority of the business system and the workflow system is uniformly managed by constructing the user authority view, so that the non-perception, real-time data mapping and synchronization to workflow execution logic are realized quickly and efficiently, and the usability, expandability, componentization modularization capability and commercial implementation convenience of the workflow are greatly improved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for workflow management.
Background
Activiti is a Business Process Management (BPM) framework published by Alfresco software at 5.17.2010, which is an open-source, flexible, easily-extensible executable process language framework covering the fields of business process management, workflow, service collaboration, etc. When the Activiti component is adopted to carry out workflow management, the Activiti component provides a set of user authority management modules, and a service system using the Activiti component also has a user authority management module, so that the user authority management maintenance needs to be respectively analyzed in the Activiti component and the service system.
In the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art:
(1) The association degree of the business process and the business data is high;
(2) The synchronous problem of maintaining the identity authority of multiple users at the same time is needed, the problem of inconsistent reading and writing is easy to exist, the cost is high, and the usability is low.
Disclosure of Invention
In view of this, the embodiments of the present invention provide a method and an apparatus for workflow management, which can decouple the association between a business process and business data, enhance the read-write rights and security of workflow sensitive data, implement unified management of user identity rights of business systems and workflow systems, quickly and efficiently implement imperceptible, real-time data mapping and synchronization to workflow execution logic, and greatly improve usability, expandability, componentization modularization capability and convenience of large-scale commercial implementation of workflows.
To achieve the above object, according to one aspect of an embodiment of the present invention, there is provided a method of workflow management, including:
constructing a user authority service table of a service system in a service data table space;
constructing a user right adaptation table crossing the table space;
and constructing a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table, so that the workflow system executes a workflow according to the user authority workflow view.
Optionally, after the user authority service table of the service system is constructed in the service data table space, the method further comprises: and updating the user authority service table.
Optionally, the workflow system executes a workflow according to the user rights workflow view, including:
creating a workflow in response to a workflow initiation request, the workflow including at least one audit role; determining approval users of each approval role in the workflow according to the user authority workflow view; if the approval character is the last approval character in the workflow, entering the next approval character after the approval user completes the approval task of the approval character; otherwise, ending the workflow.
Optionally, the user authority service table includes: a service user table, a service group table, a service user and a group relation table; the user rights workflow view includes: a workflow user view, a workflow group view, workflow users, and a group relationship view.
Optionally, the user rights adaptation table includes at least one of: workflow role whitelist, workflow role blacklist, time constraints for workflow execution.
According to a second aspect of an embodiment of the present invention, there is provided an apparatus for workflow management, including:
the service system user authority management module constructs a user authority service table of the service system in a service data table space;
the user right adaptation module constructs a user right adaptation table crossing the table space;
the workflow system user authority management module constructs a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table;
and the workflow system executing module is used for executing the workflow according to the user authority workflow view.
Optionally, the service system user authority management module is further configured to: after a user authority service table of a service system is constructed in a service data table space, the user authority service table is updated.
Optionally, the workflow system execution module executes a workflow according to the user authority workflow view, including:
creating a workflow in response to a workflow initiation request, the workflow including at least one audit role; determining approval users of each approval role in the workflow according to the user authority workflow view; if the approval character is the last approval character in the workflow, entering the next approval character after the approval user completes the approval task of the approval character; otherwise, ending the workflow.
Optionally, the user authority service table includes: a service user table, a service group table, a service user and a group relation table; the user rights workflow view includes: a workflow user view, a workflow group view, workflow users, and a group relationship view.
Optionally, the user rights adaptation table includes at least one of: workflow role whitelist, workflow role blacklist, time constraints for workflow execution.
According to a third aspect of an embodiment of the present invention, there is provided an electronic device for workflow management, including:
one or more processors;
Storage means for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention there is provided a computer readable medium having stored thereon a computer program which when executed by a processor implements the method provided by the first aspect of embodiments of the present invention.
One embodiment of the above invention has the following advantages or benefits: by constructing a special workflow data table space and carrying out layering, differentiation and independent management on the workflow data table space, the relevance between a business process and business data can be decoupled, and the read-write authority and the safety of workflow sensitive data are enhanced; by constructing the user authority view crossing the table space, unified management of user identity authorities of a business system and a workflow system is realized, and the imperceptible and real-time data mapping and synchronization to workflow execution logic are realized quickly and efficiently, so that the usability, the expandability, the componentization modularization capability and the convenience of large-scale commercial implementation of the workflow are greatly improved.
Further effects of the above-described non-conventional alternatives are described below in connection with the specific embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main flow of a method of workflow management according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of the main modules of an apparatus for workflow management according to an embodiment of the invention;
FIG. 3 is a schematic block diagram of an apparatus for workflow management in an alternative embodiment of the invention;
FIG. 4 is a workflow schematic of an apparatus for workflow management in an alternative embodiment of the invention;
FIG. 5 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 6 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
According to one aspect of an embodiment of the present invention, a method of workflow management is provided.
Fig. 1 is a schematic diagram of main flow of a method for workflow management according to an embodiment of the present invention, and as shown in fig. 1, the method for workflow management includes: step S101, step S102, and step S103.
Step S101, a user authority service table of the service system is constructed in a service data table space.
The table space belongs to a storage structure in a database, is a logic space for storing database objects (such as data files), is the largest logic unit for information storage in the database, and also comprises logic data types such as segments, areas, data blocks and the like. The tablespace is a space opened up in the database for storing objects of the database, and the database can be composed of a plurality of tablespaces, and the performance of the database can be optimized through the tablespaces.
The business data table space is used for storing business data, and the workflow data table space is used for storing workflow data. The business data table space and the workflow data table space can be located in different databases or can be located in the same database. In the embodiment of the invention, the business data table space and the workflow data table space are stored in the same database.
The user authority service table stores authority information of each user in the service system. Optionally, the user authority service table includes: service user table, service group table, service user and group relation table. The service user table is used for storing each user in the service system. The business group table is used for storing groups in the business system, and each group corresponds to one approval role in the workflow. The service user and group relation table is used for storing the corresponding relation between each user in the service user table and each group in the service group table.
Optionally, after the user authority service table of the service system is constructed in the service data table space, the method further comprises: and updating the user authority service table. For example, operations such as adding, deleting, modifying and the like are performed on the constructed user authority business table. The user authority business table of the embodiment of the invention has expandability.
Step S102, constructing a user right adaptation table crossing the table space.
The business data tablespace and the workflow data tablespace are two distinct tablespaces. The user rights adaptation table maps the user rights service table into the workflow data table space to construct a user rights workflow view of the workflow system, so the user rights adaptation table is a data adaptation table across the table space.
The user authority adaptation table is used for filtering the information in the user authority service table, and the content in the user authority adaptation table is a specific filtering condition. The filtering condition can be selectively set according to the actual situation, and the constructed user right adaptation table can be updated through operations such as adding, deleting and the like, so that the method has expandability. Optionally, the user rights adaptation table includes at least one of: workflow role whitelist, workflow role blacklist, time constraints for workflow execution. The workflow role white list is used for recording users with authority playing a certain role, the workflow role black list is used for recording users without authority playing a certain role, and the time constraint of workflow execution is used for recording the execution time limit of the workflow, for example, the execution time is 9:00-18:00 per day.
Step S103, constructing a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table, so that the workflow system executes a workflow according to the user authority workflow view.
A view is a virtual table whose contents are defined by a query. As with the real table, the view contains a series of columns and rows with names. However, the views do not exist in the database in the form of stored sets of data values. The rows and columns are from tables referenced by queries defining the view and are dynamically generated when the view is referenced. From the database system's internal perspective, a view is a query-defined virtual table made up of SELECT (a computer function) statements, made up of data in one or more tables. From the outside of the database system, the view is just like a table, and the view can be queried.
The user rights workflow view is used to determine individual users in the workflow and their rights information. Optionally, the user authority service table includes: a service user table, a service group table, a service user and a group relation table; the user rights workflow view includes: workflow user view, workflow group view, workflow user and group relationship view. The workflow user view is used to determine individual users in the workflow. The workflow group view is used to determine groups in the workflow, each group corresponding to an approval role in the workflow. The workflow user and group relationship view is used to determine a correspondence between each user in the workflow user view and each group in the workflow group view.
The invention establishes the exclusive workflow data table space, performs layering, differentiation and independent management with the business data table space, can decouple the association of the business flow and the business data, and enhances the read-write authority and the security of the workflow sensitive data; by constructing a cross-table space user authority view, only one user authority data is stored in the business system and the workflow system, unified management of user identity authorities of the business system and the workflow system is realized, real-time synchronization and refreshing of any real-time modification of the user authority data about the business system in the view of the workflow system can be achieved indiscriminately, perceivless real-time data mapping and synchronization to workflow execution logic are achieved rapidly and efficiently, and usability, expandability, componentization modularization capability and convenience of large-scale commercial implementation of the workflow are greatly improved.
Optionally, the workflow system executes a workflow according to the user rights workflow view, including: creating a workflow in response to a workflow initiation request, the workflow including at least one approval role; determining approval users of each approval role in the workflow according to the user authority workflow view; if the approval character is the last approval character in the workflow, entering the next approval character after the approval user completes the approval task of the approval character; otherwise, ending the workflow.
Illustratively, five service groups exist in the service system, and the corresponding five roles are respectively: flow initiator, flow initial check post, flow rechecking post, department lead, law approval. Assume that the roles related to a business approval workflow are only three, namely a flow initiator, a flow initial review post and a flow review post, and department leaders and legal approval in a business system are irrelevant to the flow. The users with the roles as flow originators are three, namely: roll_starter_user1, roll_starter_user2, roll_starter_user3. The users with the roles of the first review post of the process have three roles: roll_verify_user1, roll_verify_user2, roll_verify_user3. The users with the roles of flow re-checking post have three roles: roll_recheck_user1, roll_recheck_user2, roll_recheck_user3. The user roll_recheck_user3 of the process review post role cannot bear approval work (illness, leave, etc.) in the primary review process due to uncontrollable factors. The step of executing the workflow according to the user rights workflow view comprises:
(1) A user role_starter_user1 with a role as a flow initiator initiates a flow and submits a task; this task is defined as task_user1. The phase of task_user1 is changed from the initiation phase to the commit phase at this time. When a flow commit task is initiated, role_starter_user1 may specify that the next role to process the current task is a flow initial review. At the time of engineering implementation, the above specification may be specified at the time of workflow design, or may be specified by means of variable transfer and function call. Whichever way, the processing role of the next auditing stage is the process primary auditing.
(2) After logging in the workflow system, the user roll_verify_user1 with the role as the initial examination of the flow refers to the task to be handled, and can refer to the task_user1. The query thought is as follows: inquiring the user role in the workflow user and the group relation table through a user role_verify_user1 to be a flow initial review by inquiring the constructed user authority workflow view; then inquiring a task which can be processed by the first post of the flow; the task_user1 can be queried by the role_verify_user1.
Similarly, the roles are the users roll_verify_user2 and roll_verify_user3 of the process primary examination, and can also refer to the task_user1, and the query thought is similar to that of roll_verify_user1.
Similarly, after logging in the system, the user role_recheck_user1 with the role of flow checking post refers to the task to be handled and cannot refer to the task_user1; the process review post query is not able to reach task_use1 because the process specifies that the handler role is the review role during the commit phase.
If the system administrator adds a new employee user roll_verify_user4 with the role of the process initial review. Obviously, the system administrator adds the specific operation to the service data table space to realize the data addition. The user role_verify_user4 with the role as the initial review of the flow inquires about the task to be done, and the inquiry is performed in the workflow data table space, and because the view map updated on any user role authority data in the workflow data table space is effectively mapped to the workflow data table space in real time, the user role_verify_user4 can inquire about the task_user1 in the workflow data table space.
(3) After the user role_verify_user4 gets the task task_user1, checking the task to be handled again, and then the user role_verify_user4 does not have the task to be handled; the user role_verify_user4 looks at the history processing task, and then a task_user1 task exists. Likewise, the task_user1 cannot be referred to when the users roll_verify_user1 to roll_verify_user3, which are the same roles as the first review post, review their tasks to be done again, because the task is already taken by other users roll_verify_user4 of the same role.
(4) And the user roll_verify_user 4 with the role as the initial review post of the flow obtains the task and then carries out task review, and the review passes. The role that the role_verify_user4 can specify that the role of next processing the current task is a flow review post before auditing; the phase of task_user1 is changed from the commit phase to the review phase at this time.
(5) And (3) in the recheck stage, the user role_recheck_user1 of the process recheck post inquires the task and obtains the task, and the task processing rule and the calling method are the same as those in the steps (2) - (4) until the task is ended.
According to a second aspect of an embodiment of the present invention, there is provided an apparatus for implementing the above method.
Fig. 2 is a schematic diagram of main modules of an apparatus for workflow management according to an embodiment of the present invention, and as shown in fig. 2, an apparatus 200 for workflow management includes:
the service system user authority management module 201 constructs a user authority service table of the service system in a service data table space;
the user right adaptation module 202 constructs a user right adaptation table crossing the table space;
the workflow system user authority management module 203 constructs a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table;
And a workflow system executing module 204 for executing the workflow according to the user authority workflow view.
Optionally, the service system user authority management module is further configured to: after a user authority service table of a service system is constructed in a service data table space, the user authority service table is updated.
Optionally, the workflow system execution module executes a workflow according to the user authority workflow view, including:
creating a workflow in response to a workflow initiation request, the workflow including at least one audit role; determining approval users of each approval role in the workflow according to the user authority workflow view; if the approval character is the last approval character in the workflow, entering the next approval character after the approval user completes the approval task of the approval character; otherwise, ending the workflow.
Optionally, the user authority service table includes: a service user table, a service group table, a service user and a group relation table; the user rights workflow view includes: a workflow user view, a workflow group view, workflow users, and a group relationship view.
Optionally, the user rights adaptation table includes at least one of: workflow role whitelist, workflow role blacklist, time constraints for workflow execution.
The workflow management apparatus according to the embodiment of the present invention is exemplarily described below with reference to fig. 3 and 4. As shown in fig. 3, the apparatus for workflow management includes: the system comprises an S001 application aggregation core service module, an S002 business system user authority management module, an S003 user authority adaptation module, an S004 workflow system user authority management module, an S005 workflow system flow definition module, an S006 workflow system flow instance management module, an S007 workflow system task management module, an S008 workflow system history inquiry module, an S009 business and workflow parameter configuration module and an S010 workflow system flow design module. Obviously, the workflow system execution module 204 includes an S005 workflow system flow definition module, an S006 workflow system flow instance management module, an S007 workflow system task management module, an S008 workflow system history query module, an S009 service and workflow parameter configuration module, an S010 workflow system flow design module, and the like.
It is assumed that a database storing service data and workflow data is called a database_bank, and data of a service system exists in a table space business_table of the database_bank, and information related to a workflow component exists in another table space workflow_table of the database_bank. The meaning of the symbol "business_table_business_id_user" is: the data table businessjd_user stored in businesstable space.
Meanwhile, five service groups exist in the service system, and the corresponding five roles are respectively: the flow initiator roll_starter, the flow initial check roll_verify, the flow review roll_recheck, the department leader roll_leader, the law approval roll_law. It is assumed that the roles related to a business approval workflow verify-workflow are only three, namely a flow initiator role_starter, a flow initial review post r ole_verify, a flow review post role_recheck, and a department leader role e_leader and a legal approval role_law in a business system are irrelevant to the flow. The users with roles as the roll_starter flow initiator have three roles: roll_starter_user1, roll_starter_user2, ro_starter_user3. The users with the roles of flow primary trial control_verify are three, namely: roll_verify_user1, roll_verify_user2, roll_verify_user3. The users with the roles of flow re-checking role_recheck have three roles: roll_recheck_user1, roll_recheck_user2, roll_recheck_user3. The user roll_rech eck_user3 of the role cannot assume approval work (illness, leave, etc.) in the verify_workflow flow because of uncontrollable factors. There is a new staff user role_verify_user4 that does not belong to any of the three roles described above for the approval process verify_workflow, but from a emperor perspective, when a process is executed at a certain time in the future, he will be added to the role role_verify by the administrator. Obviously, the data related to the service are stored in the table space business_table of da tabase_bank.
1. The system administrator starts the S001 application aggregation core service module, and the service start can complete the start and initialization work of the S002-S010 modules.
When the system administrator starts for the first time, the configuration parameters of the S009 service and workflow parameter configuration module can be set through a preset interface as follows: db-identity-used=false. Simultaneously, setting the configuration parameters of the S003 user permission adaptation module, wherein the configuration parameters comprise: role white list: verify_work flow_whistelist= { role_starter, role_verify, role_recheck }; user blacklist: verify_workflow_blacklist= { role_recheck_user3}; time constraints for workflow execution: v_work_flow_timelmit= {9:00-18:00}.
2. This section details the user identity unified management optimization strategy (Optimization Strategy of User Identit y unified Management based on Database View Mapping of Cross Tablespace, OSUIMDVMCT strategy) based on database cross-tablespace view mapping in the embodiment of the present invention. The implementation of the OSUIMUDVMCT strategy is completed by cooperation of an S002 service system user authority management module, an S003 user authority adapting module and an S004 workflow system user authority management module.
The S002 service system user rights management module includes, but is not limited to, the following three database tables: service user table: business_id_user, service group table: business_id_group, service user and group relationship table: bussiness_id_membership. And S002, the data of the user authority management module of the business system is stored in the table space business_table space of the database.
The S004 workflow system user authority management module comprises, but is not limited to, the following three database tables: workflow user table: act_id_user, workflow group table: act_id_group, workflow user, and group relationship table: act_id_members. The data of the user authority management module of the S004 workflow system is stored in the table space workflow_table of the database_bank. It should be noted that, in the embodiment of the present invention, the data of the above-mentioned tablespace workflow_table is not used, and instead, the user identity unified management optimization strategy mapped across tablespace views based on the database is used.
The core steps of the OSUIMDVMCT strategy include:
(1) The user authority adapting module defines filtering conditions of the verify_workflow workflow in S003, specifically including:
the workflow role whitelist is:
verify_workflow_whitelist＝{role_starter,role_verify,role_recheck}
the role user blacklist is:
verify_workflow_blacklist＝{role_recheck_user3}
the time constraint of workflow execution is:
verify_workflow_timelimit＝{9:00-18:00}。
for the above-mentioned role, user, and other scenario personalized control, special, personalized, and workflow related data screening conditions may be persisted into the data table associated with the user rights adaptation module. The embodiment of the invention assumes that the data table associated with the user right adaptation module is located in the business_table.
(2) In the S004 workflow system user authority management module, three tables of act_id_user, act_id_group and act_id_members in a table space work flow_table space are deleted. Since db-identity-used=false is set in the above-mentioned parameter configuration step, the workflow system service will not check whether the above-mentioned three physical tables exist any more when starting up, so as to perform starting up check and abnormal reminding in the workflow starting up self-checking stage. The parameter "db-identity-used=false" has the meaning of allowing an active open source component to not check for the presence of the three tables at the time of initializing the flow engine.
The rule for starting the verification and abnormal reminding after the db-identity-used parameter configuration belongs to common general knowledge in the field of workflow, and the activation of an industry open source component also has mature open source implementation, and details of engineering implementation are not repeated here.
(3) The administrator grants authority to read a table such as business_ta-busspace, work flow_biz_ adapter, business _ tablespace, business _id_ user, business _busineid_ group, business _businespace, business_id_members to work flow_businespace. For example, the following database sql is executed:
grant select on business_tablespace.business_id_user to workflow_ tablespace
The business_table_business_id_user access rights may be granted to the workflow_table table space. And so on, are not repeated.
The above-described cross-tablespace read permission grant is necessary and an important component of database security and permission protection. Different tablespace data access interworking is the basis for subsequent operations.
(4) The adaptation of the service table space and the user data are combined, a view virtual table is established in the login table space work flow_t ablesace, the user and the adaptation data of the user authority management module of the S002 service system and the user authority adaptation module of the S003 service system are mapped, a virtual table is constructed, and the virtual table is mapped to the work f low_table space to generate a new table: workflow user view: act_id_user; workflow group view: act_id_group; workflow user and group relationship view: act_id_members. The three views are constructed to replace the three physical tables with the same names deleted in the previous step. Taking act_id_user as an example, act_id_user at this time represents a view virtual table, not a real physical table.
By deleting the physical table, a view virtual table is constructed, and the service system and the workflow system only store one user and identity data, so that the user permission data of the service system and the user permission data of the workflow system are unified in real time; by constructing the mapping association relation of the virtual table view, any real-time modification of the user authority data about the service system can be indiscriminately synchronized and refreshed in the user authority data of the workflow system in real time. So far, a unified user identity authority management strategy is constructed. Specifically, for example, the mapping logic of the act_id_user table view is constructed, and one of the alternative operation methods is to log into the table space workflow_table space, and the administrator executes an sql statement like the following:
CREATE OR REPLACE VIEW workflow_tablespace.act_id_user
(id_,rev_,first_,last_,email_,pwd_,picture_id)
AS SELECT
utl_raw.cast_to_nvarchar2(utl_raw.cast_to_raw(translate(a1.id_using nchar_cs))),
to_number(a1.rev_),
utl_raw.cast_to_nvarchar2(utl_raw.cast_to_raw(translate(a1.first_usin g nchar_cs))),
utl_raw.cast_to_nvarchar2(utl_raw.cast_to_raw(translate(a1.last_usin g nchar_cs))),
utl_raw.cast_to_nvarchar2(utl_raw.cast_to_raw(translate(a1.email_ps wd using nchar_cs))),
utl_raw.cast_to_nvarchar2(utl_raw.cast_to_raw(translate(a1.pwd_usi ng nchar_cs))),
utl_raw.cast_to_nvarchar2(utl_raw.cast_to_raw(translate(a1.picture_i d using nchar_cs))),
from business_tablespace.business_id_user a1,
business_tablespace.business_id_membership a2 where a1.usr_id＝ a2.usr_id and a2.rl_id in business_tablespace.verify_workflow_whitelist
The sql maps the business_id_user data of the business table space to the act_id_user of the workflow_ta-busspace table space, and performs role white list verification. The view map here uses S003 a user rights adaptation module. Similarly, more complex checks are performed in compliance with the virtual table and adaptation mapping criteria, and engineering implementation details thereof are not described in detail herein.
The meaning of the S003 user right adaptation module is that the service data like workflow data map can be substituted with sensitive or uncontrollable additional data, and when the refined differentiated hierarchical control is required, the S003 user right adaptation module is more like a role, user and right filter, in this example, through the following steps
verify_workflow_whitelist＝{role_starter,role_verify,role_recheck}
verify_workflow_blacklist＝{role_recheck_user3}
verify_workflow_timelimit＝{9:00-18:00}
The mapping of the business_table_table view to the workflow_table is controlled, so that irrelevant roles, special groups and sensitive operation time are filtered in the mapping process, and the availability of system operation is enhanced. It is clear that the workflow is not able to be developed and performed without the coverage workflow timeelimit time frame.
The real large financial system, the roles can be thousands or tens of thousands, if not filtered, the mapping of tens of thousands of roles to the workflow representation is not desirable, which can cause information leakage or irrelevant data interference. In this example, the workflow-related roles are only three, so the workflow system is a pure and clean set of workflow users that are obtained after data filtering, sensitive information rejection, legal time filtering. Other schemes that facilitate user rights adaptation and filtering, but only those that facilitate enhanced workflow data cleansing, may be implemented by the user rights adaptation table.
It should be noted that, since the three physical tables of the Activiti standard have been deleted and the view mapping relationship is now constructed, all user rights management is not needed to be maintained in the workflow_table space of the Activiti workflow module for addition, deletion and modification, and all maintenance updates of the user rights management are needed to be maintained in the business_table; the user management of the Activiti workflow is decoupled from the business logic, and the Activiti can pay more attention to the processing of the workflow logic without maintaining the user identity information.
3. The flow initiator roll_starter_user1 with the role of roll_starter initiates a verify_workflow workflow through a web or app program interface provided by the S005 workflow system flow definition module. At this time, the workflow system flow instance management module is triggered to build a new workflow instance. The workflow instance is determined by the S010 workflow system flow design module. The design diagram stored by the S010 workflow system flow design module is generally a file with a suffix of bpmn which is generated after a flow or business personnel draw the flow diagram through interface interaction, dragging and clicking, and the essence of the file is standardized flow description information by xml presoaking. In this embodiment, in order to illustrate the implementation and design essence thereof, only a simple text arrow is used to indicate the design drawing:
Start phase →
Commit phase (processing role: role_starter) →
Audit phase (processing role: role_verify) →
Review phase (processing role: role_recheck) →
And (5) ending.
The flow design module of the S010 workflow system generates and analyzes rules through graphical click and drag, belongs to common knowledge in the field of workflows, and is implemented by a mature open source in an open source component Activiti in the industry, and details of engineering implementation are not repeated here.
4. The flow initiator roll_starter_user1, which is in the role of roll_starter, initiates the flow and submits the task, which is defined as task_user1. The phase of task_user1 changes from the launch phase to the commit phase at this time.
When initiating a flow commit task, role_starter_use1 may specify that the role of the next processing current task is role_verify. When the engineering is realized, the specification can be specified in S012 workflow system flow design module parameter configuration, or can be specified in a variable transfer and function call mode; whichever way, the processing role of the next audit phase is role_verify.
5. After the user roll_verify_user1 with the role of roll_verify logs in the workflow system, the task management module of the workflow system refers to the task to be handled by itself through S007, and can refer to the task_user1. The query idea is virtual table query by using OSUIMDVMCT strategy introduced in section 2.
In the OSUIMUDVMCT strategy, an active workflow task query function interface is called, the function interface queries the virtual table of the constructed user authority workflow view, and the role of the user is role_verify in the act_id_members hip table by the user role_verify_user1. Then inquiring task which can be processed by the roll_verify; the task_user1 can be queried by the role_verify_user1.
Likewise, the task_user1 can be referred to by the users roll_verify_user2 and roll_verify_user3 having the same roles as roll_verify, and the query concept is similar to that of roll_verify_user1.
Similarly, if the user role_recheck_user1, whose role is flow review, refers to its task to be handled after logging into the system, it cannot refer to task_user1, because the foregoing flow specifies that the processor role is the audit role during the commit phase.
6. If the service system administrator adds a new employee user roll_verify_user 4 with a role of roll_verify. Obviously, the new operation of the service system administrator is realized by data addition in the table space business_table.
7. The user roll_verify_user4 with role roll_verify inquires about the task to be handled. At this time, the query is performed in the workflow_table, and because of the above OSUIMUMC strategy, the view map updated by the table space business_table for any user role authority data is mapped to the workflow_table in real time, so that the user role_verify_user4 can refer to the task_user1 when querying the workflow_table. The user roll_verify_user4 further operates on the page to get the task task_user1 through the get task function interface of the S007 workflow system task management module.
And checking the task to be handled again, wherein the user role_verify_user4 does not have the task to be handled. And the user role_verify_user4 checks the history processing task through the S008 workflow system query module, and then a task_user1 task exists.
Likewise, when the users roll_verify_user1 to roll_verify_user3 having the same role view their tasks to be handled again, the task_user1 cannot be referred to, because the task is already taken by other users roll_verify_user4 having the same role.
8. After the user roll_verify_user4 with the role of roll_verify gets the task, the task audit function interface of the task management module of the workflow system is called S007 to carry out task audit, and the audit passes. The role_verify_user4 may specify that the role of the next task to be processed is role_recheck before auditing. The phase of task_user1 changes from the commit phase to the review phase at this time.
9. The checking stage is similar to the above steps, and the user role_recheck_user1 of the process checking post role_recheck inquires the task and obtains the task, and the task processing rule and the calling method are the same as the above until the task is ended, and are not repeated again.
In the embodiment, a dedicated workflow database table space is constructed through an OSUIMDVMCT strategy, layering, differentiation and independent management are carried out on the workflow database table space, the relevance between the workflow database table space and business data can be decoupled from a data model, and the read-write authority and the safety of workflow sensitive data are enhanced; the user authority view crossing the table space is constructed, unified management of the user identity authorities of the business system and the workflow system is realized, and the problem of inconsistent reading and writing caused by the synchronous problem that a plurality of user identity authorities are required to be maintained simultaneously in the existing Acitiviti workflow is solved; meanwhile, when personnel identity information and authority information are changed in the service system, sensorless real-time data mapping and synchronization to workflow execution logic are realized rapidly and efficiently under the condition that any data configuration and software codes of the workflow system are not changed; through an Activiti workflow system with unified user identity and authority management, the usability of an Activiti workflow can be greatly improved, and the system is high in expandability, modularization capability and convenience for large-scale commercial implementation.
According to a third aspect of an embodiment of the present invention, there is provided an electronic device for workflow management, including:
one or more processors;
storage means for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention there is provided a computer readable medium having stored thereon a computer program which when executed by a processor implements the method provided by the first aspect of embodiments of the present invention.
Fig. 5 illustrates an exemplary system architecture 500 of a workflow management method or workflow management apparatus to which embodiments of the present invention may be applied.
As shown in fig. 5, the system architecture 500 may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 is used as a medium to provide communication links between the terminal devices 501, 502, 503 and the server 505. Network 504 may include various connection types such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 505 via the network 504 using the terminal devices 501, 502, 503 to receive or send messages or the like. Various communication client applications may be installed on the terminal devices 501, 502, 503, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 501, 502, 503 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 505 may be a server providing various services, such as a background management server (by way of example only) providing support for shopping-type websites browsed by users using the terminal devices 501, 502, 503. The background management server may analyze and process the received data such as the product information query request, and feedback the processing result (e.g., the target push information, the product information—only an example) to the terminal device.
It should be noted that, the method for workflow management provided in the embodiment of the present invention is generally executed by the server 505, and accordingly, the device for workflow management is generally disposed in the server 505.
It should be understood that the number of terminal devices, networks and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 6, there is illustrated a schematic diagram of a computer system 600 suitable for use in implementing an embodiment of the present invention. The terminal device shown in fig. 6 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as a internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, and the like is installed on the drive 610 as needed, so that a computer program read out therefrom is installed into the storage section 608 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 601.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor comprising: the service system user authority management module constructs a user authority service table of the service system in a service data table space; the user right adaptation module constructs a user right adaptation table crossing the table space; the workflow system user authority management module constructs a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table; and the workflow system execution module executes the workflow according to the user authority workflow view. Where the names of these modules do not constitute a limitation of the module itself in some cases, for example, a business system user rights management module may also be described as "a module that builds a user rights workflow view of the workflow system in a workflow data table space".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: constructing a user authority service table of a service system in a service data table space; constructing a user right adaptation table crossing the table space; and constructing a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table, so that the workflow system executes a workflow according to the user authority workflow view.
According to the technical scheme of the embodiment of the invention, the association between the business flow and the business data can be decoupled by constructing the exclusive workflow data table space and carrying out layering, differentiation and independent management on the exclusive workflow data table space, so that the read-write authority and the security of workflow sensitive data are enhanced; by constructing the user authority view crossing the table space, unified management of user identity authorities of the business system and the workflow system is realized, and the imperceptible and real-time data mapping and synchronization to workflow execution logic are realized quickly and efficiently, so that the usability, expandability, componentization modularization capability and large-scale commercial implementation convenience of the workflow are greatly improved.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method of workflow management, comprising:
constructing a user authority service table of a service system in a service data table space;
constructing a user right adaptation table crossing the table space;
constructing a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table so that the workflow system executes a workflow according to the user authority workflow view; the view contains a series of named columns and rows from a table referenced by a query defining the view and dynamically generated when the view is referenced;
the user authority service table comprises: a service user table, a service group table, a service user and a group relation table; the user rights workflow view includes: a workflow user view, a workflow group view, workflow users and a group relationship view;
When the workflow system is started for the first time, setting configuration parameters of the workflow system through a preset interface as follows: the existence of the following three tables is not checked at the time of initializing the flow engine: a workflow user table, a workflow group table, workflow users and a group relationship table; assigning rights read from the user rights adaptation table, the service data table space, the service user table, the service group table, the service user and the group relation table to the workflow data table space; creating a view virtual table in the workflow data table space, mapping the user authority service table and the user authority adaptation table, creating a virtual table and mapping the virtual table to the workflow data table space, and generating the user authority workflow view, including: a workflow user view, a workflow group view, workflow users and a group relationship view;
in a workflow system, deleting three physical tables of a workflow user table, a workflow group table, a workflow user and a group relation table in a workflow data table space; the method comprises the steps of combining adaptation data and user data of a business system table space, logging in a workflow data table space to establish a view virtual table, mapping the adaptation data and the user data to construct a virtual table, mapping the virtual table to the workflow data table space to generate a new table: the three views are used for replacing the deleted three physical tables with the same name.
2. The method of claim 1, further comprising, after constructing the user rights service table of the service system in the service data table space: and updating the user authority service table.
3. The method of claim 1, wherein the workflow system executing a workflow according to the user rights workflow view comprises:
creating a workflow in response to a workflow initiation request, the workflow including at least one approval role; determining approval users of each approval role in the workflow according to the user authority workflow view; if the approval character is the last approval character in the workflow, entering the next approval character after the approval user completes the approval task of the approval character; otherwise, ending the workflow.
4. A method according to any of claims 1-3, wherein the user rights adaptation table comprises at least one of: workflow role whitelist, workflow role blacklist, time constraints for workflow execution.
5. An apparatus for workflow management, comprising:
the service system user authority management module constructs a user authority service table of the service system in a service data table space;
The user right adaptation module constructs a user right adaptation table crossing the table space;
the workflow system user authority management module constructs a user authority workflow view of the workflow system in a workflow data table space according to the user authority service table and the user authority adaptation table; the view contains a series of named columns and rows from a table referenced by a query defining the view and dynamically generated when the view is referenced;
the workflow system execution module executes the workflow according to the user authority workflow view;
the user authority service table comprises: a service user table, a service group table, a service user and a group relation table; the user rights workflow view includes: a workflow user view, a workflow group view, workflow users and a group relationship view;
when the workflow system is started for the first time, setting configuration parameters of the workflow system through a preset interface as follows: the existence of the following three tables is not checked at the time of initializing the flow engine: a workflow user table, a workflow group table, workflow users and a group relationship table; assigning rights read from the user rights adaptation table, the service data table space, the service user table, the service group table, the service user and the group relation table to the workflow data table space; creating a view virtual table in the workflow data table space, mapping the user authority service table and the user authority adaptation table, creating a virtual table and mapping the virtual table to the workflow data table space, and generating the user authority workflow view, including: a workflow user view, a workflow group view, workflow users and a group relationship view;
In a workflow system, deleting three physical tables of a workflow user table, a workflow group table, a workflow user and a group relation table in a workflow data table space; the method comprises the steps of combining adaptation data and user data of a business system table space, logging in a workflow data table space to establish a view virtual table, mapping the adaptation data and the user data to construct a virtual table, mapping the virtual table to the workflow data table space to generate a new table: the three views are used for replacing the deleted three physical tables with the same name.
6. The apparatus of claim 5, wherein the business system user rights management module is further to: after a user authority service table of a service system is constructed in a service data table space, the user authority service table is updated.
7. The apparatus of claim 5, wherein the workflow system execution module executes a workflow according to the user rights workflow view, comprising:
creating a workflow in response to a workflow initiation request, the workflow including at least one approval role; determining approval users of each approval role in the workflow according to the user authority workflow view; if the approval character is the last approval character in the workflow, entering the next approval character after the approval user completes the approval task of the approval character; otherwise, ending the workflow.
8. The apparatus of any of claims 5-7, wherein the user rights adaptation table comprises at least one of: workflow role whitelist, workflow role blacklist, time constraints for workflow execution.
9. An electronic device for workflow management, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-4.
10. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010135732.7A CN111414591B (en) | 2020-03-02 | 2020-03-02 | Workflow management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010135732.7A CN111414591B (en) | 2020-03-02 | 2020-03-02 | Workflow management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111414591A CN111414591A (en) | 2020-07-14 |
| CN111414591B true CN111414591B (en) | 2024-02-20 |
Family
ID=71491027
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010135732.7A Active CN111414591B (en) | 2020-03-02 | 2020-03-02 | Workflow management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111414591B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112416966B (en) * | 2020-12-11 | 2024-01-26 | 北京顺达同行科技有限公司 | Impromptu query method, impromptu query device, computer device and storage medium |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1967560A (en) * | 2006-11-09 | 2007-05-23 | 华为技术有限公司 | Controlling method of business operations competence and generating method of relational database |
| CN101930443A (en) * | 2009-06-22 | 2010-12-29 | 金蝶软件（中国）有限公司 | Data service system and data service realization method |
| JP2014160392A (en) * | 2013-02-20 | 2014-09-04 | Mitsubishi Electric Corp | Workflow management system and workflow management method and program |
| CN106548322A (en) * | 2016-09-29 | 2017-03-29 | 中工国际工程股份有限公司 | Project examination system |
| CN107045675A (en) * | 2017-05-23 | 2017-08-15 | 成都牵牛草信息技术有限公司 | The method that workflow approval node is set examination ＆ approval role by role |
| CN107103448A (en) * | 2016-02-23 | 2017-08-29 | 上海御行信息技术有限公司 | Data integrated system based on workflow |
| CN107180334A (en) * | 2017-04-29 | 2017-09-19 | 成都牵牛草信息技术有限公司 | Based role is to the man-to-man Work-flow control method and system of user |
| CN107301335A (en) * | 2017-07-01 | 2017-10-27 | 成都牵牛草信息技术有限公司 | The list operating right authorization method of based role |
| CN108052673A (en) * | 2017-12-29 | 2018-05-18 | 中国电子科技集团公司信息科学研究院 | A kind of Internet of Things data integrates and fusion middleware system |
| CN108428112A (en) * | 2018-03-12 | 2018-08-21 | 武汉斗鱼网络科技有限公司 | A kind of generation method of list, device, computer and storage medium |
| CN109246089A (en) * | 2018-08-20 | 2019-01-18 | 北京交通大学 | A kind of the front and back end separation architecture access control system and method for based role |
| CN109615323A (en) * | 2018-12-04 | 2019-04-12 | 厦门市美亚柏科信息股份有限公司 | A kind of separation method and system of Activiti process and business |
| CN109636348A (en) * | 2018-12-17 | 2019-04-16 | 北京锐安科技有限公司 | The cross-system workflow measures and procedures for the examination and approval, system and computer readable storage medium |
| CN109816212A (en) * | 2018-12-29 | 2019-05-28 | 东软集团股份有限公司 | Creation method, device, storage medium and the electronic equipment of task list |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150089021A1 (en) * | 2013-09-21 | 2015-03-26 | Schlumberger Technology Corporation | Project data management |
-
2020
- 2020-03-02 CN CN202010135732.7A patent/CN111414591B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1967560A (en) * | 2006-11-09 | 2007-05-23 | 华为技术有限公司 | Controlling method of business operations competence and generating method of relational database |
| CN101930443A (en) * | 2009-06-22 | 2010-12-29 | 金蝶软件（中国）有限公司 | Data service system and data service realization method |
| JP2014160392A (en) * | 2013-02-20 | 2014-09-04 | Mitsubishi Electric Corp | Workflow management system and workflow management method and program |
| CN107103448A (en) * | 2016-02-23 | 2017-08-29 | 上海御行信息技术有限公司 | Data integrated system based on workflow |
| CN106548322A (en) * | 2016-09-29 | 2017-03-29 | 中工国际工程股份有限公司 | Project examination system |
| CN107180334A (en) * | 2017-04-29 | 2017-09-19 | 成都牵牛草信息技术有限公司 | Based role is to the man-to-man Work-flow control method and system of user |
| CN107045675A (en) * | 2017-05-23 | 2017-08-15 | 成都牵牛草信息技术有限公司 | The method that workflow approval node is set examination ＆ approval role by role |
| CN107301335A (en) * | 2017-07-01 | 2017-10-27 | 成都牵牛草信息技术有限公司 | The list operating right authorization method of based role |
| CN108052673A (en) * | 2017-12-29 | 2018-05-18 | 中国电子科技集团公司信息科学研究院 | A kind of Internet of Things data integrates and fusion middleware system |
| CN108428112A (en) * | 2018-03-12 | 2018-08-21 | 武汉斗鱼网络科技有限公司 | A kind of generation method of list, device, computer and storage medium |
| CN109246089A (en) * | 2018-08-20 | 2019-01-18 | 北京交通大学 | A kind of the front and back end separation architecture access control system and method for based role |
| CN109615323A (en) * | 2018-12-04 | 2019-04-12 | 厦门市美亚柏科信息股份有限公司 | A kind of separation method and system of Activiti process and business |
| CN109636348A (en) * | 2018-12-17 | 2019-04-16 | 北京锐安科技有限公司 | The cross-system workflow measures and procedures for the examination and approval, system and computer readable storage medium |
| CN109816212A (en) * | 2018-12-29 | 2019-05-28 | 东软集团股份有限公司 | Creation method, device, storage medium and the electronic equipment of task list |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111414591A (en) | 2020-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3695563B1 (en) | Apparatus, method, and computing device for selectively granting permissions to group-based objects in a group-based communication system | |
| US20210385087A1 (en) | Zero-knowledge identity verification in a distributed computing system | |
| US10410107B2 (en) | Natural language platform for database system | |
| US11082226B2 (en) | Zero-knowledge identity verification in a distributed computing system | |
| US20180232262A1 (en) | Mapping heterogeneous application-program interfaces to a database | |
| US9384361B2 (en) | Distributed event system for relational models | |
| US8887271B2 (en) | Method and system for managing object level security using an object definition hierarchy | |
| US20180232404A1 (en) | Self-recomposing program to transform data between schemas | |
| WO2015013745A1 (en) | Systems and methodologies for managing document access permissions | |
| AU2017219050A1 (en) | System and method for fast probabilistic querying role-based access control systems | |
| US9246920B2 (en) | Cloud resource cloning based on collaborative content | |
| US20160216946A1 (en) | Access operation with dynamic linking and access of data within plural data sources | |
| JP7224714B2 (en) | A group-based communication system and apparatus configured to manage channel titles associated with group-based communication channels | |
| JP7255041B2 (en) | Methods, apparatus, and computer program products for implementing communication barriers in group-based communication systems | |
| US20210144144A1 (en) | Computing system permission administration engine | |
| US9063995B2 (en) | Access control list (ACL) generation for replicated data | |
| US11341192B2 (en) | Cross platform collaborative document management system | |
| US11425132B2 (en) | Cross-domain authentication in a multi-entity database system | |
| CN111414591B (en) | Workflow management method and device | |
| US9946885B2 (en) | Process-oriented modeling and flow to restrict access to objects | |
| US11693648B2 (en) | Automatically producing and code-signing binaries | |
| US20120216240A1 (en) | Providing data security through declarative modeling of queries | |
| US11921887B2 (en) | Decentralized identity metaverse database system | |
| US11689485B1 (en) | Techniques for configuring communication process flow actions | |
| US20220138644A1 (en) | System and method for leveraging a completeness graph |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20221010 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |