Workflow: New/Updated Alias + Categorization

[monomolecular]

The .Net version of of MyMoney supports a workflow/transaction processing loop which is not yet handled in the Flutter version. There's also a little bit of room for improvement in the new implementation. Here's the basic loop...

1. New transactions - are added to the MyMoney DB.
2. Transactions are reviewed - by the user, and they payees may or may not have been handled previously with an alias. It needs to be easy to find the related and not yet merged payees so that there can be...
3. Alias additions/updates - may be needed in order to group the new transactions with any previously seen and collected under an alias. Ideally, a single regular expression, or ruleset would exist for a payee, and a small tweek might be all that's needed (e.g., changing to case insensitive, or handling multiple representations as an OR clause within the regex.
4. Recategorization - is the next step once the aliases have been cleaned up, it might be possible to automatically categorize the new transactions if all transactions share one category. If multiple exist, it would be ideal to have a short list of categories to reuse.

Notes/Thoughts:

• Assuming the transactions are being reviewed and "processed" by the user in chronological order (or perhaps alphabetic order), it adds a lot of steps and breaks the flow (in the Windows app today) to perform step # 3. It requires leaving the transaction tab, searching manually for related aliases, editing or writing some new ones, etc.
• It would be really nice to have the original payees maintained and the ability to reprocess the application of the aliases multiple times as regexes are tried.
• If there are multiple regexes, it could be nice to group them under the alias when sorted... which happens today, but moving the payee column to the left on the aliases screen might feel better and ultimately making them collapsable (regexes collapse under an alias) when the same feature is added to the category hierarchy on the category page.
• The expandable/collapsible panel shown at the bottom of the transactions screen could be used to show the aliases for a given transaction, or multi-selected set of transactions.
• Since there's no right-click on the Windows/Mac version of the app... perhaps hotkeys would be in order? Anything which could reduce the number of clicks and increase speed would be nice.

[monomolecular]

Another note on what I'm doing now. I keep both the Flutter and .Net versions open side-by-side on my widescreen monitor. The transaction view on the Flutter version is better then the .Net version... So I'm using it to backtrack through my transactions across all cards. I identify payees needing an alias and categorization in the Flutter version, and then go and fix those in the .Net version. This includes searching for variations in the payee names across multiple accounts (mostly credit cards), ideally writing one robust regex, then searching for the new alias if it didn't stay in my results (e.g. search for ATT, rename to AT&T, search for AT&T, select it, then recategorize all transactions under the new alias). I go through 10 or so, then save, then close and reopen the Flutter version so I can see the changes there. Related issue, #46.