The Outbound EDI Business Process inherits two tasks. At a minimum, one additional task is added.
- SetRouteFieldValues – This inherited task populates Field values from the Outbound EDI Route.
- Execute Transformation – This task indicates the Ruleset to transform the source data
to target format and specifies the Transformation Settings.
- SetExitStatus – This inherited task sets the Exit Status as true (pass) or false (fail).
The Outbound EDI Business Process inherits three parameters.
- route – This contains the Outbound EDI Route that references this Business Process.
This parameter assists the SetRouteFieldValues task to populate the Field values
defined within the Outbound EDI Route.
- context – This contains the values passed into the Ruleset to populate the variables
on its Variables panel in the glb and env
- inputDataFragment – This contains one Data Group.
Indicating the Ruleset can be done in two ways. You can do so directly or indirectly (“hot swap” it at runtime via the Inbound EDI Route).
It is best practice to use a Field in this Business Process to “hot swap” the Ruleset. This way, in the trading-partner-specific Outbound EDI Route you can specify either a “core” Ruleset (one-size-fits-all)
or you can treat individual trading partner needs individually by specifying a trading-partner-specific Ruleset.
But as all trading partners receiving EDI invoices from us will have their message(s) transformed the same way – using the same Ruleset – we will not use a Field here.
Please sign in to leave a comment.