Kinetic ideas that will not be implemented

Disappointed that so many of my ideas are marked not planning to implement. I still want all of these things and think they would have value to a lot of other users as well. There are plenty of ideas on the site marked delivered/in development that have only 1 or 2 votes, so I don’t think these were rejected for low vote count. It sure would be nice if there were any explanation of the reasoning why none of these will be done.

Include BAQ name in event viewer
https://epicor-manufacturing.ideas.aha.io/ideas/KNTC-I-2497

Odata feed should use BAQ labels
https://epicor-manufacturing.ideas.aha.io/ideas/KNTC-I-2491

Enterprise search should have configurable date cut offs
https://epicor-manufacturing.ideas.aha.io/ideas/KNTC-I-2385

In a process set, choose what happens when a task fails
https://epicor-manufacturing.ideas.aha.io/ideas/KNTC-I-2373

Company-specific report logos
https://epicor-manufacturing.ideas.aha.io/ideas/KNTC-I-2293

Useful security report
https://epicor-manufacturing.ideas.aha.io/ideas/KNTC-I-2265

1 Like

It seems that if an idea is popular enough, but won’t be implemented, that it’s more likely to get an admin response.

It would be nice to have one on everything, but I’m not sure how much work would go into it.
(there’s a lot of ideas)

Maybe they could add some common responses to a list that they could use for the ones that don’t need a custom response.

1 Like

Yes some kind of tagging

You should make an idea…

Ideas that won’t get implemented, the awareness has been raised for the last 26 years by whatever generations reporting tool for the decade was:

AutoClockOut lag hours field on the shift table.

Global Hot Keys for printing.

Inactive Field on all setup folder tables.

Change Log - overhauled, record was / is data for reporting.

Copy a user to create a user.

Ability to change a part number to another part number.

Log all screens, reports & dashboards a user accesses.

2 Likes

It’s like you don’t even know me. Of course I already did lol.

1 Like

Totally agree with all of these. Yet we are supposed to get excited because they moved some fields around on the kinetic screens? When that is literally the EASIEST (if not the only easy) thing to do in app studio?

Ok, I’m a developer, so I’m going to have to push back a bit on this one.

While that may be the easiest thing they can do, it doesn’t mean it’s easy.
Lots of discussions on architecture, ease of use, dev testing, user testing,
feedback etc, all has to occur.

The Epicor world is a lot bigger world than all of us loudmouths over here.


That’s not to say I wouldn’t like more information into the development process,
the architecture, usability discussions. Transparency is almost always good.

2 Likes

Granted. But my point is that I personally would rather that development effort be spent on the things I can’t easily change on my own, like the things on Patrick’s list.