Override Routing Scenario
In this example of an override routing scenario, your organization expects to receive documents of a single Document Type from multiple Partners.
If PortX has been configured to receive a document of this Document Type, PortX routes the document to an internal API.
However, one partner uses a variation of the Document Type, so you must override the standard Map that you use to transform that partner’s Document Type to your internal Document Type before routing.
If PortX has not been configured to receive a document of this Document Type, PortX rejects the document.
Background Reading
- Actors, Relationships and Artifacts
-
Introduces foundational PortX terminology.
- Transaction-Processing Framework
-
Explains how PortX works.
Actors
In this scenario, there are three Actors:
-
Partner A (configured as PartA)
-
Partner B (configured as PartB)
-
Partner C (configured as PartC)
-
YourCompany B2B
-
Any
Relationships
There are four Relationships in this scenario. Artifacts are distributed among the relationships according to how they are used. For example, the internal Endpoint API is used in all scenarios, so it is configured in the *YourCompany B2B : Any* Relationship. The Endpoints RecFromA, RecFromB, and RecFromC are used only by specific partners; therefore they are configured in the relationships that correspond to those partners. Table 1 describes these Relationships and identifies their contents.
Relationship | Description | Contains |
---|---|---|
YourCompany B2B : Any |
Universal relationship between your company any partner |
Contains Artifacts used across all partners with whom you do business |
YourCompany B2B : PartA |
Your organization’s relationship with the partner with whom you are doing business (in this case, PartA) |
Contains artifacts used only with Partner PartA |
YourCompany B2B : PartB |
Your organization’s relationship with Partner |B |
Contains artifacts used only with Partner PartB |
YourCompany B2B : PartC |
Your organization’s relationship with Partner PartC |
Contains artifacts used only with Partner PartC |
Artifacts
This tables and flow diagrams in this section identifies:
-
Artifacts that must be configured in order for a given document to be routed (that is, not rejected)
-
The Relationship in which the artifacts are configured
YourCompany B2B : Any
Artifacts in this Relationship are accessible from all Partner Relationships. Therefore, these artifacts, tabulated in Table 2, appear in each of the Transaction diagrams that follow.
Artifact | Artifact Name | Description | Configured on page |
---|---|---|---|
Y |
Document Type you use internally in your company |
||
X |
Document Type you use internally in your company |
||
Y-to-X |
Transforms a document of Document Type Y to a document of Document Type X |
||
Y-to-X |
Channel that transforms a document of Document Type Y into a document of Document Type X |
||
API |
Endpoint that points to an internal API |
||
X-to-API |
Channel that sends a document of the internal Document Type X to Endpoint API |
YourCompany B2B : PartA
Artifact | Artifact Name | Description | Configured on page |
---|---|---|---|
RecFromA |
Endpoint that points to an internal API |
||
Y-to-X-to-API |
Combination of the Source Channel Y-to-X and the Target Channel X-to-API. It receives a document of Y, maps it to a document of X and then sends it to Endpoint API. In this Transaction, the From Partner is configured as PartA and the To Partner as YourCompany B2B. |
YourCompany B2B : PartB
Artifact | Artifact Name | Description | Configured on page |
---|---|---|---|
RecFromB |
Endpoint that points to an internal API |
||
Y-to-X-to-API |
Combination of the Source Channel Y-to-X and the Target Channel X-to-API. It receives a document of Y, maps it to a document of X and then sends it to Endpoint API. In this Transaction, the From Partner is configured as PartB and the To Partner as YourCompany B2B. |
YourCompany B2B : PartC
Artifact | Artifact NamDescription | Configured on page | Endpoint |
---|---|---|---|
RecFromC |
Endpoint that points to an internal API |
||
Y' |
Document Type you expect to receive from this partner that is a variation on the standard for this Document Type. |
||
Y'-to-X |
Maps document of Y' to document of X |
Outcomes
If all artifacts in the following table are configured appropriately, then the outcome of any of the partners in the scenario sending a document of Y to the Endpoint specific to their relationship with YourCompany B2B is that PortX will route the document to that Endpoint.
If any artifact in the relationship between the partner and YourCompany B2B or in *YourCompany B2B : Any* is incorrectly configured (or not configured at all), then PortX will reject the document.
For more information, see Outcome Details.
Outcome Details
Document Accepted and Routed
Partner PartA sends a document of Document Type Y to Endpoint RecFromA
PortX:
-
Receives the document at Endpoint RecFromA
-
Attempts to resolve routes
-
Finds Transaction Y-to-X-to-API
-
Executes Y-to-X-to-API, which transforms the document to X
-
Sends the document to Endpoint API.
PartB sends document (Y) to Endpoint RecFromB
PortX:
-
Receives Document Y at Endpoint RecFromB
-
Attempts to resolve routes
-
Finds Transaction Y-to-X-to-API
-
Executes Y-to-X-to-API, which transforms the document to X
-
Sends the document to Endpoint API.
PartC sends document (Y') to Endpoint RecFromC
PortX:
-
Receives the document at Endpoint RecFromC
-
Attempts to resolve routes
-
Finds Transaction Y'-to-X-to-API
-
Executes that transaction, which transforms the document to X
-
Sends the document to Endpoint API.
Document Rejected
Partner PartA sends a document of Document Type Z to Endpoint RecFromA. Document Type Z is not configured in Relationship *YourCompany B2B : Any*; PortX rejects the document.
PortX:
-
Receives the document
-
Attempts to resolve Routes
-
Does not find a corresponding Transaction
-
Rejects the document.