View this page in the latest version of Appian. View Swift Messages Share Share via LinkedIn Reddit Email Copy Link Print On This Page This content applies solely to Appian Adapter for Swift, which must be purchased separately from the Appian base platform. This content was written for Appian 26.3 and may not reflect the interfaces or functionality of other Appian versions. The Appian adapter for Swift provides a record-based interface for viewing all inbound and outbound Swift messages processed by the adapter. Message Managers can search, filter, and drill into individual message records to review processing details, validation issues, and audit history. Prerequisites Before viewing messages, confirm the following: The Appian adapter for Swift is installed and set up. Your user account is assigned to the SMM Users group. At least one inbound or outbound message has been processed by the adapter. To access the interface, go to the Appian Adapter for Swift site. View inbound messages The INBOUND MESSAGES page displays all Swift messages received and processed by the adapter. Each row represents a single inbound message. Column Description Message UUID Unique identifier assigned to the message when received. Click to open the message record. Message Type The MT or MX message type, such as MT103 or MX camt.029.001.09. Status Current processing status of the message, such as Sent with Errors or Failed To Send. Issue Count Number of processing issues encountered during validation or transformation. Source System Identifier of the upstream system that sent the message. Received On Date and time the message was received by the adapter. Filter inbound messages Search: Enter keywords to search across message UUIDs. Status: Filter by processing status, such as Converted or Data Validation Error. Has Issues?: Filter by whether the message has processing issues. View an inbound message record Click a Message UUID in the list to open the full message record. Inbound message details Field Description Status Current processing status with a visual indicator. Received On Date and time the message was received. Source System Identifier of the upstream system that sent the message. Source Fields Additional metadata key-value pairs passed by the source system, displayed as JSON. Message Type The MT or MX message type. Swift SR Version The Swift Standards Release version applied during processing. Inbound event history The event history panel displays a chronological audit trail of processing events. Each entry shows the actor, the event description, and a timestamp. Typical events for an inbound message: System Received Inbound Swift Message: The adapter received the raw message from the upstream system. System Failed Validation Inbound Swift Message: Validation against Swift network rules detected issues. System Converted Inbound Swift Message: The adapter parsed and converted the message into a structured data object. System Failed Transformation Swift Inbound Message: An error occurred during data transformation. System Sent Inbound Swift Message: The processed message was sent to the configured downstream system. Inbound processing issues The processing issues table lists all validation and transformation problems encountered during processing. Column Description Message Detailed description of the issue. JSON Field The specific field in the message that caused the issue, if applicable. Issue Type Severity of the issue: Problem or Error. Issue Category Processing stage where the issue occurred: Validation or Transformation. Inbound message content panels The message record displays the message content at three stages of processing: Swift Message: The original raw Swift message as received in MT block format or MX XML. JSON Converted Message: The intermediate parsed representation after initial conversion. Appian Data: The final structured Appian data object sent to the downstream system. These panels show how data flows from the raw Swift format through conversion to the final structured output. View outbound messages The OUTBOUND MESSAGES page displays all messages that downstream systems have submitted for conversion and transmission to the Swift network. Each row represents a single outbound message. Column Description Message UUID Unique identifier assigned to the message. Click to open the message record. Message Type The MT or MX message type, such as MT103 or camt.054.001.08. Status Current processing status of the message, such as Sent, Sent with Errors, or Failed. Issue Count Number of processing issues encountered during validation or transformation. Destination Identifier of the upstream system the message is being sent to. Sent On Date and time the message was sent to the destination system. Filter outbound messages Search: Enter keywords to search across message UUIDs. Status: Filter by processing status, such as Sent or Failed. Has Issues?: Filter by whether the message has processing issues. View an outbound message record Click a Message UUID in the list to open the full message record. Outbound message details Field Description Status Current processing status with a visual indicator. Sent On Date and time the message was sent to the destination system. Displays a dash if the message has not been sent. Swift Version The Swift Standards Release version applied during processing. Swift Message Type The MT or MX message type identifier. Source Identifier of the downstream system that submitted the outbound request. Destination Identifier of the upstream system or channel the message is being sent to. Confirmation UUID UUID returned by the destination system to confirm receipt. Usage Guideline The message usage guideline applied, such as CBPR+. Ignore Validation Whether validation was skipped for this message. Outbound event history Typical events for an outbound message: System Received Outbound Message: The adapter received the structured data object from the downstream system. System Transformed Outbound Message: The adapter converted the data object into a Swift MT or MX message. System Failed Validation Outbound Message: Validation against Swift network rules detected issues. System Failed Send Outbound Swift Message: The adapter could not deliver the message to the destination system. Outbound processing issues The processing issues table lists all validation and transformation problems, using the same format as inbound messages. Outbound message content panels The message record displays the message content at two stages: Appian Data: The structured data object received from the downstream system. Swift Message: The generated Swift message in MT block format or MX XML produced by the adapter. These panels show the input data object alongside the generated Swift message for verifying transformation accuracy or diagnosing conversion issues. View Swift Case Management requests The SCM REQUESTS page displays all requests submitted to Swift Case Management (SCM) through the adapter. Each row represents a single case management request. Column Description Request UUID Unique identifier assigned to the request. Click to open the request record. Status Current outcome of the request, such as Success or Error. Case Type The type of investigation, such as CCNR, UTAP, GSRP, or RQFI. Case Action The action performed, such as CREATE, UPDATE, QUERY, or CANCELLATION_STATUS. Validate Only Whether the request was submitted in validation-only mode. When Yes, the adapter validated the request without sending it to Swift Case Management. Created Date and time the request was received by the adapter. Filter SCM requests Search: Enter keywords to search across request UUIDs. Status: Filter by request status, such as Success or Error. Case Type: Filter by the type of investigation, such as CCNR, UTAP, GSRP, or RQFI. View a Swift Case Management request record Click a Request UUID in the list to open the full request record. SCM request details Field Description Status Final outcome of the request, such as Success or Error. Source Identifier of the downstream system that initiated the request. Destination The target system, such as Swift Case Management. Validate Only Whether the request was submitted in validation-only mode. When Yes, the adapter validated the request without sending it to Swift Case Management. Swift Version The Swift Standards Release version applied during processing. Case Type The type of investigation, such as CCNR, UTAP, GSRP, or RQFI. Case Action The action performed, such as CREATE, UPDATE, QUERY, or CANCELLATION_STATUS. Source Response Http Code HTTP status code returned to the calling downstream system. SCM Response Http Code HTTP status code returned by Swift Case Management. SCM API Endpoint The Swift Case Management API endpoint path that was called. Created On Date and time the request was received by the adapter. SCM request processing issues The processing issues table lists any validation or transformation problems encountered while processing the request, using the same format as inbound and outbound messages: Message, JSON Field, Issue Type, and Issue Category. SCM payload panels The record displays four payloads that trace the full round-trip of the Swift Case Management request: Request sent to AAS: The request that the downstream system submitted to the adapter, including the case type, case action, content fields, and any query parameters. Response from AAS: The response that the adapter returned to the calling downstream system, including whether the request is valid, any validation problems, and the transformed request body or query parameters. Request sent to SCM: The request that the adapter sent to the Swift Case Management API, including query parameters or request body content. This panel is empty when the request was submitted in validation-only mode. Response from SCM: The raw response returned by Swift Case Management, including investigation details, case status, and any related data. This panel is empty when the request was submitted in validation-only mode. These panels show the complete request lifecycle for debugging failed requests or verifying that case data is being transmitted correctly. Next steps After reviewing messages and request records, explore related capabilities: Test Messages in the Sandbox to validate message processing with sample data before sending live traffic. Appian adapter for Swift API Reference to integrate external systems with the adapter's inbound, outbound, and Swift Case Management endpoints. Feedback Was this page helpful? SHARE FEEDBACK Loading...
