@josecgomez - I did, and it got shot down twice by development. First case (CS0002993288 - Base Date Fields in Kinetic Process MRP truncates the information in those Date Fields) the ICE TOOLS Epicare Analyst submitted PRB0247179 (Application Studio will not allow the User to increase the Width of 2 Base Date Fields in Kinetic Process MRP).
Development informed me this is not a Bug, as there is no requirement that all controls allow custom sizing. However, they stated this is a fair ask, so please use Epicor Ideas to submit this Enhancement Request directly to Development.
2nd case I was told to submit it to the MRP Team. His suggestion was to personalize it. When I explained that personalizations or app studio doesnāt allow that, just have Dev just fix it eventually, the Epicare analyst lobbed the ball back across that wall to Dev, and they lobbed it back with āSubmit an enhancement ideaā (CS0003033779 - Cut Off Date field is clipped on Kinetic Process MRP form)
Itās honestly now a waste of our time to submit bugs to EpiCare if thatās the default response that we get. Iāll spend 30-90 minutes testing in our environment, then our clean EDU database, replicate it, document steps for the EpiCare analyst to repeat on his end, and then Iām told to do more work? How about Epicare or Development does it? Or maybe I can bill Epicor at $175/hr for doing their work and we get credited to use that against our maintenance invoice or Insights?
Anyways, this is kind of forking from the Ideas topic. Maybe Ideas should create a new category of āEpicor Bugsā if Development is now using that platform to track bugs because they donāt want to fill up their queue with PRBās and make their metrics look badā¦ Weād finally be able to see all the open bugs!
Yeah except Iām pretty sure sprints are only planned off of accepted problems so that would ensure none of these bugs get fixed. I have had the same experience multiple times. Escalating doesnāt help. Even getting one of the POs on the phone doesnāt help. They just simply refuse to accept almost anything as a bug anymore.
Maybe time to link in Joe Jasper or Jason Taylor, considering they own support, and ultimately, the customer experience? We canāt be the only onesā¦ Youād think that Epicor would want to fix Kineticās issues (even small cosmetic ones) as quickly as possible. At some point Epicor wonāt be able to keep treating the Kinetic UI as betaā¦
There is a dedicated person at Epicor for Customer Experience and his name is Chris Warticki. He is also here on the list. (@cwarticki) Heās been in that position for over three years now. He may very well have been one of the people behind Epicor Ideas, who knows? His contact info:
Write up your thoughts, layout the issues, and if youāre like me, go and remove the emotional and/or sarcastic commentary. He isnāt paid to take abuse. He is there to manage the customer experience.
I believe at this point that Kinetic is so underdeveloped that it is a bug in its entirety. I donāt care about it at this point. I have tried to use it, however it is a complete waste of time at this point. Itās a pointless time sink that I donāt have time for. Iām hoping that it becomes usable before we are forced to use it.
History is repeating itself. When Epicor left the VB client for the .NET Client, it was not well-received. This is the same .NET Client that people donāt want to let go of now. Expect a bumpy ride. It will be better once we get there.
Last November we did upgrade from Vantage 6.1 to Vantage 8.03.407. Things are working pretty much the same but I can tell you that Vantage 8.03 is about 10 times slower than 6.1. We bought a new 64-bit server with ample resources and even upgraded our network to Gigabit. Weāve replace most of our desktops with new PCs. Itās still WAY slower than 6.1. The interface is quite buggy too. During our implementation and training the Epicor consultants constantly said, āSave and save often!ā They meant it.
Whatās keeping us from upgrading to Epicor 9? Well weāve only been on 8.03 for a short time and Iāve heard Epicor 9 is even slower than this version. If thatās true (we havenāt even tested it yet) we may never upgrade. If I throw more pain on our users they might decide to crucify me.
Iāve worked with Epicor since around 2006 and Iāve seen support cycle from fair, to pretty bad, to good, to really good and back more than once. Sadly we seem to be on the downslope these last few years.
While there has been improvements there is still a huge gap that needs to be tightened up to put Kinetic on-par with Classic.
The issue (and fear) I have, is the screens that are working are not very usable. When redesigning the user experience, the flow of data and how it is consumed/entered should be taken into account. So even bug free, the new UX isnāt there yet either.
Iām curious when you say not very usable - do you have examples? We havenāt started testing the kinetic screens yet but just looking at them it seems like it will be a lot easier to navigate than the mess of tabs within tabs within more tabs that exists in classic.
I believe the #1 complaint that I got was in the Job Tracker. I didnāt use it much myself, but I was told it was very hard to navigate back and forth between the tabs to get the same information you used to be able to drill down into on one tab in the classic.
Itās been a while since Iāve been in Kinetic, so I donāt remember all of the details.
Itās going to be a change for sure and people donāt like change, the whole moving and all that. Even the classic screens were many times said to be inefficient; āAll the tabs and clicking plus the number of fields we donāt useā¦ā is a pretty good summary of what I heard many times when customizing the classic forms.
The real issues Iād like to see addressed in Kinetic is the bugs; Not being able to adjust field sizes to accommodate the data, bugs and missing features in Application Studio, etc.
Weāre in testing for 2021.2.x and weāve ran into bugs but some are supposed to be addressed in 2022.x sometime at least if not already. Hoping weāve hit bottom and the āsupport swingā is on the upward trend
His contact info:
He isnāt paid to take abuse. He is there to manage the customer experience.
and all that. Even the classic screens were many times said to be inefficient; āAll the tabs and clicking plus the number of fields we donāt useā¦ā is a pretty good summary of what I heard many times when customizing the classic forms.