Describe the bug
When a user clicks on "FILE and PAY" and then returns to dashboard and clicks on the "CANCEL PAYMENT" in the dashboard
then the payment gets canceled and
When the user tries to make a filing again and the "your cart" SECTION shows the outstanding invoice from the previous filing.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://test.bcregistry.ca/cooperatives/CP0000621/'
2. Click on 'FILE AND PAY'
   3.Return to DASHBOARD and CANCEL PAYMENT
   4.Now start another FILING and continue to cart and then
   5.See Error

Screenshots
If applicable, add screenshots to help explain your problem.

Describe the bug
When an user logs in with the CP Number say for example cp0001202 then the user will be able to login,update the business profile but the dashboard page shows the error saying DASHBOARD ISN'T AVAILABLE.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://dev.bcregistry.ca/cooperatives
2. Enter cp0001202(Make sure this is in lower case) and the passboard
3. Try N navigate to dashboard page
4. See error

Expected behavior
Either the dashboard shows up no matter uppercase/lower case
OR
The user must have to login only with the uppercase (CP0001234)

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Would you mind helping me get some stats needed to measure the percent and rate of user adoption? I’m looking for:

• Cooperative name
• Cooperative number
• Count of total filings completed per cooperative
• Display filing type completed for each cooperative.
• I’m assuming all cooperatives that have completed filings are still active but if not, please check both historical and active states.

Describe the bug
The downloaded PDF contains all the information of the directors even though the stanaldone change of director's display section shows the expected output.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://coops-dev.pathfinder.gov.bc.ca/Dashboard'
2. Click on 'Login' make changes in the Directors section both in standalone or AR then print the receipt then you see the error

Expected behavior
The downloaded PDF should only contains the current and newly appointed directors and should not display the ceased directors

GO with the CP0001364 && Passcode:238276299
Now CEASE A DIRECTOR make the payment.
Then go the the PDF DOWNLOADS and then we get too see the ceased directors as well.

Describe the bug
In the Test environment, filings are completing, but the PDFs can't be downloaded from the dashboard.
The receipt works, but all others fail.

The only error, is a 500 on the following call:
GET https://legal-api-test.pathfinder.gov.bc.ca/api/v1/businesses/CP0001327/filings/173
Response:
{"message":"b'{"message": "Internal Server Error"}\n'"}

Examples:
CP0001202, 922656210
CP0001327, 646253112

To Reproduce
Steps to reproduce the behavior:

1. Complete a filing
2. Once you're back on the dashboard, click a PDF
3. See error

Describe the bug in the current situation
When a user Files a an Alteration Filing and adds a New Names Translation, then the Added tag appears on the newly added Names Translation but when the user clicks the Done button in the Names Translation component then the Corrected Tag appears on the filing.

Impact of this bug
All users filing the Nmaes Translation

Steps to reproduce the behavior:

1. Go to 'https://business-edit-dev.apps.silver.devops.gov.bc.ca/businesses/edit/BC1230109/alteration?alteration-id=111751'
2. Login with BCRE0001
3. Add a new Names Translation
4. See the Corrected Tag appears instead of the Added

Screenshots/ Visual Reference/ Source

When a user logs in and clicks on the affiliated NR then the user is redirected back to the MANAGE BUSINESSES page instead of the INCORPORATION DASHBOARD
To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://test.bcregistry.ca/cooperatives/auth'
2. Click on 'Affiliated NR'
3. See error

LOG IN CRED
BCREG0004
98904

1. Added 'Cameron Wulff' as required by Kaine Sparks
2. Fixed bug from test_job.py
3. Added /opt/app-root/data/ for temp files when program runs on docker

The Total Amount of Incorps to Date

Description: Added the total amount of incorps to date to jupyter notebook report for incorps.

Acceptance / DoD:

• Product Owner advised if task >= 1 full-day, or forms part of the business day
• Requires deployments
• Test coverage acceptable
• Peer Reviewed
• Production burn in completed

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

we need to add github workflow for filings notebook report to keep consistent with other appliations.

This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Describe the bug in current situation
When the staff lands on the correction filing and fill all the mandatory fields and when he enters the payment info then the file and pay button is not enabled thereby blocking the filing

Impact of this bug
All staff users in dev

Steps to Reproduce
Steps to reproduce the behavior:

1. Go to '.https://dev.bcregistry.ca/cooperatives/'
2. Click on Correction
3. File the Correction
4. See error

Actual/ observed behavior/ results

Expected behavior
A clear and concise description of what you expected to happen. Use the gherking language.

Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

Description:

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Describe the bug
When a user is in the AR Filings Page then the file and pay button is enabled even though the user doesn't complete the change of address,This bug was present in the Appoint new director component and has been solved the same can be implied here.
To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://coops-dev.pathfinder.gov.bc.ca/cooperatives'
2. Click on 'File Now'
3. Scroll down to 'Change of address'
4. Make some changes and dont hit the update address button
   5.Even though the File and Pay button is enabled which should not be the case.

Expected behavior
The File and Pay button should be disabled until the "Update Address" is clicked.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

PLACEHOLDER - Will need to populate this with more accurate information with details from the team.

We are going to be replacing the tokenService with a custom keycloakService. This should involve the following:

• Add keycloak services to package.json
• get the keycloak.json (config) file and add it to coops-ui
• Swap out the tokenService with the new keycloakService in main.ts
• Add any unit-tests to ensure the keycloak-service is working as expected.

*** ADD MORE DETAILS, ACCEPTANCE CRITERIA AND TASKS ***

When C1198486 tries to generate it's business summary it get an error.

Error traced to src/legal-api/reports/

business_document.py:164 - _get_template_data: 'C'

The document generation is failing in this routine because if the 'C in the company identifier.

Hi Kaine,
Would you mind helping me get some stats needed to measure the percent and rate of user adoption? I’m looking for:

• Cooperative name

• Cooperative number

• Count of total filings completed per cooperative

• Display filing type completed for each cooperative.

• I’m assuming all cooperatives that have completed filings are still active but if not, please check both historical and active states.

• from Trish Reimer

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.