1. Automatic judgment of decision authority using OpenRules
2018/11/8
Automatic judgment of decision authority using OpenRules
Yoshihito NAKAYAMA
NTT DATA INTRAMART Corporation
Thank you for this chance opportunity for presentation.
I’d like to start from self introduction.

2. Self-Introduction
-Founded NTT DATA INTRAMART CORPORATION in NTT DATA INTRAMART has acquired No. 1 share in the Japanese workflow market and listed on TSE Mothers in Currently it has installed over 6000 companies in Japan and Asia mainly. -On one hand, enrolled in doctoral course at School of Engineering, The University of Tokyo. -Received the best paper special award at ISSJ (Information Systems Society of Japan) in Research interest includes BPM, Decision Management, Process Mining, and workflow.

3. Major Logos in APAC & China
2018/11/8
Insurance
Banking
Manufacturing, Retail & Trading
These are our client’s logo. Not only Japan but also APAC , we have various type of clients.
Telecom, Public Authority

4. Features of IM-BPM 【IM-BPM】 IM-BPM is in full compliance with BPMN2.0
2018/11/8
【Java/Script Development】
【IM-BIS/Workflow】
【IM-BPM】
【IM-LogicDesigner】
【IM-FormaDesigner】
【メールサーバ】
【IM共通マスタ】
メールアドレス新規登録
ユーザ登録
完了通知
These are outline of our product. The center of this picture is our BPMS named IM-BPM.
IM-BPM is in full compliance with BPMN2.0
IM-BPM can be used to maximize the function of intra-mart which is the integration platform.
IM-BPM also can realize the short term development by combining with some non-coding tools of intra-mart.
Also, user department can create their own process flow easily.
IM-BPM can integrate the other intra-mart functions
IM-BIS （This is a Workflow Design tool. The approval workflow that is mainly operated by human）
IM-Forma Designer（Screen Design tool. User can create their own application easily by drag & drop）
IM-Logic Designer（Simple Logic making Tool. User can create their own logic on the screen by drag & drop also. Logic Designer can connect to existing system like ERP using standard adapter）
Open Rules（Rule definition and execution. We are providing Open Rules as OEM by embedding with our products）
Java/Script Development (Off course, user can write complex code and can run on the intra-mart platform)
【OpenRules】

5. BPM/Workflow Hybrid Concept
2018/11/8
①Tasks requiring approval are handled by approval flow of IM-WF ＋
＜ＩＭ－ＢＰＭ＞
③Processing result of the workflow is returned to BPM, and BPM proceed to the next task according to the approval result.
privilege
master
applicant
approver
approver
final
decision-maker
＜ＩＭ－Workflow＞
job title
master
Integration with IM-BPM and IM-Workflow makes it possible to define business process and approval flow separately. Tasks requiring approval on the business process side are handled by approval flow of IM-Workflow. After final approval, business process can be advanced to the next task.
department master
②In the Workflow, approval is carried out with multi-step approval and conditional branching and approval trait being recorded.

6. Abstract(1)
2018/11/8
Complex authorization of approval -Complex conditional branches, consultation, delegation of authority to approve and concurrent administration
Difficult to provide all of them as standard functions of the workflow, so it has often been customized individually.
This is my presentation point of today.
In China and Southeast Asia including Japan, there are many companies with complex authorization of approval, so complicated controls such as complex conditional branches, consultation, delegation of authority to approve and concurrent administration is required when introducing the workflow system.
However, since the setting patterns are different for each company, it is difficult to provide all of them as standard functions of the workflow, so far it has often been customized individually.

7. Judgment of workflow branch
Abstract(2)
2018/11/8
Automatic judgment of decision authority : realized by combining workflow system with rule engine. It is possible to drastically reduce the cost of introducing the workflow.
Explain concrete cooperation method of workflow and rule engine by taking "intra-mart" and "Open Rules" as an example.
Open Rules
Collaboration with IM-Workflow
Judgment of workflow branch
Decision Table
Therefore, in order to solve these problems, automatic judgment of decision authority is realized by combining workflow system with rule engine. It is possible to control the conditional branching with noncoding and to dynamically arrange authority for decision. Since automatic processing of workflow can be realized without customizing, it is possible to drastically reduce the cost of introducing the workflow.
In this presentation, we will explain concrete cooperation method of workflow and rule engine by taking "intra-mart" and "OpenRules" as an example.
Dynamically arrangement of authority for decision

