Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove VACOLS login #311

Closed
2 of 3 tasks
shanear opened this issue Aug 25, 2016 · 10 comments · Fixed by #362
Closed
2 of 3 tasks

Remove VACOLS login #311

shanear opened this issue Aug 25, 2016 · 10 comments · Fixed by #362
Assignees

Comments

@shanear
Copy link
Contributor

shanear commented Aug 25, 2016

Instead map CSS Station IDs to RO ids, and use that to know the user's RO.

Depends on #310

Current plan:

  • Create a mapping of Station IDs to RO ids
  • Show RO id using the mapping instead of the VACOLS id
  • Remove VACOLS login code
@shanear
Copy link
Contributor Author

shanear commented Aug 25, 2016

@KHarshawat @gmorgana-va do either of yall know where to find this mapping?

@KHarshawat
Copy link
Contributor

Emailed Chris Denno to see if I could get mappings for the remaining ROs with weird edge cases like those that end in something like RACC or COWAC, Pension Center, or Education Center.

@KHarshawat KHarshawat self-assigned this Aug 25, 2016
@shanear
Copy link
Contributor Author

shanear commented Aug 25, 2016

@KHarshawat If it's helpful, we could run some reports on which of these ROs have ever had a ceritfication done with caseflow. That way we'd know which ones to account for

@KHarshawat
Copy link
Contributor

KHarshawat commented Aug 25, 2016

@shanear Sure that'd be super helpful! Chris mentioned that may of these are not even used any more.

@KHarshawat
Copy link
Contributor

@KHarshawat KHarshawat assigned shanear and unassigned KHarshawat Aug 29, 2016
@KHarshawat
Copy link
Contributor

We've determined that we don't need to restrict usage by RO (department-of-veterans-affairs/appeals-pm#679) so I'm removing the on-hold label and moving this into the sprint backlog.

@shanear
Copy link
Contributor Author

shanear commented Sep 15, 2016

This is blocked until we start using CSS on 9/26

@shanear
Copy link
Contributor Author

shanear commented Oct 21, 2016

After a conversation with Jed, it looks like this one will be tricker than we thought:

  • 10 of the 58 Station IDs have multiple regional offices associated to them, and according to Jed, it's important for them to be correct, so we would need to force users in those RO's to disambiguate.
  • The regional offices that share the same station ID are always in the same city and state. We've received feedback that sometimes users want to certify appeals from other RO id's in their city and it's annoying to log in and log out to do this.

Proposed solution

  • If there is a 1 to 1 Station ID / RO ID mapping, then skip the VACOLS login
  • If not, keep the VACOLS login for those users
  • For certification, the only reason getting the RO correct matters is the RO id entered into the Form 8, it may be ok to just use the RO already listed on the appeal for that field, and punt on the disambiguation
  • Then for future caseflow features, speak with DRO's from the regions where they have multiple RO's and see if there's an easier way for them to disambiguate which RO they are acting under (like an RO picker?)

What do you think @KHarshawat?

@shanear
Copy link
Contributor Author

shanear commented Oct 24, 2016

postponing this for #325, since doing that will make this considerably easier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants