Jose Gomez and a fan
12 Likes
Why isnāt that your profile pic on the site yet?
3 Likes
Mr. Worldwide
1 Like
Hi there,
I thought that it was quite similar to last year, but I did see some things that I didnāt have time to do last year that were useful. The IP&O product lab was very interesting for our inventory management needs as well as the Training program with Epicor learning. I also got more familiar with the Kinetic UI, ability to personalize, and how to train users on it via various sessions. Once again, insights was a worthwhile investment for our company! 
Nancy
2 Likes
OK, if you had not posted this (and then I looked it up), I would still not know who was in the picture with @josecgomez .
I just thought someone had shrunk The Rock.
(No offense, BTW; Iām not tallā¦)
5 Likes
SIGH! How have you never heard āGive Me Everythingā
It charted for 47 weeks in Billboard Hot 100!
1 Like
Looks like Right Said Fred to me. 
5 Likes
Now I have to go find my shirt.
1 Like
This one?
3 Likes
This is probably not obvious but the reason we wrote our own test recorder is not to be playwrite - there are many great options for that. Rather we did it to get a feature that no off the shelf test recording framework can provide - recording to test shims that increase test stability / resiliency release to release.
The issue with basically all off the shelf UX test recording tools is they have to get a handle on parts of your ui and will generate the best pointer to ui elements that they can figure out and then directly interact with them like a user (lets click on that thing). That pointer if you are lucky in web is an id=āā element but its often a long xpath match. So what happens is you upgrade the software and ui elements are moved or changed somehow and your tests break and need to be updated to function again. With large volumes of tests this becomes a huge problem.
Many years ago as we built our ux platform we included a test shim framework so that we could build stable automated tests - basically there is a shim to talk to for every component with simple methods to update the data, activate it, find it by its stable id, etc and if we update the component to be structured differently we update the shim so it still works the same way in test. Our test recorder writes tests that instrument that, and that lets us have to fix dramatically less tests up each release. Thatās really the point of it - and itāll evolve more rich ui that is more similar to off the shelf tools over time.
10 Likes
Do you plan an Edge version of ReCoder? Our infrastructure team set Edge as the browser so most of our users use it instead.
Havnāt tried but Edge is chromium-based so it should work. Works for me in Brave.
Edit: it is indeed working in Edge, for me.
2 Likes
I donāt think we are testing it officially on other chromium browsers, but I think you are correct Iād generally expect it to just work.
3 Likes
That suspiciously looks like a person that works at a particular UK BI vendor (who shall remain nameless) 