8. Cooperation between workflow and rule engine (1)
2018/11/8
フロー分岐条件設定画面
Branch Condition Setting Screen
Branch Condition Setting Screen
Node name
Branch start
Branch start method
◎　Branch start with rule definition
○　No definition
Screen image of “IM-Workflow”
Branch target task name
Branch rule name
Approval
Configration
Approval
Configration
Registration
Start
Application process start
Branch start
Approval process start
Setting branch rules
Rules of Flow Setting Screen
It is possible to set a branching rule based on the value of the input items on the target screen.
This is a cooperation example of workflow and rule engine.
In the middle of workflow, there is a branching point, and user can call branch condition setting screen directory.
In this screen, it is possible to set a branching rule based on the value of the input items on the target screen.
See this screen, all input items of application in this task are listed on this left side automatically.
Then user can select the comparison method and condition value on this right side.
Rule name
Configuration
When all conditions are satisfied
When either condition is satisfied
Condition key
Comparison method
Condition Value
Clear
Task
Application/Approval Start
Fix Type
Item
Task
Is different from the next　　　　　　　▼
Type/ String
Item

9. Cooperation between workflow and rule engine (2)
2018/11/8
Approvers are dynamically placed according to the approval amount.
決裁金額が10万円未満の場合
When the approval amount is less than 1,000 USD
Node name
Dynamic Approval
Approvers will change according to the number you entered.
Target Approver
Search
Approval
amount
Target Type
Target Name
User
K.Aoyagi
決裁金額が50万円未満の場合
When the approval amount is less than 5,000 USD
Application
Application Start
Node name
Dynamic Approval
Target Approver
Search
Target Type
Target Name
Case name
Application for training videos
User
S.Katayama
Applicant
Yoshihito Nakayama
Application Date
決裁金額が200万円未満の場合
When the approval amount is less than 20,000 USD
Organization
Sales department
Priority
Normal ▼
Node name
Dynamic Approval
Coment
Target Approver
Search
Attachment files
Target Type
Target Name
Flow definition
Node Namec
Required Setting
Setting Condition
According to the results of branching rules, OpenRules can set target persons to be processed dynamically.
The setting of dynamic approval is automatically set when the application button is pressed down after inputting the values on the screen.
On the screen below, approvers are dynamically placed according to the approval amount
Organization
Sales Department
Dynamic Approval
Please set the target approver
Other
決裁金額が200万円以上の場合
When the approval amount is more than 20,000 USD
Application Start
Node name
Dynamic Approval
Target Approver
Search
Target Type
Target Name
Title
President

10. Cooperation between workflow and rule engine (3)
2018/11/8
IM-Workflow Screen
Dynamic Approval Setting Screen
Screen
Copy
Open
Change name
Remove
External Connection
Connection List
Dynamic Approval
Setting
History
History Setting
BAM Setting
File Attachment
Start
Application process start
Dynamic Approval
Dynamic Approval Setting
External Connection
How to set Dynamic Approver
Manual Setting
Change Approver OK
Confirm
Judgment Node
External Connection
Application Strat
Launch Data Mapper Screen
Dynamic Approval Setting
External Connection ： Setting the approver by OpenRules
How to set Dynamic Approver
Manual Setting ： Setting the approver by user. In the case of OpenRules,
　　　　　　　　　　　 only narrow down searchable users(see next presentation). Auto Setting ： Specify approver by OpenRules
Change Approver
It can set only if “Auto Setting”.
Can change the approver decided by OpenRules.
This is how to set dynamic approval node in workflow. Click the dynamic approval node and call setup screen.
User can select how to set dynamic approver, “Manual setting” is function that user can choose the approver from the candidate list.
OpenRules can narrow down the approval able users.
“Auto setting” is function that specify the approver automatically.
“Change approver” is function that can be set only if “Auto setting” mode.
User can change the approver decided by OpenRules.
Registration
Cancell

11. Cooperation between workflow and rule engine (4)
2018/11/8
In the case of “Manual Setting”, Specify "Search range of users to set as dynamic approvers" by rule engine (Open Rules).
Setting contents of “compare”
ge ⇒ Higher organization search
eq ⇒ Search specified only
le ⇒ Lower organization search
Data Setting
Process Setting No
Judgment Code
Company Code
Department Set Code
User Code
Department Code
Compare Code
Position Code
Public Group Set Code
Public Group Code
Role Code
Setting screen of dynamic approval user
In the case of “Manual Setting”, user can specify "Search range of users to set as dynamic approvers" by OpenRules.
See the setting contents of “compare”. “ge” means higher organization search. “eq” means only specified search. “le” means lower organization search.
For example, see this line. Only users belonging to the higher organization Include dept_sample_11 can be searched.
See this line. Only users belonging to the lower organization Include dept_sample_10 can be searched.
See this line. Only ”aoyagi” can be searched.
This is screen image. When setting a dynamic approval user, the "refining condition" item is displayed as below and only the user within the condition can be set as a approver.
Node name
Dynamic approval
Refining condition
Approver
Search @ Refining condition
Type of Approver
Approver
Registration
Type of approver
Approver
Organaization
Dept_sample_11[higher]

12. Cooperation between workflow and rule engine (5)
2018/11/8
How to set “Process Setting No.” and “Judgment Code”
Data Setting
Parameters that need to be set by “Judgment Code”
Judgment Code
Parameter 1 2 3 4 5 6 7
Company Code ○
User Code
Department Code
Position Code
Public Group Code
Role Code
Process Setting No
Judgment Code
According to the judgment code, the classification of the approval target is dynamically decided.
Specify the order　number of nodes
This slide show how to set the “Process Setting No.” and “Judgment Code”.
“Process Setting No.” is the order number of Node, and “Judgment Code” is the classification of the approval target.
So according to the “judgment code”, the classification of the approval target is dynamically decided.
And right picture show the parameter that need to be set by “Judgment Code”.
By setting contents of “compare”, the scope of approver is determined, “higher” or “equal” or “lower”.
1 ⇒ User
2 ⇒ Department
3 ⇒ Public Group
4 ⇒ Position
5 ⇒ Role
6 ⇒ Department ＋ Position
7 ⇒ Public Group ＋ Role
Setting contents of “compare”
ge ⇒ Higher organization search
eq ⇒ Search specified only
le ⇒ Lower organization search

13. Relationship between Open Rules and IM-Workflow
2018/11/8
Relationship diagram
Data Setting
Attribute Setting
Rule Execution (Execute processing in execution order)
Based on the created decision table, a judgment is carried out with the following flow.
(1) Pass values ​​from the IM - Workflow screen to the Data Mapper. (2) Values ​​are passed to the data source definition according to Data Mapper mapping. · Data mapper is a function that maps screen items and values ​​passed to Rule Engine. · By the data source definition, the Decision name to be executed, the request (variable input from IM - Workflow to Rule Engine), and the response (variable to be output from Rule Engine to IM - Workflow) are set. (3) The Decision set in the data source definition is read and the value is passed to DecisionObject. (4) Corresponds the value of DecisionObject with Glossary, and sets data to be used by Rule Engine. (5) Set the attribute with the value set in Glossary. With this attribute setting, set the data type and initial value to be used in OpenRules. (6) Execute the rule based on the set data. (7) Execute DecisionTable and Method in the order described in Decision. (8) Reflect the execution result of the rule to the data. (9) Correspond the reflected data to the Glossary. (10) Corresponds the value of Glossary and DecisionObject, and returns the value to the data source definition. (11) From the data source definition, the value is returned to the data mapper. (12) From the data mapper, the value is returned to the screen of the IM - Workflow, and the return result is displayed on the screen.
IM-Workflow
Definition of data source
Data Mapper
Screen

14. Data Mapper -> Data Source Difinition
2018/11/8
Values ​​passed to Rule Engine
Screen items
Definition of Data Source
XXXX.xls（Glossary）
Attribute Setting of Open Rules
· Data mapper is a function that maps screen items and values ​​passed to Rule Engine. · By the data source definition, the Decision name to be executed, the request (variable input from IM - Workflow to Rule Engine), and the response (variable to be output from Rule Engine to IM - Workflow) are set.

15. Workflow and rule engine collaboration case in Japan & APAC
2018/11/8
These are workflow and rule engine collaboration case in Japan and APAC.
All of them are big companies that have complex workflow and organization.
So this collaboration works efficiency very well and can reduce the installation cost of workflow compare with only using workflow.
At average, it became from quarter to one fifth.
Thank for listening.