Page History

Current Sprint -  Sprint 30 (May 12, 2016 – May 25, 2016)

LexEVS 6.4 Agile Development - Sprint Status

NCI has deployed LexEVS core API and LexEVS Remote API war files are deployed.

Tracy mentioned that she will test from her client.

Kim has been testing with the remote API. He is running into the issue related to LEXEVS-957. The Mayo team will discuss possible solutions to this issue.

Discuss Issues

• LEXEVS-1729
• LEXEVS-1730
• LEXEVS-1731
• LEXEVS-1732

We discussed the priority of these JIRA items and if they need to be in the LexEVS 6.4 release.

• Investigate if this is a bug that we can reproduce. If this is a bug, then we need to fix for 6.4

• There is a workaround. After This issue can be completed after LexEVS release 6.4.

• Feature request for 6.4.

• There is a workaround. After This issue can be completed after LexEVS release 6.4.

LexEVS core API 6.4 and LexEVS Remote API war file 6.4 war files are deployed. Tracy and Kim have been testing.

CTS2 6.3 - NCI will deploy to existing CTS2 6.3 container. NCI will let us know when this is done and Mayo and NCI will test the API on DEV.

• Cory to send a link to Tin for our online API.
  • https://lexevscts2.herokuapp.com/cts2
• Cory to send JIRA item that was fixed to Tin.

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1768

• Larry would like to move CTS2 6.3 up the tiers to PROD as soon as possible.

CTS2 6.4 - will deploy to a new container that is currently empty.

PIV card updates

No updates. form

Kumar asked if Deepak filled out by deepak vpn the form: VPN remote access user agreement. Cory will follow up with Deepak.

LexEVS External Users

• Updates

Gilberto mentioned that there was an app support question from a user at Georgetown University.

Gilberto pointed him to the LexEVS wiki about the LexEVS API and CTS2 API.

These seem to happen when indexes are deleted and the container is still

running and

holds a reference to them.

One possible workaround is to shutdown the container are restart it. NCI team will continue to look into this.