Easing The EnterpriseOne Learning Curve
Read Time:1 Min, 2 Sec
In the past year or so I have been training a very good new CNC Administrator. He’s been working with IT and World for quite a long time and is very good at picking up new things.
In doing this, sometimes I have to think back and try and see things from a more innocent, un-jaded view. Also, I try to think about what has helped me the most in learning this complex, overly-convoluted architecture?
There are the obvious answers:
- Experience
- Terminology (this was huge for me)
- EnterpriseOne SysAdmin classes
- Loyal participation in JDEList
- Etc.
However, one of the things that helps me the most when troubleshooting an issue that can’t be resolved by the normal logs and error messages is…
having a development background and the E1 developer classes.
Why? Well, as a Systems Administrator, I think I see how the system works a little better than a developer. As a developer, I am able to use the tools to logically follow the process of an application or UBE from beginning to end.
I’m sure others can put this a lot more eloquently than I, but you get the idea.
What do you think? What skill helps you out the most when troubleshooting difficult issues?
Average Rating