Adjust it so that recurring transactions that have their last occurrence
(LO) on a weekend or a holiday in the near past and HWT NEXT_WORKDAY (NW)
are also grabbed. Otherwise there would never be a reminder about them.
On the actual due date the reminder is deferred because of the HWT and
for later runs it's not grabbed because of the condition
'...LastOccurrenceGreaterThanEqual(now)'.
Also add a unit test case for this. Further add better logging.
Account groups are a simple way to group accounts. Currently the design
of the group is very sparse and supports only a name. However, as this
feature is a stepping stone for the much bigger 'Reports' feature this
will most likely be subject to change.
With this change new accounts are also required to get assigned to a group.
Previously the query was autogenerated but the WHERE clause was wrong,
because the braces where at the wrong places and thus the query matched
wrong data.
Rework POM structure:
- Move general profiles to new parent
- Add dependency management for project dependencies
- Move general properties to new parent
- Alo remove version numbers from child modules, so versioning is now done via parent
Rework POM structure:
- Move general profiles to new parent
- Add dependency management for project dependencies
- Move general properties to new parent
- Alo remove version numbers from child modules, so versioning is now done via parent
Use URLdecode also for the descriptions of (recurring) transactions.
Further fix a bug with recurring transactions that have a firstOccurrence date in the future.
Rework URL decoding into own util method because the previously used method
is only available since Java 10 (current runtime is 1.9 however).
Further adjust unit tests and test data to reflect the change.
Also add a migration script for already installed instances.
Hard-deleting recurring transaction cannot be done reliable because a transaction may have a foreign key reference to a recurring transaction of this transaction has been created from a recurring transaction. Thus hard-deleting a recurring transaction may lead to data inconsistencies.
