Problems with "Production Task Order" delivery?

永无真爱

Process: The company's business receives the production task, reports it to the "plan", then leads the "approval", and then reports to the production department and quality inspection department to start production.

Requirement: While recording the data of the entire production task order, ensure that the report is reported to the leader at the first time; the production task order that is also approved can be notified to the production department and the quality inspection department at the first time.

Please talk about experienced brothers.

ryan01

Just say two scenarios for reference:

First, some event processing mechanisms can be used. When an event (such as "reporting a plan") occurs, another event (leader approval) is triggered. If it is in the local area network, remote method call can be used here.

Second, use MSMQ. Establish two MQs. When there is a plan to report, send a message to Q1, and the leader can receive this message in time by using asynchronous monitoring (peek or recive) in MQ; after the leader agrees, send a message to Q2, and the production department can Receive the message in the same way.

blankaxwh

Seeing what you do n’t know is how to get the status change message. There are many ways to solve this, depending on the structure of your system. If it is an entire OA system, then it is simple. The internal messages can be various All kinds. If it is external data, you can consider using Socket, MSMQ, DB and so on.

永无真爱

Yeah, what I think about is mainly the problem of message passing, because its timeliness requirements are very high, it is necessary to minimize the delay in time,
The MSMQ said byryan01is indeed a good way, but I have no experience in this area, and I will consider this kind of scheme.

By the way, this is an entire OA. I don't know ifblankaxwhcan help list several good solutions.
Of course, if there are source code examples, that would be even more appreciated.

blankaxwh

Source code. . . This is a bit overdue, huh, huh.
Check again whether it is WebForm or WinForm.
If it is Web, consider AJAX. If it is WinForm, MSMQ is really worry-free and easy to use. You can pay attention to the namespace System.Messaging. There are a lot of examples of MSMQ on the Internet.
If you are unfamiliar, you can make a Socket method, but the Socket class in .NET is really not very convenient. The real-time nature of these two methods can be guaranteed. But passing data will be a bit more troublesome, you can consider the way of combining with DB :) (recommended)

永无真爱

Thank you very muchblankaxwhfor giving me such a good suggestion and I will try it (I want to keep this post for a while so that I can ask you in time if there is any problem, please understand)

wanted

mark

永无真爱

Well, all the problems are solved!
Thank you all!