Frideas for 10 May 2024

Here’s my Fridea:

https://epicor.ideas.aha.io/ideas/KIN-I-4927

KIN-I-4927: Kinetic / Classic Updatable Dashboad For Bulk Menu Changes

Please make it easy for your legacy customers to migrate to the Kinetic UI. There are 3190 menu items, and each one has to be manually changed in Menu Maintenance > Form to Use from ‘User Choice’ or ‘Classic’ to ‘Kinetic’.

This is extremely tedious! Each form has to be changed manually, in every menu location. If we want to migrate our users to use the Kinetic Purchase Order Tracker form, then we’ve got to change 10 different menu locations.

Epicor providing a dashboard where we can change forms in bulk would streamline the migration to Kinetic, and help drive earlier adoption.

EDIT: We could create an updatable dashboard or change the ‘Ice.Menu.DefaultFormType’ field to ‘URL’ via the Menu DMT template, but why should each of Epicor’s thousands of customers have to create this themselves? It’s a lot of collective work (friction) when Epicor should be interested in speeding up Kinetic adoption.

4 Likes

You make the case on a base system with no customizations. I have 4477 menu items so that means 1287 additions of custom reports and dashboards. You got my vote.

Voted. We were able to use DMT to deal with this but it was a giant pain.

1 Like

When 2021 first came out, there was a toggle on the top level menus to change all the child items at once. Not sure why they took it away.

Here is @LarsonSolutions one for today:

https://epicor.ideas.aha.io/ideas/KIN-I-4930

1 Like

When you go to the main menu in Kinetic there’s an process under the “kabob”

This can be selected at the various levels - if you want to just update Finance select the finance management level first.

image

This allows you to turn on or off the Kinetic screens…

3 Likes

Here is our dashboard for managing menus exported from 2023.2. I mostly use it for deploying customizations. Historically Epicor’s Solution Workbench is dog shit for handling menu changes.

AdvancedMenuMaint.dbd (173.7 KB)

5 Likes

Speaking of menus, this is my favorite Idea:

https://epicor-manufacturing.ideas.aha.io/ideas/KIN-I-3883

Moving security to securing the securable instead of menus entries is in my opinion one of the most critical things that needs to be fixed.

With the current security method, updates create security exceptions which require monitoring:

  • Grab a copy of Ice.Menu and Ice.Security before and after every update.
  • Look for new Menu entries. Look up the default Security applied by the update; most will be SecurityMgr = false and EntryList = '*'.
  • Verify that previously existing Menu entries have the same linked Security, and that EntryList and SecurityMgr haven’t changed.
  • Look for re-activated menu paths that you previously deactivated, those may receive a default security as well.

Then go to Menu Maintenance and apply the security you already applied to other menu instances of each process.

3 Likes

I thought this idea existed but I couldn’t find it so I just created it again, hopefully not a duplicate (but if so point me to the original!) I don’t want to have to manually turn on the filters on every grid, I just want them to be on:
https://epicor.ideas.aha.io/ideas/KIN-I-4934

Also please keep voting for this one, looks like there may possibly be movement on getting field help to stay on but its not clear:
https://epicor.ideas.aha.io/ideas/ERP-I-515

1 Like

Says right in there with an admin note. Planned for 2024.2…

Why did they take away the link to see and modify the security applied to the menu item that works so well in Classic?

I realize that I could use application studio to add a grid view of the security table.

1 Like

It’s not clear exactly what is being planned, and, prior features have been noted like that before and didn’t end up getting released due to changing priorities, that is why I am saying keep voting for it so they don’t pull it.

1 Like

https://epicor.ideas.aha.io/ideas/KIN-I-4061

1 Like

Oh I gave it a vote.

@LarsonSolutions - No way! So that’s where the old Kinetic Application Maintenance went. That’s a great tip, and will make moving full folder paths much faster to Kinetic.

In Classic-speak, the ‘Enable New UI’ checkbox sets the FormToUse to ‘URL’ - e.g. Kinetic.

‘Enable User Override’ sets FormToUse to ‘Default’ - e.g. User Choice.

And if neither are checked, then FormToUse is ‘Base’ - e.g. Classic.

@jgiese.wci Thank you! I’m trying that now.

Both of these together should save hours of time.

1 Like