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

8554 fix transaction history for resubmit #1163

Merged
merged 2 commits into from
Aug 12, 2021

Conversation

vysakh-menon-aot
Copy link
Collaborator

Issue: bcgov/entity#8554

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

@sonarcloud
Copy link

sonarcloud bot commented Aug 12, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@andrepestana-aot
Copy link
Contributor

Do we need this? I thought Severin would change RESUBMIT to NEW in the UI...

@severinbeauvais severinbeauvais merged commit e74b3b4 into bcgov:release-1.1.1 Aug 12, 2021
@severinbeauvais
Copy link
Collaborator

Do we need this? I thought Severin would change RESUBMIT to NEW in the UI...

Yes, this change is for the PAYMENT (not the REQUEST).

@vysakh-menon-aot vysakh-menon-aot deleted the feature/8554 branch August 12, 2021 16:33
@andrepestana-aot
Copy link
Contributor

andrepestana-aot commented Aug 12, 2021

Do we need this? I thought Severin would change RESUBMIT to NEW in the UI...

Yes, this change is for the PAYMENT (not the REQUEST).

But as you're going to send NEW now we won't have any RESUBMIT payment anymore, right? How can we identify it is a 'new' NR and the payment should RESUBMIT?

@severinbeauvais
Copy link
Collaborator

But as you're going to send NEW now we won't have any RESUBMIT payment anymore, right? How can we identify it is a 'new' NR and the payment should RESUBMIT?

The payment is created separately from the NR.

@andrepestana-aot
Copy link
Contributor

ok. So we're going to continue sending the request_action_cd as RESUBMIT to namex-api and namex-api needs to create a payment action as RESUBMIT? If so we'll need to change namex-api.

@severinbeauvais
Copy link
Collaborator

ok. So we're going to continue sending the request_action_cd as RESUBMIT to namex-api and namex-api needs to create a payment action as RESUBMIT? If so we'll need to change namex-api.

When the user clicks the confirm button...

  1. first the NR object is created, with action=NEW - see https://github.com/bcgov/namerequest/blob/18e008a779170b05784faf3c8b8b3236124b9aa2/src/components/dialogs/resubmit.vue#L208
  2. then the payment object is created, with action=RESUBMIT - see https://github.com/bcgov/namerequest/blob/18e008a779170b05784faf3c8b8b3236124b9aa2/src/components/dialogs/resubmit.vue#L227

@andrepestana-aot
Copy link
Contributor

ok. Yes. I think it's ok. Thanks!

@severinbeauvais
Copy link
Collaborator

Just to close this off:

Andre, I think I understand your concern: when I asked yesterday about the impact to use NEW instead of RESUBMIT action, you thought both the NR action and payment action would be changed -- but only the NR action has been changed. Preliminary testing shows that both NR and payment are working correctly. Riyaz will help with more testing.

Yes, I also think it's OK :)

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 this pull request may close these issues.

4 participants