What feature are you suggesting?

I just noticed that the licence numbers are the year and then a number. Are you able to carry over the licence numbers for each category? I need to be able to distinguish each type of licence with the corresponding category number. - n.n

Is your feature request related to a problem?

I don’t want to have new licence numbers each year for each person. We don’t worry about the year being part of the licence number. - n.n

Are there any workarounds? Are there any alternative solutions that would work?

Unlock the licence number field, and override the licence number.

Are there any other helpful details?

The current system uses a "category number - licence index" combination. Although the category number is being imported, it is a behind the scenes key that is never seen by the user. Using it in a licence number could result in confusion when new licence categories are created within the new system, and the keys are no longer numbers.

What feature are you suggesting?

A way to add upcoming payments to the transaction log for future dates. The payments should split the outstanding balance across a series of dates.

Is your feature request related to a problem?

In order to use the General Licence Manager as a payment plan initiator and tracker, this is needed.

Are there any workarounds? Are there any alternative solutions that would work?

Create individual transactions at the time of the processing.

Are there any other helpful details?

The solution must be able to export to a third party accounting system for processing, and possibly import the results from that accounting system.

What feature are you suggesting?

When exporting data from the reporting section, the underlying column names are used, which could be confusing when the user interface says something different.

Is your feature request related to a problem?

It is possible to rename the "licensee" fields, so seeing "licenseeName" in an export file doesn't make much sense.

Are there any workarounds? Are there any alternative solutions that would work?

Familiarize yourself with the backend column names.

Are there any other helpful details?

Not sure if column names should be renamed on the raw exports.

What feature are you suggesting?

At this time, the File Creation Number is the last four digits of the number of days since January 1st, 2022. An offset should be introduced to space out File Creation Numbers.

Add a fileCreationNumberOffset property to the config file.

Is your feature request related to a problem?

If multiple instances of the General Licence Manager are running, and both instances create a preauthorized batch for the same day, the two files will have the same file creation number. If the destination RBC account is the same for both batches, there will be issues processing the two files, as per RBC's documentation for the File Creation Number.

4 digit number (numeric) to identify this file, must be different from previous 9 numbers submitted for processing.

Are there any workarounds? Are there any alternative solutions that would work?

Coordinate with other instances to never process a batch on the same day, or manually adjust the File Creation Number in the file before uploading.

What feature are you suggesting?

Rather than completely blocking the ability to save a new licence when required approvals aren't checked, allow the licence record to be created, but block the ability to issue until the required approvals are met.

Is your feature request related to a problem?

It's difficult to create a pending record, and track the approval process.

Are there any workarounds? Are there any alternative solutions that would work?

Only enter records that have all of their approvals.

Code coverage just over 50%. Cypress testing can significantly increase that number.

• Add test databases environment variable.
• Limit test users to only access test database.
• Implement Cypress tests.

What seems to be the problem?

Even when the outstanding balance and the total of the batch transactions are equal, there are cases when the row will not appear green, indicating the totals match.

How can I recreate this problem?

• Create a licence worth $582.66.
• Split that amount across 7 batches.

What did you expect to happen?

When the outstanding balance and the total of the batches are equal, the row total should be green.

Is there anything else you can offer that might help?

There are other scenarios where the row remains white despite the values being equal.

What feature are you suggesting?

A way to optionally include bank numbers, branch numbers, and account numbers as part of the transaction log entry. Possibly verify bank and branch numbers against a table.

Is your feature request related to a problem?

