Scenario: an production EDI enviroment, which receives a lot of different kind of flat files, which needs to be converted to XML, and depending on the type of the document, it needs to be processed (database updated, new XML files generated, etc.)
In this scenario, we can have a lot of exceptions:
- flat files can be in the wrong format (columns out of order, data in the wrong format, mandatory data absent, etc.)
- the sender can be unindentified (os misindentified)
- a business rule can be violated, and in this case, the transaction must be rejected
- and many other cases.
When all those mess happens, an alert must be sent to a console; and the console can forward the alert to someone who is responsible for that kind of alert/that document.
Does GNU6 have any framework supporting all these needs??
If it has to be done, how should it be modeled?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Scenario: an production EDI enviroment, which receives a lot of different kind of flat files, which needs to be converted to XML, and depending on the type of the document, it needs to be processed (database updated, new XML files generated, etc.)
In this scenario, we can have a lot of exceptions:
- flat files can be in the wrong format (columns out of order, data in the wrong format, mandatory data absent, etc.)
- the sender can be unindentified (os misindentified)
- a business rule can be violated, and in this case, the transaction must be rejected
- and many other cases.
When all those mess happens, an alert must be sent to a console; and the console can forward the alert to someone who is responsible for that kind of alert/that document.
Does GNU6 have any framework supporting all these needs??
If it has to be done, how should it be modeled?