Skip to content

W-23604182 test build error fixes #287

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hannanelson merged 1 commit into from
Jul 28, 2026
+5 −4
Merged

W-23604182 test build error fixes #287

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions modules/ROOT/pages/edifact-receive-read-settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ a|* If selected, Partner Manager rejects a message that contains segments that r
|Enforce code set validations
a|* If selected, Partner Manager enforces EDIFACT code set validations, as defined in the EDIFACT schemas.
* If not selected, Partner Manager accepts the message.
|Disabled
|===

If a message does not meet an enabled rule, Partner Manager rejects it.
Expand Down
6 changes: 3 additions & 3 deletions modules/ROOT/pages/message-type-send-to-partners.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Enables you to import a customized xref:connectors::x12-edi/x12-edi-schema-langu
+
When using a customized EDI schema, you can assign a custom name to the message type definition, for example, `EDIFACT-d97a-ORDERS-<PartnerName>`.
| Use standard EDIFACT- <version>| Yes
|Name |Message type name that Partner Manager automatically generates from the schema filename. You can modify this name. | Yes
|Name |Message type name that Partner Manager automatically generates from the schema filename. You can modify this name. | | Yes
|===

== JSON or XML
Expand All @@ -46,7 +46,7 @@ If you process cXML messages with <DOCTYPE> tags, you must set the `minMuleVersi
|Usage | Message usage. Allowed value is `Send to partners`. | | Yes
|Format | Format of the message. Allowed value is `JSON` or `XML`. | |Yes
|Schema | Imported JSON or XSD schema file for the message type. | |No
|Name | Name of the new message type |Yes
|Name | Name of the new message type | |Yes
|===

== X12
Expand All @@ -70,7 +70,7 @@ Enables you to import a customized xref:connectors::x12-edi/x12-edi-schema-langu
+
When using the customized EDI schema, you can assign a custom name to the message type definition, for example, `X12-7050-204-PartnerName`.
| Use standard X12-<version> |Yes
| Message type name that Partner Manager automatically generates from the schema filename. You can modify this name. | |Yes
|Name | Message type name that Partner Manager automatically generates from the schema filename. You can modify this name. | |Yes
|===

For an example that shows how to customize an X12 schema, see https://www.mulesoft.com/exchange/works.integration/b2b-x12-custom-schema-example[Customize EDI X12 Schema for B2B Integrations] in Anypoint Exchange.
Expand Down
2 changes: 1 addition & 1 deletion modules/ROOT/pages/x12-receive-read-settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ When unchecked, the AK3 segment of the generated 997 functional acknowledgment d
|Enabled

|Report segment details
||If selected, the details of segment errors are included in the functional acknowledgements generated (997) •
|If selected, the details of segment errors are included in the functional acknowledgements generated (997).

|Enabled

Expand Down