Test Messages in the Sandbox

The Appian adapter for Swift Sandbox is a dedicated testing environment where Sandbox Testers can run sample Swift messages through the adapter's processing pipeline without calling the APIs from an external system. Use the Sandbox to verify how the adapter validates, converts, and transforms specific message types before going live.

Prerequisites

Before testing messages in the Sandbox, confirm the following:

• The Appian adapter for Swift is installed and set up.
• Your user account is assigned to the SMM Test Users group.

To access the testing pages, go to the Appian Adapter for Swift Sandbox site and open the SANDBOX dropdown in the navigation menu.

The SANDBOX dropdown includes three pages for testing:

• INBOUND SAMPLES: Test inbound message processing using pre-loaded sample Swift messages.
• OUTBOUND SAMPLES: Test outbound message processing using pre-loaded sample data objects.
• SCM API: Test Swift Case Management API requests using pre-loaded sample payloads.

Test inbound messages

The INBOUND SAMPLES page runs a sample Swift message through the full inbound processing pipeline: validation, conversion, and transformation.

To test an inbound message:

1. From Use Swift SR Version, select the Swift Standards Release version to apply during processing. The default is the version configured in the SMM_DEFAULT_SWIFT_VERSION constant.
2. In the Available Templates tree, expand a version folder such as SR 2025 or SR 2026, then select a category:
   • MT Messages: Sample MT format messages.
   • MX CBPR+ Messages: Sample MX messages that follow Cross-Border Payments and Reporting Plus schemas.
   • MX Messages: Sample MX messages in standard ISO 20022 format.
3. Select a specific sample message file from the list.
4. (Optional) If you want to validate BIC codes in the message against the local BIC directory, select Yes for Validate BIC?.
5. (Optional) If you selected SR2026 or a newer standards version, select Yes for Validate ISO Contingency Measures (ICM)? to apply ICM validation. This option applies only to SR2026 and newer.
6. Click PROCESS MESSAGE.

After processing completes, the page displays the results:

• Is Message Valid?: Whether the message passed all validation rules.
• Validation Problems: Any validation issues detected, or N/A if none.
• Message UUID: The unique identifier assigned to the processed message. Click Link to Message record to view the full message record in the INBOUND MESSAGES page.

The three result panels show the message at each transformation stage:

• Swift Message: The raw input message in MT block format or MX XML.
• JSON Converted Message: The intermediate parsed representation after initial conversion by the Prowide library.
• Appian Data: The final structured Appian data object that would be sent to a downstream system in production.

Test outbound messages

The OUTBOUND SAMPLES page runs a sample Appian data object through the full outbound processing pipeline: transformation, validation, and message generation.

To test an outbound message:

1. From Use Swift SR Version, select the Swift Standards Release version to apply during processing.
2. In the Available Templates tree, expand a version folder, then select a category: MT Messages, MX CBPR+ Messages, or MX Messages.
3. Select a specific sample data object file from the list.
4. (Optional) If you want to skip validation and test only the transformation, select Yes for Ignore Validation?.
5. (Optional) If you want to validate BIC codes against the local BIC directory, select Yes for Validate BIC?.
6. (Optional) If you selected SR2026 or a newer standards version, select Yes for Validate ISO Contingency Measures (ICM)? to apply ICM validation. This option applies only to SR2026 and newer.
7. Click PROCESS MESSAGE to run the full outbound pipeline, which transforms, validates, and sends the message to the configured upstream system.

After processing completes, the page displays the results:

• Is Message Valid?: Whether the generated Swift message passed all validation rules.
• Processing Issues: Any validation or transformation issues detected.
• Usage Guideline: The message usage guideline applied during processing, such as CBPR+.
• Message UUID: The unique identifier assigned to the processed message. Click Link to Message record to view the full message record in the OUTBOUND MESSAGES page.

The two result panels show:

• Appian Data: The structured input data object selected from the template.
• Swift Message: The generated Swift message in MT block format or MX XML.

Validate without sending

Click CALL VALIDATION API to run the sample through the Transform and Validate endpoint without sending the message to a destination. This performs the same dry-run validation available through the /webapi/transform-and-validate API. The raw validation response displays inline, showing the transformation result and whether the message is valid.

Test Swift Case Management requests

The SCM API page runs a sample request against the Swift Case Management API through the adapter's case management pipeline.

To test a Swift Case Management request:

1. In the Available Templates tree, select a category:
   • Appian Data: Pre-built JSON payloads structured by case type and action, such as "CCNR Create Request" or "CCNR Query Request."
   • MX Messages: Sample MX message payloads for use with the mxContent mode.
2. Select a specific sample file from the list. The Inputs panel populates with the selected payload.
3. From SCM API Service, select the Swift Case Management service to call, such as "Respond to Claim Non Receipt Investigation - CCNR" or "Get Unable To Apply Investigation - UTAP."
4. (Optional) If you want to validate BIC codes against the local BIC directory, select Yes for Validate BIC?.
5. (Optional) If you want to validate the request without sending it to Swift Case Management, select Yes for Validate Only? (Do not send to SCM). In validation-only mode, the adapter transforms and validates the request and returns the result without submitting it.
6. Click CALL SCM SERVICE.

After the request completes, the three result panels display:

• Inputs: The sample data object you selected from the template.
• API Request Body: The request payload that the adapter constructed and sent to the Swift Case Management API endpoint.
• API Response Body: The response returned by Swift Case Management, including whether the request is valid, any validation problems, the case status, and any case data returned.

If the request fails, the API Response Body panel shows the error response with the status code, error message, and any validation details returned by Swift Case Management.

Next steps

After validating message processing in the Sandbox, explore related capabilities:

• View Swift Messages to review processed messages, validation issues, and audit history in the main application.
• Appian adapter for Swift API Reference to integrate external systems with the adapter's inbound, outbound, and Swift Case Management endpoints.

Feedback