Changelog

Send transformed file failed events to your API

You can now use Stedi mappings to automatically transform file.failed.v2 events into a custom shape before sending them to external APIs.

Stedi emits file.failed.v2 events when it cannot parse an inbound EDI file, or it cannot deliver an outbound EDI file to the configured connection. You may want to automatically send these events to an external platform like Slack or Jira, so your team can receive alerts and monitor issue resolution.

You can now create a Stedi mapping to transform the file.failed.v2 event JSON into the shape your external systems can receive and ingest. Then, you can attach the mapping to a Destination webhook to automatically forward the transformed event data to your API.

Add attachments to Stedi guides

You can now attach files to any Stedi guide and choose whether the attachments are public or private (only available to members of your Stedi account). 

Stedi guides are a machine-readable representation of the EDI specifications that your trading partners provide to you or that you provide to your trading partners. Attachments provide additional information about the guide. 

For example, you may want to add private attachments that help your team debug issues in your EDI pipeline, such as the original PDF specifications or a changelog. For a public guide, you may want to attach an appendix with a supplementary code list or a diagram that helps your partners understand the messaging flow.

To add attachments to a guide in your account, navigate to its Overview page, scroll to the Attachments section, and click Attach file.

Destination webhooks now support OAuth 2.0

You can now use OAuth 2.0 with Destination webhooks. 

Destination webhooks allow you to send transaction data and events from Stedi to any external API. To configure a destination webhook, you first create an auth configuration that defines how to authenticate with a set of URL endpoints. 

The OAuth 2.0 configuration includes setting the Authorization endpoint and parameters, the HTTP method, a client ID, and a client secret. You can create a new OAuth 2.0 configuration from the Event Destinations page.

Automatically delete artifacts after a set time period

Stedi accounts on the Enterprise plan can now set an automatic data removal time frame in Stedi.

Artifacts refer to the transaction and file execution payloads from files Stedi has processed. They contain the actual input/output transaction data in EDI, JSON, or another format. You may want Stedi to remove artifacts after a certain time frame - for example, to comply with your company's PII/PHI retention policies.

Once you set a retention period, Stedi deletes artifacts after the retention window has passed. This affects both existing and future data in your account.

For example, if you set a retention period of 30 days and process a file today, Stedi will delete the artifact after 30 total days have elapsed. Stedi will also delete any artifact created more than 30 days prior. For more details on how artifact retention works, please visit the docs.You can set an automatic data removal time frame from the Settings page.

Automatically process inbound TA1 Interchange Acknowledgments

Your trading partner may send you TA1 Interchange Acknowledgments in response to outbound EDI files.

Stedi now automatically processes inbound TA1s and displays the data in the File executions and Transactions pages for inspection.

You can also set the acknowledgmentRequestedCode outbound EDI files to request interchange acknowledgments from your trading partner. Visit the Generate EDI docs for details.

TA1s indicate receipt of an interchange and identify any errors in the interchange's envelope (ISA and IEA) information.

Generate inbound test files from your browser

You can now generate and send inbound test files to simulate receiving a file from your trading partner. This is useful for testing your downstream integration, since the inbound file will trigger configured destination webhooks.

To generate an inbound test file:

1. Go to the File executions page or navigate into a partnership and click Test inbound.

2. Select a partnership and an Inbound transaction setting.

3. Autogenerate the test file from a sample EDI file in the guide or paste your own test data into the editor.

4. Click Ingest file.

Stedi immediately processes the generated file and triggers any configured webhooks. You can review the results on the File Executions and Transactions pages.

Improvements to Stedi AS2

Stedi provides fully-managed AS2 connections that take care of the intricacies of AS2 and scale automatically to meet your demand. We recently made the following improvements:

• We added extensive conditional validation to reduce common configuration errors.

• You can now view and filter provisioning logs for each AS2 connection. These logs detail each step to create or update the connection, such as provisioning the certificates, making it easier to diagnose errors. To view provisioning logs, go to the partnership associated with the connection, and then click the connection to view its details page.

• When creating or updating an AS2 connection, Stedi now clearly indicates when there are previously uploaded encryption and signing certificates and provides the option to update them. Previously, adding or updating certificates was a separate workflow.

Introducing Fragments: Split large transaction payloads

Stedi accounts on the Enterprise plan can now use fragments to split large transaction payloads from Stedi into smaller, more manageable chunks for downstream processing.

Large EDI files are often the result of transaction sets containing many repeated loops or segments. For example, a company may receive an 837 Health Care Claim file containing many insurance claims, or a retailer may receive an 846 Inventory Inquiry/Advice file containing millions of SKUs. To avoid overloading downstream systems, you can enable fragments on the repeated EDI segment.

Once enabled, Stedi splits the transaction payload into chunks based on that segment.For example, you might enable fragments on the LIN loop (list of inventory items) in an 846 Inventory Inquiry/Advice. For each processed 846, Stedi will emit fragment.processed.v2 events that each contain a chunk of LIN loop iterations.

You can create destination webhooks to automatically send fragment data to your downstream systems, or you can use the API to request the fragments for each processed transaction.

Guide builder now shows warnings for missing ID element codes

Stedi's guide builder now shows warnings when an ID element does not specify the set of allowed codes. You can see which fields are missing ID codes and specify the allowed values from the provided list or supply your custom codes.

Code warnings are available to help improve the quality of your guides, and you can ignore them without affecting Stedi's ability to use the guide for EDI processing. Warnings only appear for ID fields where the X12 specification includes the allowed code values. For example, they will not appear for State or Province codes.

Why element codes are important

ID element codes are a powerful component of the X12 EDI specification to provide additional information about data fields and reference well-known values. For example, you can use ID codes to specify the currency code of a monetary value, the meaning of a date value, or the reason for a shipment delay.

Many elements offer 1,000 or more possible codes, but most trading partners only expect to use just one or a few of these values. If a guide does not indicate which codes are accepted, trading partners often have to engage in costly follow-up with EDI departments or conduct multiple rounds of testing as they discover more code values in use.

The new warnings in Stedi's guide builder help ensure you and your trading partners work with the most accurate EDI specifications on the market.

Pre-built guides: Instead of building guides from scratch, you can find hundreds of free guides for popular trading partners in the Stedi Network.

Add a mapping to destination webhooks

You can now add a mapping to destination webhooks to automatically transform transactions before delivering them to external APIs.Stedi parses EDI files into Guide JSON, which reflects the structure of an EDI transaction in a modern format. You can use a mapping to transform Guide JSON into the shape required by your internal systems and business applications. Mappings provide a visual interface for building JSON-to-JSON transformations and are available in the Cloud and Enterprise plans.

To add a mapping to a destination webhook:

1. Use the mappings editor to create a transformation for the transaction.processed.v2 event. Visit the mappings documentation for instructions.

2. Select the mapping in the Mapping menu when creating a transaction.processed.v2 event binding. Visit the webhooks documentation for complete instructions.