When exporting transactions to be processed ( #32 ), the banking details are needed in a structured way to properly process the transaction.

Are there any workarounds? Are there any alternative solutions that would work?

Use licence fields to track banking information.

What feature are you suggesting?

Is it possible to disable [related licences] for our licensing system. - n.n

Is your feature request related to a problem?

This isn’t an option we would use and I don’t want anyone to accidentally try it and make changes to the system that aren’t required. - n.n

Are there any workarounds? Are there any alternative solutions that would work?

Just don't use it.

Are there any other helpful details?

• Feature added for a different installation.
• Feature could help link together licences that are often issued together, like vehicle and driver licences.

What feature are you suggesting?

A way to export transactions in a format compatible with banks, namely the Royal Bank of Canada.

Is your feature request related to a problem?

If upcoming preauthorized payments ( #30 ) are being tracked, they need to get to the bank for processing.

Are there any workarounds? Are there any alternative solutions that would work?

Manually process like a cash payment in the financial system.

Are there any other helpful details?

Originally, it was thought that the transactions would be processed by the accounting software.

What feature are you suggesting?

The only time a licence is deleted from the system is if they didn’t renew the previous year. This keeps our records on the system current and clean. We delete the old licences from the system to ensure that if the person tried to claim that they had a licence the previous year and their name is no longer in our system, then we know they didn’t renewal and they now have to pay the initial licence fee not the renewal fee. At the end of each year, I print out the spreadsheet that lists all of the licences we issued with the licensees information. Is there a way for the new system to provide the option for a year-end roll over to clear out the fees, and if possible to delete any non-renewals. - n.n

Is your feature request related to a problem?

This keeps our records on the system current and clean. - n.n

I don’t want to have new licence numbers each year for each person. ... I would like to be able to pull up an individual’s licence from the previous year, issue a renewal and update their information if required. The licence number should not change. - n.n

Are there any workarounds? Are there any alternative solutions that would work?

• History is not maintained.
• Additional filtering on past licences could help.

Are there any other helpful details?

The previous legacy system does not maintain history in the database, so this would maintain existing behaviour.

What feature are you suggesting?

A way to verify that the bank institution numbers, and possibly transit numbers, are valid.

Is your feature request related to a problem?

At this time, a user can enter any three digits for an institution number, and any five digits for a transit number. This could result in possible errors.

Are there any workarounds? Are there any alternative solutions that would work?

Don't make mistakes!

What feature are you suggesting?

The ability to track multiple licences of the same category on one record.

Is your feature request related to a problem?

No.

Are there any workarounds? Are there any alternative solutions that would work?

Create two related licences.

Are there any other helpful details?

This one is more about using the system to track ticket holders with multiple tickets.

What feature are you suggesting?

A way to unissue licences.

Is your feature request related to a problem?

If a licence is issued by mistake, there is no way to undo it.

Are there any workarounds? Are there any alternative solutions that would work?

Not really.

What feature are you suggesting?

Tracking tax in a separate column.

Is your feature request related to a problem?

Although most licences don't collect tax, other types of things that can be managed in this system could include tax.

Are there any workarounds? Are there any alternative solutions that would work?

Track the whole amount of the licence cost, including taxes.

What feature are you suggesting?

Hide the replacement fee.

Is your feature request related to a problem?

Confusing for systems that don't require replacement fees.

Are there any workarounds? Are there any alternative solutions that would work?

Ignore it.

What feature are you suggesting?

When editing a licence, clicking on a related licence should open the related licence in edit mode if the licence can be edited.

Is your feature request related to a problem?

When maintaining two related licences at the same time, bouncing between the two to make changes is cumbersome.

Are there any workarounds? Are there any alternative solutions that would work?

Open the related licence, then switch to edit mode.

Are there any other helpful details?

Watched a user maintain two sister licences at the same time, and heavily relied on the related links to bounce between licences, even after having the licences open in other tabs already. Kept having to switch to edit mode.

What feature are you suggesting?

I noticed that under the fee, we need to add a category for re-inspection. This is only for certain licences.

A re-inspection fee is at the discretion of the by-law officer or police officer. We would charge that in addition to the renewal fee.

Is your feature request related to a problem?

No.

Are there any workarounds? Are there any alternative solutions that would work?

Any amount can be added to the transaction log, including a re-inspection fee. There are notes available as well to further specify the nature of the transaction.

Are there any other helpful details?

Additional fees will affect determining the outstanding balance on a licence,

What feature are you suggesting?

Hide the table exports in the Reports section.

Is your feature request related to a problem?

The purpose of the table exports in being regularly misunderstood.

Are there any workarounds? Are there any alternative solutions that would work?

Read the notice above the exports that they are "full, unfiltered, and unformatted".

What feature are you suggesting?

In the Transaction Batch Builder, there should be a way to quickly split all licence balances across all of the batches.

Is your feature request related to a problem?

No.

Are there any workarounds? Are there any alternative solutions that would work?

Visit each licence row, and split each individually.

Are there any other helpful details?

Consider licences that already have amounts for their batches. Should those values be overwritten?

What feature are you suggesting?

Is it possible to adjust the new licence to have the same appearance as the current licence? - n.n

We find the [new] licence very plain looking and not very professional in appearance. I would like the City Crest to be bigger and maybe a border around it or something to spice it up (look more professional). Not sure if that is done with adding some color? - n.n

Is your feature request related to a problem?

No.

Are there any workarounds? Are there any alternative solutions that would work?

No.

Are there any other helpful details?

The licence in current system was created with a drag-and-drop reporting tool, so there are a variety of alignments that cannot easily be created in HTML.

What feature are you suggesting?

Show the outstanding balance in the transaction panel.

Is your feature request related to a problem?

No.

Are there any workarounds? Are there any alternative solutions that would work?

Look at the fee and the total in the transactions table. Calculate the difference yourself.

More and more dependencies are dropping support for Node 14 and Node 16 since both versions have reached end-of-life.

In November 2023, this project will follow suit, stop testing against these older versions of Node, and fully embrace Node 18 and Node 20.

• Update engines block in package.json to >=18.0.0.
• Unblock dependency updates that discontinue support for Node 14 and Node 16.
• Update Node versions in coverage.yml.

What seems to be the problem?

When updating transactions, it looks like the note is not displayed, and $0.00 transactions are not highlighting the amount in red.

How can I recreate this problem?

Add or update a transaction where another existing that has a note or $0.00 amount.

What did you expect to happen?

A similar look to the read only view.

What feature are you suggesting?

A way to group together licences by licensee, possibly in a sibling relationship.

Is your feature request related to a problem?

If a licensee holds two related licences (i.e. Taxi Driver Licence and a Taxi Vehicle Licence), there is duplicated work to maintain those two licences. Also, changes to one of those licences may affect the other, so finding the other licence quickly would be helpful.

Are there any workarounds? Are there any alternative solutions that would work?

Enter the information is twice. Use the licensee search filter to find the multiple licences.

What feature are you suggesting?

An admin interface to purge deleted records.

Is your feature request related to a problem?

When most records are "deleted", they are simply hidden from view.

Are there any workarounds? Are there any alternative solutions that would work?

Don't worry about it, or connect to the database directly and purge the records.

Are there any other helpful details?

May help keep the database cleaner after running the (under development) year-end process. ( #95 )

What feature are you suggesting?

The ability to update a transaction on a licence.

Is your feature request related to a problem?

Once upcoming transactions are possible ( #30 ) and tracking banking details is implemented ( #33 ), it may be necessary to update banking information for upcoming transactions.

Are there any workarounds? Are there any alternative solutions that would work?

Delete and recreate the transactions.

What feature are you suggesting?

There are certain licence categories that expire March 30th of the following year, regardless of the date of issue.

Is your feature request related to a problem?

Yes. Not all licences simply expire based on the start date of the licence.

Are there any workarounds? Are there any alternative solutions that would work?

Unlock the end date, and manually set it to March 30th of the next year.

What feature are you suggesting?

Is the system able to read a deadline date for licences and if the applicant is renewing after the deadline can the system revert the fee back to the original fee or to the late fee? - n.n

Is your feature request related to a problem?

If not no worries, we will just need to make sure that we keep an eye on the fee being charged. - n.n

Are there any workarounds? Are there any alternative solutions that would work?

Manually apply it.

Are there any other helpful details?

May be possible to implement using a formula additional fee, where licences created during a certain time range have an amount, while licences created outside the time range have an amount of $0.00. Would have to watch for fee recalculations changing the fee amount, and possibly hide required fees with a value of $0.00.