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.

Sign up for GitHub

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

Jump to bottom

EFT - Create migration that updates suspension_reason_code #21204

Closed
seeker25 opened this issue May 10, 2024 · 5 comments
Closed

EFT - Create migration that updates suspension_reason_code #21204

seeker25 opened this issue May 10, 2024 · 5 comments
Assignees
@sameer0422
Labels
Pay Work for Pay Team

Comments

@seeker25
Copy link
Collaborator

seeker25 commented May 10, 2024 •
edited
Loading

EFT - Create migration or data fix that updates suspension_reason_code

It's missing currently and blank in PROD.

bcgov/sbc-auth#2812
@seeker25 seeker25 added the Pay Work for Pay Team label May 10, 2024
@seeker25 seeker25 mentioned this issue May 10, 2024
Merged
@Jxio
Copy link
Collaborator

Jxio commented May 23, 2024

where to grab data as suspension_reason, only for NSF_SUSPENDED ones?
image.png

@seeker25
Copy link
Collaborator Author

seeker25 commented May 24, 2024 •
edited
Loading

I'd just set all the ones currently to whatever suspension_reason_code we're using for PAD NSF as a start?

Anything for EFT can be added in afterwards via code?

@Jxio
Copy link
Collaborator

Jxio commented May 28, 2024

OVERDUE_EFT_PAYMENTS?

@seeker25
Copy link
Collaborator Author

I thought we had one in there for EFT? need one for PAD?

@Jxio
Copy link
Collaborator

Jxio commented May 28, 2024

yeah I agree add to suspension_reason_code

@sameer0422 sameer0422 self-assigned this May 29, 2024
@sameer0422 sameer0422 mentioned this issue May 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sameer0422 sameer0422

Labels
Pay Work for Pay Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@seeker25 @Jxio @sameer0422