Versions Compared

Version Old Version 1 New Version Current
Changes made by

Deepthi Rodrigues

Deepthi Rodrigues

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jun 16 - June 30, 2014

Executive Summary

Overall Status

The Product team prioritized the following themes and tasks for Sprint 134 comprising 34 points. Sprint status is fine and the team completed all the tasks for the themes this sprint totaling XX points .  These themes included -   

...

In addition to the rest of the themes described above the Product Team will continue its support of the community(Tiani/INHS), ongoing support for VA on their 4.2.1 upgrade, work with OHT and Healtheway product certification testing.

The team completed XX  task 19 task oriented tickets totaling XX 34 points this sprint. XX tickets were not completed (CONN-XX, CONN-XX, CONN-XX) and will be moved over to the next sprint. 

...

A couple of tickets were pulled out of the sprint to to account for the additional support work that was required during the sprint.

Burndown

Image Added

 

Sprint Themes and related tickets for Sprint 134:

  • Community Implementation support
    • Responded to forum posts - http://www.connectopensource.org/developer-resources/forums
    • Support VA with 4.2.2.1 upgrade (CONN-1174,CONN-1179)
      • Continued discussions with VA as they work on the 4.2.1 upgrade. Fixed an issue in 
      • Provided information to the VA implementation team on implementing fan-out with standard mode of the gateway and discussed considerations for the same.
      • /wiki/spaces/CONNECTWIKI/pages/17825814
      1211)
      • CONNECT Development Team were assisting the VA implementation team to resolve the CONNECT 4.2.x deployment and configuration issues in the VA SQA2 & Dev environments
      • Supporting VA team few times through phone and were related to questions about DR, DS and DQ configuration setup.
      • VA team reported an time out error after receiving a DQ response from one of their partners and we suggested to fix the internalconnectioninfo and looks like that resolved the issue
      • VA team were getting an endpoint url null error on a DS outbound request and the issue was resolved by fixing the internalconnectioninfo and also the gateway.properties
    • Continued discussion with CMS on X12 support and understanding requirements (CONN-11541173)
    • Discussed at a high level scope and priority.
    • Open questions were published for further discussion with CMS contacts particularly around specifications.
    • Worked on WSDL definitions and sample message formats for further review with the CMS teams.(CONN-1148)
    • Updated wiki page  - Support for X12 messaging(Draft) 
    • Draft story plan for 278 to discuss our understanding with CMS - 278 Story Plan(Draft) 
      • WSDL definitions and sample message to discussion our understanding with CMS (CONN-1148)/wiki/spaces/CONNECTWIKI/pages/17203353
    • Supported DoD and investigated issue related to SAML Issuer.(CONN-1215)
      • The team investigated the issue and ran a few tests against the DIL and saw that 4.3 successfully passed. 
      • The team also did some additional scenarios testing related to SAML issuer and Subject Name IDs. If the proper values are provided in the Entity request, the values get propagated into the SAML headers in the NwHIN message. The issue was later attributed to a known defect in the DIL related to the sequence of the CN value in the distinguished name.
    • Follow-up with Tiani/INHS with timestamp/signature validation (CONN-1177)
      • Support involved analysis of logs and providing guidance.
  • Next Release (4.4)
    • Feature checkpoint for Direct and Admin GUI completed(CONN-1150)
      • All Direct and Admin GUI tickets that have been identified, are created in the backlog associated with the appropriate feature epic and Release 4.4.
    • Direct enhancements
      • Converted CONNECTDirectConfig to use HIbernate for database access(CONN-1161, CONN-1139)
      • Created test artifacts for Direct test cases using Trust Bundles (CONN-1113)
      • Updated Direct design to include message monitoring(CONN-1088)
      • Tested Direct config services on all application servers (CONN-729)
        • Validated that it works on GlassFish, WebSphere and JBoss. 
        • Identified a known issue with Auto refresh implementation using camel and will be addressed later.
          • CONN-1188 will be addressed later, added to backlog
        • Deployment issues were discovered with WebLogic (will be addressed next sprint including retesting on all app servers)
    • Admin GUI feature
    • Provided a demo to the federal partners during the product manager meeting on what has been accomplished this far on the Admin GUI feature.
      • Demo'd Create user, role based access, login, logout,remote gateway transaction display list and a list of sample screens for the Direct config GUI.
      • Demo was well received by the partners.
    • Admin GUI was successfully tested in IE 8.(CONN-1185)
    • Fixed login exceptions (CONN-1099)
      • All current PrimeFaces to be updated to Direct enhancements
      • Fixed CONNECTDirectConfig Deployment Issues on Weblogic 12c(CONN-1190)
        • Retested and redeployed successfully on all 4 supported application servers. 
      • Merged Direct Feature Branch Onto CONNECT Main Branch (CONN-1191)
        • Issue with Admin GUI loading on WAS 8.5. All other application servers work fine with Direct Config and Admin GUI together.
        • CONN-1222 created to address issue on WAS 8.5 next sprint.
      • Implemented message monitoring framework for Quality of Service(CONN-1195, CONN-1198)
      • Removed Apache Camel references from DirectConfig(CONN-1196)
        • Apache Camel's timer route for automatically refreshing bundles caused deployment to fail on JBoss; and team also suspected that there will be deployment issues on WebLogic. 
        • Removed for now. Auto-refresh needs to be looked at later.
      • Created test scenarios for Quality of Service (CONN-1199)
    • Admin GUI feature
      • Updated all current PrimeFaces pages with the correct CSS for look and feel including Direct Config GUI pages(CONN-1142 and associated tasks, CONN-11891151 and supporting tasks)
      • Left navigation, top navigation, footer, status, account management page
      • Migrated all Direct Config GUI wireframes to PrimeFaces (CONN-1118)
    • Support for NwHIN CAQH Core X12 Document submission serviceBug fixes
    • Bug fixes
      • CONNECT does not properly log WebServiceExceptions in doc query.(CONN-1180)

JIRA Planning Board of Committed User Stories for Sprint

...

134:

 Image Added

Image Added

Related Files


Sprint 134 code tag