On Friday, it’s EpiUsers Frideas Day! Have you been to the Epicor Ideas Portal recently? If so, are there some ideas you want to encourage other users to vote for? Maybe want to add comments to an existing idea?
There is this idea about combining all forms of shipping into one app. It has some… disagreement on the forum here.
Create an Inspection Queue Manager similar to Material Queue Manager. I picture this working much the same at Material Queue Manager and Material Request Queue.
A nonconformance would be entered the same as it is now. NCMs would show in the Inspection Queue Manager grid where a QA Dept Manager could assign them to specific Inspectors. There would be a Inspection Request Queue where an Inspector could select NCMs to work on, selecting them like a Material Handler does a Material Request. Those selected and/or assigned NCMs would show in a ‘My Inspections’ tab/grid where the Inspector would process them.
The power of Part Entry makes it useful, sure, but I loathe giving people access to it because it does EVERYTHING.
What I mean is that this single screen has these components:
Class (affects accounting)
Group (accounting and sales)
Revisions (for Engineering)
Buyers/suppliers (purchasing dept.)
Manufacturing lot sizes (production and purchasing)
Country of origin (for shipping)
Alternate parts (for sales orders)
Adding warehouses (affects material movement)
Qty-bearing (accounting and others)
Source Type - i.e. manufactured vs. purchased (sourcing dept.)
Days of Supply (planning dept. [MRP])
ABC codes (cycle counting)
Inspection Required (QA)
Attachments (safety dept. uploading SDS, for example)
The breadth of roles here is astounding.
Basically I just never let people use Part Entry except for a very small handful.
Over the years I have made probably dozens of updatable dashboards for users to update Part-Entry-kind of settings instead of granting access to Part Entry. Likewise I’ve made several BPMs to prevent anyone from changing things they ought not.
But if Part Entry could be sectioned off into areas with their OWN permissions, that would be really nice.
We need additional hooks/triggers in App Studio such as OnMouseEnter/OnHover, KeyPressed, DataView Initialize (load) Before and After, and others.
Additional Grid component event hooks would be nice. Before and After ApplyFiler for example. The grid appears to do client-side filtering when HasMorePages=false. In this case, dataview change events aren’t raised so there’s no reliable hook for onApplyFilter.
When selecting a certain View Option that required a selection for a From or To range it would be nice to have these boxes show up automatically and stay hidden otherwise.
It is not intuitive when on an ALL view with the ranges also being displayed and adding a range without change the view will not filter the correct information.
When a particular View Option is selected then we should be able to intercept that using a client event.
But specifically tied to the changing of the view options dropdown, so you can do things like hide filter/date picker fields that are tied to specific view options.
This i vote for. I have created multiple versions of Part Entry over the years due to access required by various users/departments that you dont want to have access to certain parts of Part Entry. This was mainly because people before me had customised the F*** out of Part Entry to add fields to it that should never be there but also because i started to lock down access right.
