Note This repository should only be relied on for existing users. New users should not deploy this version of bootstrap, and instead should use Stedi Core to send and receive EDI files. Please don't hesitate to contact us with any questions!
Previous README contents
This repository contains an end-to-end configuration for building an X12 EDI system using Stedi products. This implementation demonstrates one way to build an integration for common EDI read and write use cases. Your solution may differ depending on your systems and requirements.
We strongly recommend reviewing the documentation for Stedi Core before deploying the bootstrap implementation.
- Hands-on support
- Bootstrap read and write workflow
- Requirements
- Deploying bootstrap resources
- Testing the workflows
- Clean up bootstrap resources
- Customizing the workflows
- Troubleshooting
We'd like to help set up and customize the bootstrap repository with you. Working together helps us understand what Stedi customers need and helps get your solution into production as quickly as possible. We offer free hands-on support that includes:
- Help deploying the bootstrap workflows and customizing them for your use cases
- Best practices for designing scalable connections between Stedi and your systems
- EDI experts to answer your questions
- Live troubleshooting over Slack or video call
Contact us to get started.
The Stedi Core module ingests data and emits events with the results of its conversion and validation processing. For example, Core emits an event when it receives a new file or successfully processes a transaction set.
To create a custom end-to-end EDI system on Stedi, you need to automate tasks like adding files from your input buckets and reacting to the emitted events. For example, you may want to automatically forward translated EDI files to an API, FTP server, AS2 server, or a Stedi function to run custom code.
Bootstrap contains opinionated Stedi functions that you can customize through configuration. For example, you can add Destinations where the bootstrap workflows will send incoming and outgoing data. The following sections describe these built-in functions.
The edi-inbound function listens to Stedi Core transaction.processed events, which contain the partnership, document
direction, location of the translated document, and document transaction set ID for a single EDI transaction set. When
it receives an event, it performs the following steps:
- Read the translated EDI-like JSON data from the Stedi bucket configured to receive Core output.
- Look up configured destinations for the specific partnership and transaction set ID. Refer to Destinations for details.
- If a destination has a Stedi Mapping configured, apply the mapping transformation the JSON.
- Send the JSON to each destination.
- Send failures (such as invalid mappings or missing guides) to Execution Error Destinations.
- Retry function execution failures 2 more times. These retries can result in destinations receiving multiple messages, so you must handle at-least-once message delivery separately. We recommend using payload control numbers and message timestamps for deduplication.
The edi-outbound function performs the following steps when it receives a payload and a metadata object. The payload
must match the shape of the Guide's JSON Schema for writing EDI. Or, if a mappingId is specified, then the payload is
the input for a mapping which will output valid Guide JSON data.
- Use the metadata to look up the configuration values required to construct an EDI envelope. The
partnershipIdis the only required field. - If a Stedi Mapping is specified, apply the mapping transformation to the JSON.
- Call Stedi EDI Translate to transform the JSON payload into an EDI file.
- Look up configured destinations for the specific partnership and transaction set ID. Refer to Destinations for details.
- Send failures to Execution Error Destinations.
- Retry function execution failures 2 or more times. These retries can result in destinations receiving multiple messages, so you must handle at-least-once message delivery separately. We recommend using payload control numbers and message timestamps for deduplication.
The edi-acknowledgement function listens to Stedi Core functional_group.processed inbound events, which contain the
partnership, document direction, and envelope data for a single functional group. When it receives an event, the
function performs the following steps:
- If the direction is
RECEIVED, look up up 997 acknowledgment configuration for the specific partnership and transaction set Ids in the functional group. Refer to Acknowledgments for details. - If transaction sets are in the functional group with 997 acknowledgments configured, generate a 997 EDI-like JSON
file and send it to the
edi-outboundfunction for processing.
The events-file-error function listens to Stedi Core file.failed events, which Stedi emits when there is an error
processing a file. When it receives an event, the function performs the following steps:
- Look up the configured file error destinations. Refer to File Error Destinations for details.
- Forward the errors to each destination.
-
Install Node.js (minimum version: 18)
-
Clone the bootstrap repository and install the necessary dependencies:
git clone https://github.com/Stedi-Demos/bootstrap.git cd bootstrap npm ci -
Create a Stedi account and enable Core. Bootstrap does not overwrite existing Core settings or data.
-
Rename the bootstrap's
.env.examplefile to.envand update the following environment variables:STEDI_API_KEY: A Stedi API key is required for authentication. You can generate an API key in your Stedi account.DESTINATION_WEBHOOK_URL: Go to webhook.site and copy the unique URL. The bootstrap workflow sends output to this webhook.
Example
.envfileSTEDI_API_KEY=<YOUR_STEDI_API_KEY> DESTINATION_WEBHOOK_URL=<YOUR_WEBHOOK_URL>
Run the following command in the bootstrap directory:
npm run bootstrapBootstrap creates resources in your Stedi account. It may take several minutes for Stedi to deploy all required resources. When deployment is finished, your CLI displays a message similar to the following.
Example CLI output (click to expand):
[email protected] bootstrap
npm run configure-storage && npx ts-node-esm ./src/setup/bootstrap.ts && npm run deploy
[email protected] configure-storage
npm run ensure-keyspaces-exist && npm run configure-buckets
[email protected] ensure-keyspaces-exist
ts-node-esm ./src/setup/bootstrap/ensureKeyspacesExist.ts
Creating keyspaces...
Waiting for keyspaces to become active...
Waiting for keyspaces to become active...
[email protected] configure-buckets
ts-node-esm ./src/setup/configureBuckets.ts
Configuring buckets...
done
Guide created: 01GZM3TCTWE94FQZWTHDR1HP8K
Guide created: 01GZM3TD8C4233TNVZFBADNS7E
Creating X12 Trading Partner Profile in Partners API
[email protected] deploy
ts-node-esm ./src/setup/deploy.ts
Waiting for function deploys to complete
Finished deploying function: edi-acknowledgment
Finished deploying function: events-file-error
Finished deploying function: edi-outbound
Finished deploying function: csv-to-json
Finished deploying function: ftp-external-poller
Finished deploying function: csv-from-json
Finished deploying function: edi-inbound
Creating event bindings
Waiting for event binding deploys to complete
Deploy completed at: 5/4/2023, 3:35:21 PM
Bootstrap deploys the following resources to your account:
- A Stedi bucket with directories for you
_stediand trading partnerstrading_partners. In thetrading_partnersdirectory is a single directory for a fictional trading partner calledANOTHERMERCH. WithinANOTHERMERCH, are directories for inbound and outbound files. Theinbounddirectory is where your partners would drop new files to send to you and theoutbounddirectory is where Stedi sends EDI files generated for that trading partner. - A Stash keyspace called
partners-configuraion. This keyspace contains configuration for bootstrap, including destinations for incoming and outgoing files. If you click thedestinations|this-is-me_another-merchant|855key/value pair, you'll see that bootstrap is configured to send incoming 855 EDI documents to your webhook. - Several Stedi functions, including functions required to read and write EDI and generate functional acknowledgements.
Core automatically processes new files in the designated bucket for incoming data. When Core processes a file, it emits
events that automatically invoke the edi-inbound function for each processed transaction set.
-
Go to the Buckets UI and navigate to the
inbounddirectory for your trading partner:<SFTP_BUCKET_NAME>/trading_partners/ANOTHERMERCH/inbound -
Upload the input X12 5010 855 EDI document to this directory.
-
Look for the output of the function wherever you created your test webhook. The function sends the translated JSON payload to the endpoint you configured.
Example webhook output (click to expand):
{ "envelope": { "interchangeHeader": { "authorizationInformationQualifier": "00", "authorizationInformation": " ", "securityQualifier": "00", "securityInformation": " ", "senderQualifier": "14", "senderId": "ANOTHERMERCH ", "receiverQualifier": "ZZ", "receiverId": "THISISME ", "date": "2022-09-14", "time": "20:22", "repetitionSeparator": "U", "controlVersionNumber": "00501", "controlNumber": "000001746", "acknowledgementRequestedCode": "0", "usageIndicatorCode": "T", "componentSeparator": ">" }, "groupHeader": { "functionalIdentifierCode": "PR", "applicationSenderCode": "ANOTAPPID", "applicationReceiverCode": "MYAPPID", "date": "2022-09-14", "time": "20:22:22", "controlNumber": "000001746", "agencyCode": "X", "release": "005010" }, "groupTrailer": { "numberOfTransactions": "1", "controlNumber": "000001746" }, "interchangeTrailer": { "numberOfFunctionalGroups": "1", "controlNumber": "000001746" } }, "transactionSets": [ { "heading": { "transaction_set_header_ST": { "transaction_set_identifier_code_01": "855", "transaction_set_control_number_02": 1 }, "beginning_segment_for_purchase_order_acknowledgment_BAK": { "transaction_set_purpose_code_01": "00", "acknowledgment_type_02": "AD", "purchase_order_number_03": "365465413", "date_04": "2022-09-14", "date_09": "2022-09-13" }, "reference_information_REF": [ { "reference_identification_qualifier_01": "CO", "reference_identification_02": "ACME-4567" } ], "party_identification_N1_loop_ship_to": [ { "party_identification_N1": { "entity_identifier_code_01": "ST", "name_02": "Wile E Coyote", "identification_code_qualifier_03": "92", "identification_code_04": "DROPSHIP CUSTOMER" }, "party_location_N3": [ { "address_information_01": "111 Canyon Court" } ], "geographic_location_N4": { "city_name_01": "Phoenix", "state_or_province_code_02": "AZ", "postal_code_03": "85001", "country_code_04": "US" } } ], "party_identification_N1_loop_selling_party": [ { "party_identification_N1": { "entity_identifier_code_01": "SE", "name_02": "Marvin Acme", "identification_code_qualifier_03": "92", "identification_code_04": "DROPSHIP CUSTOMER" }, "party_location_N3": [ { "address_information_01": "123 Main Street" } ], "geographic_location_N4": { "city_name_01": "Fairfield", "state_or_province_code_02": "NJ", "postal_code_03": "07004", "country_code_04": "US" } } ] }, "detail": { "baseline_item_data_PO1_loop": [ { "baseline_item_data_PO1": { "assigned_identification_01": "item-1", "quantity_02": 8, "unit_or_basis_for_measurement_code_03": "EA", "unit_price_04": 400, "product_service_id_qualifier_06": "VC", "product_service_id_07": "VND1234567", "product_service_id_qualifier_08": "SK", "product_service_id_09": "ACM/8900-400" }, "product_item_description_PID_loop": [ { "product_item_description_PID": { "item_description_type_01": "F", "description_05": "400 pound anvil" } } ], "line_item_acknowledgment_ACK_loop": [ { "line_item_acknowledgment_ACK": { "line_item_status_code_01": "IA", "quantity_02": 8, "unit_or_basis_for_measurement_code_03": "EA" } } ] }, { "baseline_item_data_PO1": { "assigned_identification_01": "item-2", "quantity_02": 4, "unit_or_basis_for_measurement_code_03": "EA", "unit_price_04": 125, "product_service_id_qualifier_06": "VC", "product_service_id_07": "VND000111222", "product_service_id_qualifier_08": "SK", "product_service_id_09": "ACM/1100-001" }, "product_item_description_PID_loop": [ { "product_item_description_PID": { "item_description_type_01": "F", "description_05": "Detonator" } } ], "line_item_acknowledgment_ACK_loop": [ { "line_item_acknowledgment_ACK": { "line_item_status_code_01": "IA", "quantity_02": 4, "unit_or_basis_for_measurement_code_03": "EA" } } ] } ] }, "summary": { "transaction_totals_CTT_loop": [ { "transaction_totals_CTT": { "number_of_line_items_01": 2 } } ], "transaction_set_trailer_SE": { "number_of_included_segments_01": 17, "transaction_set_control_number_02": "0001" } } } ], "delimiters": { "element": "*", "composite": ">", "repetition": "U", "segment": "~" } }
You can invoke the edi-outbound function through the UI for testing.
-
Navigate to the
edi-outboundfunction in the (Functions UI)https://www.stedi.com/app/functions/edi-outbound/edit. -
Click the
Edit execution payloadlink, and paste the contents of src/resources/X12/5010/850/outbound.json into the payload modal, and click save. -
Click Execute and choose the Synchronous option. If successful the
Outputshould look similar to the following:Example function output (click to expand):
{ "statusCode": 200, "deliveryResults": [ { "type": "bucket", "payload": { "bucketName": "<STEDI_ACCOUNT_ID>-sftp", "key": "trading_partners/ANOTHERMERCH/outbound/1-850.edi", "body": "ISA*00* *00* *ZZ*THISISME *14*ANOTHERMERCH *230113*2027*U*00501*000000005*0*T*>~GS*PO*MYAPPID*ANOTAPPID*20230113*202727*000000005*X*005010~ST*850*0001~BEG*00*DS*365465413**20220830~REF*CO*ACME-4567~REF*ZZ*Thank you for your business~PER*OC*Marvin Acme*TE*973-555-1212*EM*[email protected]~TD5****ZZ*FHD~N1*ST*Wile E Coyote*92*123~N3*111 Canyon Court~N4*Phoenix*AZ*85001*US~PO1*item-1*0008*EA*400**VC*VND1234567*SK*ACM/8900-400~PID*F****400 pound anvil~PO1*item-2*0004*EA*125**VC*VND000111222*SK*ACM/1100-001~PID*F****Detonator~CTT*2~AMT*TT*3700~SE*16*0001~GE*1*000000005~IEA*1*000000005~" } } ] } -
You can view the file using the Buckets UI. The output of the function includes the
bucketNameandkey(path within the bucket) of where the function saved the generated EDI.
The bootstrap workflow uses sample Partners, a Partnership associating the two partners, and configuration values for destinations configured in Stash to set up and test the read and write EDI workflows. You can customize the bootstrap workflow by doing one or all of the following:
- Edit a partner profile to replace the test trading partner with your real trading partners' details and requirements.
- Customize configuration in Stash. Add partnership and transaction set configurations for partnerships, set one or more destinations for a given configurations, forward errors to external services or archive in buckets, configure mappings, and send 997 acknowledgments.
- Create Stedi mappings. Add a
mappingIdproperty to a Stash destination configuration to transform the inbound payload before sending to a destination. Or, when sending EDI, themappingIdcan transform the event payload into the JSON schema required for translating to EDI. - Create SFTP users for your trading partners, so they can send and retrieve EDI documents from Stedi Buckets.
You may want to use additional Stedi products to further optimize your EDI workflows. We can help you customize the bootstrap workflow and determine which products and approaches are right for your use cases. Contact us to set up a meeting with our technical team.
You can poll remote FTP and SFTP servers to download files from your trading partners. Visit the External FTP / SFTP poller README for details.
To delete all the resources created by the bootstrap, run the following command:
npm run destroyStedi Stash is a key/value store. You can add and edit Stash key-value pairs to configure destinations for incoming and outgoing documents, destinations for errors, and which transaction sets require functional acknowledgements.
key: destinations|${partnershipId}|${transactionSetId}
value: JSON Schema
key: destinations|errors|execution
value: JSON Schema
key: destinations|errors|execution
value: JSON Schema
key: functional_acknowledgments|${partnershipId}
value: JSON Schema
There was an issue installing the dependencies using your local npm installation, please check your .npmrc and try again.
If you created a .npmrc in this repository, please remove it.
If you still see this error, you may have a registry override in your npm config. Run npm config list and search
for registry like below. Comment out that line and try again.
@stedi:registry = "https://npm.pkg.github.com/"