CN109886656A - A kind of workflow engine system for supporting multisystem - Google Patents
A kind of workflow engine system for supporting multisystem Download PDFInfo
- Publication number
- CN109886656A CN109886656A CN201910144577.2A CN201910144577A CN109886656A CN 109886656 A CN109886656 A CN 109886656A CN 201910144577 A CN201910144577 A CN 201910144577A CN 109886656 A CN109886656 A CN 109886656A
- Authority
- CN
- China
- Prior art keywords
- workflow engine
- interface
- engine system
- workflow
- 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.)
- Granted
Links
Abstract
The invention discloses a kind of workflow engine system for supporting multisystem, workflow engine system audits the business of not homologous ray by unified place by routine interface and each operation system functional module Interworking Data.The present invention has the following advantages: 1 is versatile.This workflow engine system can access multiple and different operation systems by http interface, provide examination & approval for different operation systems.If different operation systems realizes callback interface, workflow engine can also adjust back operation system and realize workflow to the readjustment of operation system.So versatility is very strong.2 maintenance costs are low.Operation system access workflow passes through interface completely, by configuring, without volume code.3 graphic process are drawn.Workflow is drawn by way of graphically pulling, it is easy to operate, using simple.
Description
Technical field
The present invention relates to business flow processing field, in particular to a kind of workflow engine system for supporting multisystem.
Background technique
Many corporate business auditing flows are relatively more, system is more, the otherness of each approval process is bigger, in order to simultaneous
Hold existing each system and the development in view of company informatization, so devising this workflow engine system.
Existing workflow engine system mainly has the disadvantages that
1 couples with operation system depth, and maintenance cost is high；
2 only have access single channel；
3 can only support certain a kind of user.
Summary of the invention
It is an object of the invention to overcome the deficiencies of the prior art and provide a kind of workflow engine systems for supporting multisystem
System.
The purpose of the present invention is achieved through the following technical solutions:
A kind of workflow engine system for supporting multisystem, workflow engine system pass through routine interface and each business system
System functional module Interworking Data；It calls setting address to create workflow instance when operation system start flow, passes through parameter " sys_
Id " indicates different systems, and sys_id=APP indicates that this business is initiated by APP channel, and sys_id=PC indicates this business by official
Square website is initiated, and sys_id=WECHAT indicates that this business is initiated by wechat system；
Operation system is initiated or when some operation flow is audited at operation system end, and the circulation of process is by workflow engine
System control, operation system can request workflow engine system to execute corresponding operation, and workflow engine system is finished
After can call starting callback operation；
Workflow engine system passes through the ground of the corresponding operation system readjustment of database lookup according to the value of " sys_id "
It is adjusted back to realize location；
Operation system logic returns to code value after running succeeded and gives workflow engine system, and workflow engine system is again
Code value is returned to operation system.
It is preferred that operating and accessing by web interface, the workflow task of each system had both been realized in this way
Again each workflow situation can be uniformly seen in this system.
It is preferred that operation system passes through http interface Transfer Parameters to workflow engine system, workflow engine
Then one flow instance of system creation is called the logic of operation system by http interface, returns after logic success and successfully mark
Will returns again to workflow and gives creation interface.
It is preferred that routine interface includes that flow instance creation interface, process list query interface, process details are looked into
It askes interface and flow nodes jumps interface.
It is preferred that flow instance creation includes the following steps:
1) the business number (bus_id) transmitted by operation system gets corresponding process id；
2) value of business needs is deposited into argument table；
3) the interface runtimeService.startProcessInstanceById () of activity is called to create one
New example；
4) transactor is found, mongodb is called when looking for transactor, obtains the information such as the name of personnel, and will receive
Personal information, sends personal information, and transactor's history lists is written in procedure information；
5) object that encapsulation returns.
It is preferred that process list query includes the following steps:
1) called side transmits processing people's information, task id, Action number, other parameters variable；
2) it sees that execution is submitted according to Action number still to retract, if it is submission, call method
taskService.complete(taskid,dyna_arg)；
If it is retracting, then new path is created by the original path of deletion to realize；
It returns to which node and can be transmitted through by called side come or on stream specify, directly configuration is in configuration information
In；
If next link is sub-process, it is also necessary to assemble the transactor of more examples, be placed in variable；
3) find transactor, transactor may be specified role, customer manager, specified people, these information be all
It is obtained in monggodb, and transactor's history lists is written into reception staff's information, transmission personal information, procedure information；
4) argument table is written into important information；
5) object that encapsulation returns；
6) interface for adjusting back operation system, changes the state of business datum.
It is preferred that being configured with by node if process list query further includes step 7) and sending short message
Listener can call the listener for sending short message when generating new task.
It is preferred that the inquiry of process details includes the following steps:
1) pending, to have done, finished be an interface IP address, pass through what data parameter querytype judgement inquires；
2) pending: the information such as data, the name that is taken out from mongodb in the act_ru_task table of activity,
Obtained by example table, the four table conjunctive query of button arrangement table；
It if it is more instant nodes and is to execute parallel, it is also necessary to which having handled on more instant nodes for task is picked
It removes；
Done interface, finish interface by example table, button arrangement table, history lists inquiry.
It is preferred that the inquiry of process details is filtered the data of querying individual according to user id or is inquired proprietary
It is pending, determine that (allorpart parameter is as follows: 0 indicates to inquire all user tasks according to allorpart；1 indicates according to user
Id query task)；
Filtering further includes according to system, type of service, substation, and the parameters such as Business Name are filtered.
It is preferred that procedure information invocation step:
1) called side, which is transmitted through, carrys out an example id, passes through the relevant information of case-based system process；
2) return includes process id, title, business number, Business Name, company's information, heading message, founder, creation
Time, traffic table id, traffic table major key, each nodal operation historical record.
The beneficial effects of the present invention are:
The present invention has the following advantages:
1 is versatile.This workflow engine system can access multiple and different operation systems by http interface, be different
Operation system provides examination & approval.If different operation systems realizes callback interface, workflow engine can also adjust back business system
System realizes workflow to the readjustment of operation system.So versatility is very strong.
2 maintenance costs are low.Operation system access workflow passes through interface completely, by configuring, without volume code.
Detailed description of the invention
Fig. 1 is workflow engine system and operation system connection schematic diagram；
Fig. 2 is workflow schematic diagram of the present invention；
Fig. 3 is argument table structural schematic diagram；
Fig. 4 is that act_ru_task activity task presentation is intended to (table 1)；
Fig. 5 is wf_run_history transactor historical record schematic diagram (table 2)；
Fig. 6 is wf_run_instance example table schematic diagram (table 3)；
Fig. 7 is that button_config_table button arrangement indicates to be intended to (table 4)；
Fig. 8 is act_hi_actinst activity history table (table 5).
Specific embodiment
Technical solution of the present invention is described in further detail with reference to the accompanying drawing, but protection scope of the present invention is not limited to
It is as described below.
As depicted in figs. 1 and 2, a kind of workflow engine system for supporting multisystem, workflow engine system pass through program
Interface and each operation system functional module Interworking Data；Call setting address creation workflow real when operation system start flow
Example indicates different systems by parameter " sys_id ", and sys_id=APP indicates that this business is initiated by APP channel, sys_id=
PC indicates that this business is initiated by official website, and sys_id=WECHAT indicates that this business is initiated by wechat system；
Operation system is initiated or when some operation flow is audited at operation system end, and the circulation of process is by workflow engine
System control, operation system can request workflow engine system to execute corresponding operation, and workflow engine system is finished
After can call starting callback operation；
Workflow engine system according to the value of " sys_id " by database (database build Workflow system in, one
Library, other systems cannot access database, can be called by interface and obtain data) search the ground that corresponding operation system is adjusted back
It is adjusted back to realize location；
Operation system logic returns to code value after running succeeded (value of code=100, code are a meaning definition, mesh
The interface of preceding all operation systems run succeeded return value be 100；The new interface developed later can adjust according to demand；If not
It is to have what special circumstances, it is constant that success value returns to 100) workflow engine system is given, workflow engine system returns again to
(value of code=200, code are the definition of meaning to code value, and the run succeeded value of return of interfaces all at present is 200；
The new interface developed later can adjust according to demand；If not being to have what special circumstances, it is constant that success value returns to 200) give business
System.
In a preferred embodiment, it operates and accesses by web interface, both realized the work of each system in this way
Stream task can uniformly see each workflow situation in this system again.
In a preferred embodiment, operation system passes through http interface Transfer Parameters to workflow engine system, work
It flows automotive engine system and creates a flow instance, the logic of operation system is then called by http interface, is returned after logic success
Success Flag (such as: operation system changes the code=100 that state is successfully given) to workflow (workflow engine system), then return
Back to creation interface.
In a preferred embodiment, routine interface includes flow instance creation interface, process list query interface, process
Details query interface and flow nodes jump interface.Node jumps, submits, retracts that belong to flow operations interface (only specific
Operation it is different, it is also expansible other to operate)
The degree of coupling of traditional Workflow system and operation system is too high, reusability is too low, one complicated industry of every exploitation
Business system can all put into a large amount of man power and material and remove retrofit work stream engine.This workflow engine system provides powerful connect
Mouth function, supports multiple and different operation systems to access, and cost of access is cheap.
1 interface specification of table
X expression in table 1 can be customized.
In a preferred embodiment, flow instance creation includes the following steps:
1) the business number (bus_id) transmitted by operation system gets corresponding process id；
2) value of business needs is deposited into argument table
Argument table is the argument table of activity, and the runtimeService.startP by operating activity
RocessInstanceById (flowid, dyna_arg) and taskService.complete (taskid, dyna_arg) this
The variable of two methods；Dyna_arg is the Map container of a storage variable.The field of argument table setting is as shown in Figure 3.
3) interface of activity is called (when having got process id by bus_id (business id), just to call
The creation interface of activity) runtimeService.startProcessInstanceById () one new reality of creation
Example；
4) transactor is found, mongodb is called when looking for transactor, obtains the information such as the name of personnel, and will receive
Personal information, sends personal information, and transactor's history lists is written in procedure information；
A large and complete organizational structure is stored in mongodb, the transactor configured in process may be a tool
The id of body, this is to need that mongodb is called to obtain the corresponding name of personnel, the information such as phone (send short messages and use)；It may also match
That set is a role id, needs to find the personnel under this role in monggodb；What may also be configured is certain relationship,
For example find the customer manager of application user, it is also desirable to the corresponding customer manager of user be gone in mongodb to find.
Mongodb is an independent database, and workflow has only linked this library.
Transactor's history lists is the table individually created, because of Workflow system inorganization Schema information, for convenience
The transactor of each step, has been deposited portion by the evidence of list interface access below.
5) object that encapsulation returns.Contents of object include (process id, process name, process key, current node information, under
The name (may be multiple) of one node, the transactor (may be multiple) of next node, the operating rights that next node possesses
It limits (for example submit, retract), task id (may be multiple) etc.)
In a preferred embodiment, process list query includes the following steps:
1) called side, which transmits, handles people's information, task id (taskid), Action number (expression is to submit or retract),
His parametric variable；
Handle people, that is, transactor；Human roles have three classes: founder (I initiates when this application, I is exactly founder,
Founder once initiates success, while also becoming and having done people), processing people (is also pending people, this task currently needs here
Reason, I is exactly to handle people), done people (I has handled and am over task, and identity at this time, which has reformed into, has done people).
Other parameters are usually the data in service logic, for assisting or the trend of control flow, such as business
It is the amount of the loan that a variable is transmitted in side.The amount of money is of different sizes, and the flow line walked is just different, this data can pass through change
Amount, which is transmitted through, to be come.As long as business side thinks that valuable data are placed in variable, for assisting simultaneously control flow trend.
2) it sees that execution is submitted according to Action number still to retract, if it is submission, call method
TaskService.complete (taskid, dyna_arg) (interface of activity)；
If it is retracting, then new path is created by the original path of deletion to realize；
(retraction operation is executed if it is in more instant nodes, needs the task that other are not handled also to delete, passes through setting
The value of nrOfInstances variable is 1 to realize)
It returns to which node and can be transmitted through by called side come or on stream specify, directly configuration is in configuration information
In；
If next link is sub-process, it is also necessary to assemble the transactor of more examples, be placed in variable；
Transactor can be regarded as processing people.For initiating sub-process, it may be desirable to initiate multiple sub-processes, each
People is each responsible for a task, these are mutually incoherent.It just needs personnel to be assembled into a list this when to concentrate, be tied to
It draws on variable name specified when flow chart.
3) find transactor, transactor may be specified role, customer manager, specified people, these information be all
It is obtained in monggodb, and transactor's history lists is written into reception staff's information, transmission personal information, procedure information；
4) argument table is written into important information；
The middle data that argument table is written herein are generally used to control flow trend, and argument table is as shown in Figure 3.
5) object that encapsulation returns, content include that (process id, process name, process key, current node information are next
The name (may be multiple) of node, the transactor (may be multiple) of next node, the operating right (ratio that next node possesses
Such as submit, retract), task id (may be multiple) etc.)
6) interface for adjusting back operation system, changes the state of business datum
Workflow needs to change the state of business datum to some node, this node needs to configure a change state
Listener, in this lisntener, by getting the System Number of the flow instance, get this from allocation list
The url interface of the corresponding change state of a system, by calling this interface to change business datum.The table name here related to,
Major key name, id value these be all to be directly transmitted to called side just in the variable for existed activity.
In a preferred embodiment, it is configured with by node if process list query further includes step 7) and sends short message
Listener can call the listener for sending short message when generating new task.Traditional Workflow system is generally only fitted
With with the end PC or be only applicable to the end APP, and the mode without other active warnings approving person or other alerting patterns are unknown
It is aobvious.Traditional Workflow system is generally notified at the end PC.This workflow integration end PC, the end APP and SMS.This three
A channel can all have pending notice, and for the same workflow nodes, different channels can have different functions.
SMS function realizes that i.e. triggering scene configuration and message template is configured by two allocation lists, generates every time pending
System can call the interface class of java to search the number with the process and the node matching from scene configuration table when task
According to no need to send short messages for expression if not finding data, and the note numbering if finding data further according to configuration is found
Then message template realizes that short message is sent with the variable of process variable replacement message template.
In a preferred embodiment, process details inquiry includes the following steps:
1) pending, to have done, finished be an interface IP address, pass through what data parameter querytype judgement inquires
(parameter of querytype is as follows: 1 indicates to act on behalf item, and 2 indicate item of having handled affairs, and 3 indicate to finish item)
2) pending: by table act_ru_task (table 1, activity task list), wf_run_history (table 2, transactor
History table), wf_run_instance (table 3, example table), button_config_table (table 4, button arrangement table) this
Obtained by four table conjunctive queries.The PROC_INST_ID_ field of table 1 is closed with the instanceid of table 2, the instanceid of table 3
Connection；The flowkey of table 3 is associated with the FLOWKEY of table 4.The characteristics of this table of act_ru_task is that task is handled, and record is just
It deletes.
Table 1 (as shown in figure 4, being table 1): field from left to right is respectively: id, version number, executes id, example id, stream
Journey id, nodename, the task id (sub-process just has value) of father's process, task description, nodename, the owner, transactor (when
Node just has value when handling artificial specific people)；
Table 2 (as shown in figure 5, being table 2): when from left to right respectively: process id, process name, example id, node i d, section
Point title, sender id, sender's title handle people id, and processing name claims, sending time, task id.
Table 3 (as shown in fig. 6, being table 3): it is respectively from left to right: process id, process name, example id, title, creation
People, creation time, the current state of example, business id, Business Name, System Number, traffic table Major key, the table of operation system
Name, the Business Name of applicant, process key.
Table 4 (as shown in fig. 7, being table 4) is respectively from left to right: process KEY, node i d, and pending operation button number is (more
A branch separates), pending operation button title (multiple branches separate), node remarks (i.e. nodename) have done operation button
It numbers (multiple branches separate), has done operation button title (multiple branches separate).
Table 1, table 2,3 example id of table association, the process key of table 3 are associated with the process key of table 4.
The state of table 3 is known that the example whether processing is over, is now in what state (14001: not submitting；
14002: in audit；14003: passing through；14004: not passing through；14005: cancelling；14006: rejecting；14007: filling in basic letter
Breath；14008: filling in details；14009: terminating；14010: pause；14011: credits appraisal meeting evaluation；14012: credits load
The examination & approval of guarantor company；14013: creditor bank's examination & approval；14014: credits finance does examination & approval).
It if it is more instant nodes and is to execute parallel, it is also necessary to which having handled on more instant nodes for task is picked
It removes；
It done interface, finished interface by example table (wf_run_instance), button arrangement table (button_
Config_table), history table inquiry (table 5, activity history lists act_hi_actinst).wf_run_
The PROC_INST_ID of instanceid and the act_hi_actinst table of instance table is associated with, wf_run_instance's
Instanceid is associated with the FLOWKEY of button_config_table.
Table 5 (as shown in figure 8, being table 5) is respectively from left to right: process id, example id execute id, node i d, task
Id, transactor handle duration, job start time, job end time.
In a preferred embodiment, data or the inquiry institute of querying individual are filtered in the inquiry of process details according to user id
Someone's is pending, determines that (allorpart parameter is as follows: 0 indicates to inquire all user tasks according to allorpart；1 indicates root
According to user id query task)；
Filtering further includes according to system, type of service, substation, and the parameters such as Business Name are filtered.
In a preferred embodiment, procedure information invocation step:
1) called side, which is transmitted through, carrys out an example id, passes through the relevant information of case-based system process；
2) return includes process id, title, business number, Business Name, company's information, heading message, founder, creation
Time, traffic table id, traffic table major key, each nodal operation historical record.
In a preferred embodiment, since internet end subscriber and administrator's end subscriber are two sets of different users, this
Workflow engine system supports internet end and administrator's end subscriber to be collectively used together.The i.e. same approval process can be by mutual
End subscriber of networking is initiated, backstage manager user's audit.
System just uses foreground user and backstage manager from the security consideration of system when designing user module
The data at family, which are stored separately, is stored in different tables, and the entry address on the backstage that do not open to the public.Theoretically come
Say that foreground user is possible to identical as background user name, for foreground user name, workflow engine when workflow processing
Module increases prefix " C_ " background user automatically and increases prefix " B_ " for distinguishing.
In a preferred embodiment, for the same approval node, different permissions is needed on different channels,
Such as button of " replacement transactor ", due to bad displaying on displaying relatively good on the more pc of candidate transactor but APP, so
APP is upper, and there is no need to this buttons.System solves this problem by way of configuring, and has reached the button shown on APP
It is not identical as the button that is shown on pc.
Button grade authority configuration, by a database allocation list by the different node of the same process in different roles
When with calling on different channels, different button permissions are returned.Graphic process is drawn.Pass through the side graphically pulled
Formula draws workflow, easy to operate, using simple.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, it is noted that all
Made any modifications, equivalent replacements, and improvements etc. within the spirit and principles in the present invention should be included in guarantor of the invention
Within the scope of shield.
Claims (10)
1. a kind of workflow engine system for supporting multisystem, it is characterised in that: workflow engine system by routine interface with
Each operation system functional module Interworking Data；It calls setting address to create workflow instance when operation system start flow, leads to
The system that parameter " sys_id " indicates different is crossed, sys_id=APP indicates that this business is initiated by APP channel, sys_id=PC table
Show that this business is initiated by official website, sys_id=WECHAT indicates that this business is initiated by wechat system；
Operation system is initiated or when some operation flow is audited at operation system end, and the circulation of process is by workflow engine system
Control, operation system can request workflow engine system to execute corresponding operation, meeting after workflow engine system is finished
Call starting callback operation；
Workflow engine system according to the value of " sys_id " by the address of the corresponding operation system readjustment of database lookup come
Realize readjustment；
Operation system logic returns to code value after running succeeded and gives workflow engine system, and workflow engine system returns again to
Code value is to operation system.
2. a kind of workflow engine system for supporting multisystem according to claim 1, it is characterised in that: by web circle
Face operates and accesses, not only realized the workflow task of each system in this way but also can uniformly see each process in this system
Circulate situation.
3. a kind of workflow engine system for supporting multisystem according to claim 1 or 2, it is characterised in that: business system
System is created a flow instance, is then led to by http interface Transfer Parameters to workflow engine system, workflow engine system
The logic that http interface calls operation system is crossed, Success Flag is returned after logic success to workflow, returns again to and gives creation interface.
4. a kind of workflow engine system for supporting multisystem according to claim 1 or 2, it is characterised in that: program connects
Mouth includes that flow instance creation interface, process list query interface, process details query interface and flow nodes jump interface.
5. a kind of workflow engine system for supporting multisystem according to claim 4, which is characterized in that flow instance wound
It builds and includes the following steps:
1) the business number (bus_id) transmitted by operation system gets corresponding process id；
2) value of business needs is deposited into argument table；
3) call the interface runtimeService.startProcessInstanceById () of activity create one it is new
Example；
4) transactor is found, mongodb is called when looking for transactor, obtains the information such as the name of personnel, and by reception staff
Information, sends personal information, and transactor's history lists is written in procedure information；
5) object that encapsulation returns.
6. a kind of workflow engine system for supporting multisystem according to claim 4, which is characterized in that process list is looked into
Inquiry includes the following steps:
1) called side transmits processing people's information, task id, Action number, other parameters variable；
2) it sees that execution is submitted according to Action number still to retract, if it is submission, call method taskService.complete
(taskid,dyna_arg)；
If it is retracting, then new path is created by the original path of deletion to realize；
It returns to which node and can be transmitted through by called side come or on stream specify, directly configuration is in configuration information；
If next link is sub-process, it is also necessary to assemble the transactor of more examples, be placed in variable；
3) find transactor, transactor may be specified role, customer manager, specified people, these information be all
It is obtained in monggodb, and transactor's history lists is written into reception staff's information, transmission personal information, procedure information；
4) argument table is written into important information；
5) object that encapsulation returns；
6) interface for adjusting back operation system, changes the state of business datum.
7. a kind of workflow engine system for supporting multisystem according to claim 6, which is characterized in that process list is looked into
If inquiry further includes that step 7) is configured with the listener for sending short message by node, transmission can be called when generating new task
The listener of short message.
8. a kind of workflow engine system for supporting multisystem according to claim 4, which is characterized in that process details are looked into
Inquiry includes the following steps:
1) pending, to have done, finished be an interface IP address, pass through what data parameter querytype judgement inquires；
2) pending: information, example such as data, the names that is taken out from mongodb in the act_ru_task table of activity
Obtained by table, the four table conjunctive query of button arrangement table；
It if it is more instant nodes and is to execute parallel, it is also necessary to which having handled on more instant nodes for task is rejected；
Done interface, finish interface by example table, button arrangement table, history lists inquiry.
9. a kind of workflow engine system for supporting multisystem according to claim 8, which is characterized in that process details are looked into
Inquiry is proprietary pending according to the data of user id filtering querying individual or inquiry, is determined according to allorpart；
Filtering further includes according to system, type of service, substation, and the parameters such as Business Name are filtered.
10. a kind of workflow engine system for supporting multisystem according to claim 1, which is characterized in that procedure information
Invocation step:
1) called side, which is transmitted through, carrys out an example id, passes through the relevant information of case-based system process；
2) return include process id, title, business number, Business Name, company's information, heading message, founder, create when
Between, the historical record of traffic table id, traffic table major key, each nodal operation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910144577.2A CN109886656B (en) | 2019-02-27 | 2019-02-27 | Workflow engine system supporting multiple systems |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910144577.2A CN109886656B (en) | 2019-02-27 | 2019-02-27 | Workflow engine system supporting multiple systems |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109886656A true CN109886656A (en) | 2019-06-14 |
| CN109886656B CN109886656B (en) | 2021-06-29 |
Family
ID=66929552
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910144577.2A Active CN109886656B (en) | 2019-02-27 | 2019-02-27 | Workflow engine system supporting multiple systems |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109886656B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110322230A (en) * | 2019-07-08 | 2019-10-11 | 佛山市众联成云科技有限公司 | A kind of Workflow system docks specification implementation method with operation system |
| CN110659018A (en) * | 2019-09-20 | 2020-01-07 | 中国银行股份有限公司 | Flow engine implementation method and device |
| CN110968408A (en) * | 2019-11-13 | 2020-04-07 | 泰康保险集团股份有限公司 | Execution stream removing method and device, electronic equipment and storage medium |
| CN111353766A (en) * | 2020-03-31 | 2020-06-30 | 中国建设银行股份有限公司 | Service process processing system and method of distributed service system |
| CN111461656A (en) * | 2020-03-31 | 2020-07-28 | 上海星移软件有限公司 | Process data processing method and device of business process management system |
| CN111880837A (en) * | 2020-07-21 | 2020-11-03 | 上海伯俊软件科技有限公司 | Business process engine system supporting dynamic expansion and visual configuration |
| CN111897815A (en) * | 2020-07-15 | 2020-11-06 | 中国建设银行股份有限公司 | Service processing method and device |
| CN112241430A (en) * | 2020-10-26 | 2021-01-19 | 浪潮云信息技术股份公司 | Model applied to multi-system docking processing |
| CN112633830A (en) * | 2020-12-21 | 2021-04-09 | 北京恒泰实达科技股份有限公司 | Workflow system and method capable of quickly integrating application systems |
| CN112650598A (en) * | 2020-12-21 | 2021-04-13 | 思创数码科技股份有限公司 | Multi-application access method for workflow system |
| CN113537667A (en) * | 2020-04-16 | 2021-10-22 | 河北网星软件有限公司 | Workflow batch processing method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104850405A (en) * | 2015-05-25 | 2015-08-19 | 武汉众联信息技术股份有限公司 | Intelligent configurable workflow engine and implementation method therefor |
| US9384468B2 (en) * | 2011-05-17 | 2016-07-05 | Benjamin Harold Lesh | Method for adding game elements to information aggregation |
| CN107239875A (en) * | 2017-04-26 | 2017-10-10 | 北京妙医佳信息技术有限公司 | The system for realizing the healthy service management of enterprise's rapid build |
| CN107392564A (en) * | 2017-06-21 | 2017-11-24 | 安徽森度科技有限公司 | A kind of workflow visual configuration platform based on activiti technologies |
| CN107590282A (en) * | 2017-09-29 | 2018-01-16 | 深圳市安诺软件有限公司 | The processing method and workflow engine of a kind of workflow engine |
| CN108052318A (en) * | 2018-01-03 | 2018-05-18 | 上海火杉信息科技有限公司 | It is a kind of that collaborative platform is knitted based on the multigroup of SaaS patterns |
-
2019
- 2019-02-27 CN CN201910144577.2A patent/CN109886656B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9384468B2 (en) * | 2011-05-17 | 2016-07-05 | Benjamin Harold Lesh | Method for adding game elements to information aggregation |
| CN104850405A (en) * | 2015-05-25 | 2015-08-19 | 武汉众联信息技术股份有限公司 | Intelligent configurable workflow engine and implementation method therefor |
| CN107239875A (en) * | 2017-04-26 | 2017-10-10 | 北京妙医佳信息技术有限公司 | The system for realizing the healthy service management of enterprise's rapid build |
| CN107392564A (en) * | 2017-06-21 | 2017-11-24 | 安徽森度科技有限公司 | A kind of workflow visual configuration platform based on activiti technologies |
| CN107590282A (en) * | 2017-09-29 | 2018-01-16 | 深圳市安诺软件有限公司 | The processing method and workflow engine of a kind of workflow engine |
| CN108052318A (en) * | 2018-01-03 | 2018-05-18 | 上海火杉信息科技有限公司 | It is a kind of that collaborative platform is knitted based on the multigroup of SaaS patterns |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110322230A (en) * | 2019-07-08 | 2019-10-11 | 佛山市众联成云科技有限公司 | A kind of Workflow system docks specification implementation method with operation system |
| CN110659018A (en) * | 2019-09-20 | 2020-01-07 | 中国银行股份有限公司 | Flow engine implementation method and device |
| CN110659018B (en) * | 2019-09-20 | 2023-09-19 | 中国银行股份有限公司 | Method and device for realizing flow engine |
| CN110968408B (en) * | 2019-11-13 | 2023-04-07 | 泰康保险集团股份有限公司 | Execution stream removing method and device, electronic equipment and storage medium |
| CN110968408A (en) * | 2019-11-13 | 2020-04-07 | 泰康保险集团股份有限公司 | Execution stream removing method and device, electronic equipment and storage medium |
| CN111461656A (en) * | 2020-03-31 | 2020-07-28 | 上海星移软件有限公司 | Process data processing method and device of business process management system |
| CN111353766A (en) * | 2020-03-31 | 2020-06-30 | 中国建设银行股份有限公司 | Service process processing system and method of distributed service system |
| CN113537667A (en) * | 2020-04-16 | 2021-10-22 | 河北网星软件有限公司 | Workflow batch processing method and system |
| CN113537667B (en) * | 2020-04-16 | 2023-03-24 | 河北网星软件有限公司 | Workflow batch processing method and system |
| CN111897815A (en) * | 2020-07-15 | 2020-11-06 | 中国建设银行股份有限公司 | Service processing method and device |
| CN111880837A (en) * | 2020-07-21 | 2020-11-03 | 上海伯俊软件科技有限公司 | Business process engine system supporting dynamic expansion and visual configuration |
| CN111880837B (en) * | 2020-07-21 | 2024-02-20 | 上海伯俊软件科技有限公司 | Business process engine system supporting dynamic expansion and visual configuration |
| CN112241430A (en) * | 2020-10-26 | 2021-01-19 | 浪潮云信息技术股份公司 | Model applied to multi-system docking processing |
| CN112633830A (en) * | 2020-12-21 | 2021-04-09 | 北京恒泰实达科技股份有限公司 | Workflow system and method capable of quickly integrating application systems |
| CN112650598A (en) * | 2020-12-21 | 2021-04-13 | 思创数码科技股份有限公司 | Multi-application access method for workflow system |
| CN112650598B (en) * | 2020-12-21 | 2023-08-18 | 思创数码科技股份有限公司 | Multi-application access method for workflow system |
| CN112633830B (en) * | 2020-12-21 | 2024-03-01 | 北京恒泰实达科技股份有限公司 | Workflow system and method capable of realizing rapid integration of application system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109886656B (en) | 2021-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109886656A (en) | A kind of workflow engine system for supporting multisystem | |
| US10521853B2 (en) | Electronic sales system | |
| US7131071B2 (en) | Defining an approval process for requests for approval | |
| US20040230466A1 (en) | Adaptable workflow and communications system | |
| US11537958B2 (en) | Automated adaptation of business process tracking and communications | |
| US8700506B2 (en) | Distributed commerce system | |
| JP4937944B2 (en) | How to manage networked commercial interactions | |
| US20030225607A1 (en) | Commoditized information management system providing role aware, extended relationship, distributed workflows | |
| US10505873B2 (en) | Streamlining end-to-end flow of business-to-business integration processes | |
| US8478795B2 (en) | Method and system for automatically defining organizational data in unified messaging systems | |
| US11582138B2 (en) | Configurable system for resolving requests received from multiple client devices in a network system | |
| CN108023948A (en) | A kind of system and method for handling third party system information | |
| CN113821500A (en) | Business object construction method based on government affair service scene | |
| WO2003098518A2 (en) | Patent resource systems and methods |
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 | ||
| GR01 | Patent grant |