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

Add confirmation number #161

Merged
merged 8 commits into from
Sep 30, 2016
Merged

Add confirmation number #161

merged 8 commits into from
Sep 30, 2016

Conversation

lihanli
Copy link
Contributor

@lihanli lihanli commented Sep 26, 2016

fixes #106

describe '#confirmation_number' do
it 'should return the right confirmation number' do
subject.save!
expect(subject.confirmation_number).to eq("vets_gov_education_benefits_claim_#{subject.id}")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like the test is just a replication of the code. What if you tested that you can look up the claim number and get back the same claim?

@@ -37,6 +37,10 @@ def parsed_form
@parsed_form ||= JSON.parse(form)
end

def confirmation_number
"vets_gov_#{self.class.to_s.underscore}_#{id}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this get displayed to the user? Is there any reason not to create a random uuid for this? My assumption is that this is used to communicate with the call center, and I would be concerned about giving a sequential identifier without knowing what other checks the call center does to verify identity

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In an email, Shay wrote:

The confirmation number is displayed to the user when they submit. It is just used to trace the application, if needed. (We can pull up the application in VONAPP Admin based on the confirmation number).

It has no effect on the processing of the claim.

I'll ask for some followup on what "trace" means.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's an Admin Interface in VONAPP where admins can look up forms by submission ID, and print copies of them out. The call center just passes those confirmation numbers along to someone with access to that admin interface. We can use basically whatever we want, but we also may need to make some sort of 'retransmit' mechanism to send the 22-1990 to a different processing center.

Copy link
Contributor

@markolson markolson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you modify the 22-1990.erb template to use this, as well as changing the documentation to use vets_gov?

@lihanli
Copy link
Contributor Author

lihanli commented Sep 29, 2016

@markolson which documentation?

@@ -42,7 +42,8 @@ Content-Type: application/json
// when it was first submitted
"submittedAt": "2016-09-09T23:48:07.766Z",
// address of the VA regional office where it will be processed
"regionalOffice": "Eastern Region\nVA Regional Office\nP.O. Box 4616\nBuffalo, NY 14240-4616"
"regionalOffice": "Eastern Region\nVA Regional Office\nP.O. Box 4616\nBuffalo, NY 14240-4616",
"confirmationNumber": "vets_gov_education_benefits_claim_18"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lihanli this is the documentation I mentioned in the view

@lihanli lihanli merged commit eb55e4d into master Sep 30, 2016
@lihanli lihanli deleted the add-confirmation-number branch September 30, 2016 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

need confirmation number to give to frontend
4 participants