Recently, the work pressure is relatively high, one is the research and development of the company's OA system (java), and the other is the hospital's system program (C#), which mainly implements functions such as message notification. One thing in common between these two systems is that the frameworks have implemented the functions based on the workflow engine. This article mainly shares the comparison of the use of the two workflows developed in different languages.
1.java version, workflow engine activiti, the flow chart is a standard bpmn flow chart, classified as "start", "user task", "gateway", "end" and many other standardized icons, when designing the process, It is necessary to specify a handler on the user task node, so that when the process reaches this node, it will be automatically triggered, and an instant message reminder will be sent to the corresponding handler. It is also a case that meets the needs of the oa system I am doing now.
2. C# version, this is a process management tool based on C/S, and also has a visual process design interface, but the content that can be set is relatively simple, including "start", "interaction node", "logical node", "End node" is not a drag-and-drop method, but a click, and then click on the canvas to come out. When drawing a connection line, you must first select the previous processing node, and then press and drag to the next node. , completes the connection of two nodes, it sets the control of process processing, not on the node itself, but on the connection line. Process variables will be set on the process node, and judgment conditions based on process variables can be added to the connection line, and the process will continue when the conditions are met.
Of course, both are based on the standard bpmn flow chart. From the user's point of view, the java version is good for drawing and setting variables, it feels very natural, and it is very in line with the operating habits of people who use software in general, but from the flow chart, some details are not reflected very well . The C# version is just the opposite. Because the condition is judged on the connection line, you can intuitively know what processing action is in this step, but the disadvantage is that the operation experience of the process of drawing the flowchart is relatively poor, and sometimes the screen will be inexplicably blank. This feature needs to be turned back on to continue editing.
I recently opened a website, which has just been launched. There are still many shortcomings. I hope you can give me more advice.
The website is: www.yeegee.com
If you have any suggestions or comments, you can leave me a message, or you can join the QQ group 760728310 for communication