Please enable JavaScript.
Coggle requires JavaScript to display documents.
Outbound Transaction Support (GUI Changes (Add support for Context Based…
Outbound Transaction Support
GUI Changes
Add option of Outbound transaction in Transaction Template
Add support for Context Based Routing
For the file-based applications, it will support file name parameter in routing rule
Add support for Context Based Routing based on other parameters in future release of AC 2.0 :no_entry:
For the file-based application, do we need to add support for routing based on file path parameter in v1 of AC 2.0? It is not yet supported in Adeptia Connect 1.0 :silhouettes:
Add support for Content Based Routing in future release of AC 2.0 :no_entry:
Add support for Broadcast option
Backend Changes
Changes in AC 2.0 PF to support outbound process
Approach 2 (used in AC 1.0): Insert a job in the backend database in the main process flow and invoke a thread in kernel that will read that job, identify the partners that satisfies the routing rule condition and then invoke subprocess flow
Another thread runs in the backend that updates the log record for the company after all subprocess flow (invoked for each partner) have completed
A new thread (that will be started on kernel boot up) runs in the backend that takes care of recovery - if system goes down during the process of invoking the subprocess flow for each partner
Approach 1 (Recommended)
: Loop inside the main process flow for each partner that satisfies the routing rule condition and spawn subprocess flow :check:
The main process flow will wait at the end for all spawned subprocess flow to complete via sync action and then update the log record for the company
Recovery will be handled as part of main process flow design by adding checkpoints at relevant steps
Add support in PF initialization code for outbound scenario
Add support for subprocess flow that will be executed for each partner that satisfies the routing rule
Transaction execution logging
Have separate log entry for company and each partner execution that satisfies the routing rule condition
Not sure how single log entry approach will work for the outbound scenario - like we did for inbound. Need to discuss :silhouettes:
Maybe, we go with the approach of having multiple log entries (one for company and each partner) in case of broadcast option while for routing rule (assuming that only one partner satisfies the condition) we have one log entry (like we have it for inbound scenario) :silhouettes: