Better Release Note Structure (Protocol-Based View)

Problem Statement

Current Sterling B2B Integrator release notes are generally organized by APARs, components, or generic fix categories. For administrators and support teams managing protocol-specific implementations (SFTP, AS2, Connect:Direct, FTPS, HTTP/S, EBICS, etc.), it becomes difficult and time-consuming to identify all relevant changes impacting their environment.

Operational teams often need to manually search the entire release note document to determine:

• Which protocols are affected
• Whether security fixes impact a specific adapter
• Which changes require regression testing
• Which protocol-specific configurations may break after upgrade

This increases upgrade assessment effort and introduces the risk of missing critical protocol-impacting fixes.

Proposed Enhancement

Introduce a Protocol-Based Release Note View in addition to the existing release note format.

Example structure:

• SFTP Changes
• AS2 Changes
• Connect:Direct Changes
• HTTP/HTTPS Changes
• FTPS Changes
• Mailbox/Storage Changes
• Security/Authentication Changes
• UI/REST API Changes

Each section should include:

• APAR ID
• Component impacted
• Severity
• Upgrade action required
• Configuration impact
• Backward compatibility notes
• Regression testing recommendations

Benefits

• Faster impact assessment during upgrades
• Improved usability for administrators and support teams
• Reduced risk of missed protocol-specific changes
• Better planning for regression testing
• Simplified operational review process
• Reduced dependency on manual release note analysis

Business Value

This enhancement would significantly improve customer upgrade experience, especially for enterprises managing multiple protocols across large-scale Sterling environments.