-
Notifications
You must be signed in to change notification settings - Fork 59
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
BE - CoA Corrections - Filer #3162
Comments
shahriar-khan-fw
modified the milestones:
Entities 26 - Complete Step 2; Start Step 3,
Entities 27 - Step 3 - BComp - Share Structure
Apr 1, 2020
shahriar-khan-fw
modified the milestones:
Entities 27 - Step 3 - BComp - Share Structure,
Entities 28: BCOM Step 5
Apr 14, 2020
Kaineatthelab
modified the milestones:
Entities 28: BCOMP Step 5,
Entities 29 - BComp NR flow & FED
Apr 29, 2020
shahriar-khan-fw
modified the milestones:
Entities 29 - BComp NR flow & FED,
Entities 30 - Outputs, Notification, BN Messaging
May 13, 2020
I removed this from LEAR - Release 2.10 as that's going out today and this ticket is still In Progress. I left Releases blank for now. We can assign this to a release later. |
shahriar-khan-fw
modified the milestones:
Entities 32 - Testing, Bugs, Dashboard,
Entities 33 - End to End Testing
Jun 24, 2020
shahriar-khan-fw
modified the milestones:
Entities 33 - End to End Testing,
Entities 34 onwards
Jul 8, 2020
shahriar-khan-fw
modified the milestones:
Entities 34 - BComp maintenance filings,
Entities 35 - Maintenance filings, Staff payment
Jul 22, 2020
jdyck-fw
removed this from the Entities 36 - Complete Maintenance Filings, BCOL Payment, Corrections and Name Request changes milestone
Aug 20, 2020
This is no longer needed |
This was referenced Nov 29, 2023
This was referenced Nov 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Write the Filer portion of:
Scenario: Staff files a correction to en existing CoAddress
Background A customer has recognized that a CoA has the wrong information and wants to correct it, by sending in a correction to staff
Feature A CoA correction needs to be filled by a staff member
GIVEN There is an existing CoA Filing that is past the Bob date
WHEN Staff correct the online CoA and it is submitted
THEN the API should store the CoA after validating ii
AND then place it on the Queue for processing
AND the queue filer should adjust the model history to reflect the correction.
The text was updated successfully, but these errors were encountered: