Thread regarding Wells Fargo & Co. layoffs

Teamworks Team Member Lookup functionality has been updated

And of course it's already broken.

by
| 1619 views | | 10 replies (last July 13, 2021) | Reply
Post ID: @OP+1bNJWvC7

10 replies (most recent on top)

Will this help us know what stealth laid off this week anlittle easier?

by
| | Reply
Post ID: @1ney+1bNJWvC7

Oh ye nay sayers!!!

AI is being incorporated in the search functionality and those of you who do not upskill and learn how the machine will read your minds to determine what you wish to search for, will not be around to see the full implementation of a beautiful process.

by
| | Reply
Post ID: @1cvs+1bNJWvC7

Don't forget DevSecOps too, they put you back 2 weeks alone.

by
| | Reply
Post ID: @1nck+1bNJWvC7

Sorry, but to make the change will require a code change, which necessitates us to go through DAST, and then we will need to go through qa, then testing approval, code freeze, unfortunately that will put us up against month end freeze so most likely mid August this will be fixed

by
| | Reply
Post ID: @yke+1bNJWvC7

Teamworks has the worst search functions of any web site in history. They are so bad, and always have been. They won't find anything helpful unless you type in EXACTLY what it's looking for. Rando search engines from the mid 90s, you know, the ones that went out of business and we never heard from again? They worked better than this. Thanks techies.

by
| | Reply
Post ID: @lgc+1bNJWvC7

It works!

I type in "useless & ineffective", and my name pops up!

by
| | Reply
Post ID: @blx+1bNJWvC7

It'll be fixed next sprint.

by
| | Reply
Post ID: @low+1bNJWvC7

lookup.wellsfargo.com/namesearch.aspx

by
| | Reply
Post ID: @wxl+1bNJWvC7

The need so search on "Employee Lookup" NOT "Team Member Lookup" ... they SQL should reflect this change.

by
| | Reply
Post ID: @kpi+1bNJWvC7

Confirmed.
Maybe they have to change it from "where [Team Member Lookup] = '%@q%'
" to "where [Employee Lookup] = '%@q%'" in the SQL statement.

by
| | Reply
Post ID: @lxe+1bNJWvC7

Post a reply

: