Perform the Annual Standards Update

When Appian releases a new version of the Appian adapter for Swift to align with updated Swift Standards, each release maintains full backward compatibility with previous versions. You can adopt updated standards at your own pace.

This page explains how the Swift Standards Release version is applied at runtime and provides a transition strategy for upgrading between annual releases.

How the Swift standards version is applied

The SMM_DEFAULT_SWIFT_VERSION constant determines which Swift Standards Release the adapter uses at runtime. This constant governs the processing of inbound messages, outbound messages, and Swift Case Management requests. Supported values for Appian adapter for Swift 1.3 are "2025" and "2026".

For example, to adopt the SR2026 standards, set the constant value to "2026".

Override the default version per request

To bypass the default configuration for a specific API call, pass the optional swiftVersion parameter in the request body. For example, specifying "swiftVersion": "2025" in an inbound message processing request instructs the adapter to apply 2025 standards for that request, regardless of the default constant value.

This is useful during transition periods when you need to process messages under both the old and new standards simultaneously.

Transition strategy for annual upgrades

Each November, Swift implements network-wide updates at a designated date and time. All subsequent network transmissions must follow the newly established standards. To facilitate a smooth transition, follow this deployment workflow:

1. Deploy the newest Appian adapter for Swift release in a designated testing environment.
2. Set the SMM_DEFAULT_SWIFT_VERSION constant to the upcoming Swift Standards Release version (for example, "2026").
3. Validate functionality by testing inbound messages, outbound messages, and Swift Case Management requests against the new standards.
4. Deploy the latest Appian adapter for Swift release in your production environment ahead of the official Swift update. Leave the SMM_DEFAULT_SWIFT_VERSION constant unchanged to keep the new standards dormant.
5. Update the SMM_DEFAULT_SWIFT_VERSION constant in production at the exact scheduled cutover time, following your team's standard deployment guidelines for the annual Swift release.

Next steps

After completing the annual standards update, validate the new version:

• Test Messages in the Sandbox to run sample messages against the new Swift Standards Release version and confirm expected behavior.
• View Swift Messages to monitor messages processed under the updated standards and review any new validation issues.

Feedback