nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bug - transactionRules pasting payee name removes last word

Randy1234

Pasting into payee field removes last word.

Explanation pasting 4 words results in 3 "word blocks" being created.

Example below.

Action: Pasting "Tim Hortons"

Expected result: should create 2 word blocks for the words "tim" and "hortons"

Actual result: creates only the "tim" word block

Screenshot-Google Chrome-2024-12-01 08.25PM.png

Find more posts tagged with

Transaction Rules

Comments

UrsulaA

I noticed this behavior too but did not report it. I just type the second word again, press tab, and the rule gets created as intended with two or more words.

Randy1234

ya mostly a pain with manual accounts where I may add 30+ payee rules in a review.

fix is isolated and straightforward (intercept paste, trim trailing space and readd trailing space (to maintain current text entry logic)

Coach Natalie

@Randy1234, thank you for taking the time to report this to the Community!

It looks like this issue has already been reported, so I've started tracking the ticket and will post back here with updates.

-Coach Natalie

SIMPL-21941

Coach Natalie

@Randy1234, hello!

I'm going through old escalations, and I just wanted to let you know that the ticket for this issue is still open and being worked on. I gave it a bump in hopes of getting some movement on it.

Thank you for your continued patience as this is worked on!

Coach Natalie

@Randy1234, hello!

I'm checking open escalations, and I just wanted to let you know the ticket for this issue is still open and being worked on. We will continue to post back here with any updates.

Thanks for your continued patience!

Coach Natalie

@Randy1234, a fix for this issue is expected with the 6.11.0 Web Release.

Thank you!

Coach Natalie

Web Release 6.11.0 is out, and this issue should now be fixed.

Thanks!