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

Return requirements link referral #862

Merged

Conversation

Demwunz
Copy link
Contributor

@Demwunz Demwunz commented Mar 26, 2024

https://eaflood.atlassian.net/browse/WATER-4385

When a user clicks a "change" link on the "Check your Answers" page, they are directed back to the original input page for the answer.

This change will allow the user to submit the page again and return the "Check your Answers" page.

https://eaflood.atlassian.net/browse/WATER-4385

When a user clicks a "change" link on the "Check your Answers" page, they are directed back to the original input page for the answer.

This change will allow the user to submit the page again and return the "Check your Answers" page.
@Demwunz Demwunz added the enhancement New feature or request label Mar 26, 2024
@Demwunz Demwunz self-assigned this Mar 26, 2024
@Demwunz Demwunz force-pushed the WATER-4385-implement-rtn-req-check-your-answers-referral branch from b41561d to b0f284b Compare April 4, 2024 17:05
Demwunz and others added 8 commits April 4, 2024 18:06
https://eaflood.atlassian.net/browse/WATER-4403

In [Bump supplementary end year if no annual bill run](#875) we amended our billing engine for supplementary. We made it possible for users to generate supplementary bill runs in years where no annual has yet been created and sent.

Previously, the Billing & Data team would have to put a block on creating bill runs until the annuals were generated. This is because supplementary takes into account previous transactions whereas annual doesn't. Without the change creating a supplementary followed by an annual bill run would result in the customer getting charged twice.

We now determine when the last annual bill run was sent and use its financial end year as the end year for the supplementary bill run. Annual created in this billing period? Then the supplementary will start there and work back 5 years. If the last sent annual was for the previous billing period the supplementary will start _there_ and work back 5 years.

So, what's the problem? In this explanation, we keep referring to the last sent 'annual' bill run. But we've just spotted the logic which looks for the last sent bill run does not include batch type in the `where()` clause. Theoretically, we could create a two-part tariff bill run, send it and that would then match our query!

This change corrects the query we use to find the last sent annual bill run for a region.
…t-rtn-req-check-your-answers-referral' into WATER-4385-implement-rtn-req-check-your-answers-referral
@Demwunz Demwunz force-pushed the WATER-4385-implement-rtn-req-check-your-answers-referral branch from 71fae09 to e83eebc Compare April 5, 2024 17:39
@Demwunz Demwunz force-pushed the WATER-4385-implement-rtn-req-check-your-answers-referral branch from 81272f9 to 7aae747 Compare April 5, 2024 17:44
@Demwunz Demwunz marked this pull request as ready for review April 8, 2024 11:12
@Demwunz Demwunz merged commit 536642d into main Apr 9, 2024
5 of 6 checks passed
@Demwunz Demwunz deleted the WATER-4385-implement-rtn-req-check-your-answers-referral branch April 9, 2024 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants