CIC can identify source data based on source directory location and then facilitate the specific routing of different document types, payloads, or files to their respective Transformation business flows or processes. This is accomplished by using a specific Data Flow configuration of Partner Mailbox Endpoint subfolders (as source) and event processing in the transformation engine.
Benefits include:
- An integration design that allows all documents to flow through one Event (as part of Transformation Endpoint configuration).
- A streamlined Data Flow creation during the onboarding process.
- The potential for one Partner Mailbox to Transformation Data Flow to be able to manage all inbound documents of a specific type for all trading partners.
Note: This functionality applies to Partner Mailbox-to-Transformation Data Flows only.
How it works
Consider a use case in which your Partner Mailbox contains a subfolder structure meant to capture similar document types for several trading partners. The Partner Mailbox is the source Endpoint that is part of a Dataflow using a Transformation Endpoint as the destination.
The parent directory for this subfolder sample is named Inbound_FF_Invoices containing subfolders for Acme, BigStore, Costco, and Depot.
The Transformation Endpoint associates an Event (the object in CIC Studio), which is the method by which data enters the Transformation Engine for further processing as part of the Data Flow.
By associating the Event with specific metadata in the Partner Mailbox Endpoint (subfolders), CIC can look at the inbound path of each file and determine how to process it in the Transformation Engine.
See the step below that describes how to edit an Event so that it can work with the associated Endpoint's metadata. This step is required for any Event you plan to associate with Partner Mailbox subfolders.
Associate the Event in CIC Studio
From the Event editor's Parameter section, create a parameter explicitly named cicPayloadLocation.
This parameter must also be mapped to a corresponding Business Process parameter within the Parameter Mapping area of the BP editor.
In our use case, the Business Process inspects the Partner Mailbox path of each file (coming from the cicPayloadLocation parameter) to determine if the path matches a specific trading partner name. When a match is identified, a corresponding step will execute a transformation specific to that partner. In the example below, these two steps are shown for Acme.
You could also configure this Business Process to send an email notification if a file fails to find a match.
Note: For this scenario, the expected format path in the Business Process is:
Inbound_FF_Invoices/*TradingParter*
Mailbox-to-Transformation Data Flow
Before you create the Data Flow, make sure you have a Partner Mailbox Endpoint set up with the correct subfolders.
In the Data Flow page, create a Data Flow with a Partner Mailbox as the From Endpoint and Transformation as the To Endpoint.
- For the Partner Mailbox Endpoint, make sure you select the subfolders you want to be processed. In this case, a folder
Inbound_FF_Invoiceswith subfoldersAcme,BigStore,Costco, andDepot. - For the Transformation Endpoint, make sure you select the Event you configured to handle the subfolders you selected above.
Comments
0 comments
Please sign in to leave a comment.