ECL Service Sample Profile Workflow

The following describes the profile workflow:

Step 1. [01) Create and Register ECL Route]:

The route creates and registers the ECL WestCoastUSStates by using the ECL Update component. Later, this ECL is used to validate input transactions against US West Coast States, for example, Washington, California, and Oregon.

Step 2. [02_06_10) Code Lookup Route]:

Then, the route checks to see if the States codes ("WA", "CA", "OR") are available in the ECL by using the ECL Lookup component. With the ECL components, you can search for codes in the external code list repositories during a route's run time. The component verifies whether the specific code is available in the code list and returns search results in the form of XEServer exchange properties (the properties are set on the component's original output). The value of the property "ECLResultsCount" indicates whether the specified code is available or not. The value of "ECLResultsCount" 0 indicates that the code is not available, and the value of "ECLResultsCount" more than zero indicates that the code is available and shows the total number of the codes retrieved.

Step 3. [03_07_11) Validate Route]:

The route validates the transaction. To validate a transaction against the ECL WestCoastUSStates, the following OnNodeUser script rule is used:

ECVerifyCode2 ("WestCoastUSStates", 190610, "This US State is not listed in the WestCoastUSStates ECL");

This JavaScript rule is applied to the node Element(ID = '156')[1].Segment(ID = 'N4')[1].Loop(ID = '2100A')[1].Loop(ID = '2000')[1].Transaction(ID = '834')[1] of the guideline 834_Guideline_ECL-WestCoastUSStates.ecs located at ${XESProfileConfig}/artifacts/guideline.

Step 4. [04) Insert Code XES Exchange Route]:

The route inserts the code "WA" into the ECL WestCoastUSStates by using the ECL Update component. The component uses XEngine Server Exchange as a source of input data to identify the codes that have to be inserted. With this option, the data for inserting a new code is retrieved from each XEServer message that is a part of the incoming exchange.

Step 5. [05) Insert Code DFF File Route]:

The route inserts the codes "CA" and "OR" into the ECL WestCoastUSStates by using the ECL Update component. The component uses DFF file as a source of input data to identify the codes that have to be inserted. This option is used to extract code-specific information from an XEServer message body that carries a DFF file.

Step 6 is a repeat of Step 2.

Step 7 is a repeat of Step 3.

Step 8. [08) Delete Code XES Exchange Route]:

The route deletes the code "CA" from the ECL WestCoastUSStates by using the ECL Update component. The component uses XEngine Server Exchange as a source of input data to identify the codes that have to be deleted. With this option, you can dynamically delete required data by extracting the code from the XEServer exchange properties.

Step 9. [09) Delete Code DFF File Route]:

The route deletes the codes "WA" and "OR" from the ECL WestCoastUSStates by using the ECL Update component. The component uses DFF File as a source of input data to identify the codes that have to be deleted. With this option, you can dynamically delete a code by using the code from the XEServer exchange properties. This option is used to extract code-specific data from the XEServer message body that carries a DFF file.

Step 10 is a repeat of Step 2.

Step 11 is a repeat of Step 3.

Step 12. [12) Unregister and Delete ECL Route]:

The route unregisters and deletes ECL WestCoastUSStates by using the ECL Update component.