buckle up for caseing changes in methods as you go to 500 and 600 
e.g.OnChangeBinNum to onChangeBinNum sort of stuff lol
3 Likes
I can only imagine… what is the benefit to this? More income for CSG? 
I think you could argue that this is something for Epicor Ideas. It might help impress upon people the butterfly effect.
3 Likes
Didnt see that documented anywhere in their release guides under Software / Framework changes. hmmm 
1 Like
Good idea! I’ve submitted the idea here if anyone else wants to vote for it:
https://epicor-manufacturing.ideas.aha.io/ideas/ERP-I-357
1 Like
So … Are releases notes ever updated? Or are they carved in stone at the time of the release?
The closest thing I see to any Revision indicator is on the Disclaimer page
How convenient that there’s no Rev code (A, B, C, 1, 2, etc…) to indicate that this an update on prior revisions.
I was referring to the Change List - PDF section which is an accumulation of all the updated modules and the resolution types between minor revisions from the base version. I focus on the “All Changes” and “Software Interface Changes” between the version I have installed and the version I plan to install.
I added my +3 votes to Ideas. We got seriously burned when upgrading from 10.2.300.x to 10.2.300.y when they added an undocumented requirement that the counter sales prefix can only be 1 character.
Trust us, they say… Dot releases are minor changes that don’t affect the framework they say… Just install the patches and don’t worry about doing a full month-long testing series with each department they say. Ha ha! I won’t do that again… I wish we could patch earlier and more often, but it needs to be tested, especially if the release notes aren’t documented well.
1 Like
Glad I’m not the only one getting burned here. Thanks for the up vote, hope it helps. 
Honestly, even IF changes are documented perfectly, will the users read them and test those items properly? And still, should we only test our modifications or also the functionality we expect to see in the product?
I think I would prefer Epicor’s help in created automated testing - as one might do in, oh, I don’t know, maybe…
DevOps!
2 Likes
@Mark_Wonsil I strongly agree with this as well (https://epicor-manufacturing.ideas.aha.io/ideas/ERP-I-139), that will be awesome when that day comes. In the mean time, the fact they are missing system behavior changing release documentation to me either indicates a lack of discipline or a lack of customer awareness. As far as customers reading the notes, that is on us and Epicor should expect nothing less of us. They can throw it back at us or ignore us if we don’t do our due diligence!
2 Likes
Voted!!!
Also @Mark_Wonsil in regards to automated testing, there it the Epicor ATE tool which allows you to script out tests. I need to spend more time with it, but it seems very powerful.
1 Like
- a few from me too
1 Like
Thanks for the information @tanner . I got a BPM on ARInvoice.GetFScalls for passing current plant as a parameter. I will review it.
ATE is a good Integration tester for sure but it only tests the .Net client if I recall. As we get to an all web client, there will be other options.
I know I’m reaching here but I’d love to have some unit testing capability in addition to integration testing. Some of this can be done with Postman or PowerShell. But it would be REALLY cool to Be able to do some XUnit on our BPMs, Functions, and Configurators. I also suggested to Jose and Josh that Trace Replay would be a cool feature to add but they got day jobs… 
5 Likes
As was I. That screen grab is from the 2nd page of the document:
Release Notes 10.2.300.x Update
Epicor 10.2.300 to 10.2.300.9
I cast the maximum of 3 votes for Tanner’s idea. I also created a new idea (https://epicor-manufacturing.ideas.aha.io/ideas/ERP-I-721) related to his idea and Tanner reciprocated with his votes. Please consider the additional idea, and then if you like it, please also support it with your votes!
Just wanted to say “thank you” to everyone who voted for idea #721, which Epicor has now implemented according to the following message that I received from Epicor today:
“we have updated our Release Notes production process to include ServiceNow IDs (PRB numbers) in the Change List. You will be able to find them in Update Release Notes starting with version 10.2.700.12, 10.2.600.23, 10.2.500.33, 10.2.400.38, and, of course, in version 11.1.100 when it’s released. Hope PRB numbers will help you work with Epicor ERP updates more efficiently.”
10 Likes
Power Automate Desktop Perhaps might help when 11.1 comes about and testing on Kinetic is needed.
I am yet to play with it in detail, but the demos look not too shabby.
I would love to read some release notes. We are trying to go from 10.2.500.16 to patch 10.2.500.40. I only see .39 on EpicWeb. I am hoping this fixes a ton of issues we are having.