Skip to content
This repository has been archived by the owner on Nov 16, 2019. It is now read-only.

Auto complete addresses and more

Latest
Latest
Compare
Choose a tag to compare
@mischa-s mischa-s released this 25 Jun 02:19
· 267 commits to master since this release
0.27
570ce4a
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Notes - RR Application Form (version 0.27)

  1. Addresses are now auto-completed when a dataset has been provided from a council (currently Kāpiti and Tauranga) (RR-489)

  2. The question asking for total rates has been completely removed for all councils. This amount will be populated auto-magically in the council view when addresses have been matched based on council datasets. The total rates amount is still displayed (needs to be signed) as part of the signature flow (RR-489)

  3. Added a reference to the calculator on the first page of the application form to help decide whether to apply (and reduce the number of people applying unsuccessfully) (RR-451)

  4. Fixed typos (including a typo for "dependant") (RR-480)

  5. Fixed layout issues on small (mobile) screens where the long supporting content on the dependants question caused the keyboard to be displayed, but the field to be off the bottom of the screen (RR-428)

  6. Fixed an issue where users were taken to the bottom of the next page when clicking "Next" (RR-248).

  7. Fixed an issue where very long email addresses were not breaking across multiple lines on the application summary screen (and causing layout issues) (RR-429)

  8. Significantly reduced the amount of content on the first page of the application form based on feedback (RR-398)

  9. Moved the value proposition for entering an email closer to the email field (i.e. that you'll get an email confirmation) (RR-411)

  10. Fixed an issue where users clicking the back button while in the application form (instead of previous) were taken to the first page of the application every time (RR-436)

Known Issues

  1. Very long batch names break the page layout on the "Batched" screen (please let us know if this is a real problem).

  2. The additional question (displayed when income entered is < $5000) "How did you support yourself on less than $5,000?" has not yet been implemented.

Release Notes - Pancake (version 0.27)

  1. Application for which addresses have been auto-completed (and were accepted as a match) when ratepayers apply will have Valuation ID and Total Rates pre-populated in the council view (RR-491)

  2. The layout of the batch screen has been cleaned up, including the addition of download icons to make it clear when header sheets have been uploaded (and for DIA users: that all applications in a batch can be downloaded) (RR-514)

  3. It is now possible to enter an Application ID against an application. Valuation ID, Customer ID, and Application ID can be edited in both in "Not signed" and "Signed" state independently of the core (signed) data making up an application (and without needing to re-sign the application). This change supports the Kāpiti workflow, and we believe it paves the way to further integration in a later phase.

  4. Both Valuation ID and Application ID are displayed on the "Processed" tab/screen. This supports the Kāpiti workflow (and likely other councils with similar workflows if/when they join in later phases).

Known Issues

  1. On the batch edit screen the eRMS Header Sheet is referred to as a "Cover sheet".

  2. Support for the additional question "How did you support yourself on less than $5,000?" has not yet been implemented.

Assets 2
Loading