In one of the previous examples that talked about convoys within BizTalk, I had the following orchestration:In one of the previous examples that talked about convoys within BizTalk, I had the following orchestration:
The purpose of this map within the orchestration was to receive a message that followed the Claim schema, transform it into the ClaimValidation schema and set the Status to CONTRACT VALIDATION COMPLETED. It’ll see a bit contrived, but we can move the map so that it’s called on the receive port if required so that we’ll always be dealing with a ClaimValidation message inside of the orchestration.
We’ll also use the map from the previous example which determined the Pass/Fail Validation response based on whether or not the ClaimID is odd.
Within the orchestration we’ll still construct an outbound message and set the Status.
Since the inbound map (which we’ll discuss in a bit) happens before the orchestration runs, the receive port deals only with messages of the ClaimValidation schema.
After the orchestration is deployed, we can specify the inbound map on the physical receive port in BizTalk Administration Console.
With this in place, we can drop messages of the Claim and ClaimValidation schemas into the receive locations. If the message is of the Claim schema, it will first be transformed into the ClaimValidation schema, and if it’s of the ClaimValidation schema it will pass directly through to the orchestration.
\Source code for this example can be found here.