Add a how-to guide for processing inbound EDI purchase orders - #631
Draft
niveathika wants to merge 5 commits into
Draft
Add a how-to guide for processing inbound EDI purchase orders#631niveathika wants to merge 5 commits into
niveathika wants to merge 5 commits into
Conversation
Nothing in the docs walks through a whole EDI flow end to end. This guide does it in two parts, in the order the work actually happens: identify the trading partner from the envelope, which needs no schema, then parse the orders with a generated library, quarantining the messages the schema cannot read. The finished workspace lives in wso2/integration-samples, and the screenshots are of that project running in the Visual Designer.
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…nges The prebuilt EDIFACT packages handle envelope headers and batches, so that is no longer the reason this guide generates a module. Point at the schema adjustment in step 5 instead, which is the reason that still holds.
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Part of the EDI documentation pass for the envelope-aware API (ballerina-spec#1441).
The EDI pages explain the tool and the API, but nothing walks through a whole flow end to end. This adds a how-to guide that does, in the order the work actually happens.
The guide
en/docs/guides/howtoguides/edi-purchase-order-processing.md, patterned on the SAP B1 how-to guide (Visual Designer / Ballerina Code tabs, screenshots, prerequisites block):edi:edifactHeadersFromEdiFilereads theUNBenvelope with no schema and only the first 512 characters of the file, and the flow stops if the sender is not the expected partner. This part works before any code is generated.interchangeFromEdiStringwith the fail-safe per-transaction body: two orders processed, one malformed message quarantined with its parse error.The narrative is deliberately the one a real user follows — convert the spec, edit the schema, generate the library, add it to the project — with a note up front that a prebuilt
ballerinax/edifact.d03a.*package can be imported instead when it fits as-is, and a note that X12 specifications are licensed from ASC X12 with a pointer to contact us.The prebuilt-package note originally said the schema generation could be skipped entirely for standard D03A types. That is wrong for this guide's flow: The prebuilt
ballerinax/edifact.d03a.*packages are at0.9.0and predate the envelope-aware API: their schemas carryignoreSegments: ["UNA", "UNB", "UNH", "UNT", "UNZ"]and noenvelope, sofromEdiStringparses a single message body and discards the interchange. Checked against Central: a two-message interchange fails outright. The note now states the limitation, since identifying the partner fromUNBand splitting a batch are exactly what the guide does.Verification
npm run buildon this branch alone reports one broken anchor,/develop/transform/edi#adjusting-a-schema-for-a-trading-partner. That heading is added by Align EDI docs with the envelope-aware module and tool #551, so the anchor resolves once Align EDI docs with the envelope-aware module and tool #551 merges — building this branch merged with Align EDI docs with the envelope-aware module and tool #551 reports no broken links and no broken anchors other than the pre-existing one on/guides/patterns/message-mapper.develop/integration-artifacts/service.mdwas also caught and fixed:integration-artifacts/serviceis a directory of protocol pages with noservice.md. The What's next bullet now points atintegration-artifacts/file/local-files.mdandintegration-artifacts/file/ftp-sftp.md.Depends on