Sprint 141 Progress Summary

September 22nd - October 6th

Executive Summary:

Overall Status

Sprint status is good. The Product Team prioritized the following themes and tasks for Sprint 141 comprising 17 points. These themes included -

• Partner and Community support

Forum discussions
VA 4.2.2.2 implementation
SSA 4.3.2 implementation
Partner Questions
Community and OHT support

• X12 (Continued Internal Testing, Cleanup/ Refactoring, CMS Testing)

• Direct ( End to End Testing of Message Monitoring)

• Admin GUI (Multiple Call Issue, Continued Cleanup, Must Haves Ticket)

The team completed 34 points this sprint. The team pulled in support tickets during the sprint along with a few issue tickets related Admin GUI discovered during internal QA testing.

The team supported VA with some production related questions as well as CMS with implementation/testing questions related to X12 service in their development environment. The team reviewed the backlog and organized the tickets preparing for release. The team completed X12 development for CMS and is currently helping with CMS on setting it up on their development/testing. The team made great progress on fixing Admin GUI related discrepancies and bugs. The team also started working on testing the Direct feature and will continue to work on it next sprint.

Burndown:

Sprint Themes and related tickets for Sprint 141:

Partner and Community support

Forum discussions
VA 4.2.2.2 implementation (CONN-1366)
- 4.2.2.2 release information can be found here - 4.2.X Patches
- The team supported VA with various questions related to SAML headers as well as provided insight and detail into probably causes of an issue seen on the production/implementation with one of their trading partners.
CMS X12 testing (CONN-1365)
- The team supported CMS with installation related questions as they were deploying the last sprint tag in their QA environments for testing both XDR and X12 services.
Partner Questions
Community and OHT support

Next Release (4.4)

The team reviewed the 4.4 backlog this sprint and discussed priorities for release backlog tickets. The team has a good understanding of the work to be completed for the next few sprints.

Support for NwHIN CAQH Core X12 Document submission service

Team reviewed the progress made last sprint with CMS team
- CONNECT team demonstrated Generic Batch Submission transaction request and responses with large payload being sent through two separate CONNECT gateways via SOAP UI
- CONNECT team also demonstrated the X12 error handling scenarios at the gateway
Implemented and successfully tested two way large payload testing for batch requests and responses. Tested with payload sizes up to 1GB (CONN-1329)
Created manual test case documentation for X12 large payloads (CONN-1336)
- /wiki/spaces/CONNECTWIKI/pages/24576043
Created automated test cases for error handling(CONN-1339)
Completed user stories for X12 development to support real time and generic batch X12 document submissions (CONN-1319, CONN-1320)
X12 Document Submission service documentation
- Requirements wiki page - https://connectopensource.atlassian.net/wiki/x/aYCb
- Story plan -https://connectopensource.atlassian.net/wiki/x/VoAGAQ
- Error handling- https://connectopensource.atlassian.net/wiki/x/NABTAQ
- Design approach - https://connectopensource.atlassian.net/wiki/x/BQBNAQ
- Regression suite was updated with New Feature scripts.

Admin GUI

- Fixed issues related to UI discrepancies and small issues discovered during testing
  - Updated Direct AdminGUI backing bean's to have single calls config services on each load (CONN-1220)
  - Moved Hibernate Config file for AdminGUI into CONNECT source Properties folder to fix deployment issue (CONN-1348)
  - Fixed tabs issue in Direct Configurations tab (CONN-1356)
  - Fixed issue related to wrong agent setting being deleted (CONN-1345)
  - Fix issue related to Add Certificate (CONN-1265)
  - Code cleanup (CONN-1121)
- Fixed CONNECT Direct Deployment failing when the application server is restarted in JBoss, Weblogic and Websphere (CONN-1213)
- Created testing artifacts for Admin GUI functionality
  - Direct configuration - https://connectopensource.atlassian.net/wiki/x/TgB3AQ (CONN-1346) (Not completed, moved to next sprint)
  - Login status and account management - https://connectopensource.atlassian.net/wiki/x/UAB3AQ (CONN-1165)
- Hide all the Direct AdminGUI pages if Direct components are not deployed (CONN-1166)

Direct

Validated the scenario where the Sending gateway receives a positive or negative delivery notification message from the Responding gateway and sends out a success or failed message to the adapter.
- Research how CONN-202 scenario#4 can be tested in an automated way. (CONN-1231)
- The scenario is related that once the gateway has notified the sender/edge of positive or negative delivery of a Direct message to a particular destination, the gateway SHALL provide no further notification to the sender of positive or negative delivery of that particular Direct message to that destination.
- Scenario was tested on WebLogic (CONN-1229)
Moved the custom parameters to gateway.properties file for message monitoring parameters.(CONN-1351)