CN112364057A - Intelligent notification system for business process execution state - Google Patents
Intelligent notification system for business process execution state Download PDFInfo
- Publication number
- CN112364057A CN112364057A CN202011245403.4A CN202011245403A CN112364057A CN 112364057 A CN112364057 A CN 112364057A CN 202011245403 A CN202011245403 A CN 202011245403A CN 112364057 A CN112364057 A CN 112364057A
- Authority
- CN
- China
- Prior art keywords
- event
- notification
- personnel
- message
- definition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 230000008569 process Effects 0.000 title claims abstract description 59
- 230000008859 change Effects 0.000 claims abstract description 5
- 230000000694 effects Effects 0.000 claims description 64
- 230000009191 jumping Effects 0.000 claims description 11
- 230000009850 completed effect Effects 0.000 claims description 9
- 239000007858 starting material Substances 0.000 claims description 7
- 239000003999 initiator Substances 0.000 claims description 5
- 230000001960 triggered effect Effects 0.000 claims description 3
- 238000009877 rendering Methods 0.000 claims description 2
- 230000009471 action Effects 0.000 description 12
- 230000005540 biological transmission Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 3
- 238000001914 filtration Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000013334 tissue model Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
- G06F16/24565—Triggers; Constraints
-
- 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/22—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computational Linguistics (AREA)
- Multimedia (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention belongs to the field of intelligent notification of business process execution, and particularly discloses an intelligent notification system of business process execution state, which comprises a notification rule definition module for determining the correct sending time of a message, a notification content definition module for determining the accuracy of message content, and a notified personnel algorithm matching module for determining that the message is notified to correct personnel; the notification rule definition module is based on ECA rules and is provided with an event definition unit, a condition definition unit and a notification range definition unit, wherein the event definition unit is used for defining simple events in the business process, and the occurrence of the events reflects certain state change in the business execution process. The invention realizes the accuracy, the flexibility and the expandability of the intelligent notification system of the service process execution state through the three modules of the notification rule definition module, the notification content definition module and the notified personnel algorithm matching module, and each module is clear and has strong expandability.
Description
Technical Field
The invention relates to the field of intelligent notification of business process execution, in particular to an intelligent notification system of business process execution state.
Background
BPMS (business process management system) standardizes, standardizes and automates the process of management lines by means of modern workflow software technology, thereby effectively improving business operation efficiency, reducing cost, and providing guarantee for realizing strategic objectives of enterprises, and is receiving more and more attention from enterprises. BPMS generally implements information transfer, data synchronization, business monitoring, and continuous upgrade optimization of enterprise business processes in the Internet manner, thereby implementing enterprise operations across applications, departments, partners, and clients. Obviously, the BPM not only covers the categories of process transmission and process monitoring of the traditional "workflow", but also breaks through the bottleneck characteristic of the traditional "workflow" technology.
In the process of executing the business process, it is very important to transmit correct information to correct participants and related personnel at correct time in order to ensure the smooth progress of the process. On one hand, the correctness and the accuracy of the message content are ensured, and the relevant information of the execution state of the business process is clearly expressed; on the other hand, to ensure that the message is notified to the correct relevant personnel at the correct time, if this cannot be done, the message loses its timeliness and accuracy, so the business process management system must ensure correctness, adaptability and usability.
Disclosure of Invention
The present invention is directed to a system for intelligently notifying the execution status of a business process, so as to solve the problems mentioned in the background art.
In order to achieve the purpose, the invention provides the following technical scheme: an intelligent notification system of a business process execution state comprises a notification rule definition module used for determining the correct sending time of a message, a notification content definition module used for determining the accuracy of the content of the message, and a notified person algorithm matching module used for determining that the message is notified to the correct person; the notification rule definition module is based on an ECA rule and is provided with an event definition unit, a condition definition unit and a notification range definition unit, wherein the event definition unit is used for defining simple events in a business process, the occurrence of the events reflects certain state change in the business execution process and is represented by a quadruplet (eventID, eventType, timetag and processID), the eventID in the quadruplet is an event identifier, the eventType is an event type, the timetag is an event occurrence timestamp, and the processID is an event related flow; the condition definition unit is used for defining conditions which need to be met when the condition variables are triggered to be sent in the event context; the notification range defining unit is used for defining the occurrence of an event and what conditions are met by a variable and sending a message.
Preferably, the definition of the notification rule includes an event definition, a condition definition and a notification scope definition. The definition of the notification rules is based on the implementation of ECA rules, rule RiDefining events E that trigger notifications during the course of a serviceiCondition CiAnd actions performed when event triggers and conditions are satisfied.
For event E that triggers a notification action1Notification rule R1The format is as follows:
[{"event":1,"condition":[],"action":[{"operation":"create","target":
"message"，"where"：{"message-type":"overtime","recipent":"starter"}}]}]
wherein, the value of the event field corresponds to the ID of the trigger event, and the value of the condition field represents the condition C required to be satisfied1The value of the action field represents the action to be executed, the value of the operation field represents the execution operation, the value of the target field represents the operation object, the value of the where field matches the information required by the message receiver and the message template selection, the value of the message-type represents the message type, and the value of the recipient field represents the mode of sending the message. The rules specify: whenever event E1And if the condition is not satisfied, a timeout message is sent to the initiator of the process of the activity.
Preferably, through filtering and pattern matching of simple events, meaningful aggregate events, i.e. complex events, can also be obtained, which are represented by quadruplets (eventID, patterren, timemap, processID). The pattern is a complex event pattern, the system detects the occurrence of the complex event by matching the field, and the rest fields have the same meaning as the simple event fields. The concept of the event is introduced into the intelligent notification system, so that the system has more practicability, flexibility and expansibility. The simple event types related to the active state in the current business process are: activity initialization, activity start, activity end, activity timeout, activity error, activity abandon.
Preferably, the notification content definition module comprises a character string template unit, a setting unit and a rendering unit, wherein the character string template unit is used for setting a variable character string in a java character string template, and the setting unit uses related variables in triggering events and conditions to render the variable character string set in a specified template; the specific definition step of the notification content definition module comprises the following steps:
A. setting a variable character string in a java character string template;
B. using related variables in the triggering event and the condition to render the set variable character string in the specified template;
C. and generating different types of message templates according to the selected message types during rule configuration.
Preferably, the notified person algorithm matching module matches the notified person by determining the relationship between the flow and the person, the relationship between the person and the person, and by triggering the event, the condition and the selected sending mode, and the value of the sending mode recipient field in the notification rule has: all: sending the information to all participants in the process; a starter: sending to the initiator of the process; related: sending the information to relevant personnel of relevant activities, if the relevant activities have binding personnel, sending the information to the binding personnel, otherwise, sending the information to possibly responsible personnel of the activities; department: the message will be sent to the department responsible for the activity responsible.
all: all activities in the flow are obtained by a predefined function findActityByID (processID). For the completed activity to which the staff has been assigned to execute, the corresponding staff can be obtained by getpersonidbynactityid (processID, activityID); for activities that have not been executed yet, the roles and the prescribed departments required for the activities may be obtained through predefined functions getRoleListByActivity (process id), getdepartment minlistbyactityandrole (process id, activity id, role id), getallpersofnrom oleAndDepartment (role id), locating the corresponding persons according to the roles and departments.
A starter: the corresponding person is directly obtained by the predefined function getstartid (processid).
related: when the transmission mode is set to this mode, a field of related activity is added. For the case that the related activity is completed, the corresponding person may be acquired by getpersonidbyaactivityid (processID, activityID); for the case that the related activities have not been completed, the roles and the prescribed departments required for the activities may be obtained through predefined functions getrallistbyactivity (process id), getdeparatmentlistbyactivity androle (process id, activity id, role id), getallpersofromrole and deparatment (role id), and the corresponding persons are located according to the roles and departments.
department: for the activity a obtained in S1, as in the above mode, the corresponding person of the activity is obtained through a predefined function, then the department to which the corresponding person belongs is obtained through a predefined function, and finally the person in charge of the corresponding department is located through a predefined function getallpersofromrolodeanddeputy (roleID, deparatmentid).
Preferably, the specific steps executed by the informed person algorithm matching module include:
s1: analyzing the event quadruplet, obtaining the value of the eventType field in the quadruplet, positioning the activity A related to the event in the flow, and jumping to S2;
s2: analyzing the rule, acquiring the value of the condition field, judging whether the corresponding condition is satisfied, if so, jumping to S3, and if not, jumping to S5;
s3: analyzing the rule, acquiring the value of the recipient field, and jumping to S4;
s4: according to different sending modes, namely, relevant context information in the process is obtained from the corresponding tuple, receiving personnel are matched, and the process jumps to S5 after matching is completed;
s5: and finishing matching.
Compared with the prior art, the invention has the beneficial effects that:
by the intelligent notification system, related personnel can be notified when the state of the business process is changed; the intelligent notification system of the invention is mainly divided into three parts: the intelligent notification system realizes the accuracy, the flexibility and the expandability of the intelligent notification system of the service process execution state through a notification rule definition module, a notification content definition module and a notified person algorithm matching module, and each module of the intelligent notification system is clear and has strong expandability.
Drawings
FIG. 1 is a block diagram of a system flow in an embodiment of the invention;
FIG. 2 is a diagram of an intelligent notification model architecture in an embodiment of the present invention;
FIG. 3 is a diagram of an organization model in a business process in an embodiment.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1-2, the present invention provides a technical solution: an intelligent notification system of a business process execution state comprises a notification rule definition module used for determining the correct sending time of a message, a notification content definition module used for determining the accuracy of the content of the message, and a notified person algorithm matching module used for determining that the message is notified to the correct person; the notification rule definition module is based on an ECA rule and is provided with an event definition unit, a condition definition unit and a notification range definition unit, wherein the event definition unit is used for defining simple events in a business process, the occurrence of the events reflects certain state change in the business execution process and is represented by a quadruplet (eventID, eventType, timetag and processID), the eventID in the quadruplet is an event identifier, the eventType is an event type, the timetag is an event occurrence timestamp, and the processID is an event related flow; the condition definition unit is used for defining conditions which need to be met when the condition variables are triggered to be sent in the event context; the notification range defining unit is used for defining the occurrence of an event and what conditions are met by a variable and sending a message.
The definition of the notification rule comprises an event definition, a condition definition and a notification range definition. The definition of the notification rules is based on the implementation of ECA rules, rule RiDefining events E that trigger notifications during the course of a serviceiCondition CiAnd actions performed when event triggers and conditions are satisfied.
For event E that triggers a notification action1Notification rule R1The format is as follows:
[{"event":1,"condition":[],"action":[{"operation":"create","target":"message"，"where"：{"message-type":"overtime","recipent":"starter"}}]}]
wherein, the event field represents the ID of the trigger event, and the condition field represents the condition C required to be satisfied1The action field represents actions to be executed when events occur and conditions are met, the operation field represents execution operation, the target field represents an operation object, the where field represents triggering event-related activities, the message-type field represents a message type, and the recipient field represents a message sending mode. The rules specify: whenever event E1And if the condition is not satisfied, a timeout message is sent to the initiator of the process of the activity.
Defining an event, namely defining a simple event E in a business process;
represented by the quadruple (eventID, pattern, timestamp, processID), the occurrence of an event reflects some state change during the execution of the service. Wherein the eventID is an event identifier, the eventType is an event type, the timetag is an event occurrence timestamp, and the processID is an event related flow.
In the embodiment, through filtering and pattern matching of simple events, a meaningful aggregation event, i.e., a complex event, can be obtained, and is represented by a quadruple (eventID, pattern, timestamp, processID). The pattern is a complex event pattern, the system detects the occurrence of the complex event by matching the field, and the rest fields have the same meaning as the simple event fields.
The concept of the event is introduced into the intelligent notification system, so that the system has more practicability, flexibility and expansibility.
The simple event types related to the active state in the current business process are: A. initializing activities; B. the activity starts; C. ending the activity; D. an activity timeout; E. an activity error; F. the activity is abandoned.
For example, for event E (1, B (1), "2020-09-30-10-30",23), where the first field 1 represents the event with an event ID of 1, the second field B (1) represents the start of activity 1, and the third field represents event E1At 10 o' clock 30/9/2020, a fourth field indicates that the event is associated with flow number 23. So the meaning of the quadruple is event E1Activity 1, corresponding to flow No. 23, began at 10 o 30 on month 9 and 30 of 2020.
Condition definition, defining event EiCondition C that a variable in the context that is to trigger a sending condition needs to satisfyi，CiIs any set of equalities or inequalities.
CiEquation 1, equation 2, equation m, inequality 1, inequality 2, inequality n
In actual use, the message sending scene can be more refined by using the condition.
The notification scope defines what events and variables occur and what conditions are satisfied when a message is sent.
Templatized definition of notification content:
A. setting a variable character string in a java character string template;
B. using related variables in the triggering event and the condition to render the set variable character string in the specified template;
C. and generating different types of message templates according to the selected message types during rule configuration.
Automatic matching algorithm for notified person
On-going traffic flowIn the process context, a workflow model consists of a set of activities. The activities being of different types, each activity aiConsists of a basic set of attributes, represented by a tuple (aid, name, type.).
Role r defines a set of functions or permissions required to perform certain types of activities. One role can inherit another role. If r1 inherits r2 (which can be expressed as
) Then role r1 will contain all the functions or permissions of r2 and this relationship is transitive.
Each employee may be assigned one or more roles to reflect their competency, while each employee s belongs to only one department d, available tuple (sid, r)1,...rnAnd d) represents.
When the workflow model is instantiated as a flow, activity A in the flowiThis relationship should be represented by a triplet (aid, r, d) according to which the role r and the prescribed department d required for the activity are assigned to the employee for execution. The above tissue model is shown in fig. 3.
The values of the transmission mode recipient field in the notification rule defined during process modeling are as follows:
all: to all participants in the process.
Starter: and sending the information to the initiator of the process.
C, related: sending the information to relevant personnel of relevant activities, and if the relevant activities have binding personnel, sending the information to the binding personnel; otherwise to the person for whom the activity may be responsible.
D.department: the message will be sent to the department responsible for the activity responsible.
The automatic matching algorithm of the notified person comprises the following specific steps:
s1, analyzing event EiFour-tuple, obtaining the value of eventType field in the four-tuple, locating the event E in the flowiThe associated activity a, jumps to S2;
s2, analysis rule RiObtaining the value of condition field, and judging whether the corresponding condition is satisfiedIf the result is not true, the step goes to S3, and if the result is not true, the step goes to S5;
s3, analysis rule RiAcquiring the value of the recipient field, and jumping to S4;
s4, acquiring related context information in the process from the corresponding tuple according to different sending modes, matching receiving personnel, and jumping to S5 after matching is completed;
and S5, finishing matching.
For the different transmission modes, the specific operation is as follows,
all: all activities in the flow are obtained by a predefined function findActityByID (processID). For the completed activity to which the employee has been assigned to execute, the corresponding person may be acquired by getpersonidbyactive id (processID, activityID); for activities that have not yet been executed, the role and the prescribed department required for the activity may be obtained by predefined functions getrallistbyactivity (process id), getdeparatmentlistbyactityandrole (process id, activity id, role id), getallpersofromroleindroleanddeparatment (role id), locating the corresponding person according to the role and the department.
A starter: the corresponding person is directly obtained by the predefined function getstartid (processid).
related: when the transmission mode is set to this mode, a field of related activity is added. For the case that the related activity is completed, the corresponding person may be acquired by getpersonidbyaactivityid (processID, activityID); for the case that the related activity has not been completed, the role and the prescribed department required for the activity can be obtained through predefined functions getrallistbyactivity (process id), getdeparatmentlistbyactivity androle (process id, activity id, role id), getallpersofromrole and deparatment (role id), and the corresponding person can be located according to the role and the department.
department: for the activity a obtained in S1, as in the above mode, the corresponding person of the activity is obtained through the predefined function, then the department to which the corresponding person belongs is obtained through the predefined function, and finally the person in charge of the corresponding department is located through the predefined function getallpersofromrolodeanddepartment (roleID, departme ntID).
In specific implementation, for event E (1, D (1), "2020-09-30-10-30",23), the rule of correspondence R is
[{"event":1,"condition":[],"action":[{"operation":"create","target":"message"，"where"：{"message-type":"overtime","recipent":"department"}}]}]
S1, analyzing the event E quadruplet, obtaining the value of the eventType field in the quadruplet as D (1), and positioning the event E related in the flow as activity A1；
S2, analyzing rule R, and obtaining the value of condition field as null list. If no condition is required to be met, jumping to S3;
s3, analysis rule RiAcquiring the value of a recipient field as default;
s4, obtaining the execution activity A through predefined functions getPersonadByActivtyID (processID, activity ID) or getRelistByActivty (processID, activity ID), getDeparttmlistByActivtyAndRole (processID, activity ID, roliID), getAlSonFlomRoleAndDepartment (roliID, deputy ID)1Then obtaining the corresponding department of the corresponding person through a predefined function, and finally positioning the responsible person of the corresponding department through a predefined function getAllPersonFormRoleAndDepartment (roleID);
and S5, finishing matching.
Not only can such a simple example be realized by the above three module implementation, but an event E can be fully usediTriggering, setting a number of different conditions and transmission modes to achieve more complex and accurate notification actions. For example for an event EiIn the rule RiIn setting different conditions
For the
Setting the corresponding recipient field as Mode1(ii) a For the
Setting the corresponding recipient field as Mode2。
Then rule RiCan be expressed as:
[{"event":i,"condition":
"action":[{"operation":"create","target":
"message"，"where"：{"message-type":
"recipent":"Mode1"}}]}
{"event":i,"condition":
"action":[{"operation":"create","target":
"message"，"where"：{"message-type":
"recipent":"Mode2"}}]}]
in this way, the same trigger event E can be realizediAnd under different conditions, different sending modes are selected to send the message to different people.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (4)
1. An intelligent notification system of a business process execution state is characterized by comprising a notification rule definition module for determining the correct sending time of a message, a notification content definition module for determining the accuracy of the content of the message, and a notified personnel algorithm matching module for determining that the message is notified to the correct personnel; the notification rule definition module is based on an ECA rule, and is provided with an event definition unit, a condition definition unit and a notification range definition unit, wherein the event definition unit is used for defining a simple event in a business process, the occurrence of the event reflects certain state change in the business execution process, and the event definition unit is represented by a four-tuple event ID, event type, timetag and processID, the event ID in the four-tuple event is an event identifier, the event type is an event type, the timetag is an event occurrence timestamp, and the processID is an event related flow;
the condition definition unit is used for defining conditions which need to be met when the condition variables are triggered to be sent in the event context;
the notification range defining unit is used for defining the occurrence of an event and what conditions are met by a variable and sending a message.
2. The system of claim 1, wherein the notification content definition module comprises a string template unit, a setting unit and a rendering unit, wherein the string template unit is configured to set a variable string in a java string template, and the setting unit renders the variable string set in a specific template using a trigger event and a relevant variable in a condition; the specific definition step of the notification content definition module comprises the following steps:
A. setting a variable character string in a java character string template;
B. using related variables in the triggering event and the condition to render the set variable character string in the specified template;
C. and generating different types of message templates according to the selected message types during rule configuration.
3. The system of claim 1, wherein the notified personnel algorithm matching module matches the notified personnel by determining the relationship between processes and personnel, the relationship between personnel and personnel, and by triggering events, conditions and selected sending modes, and the sending mode recipient field in the notification rule has the following values: all: sending the information to all participants in the process; a starter: sending to the initiator of the process; related: sending the information to relevant personnel of relevant activities, if the relevant activities have binding personnel, sending the information to the binding personnel, otherwise, sending the information to possibly responsible personnel of the activities; department: the message will be sent to the department responsible for the activity responsible.
4. The system of claim 1, wherein the informed human algorithm matching module performs specific steps comprising:
s1: analyzing the event quadruplet, obtaining the value of the eventType field in the quadruplet, positioning the activity A related to the event in the flow, and jumping to S2;
s2: analyzing the rule, acquiring the value of the condition field, judging whether the corresponding condition is satisfied, if so, jumping to S3, and if not, jumping to S5;
s3: analyzing the rule, acquiring the value of the recipient field, and jumping to S4;
s4: according to different sending modes, namely, relevant context information in the process is obtained from the corresponding tuple, receiving personnel are matched, and the process jumps to S5 after matching is completed;
s5: and finishing matching.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011245403.4A CN112364057A (en) | 2020-11-10 | 2020-11-10 | Intelligent notification system for business process execution state |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011245403.4A CN112364057A (en) | 2020-11-10 | 2020-11-10 | Intelligent notification system for business process execution state |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112364057A true CN112364057A (en) | 2021-02-12 |
Family
ID=74509449
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011245403.4A Pending CN112364057A (en) | 2020-11-10 | 2020-11-10 | Intelligent notification system for business process execution state |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112364057A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1816811A (en) * | 2003-12-05 | 2006-08-09 | 松下电器产业株式会社 | Information notification apparatus and information notification method |
| CN102562162A (en) * | 2011-12-14 | 2012-07-11 | 北京邮电大学 | Event-handling-based coal mine alarm system and method |
| CN104618433A (en) * | 2014-12-26 | 2015-05-13 | 国家电网公司 | ECA (Event-Condition-Action) rule based service combination method |
-
2020
- 2020-11-10 CN CN202011245403.4A patent/CN112364057A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1816811A (en) * | 2003-12-05 | 2006-08-09 | 松下电器产业株式会社 | Information notification apparatus and information notification method |
| CN102562162A (en) * | 2011-12-14 | 2012-07-11 | 北京邮电大学 | Event-handling-based coal mine alarm system and method |
| CN104618433A (en) * | 2014-12-26 | 2015-05-13 | 国家电网公司 | ECA (Event-Condition-Action) rule based service combination method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Aiken et al. | Integrating expert systems with group decision support systems | |
| US8301573B2 (en) | Dynamic interface between BPSS conversation management and local business management | |
| AU2005310976B2 (en) | Performance monitoring witin an enterprise software system | |
| CN1617501B (en) | Flexible architecture for notifying applications of state changes | |
| US8655832B2 (en) | Publishing activity tasks in a collaborative environment | |
| US20040204947A1 (en) | System and method for generic business scenario management | |
| US20110307474A1 (en) | Party reputation aggregation system and method | |
| US20040119752A1 (en) | Guided procedure framework | |
| US7882433B2 (en) | System and apparatus for managing personal and work-related matters | |
| US10528906B2 (en) | System and method for responsive process management driven by business visibility and complex event processing | |
| CN107809369A (en) | Communications status processing method and communications status processing unit | |
| Poort et al. | Architecting as a risk-and cost management discipline | |
| US20100169149A1 (en) | Motivating equitable behavior in calendar events | |
| Neal et al. | Identifying requirements for business contract language: a monitoring perspective | |
| US20200005207A1 (en) | Blockchain tracking of organizational time for cost analysis and scheduling | |
| CN112597511A (en) | Remote government affair service cooperation method and device | |
| CN112364057A (en) | Intelligent notification system for business process execution state | |
| CN112633823A (en) | Real-time tracking method of production progress, storage medium and computer equipment | |
| CN109118151A (en) | A kind of work order transaction methods and work order transacter | |
| CN114254881A (en) | Data processing method and device, electronic equipment, readable storage medium and product | |
| US20070203730A1 (en) | Real property transaction database and method to monitor the status of a real property transaction | |
| US20150127402A1 (en) | Method and system for structuring information background of the invention | |
| Barton | New Labour's management, audit andwhat works' approach to controlling theuntrustworthy'professions | |
| CN110825354A (en) | Intellectual property agency service management system based on SOA system | |
| TWI530892B (en) | Method and system for structuring inforamtion |
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 |