DBohner-(db)
Legendary Poster
First, let me start by saying, I do understand why there should be a no mod
policy... But, even in a No Mod World, new objects are copied/created and
underlying business objects change when ESUs are applied....
We all live in the real world... so, I need some suggestions about the real
world JDE development cycle. So, here goes...
In a typical development cycle there should be three environments
(Development - where the programmers play, Prototype - where the users test
what the programmers played with & Production - where the programmers can't
play).
Now comes, that little monster I fear so much, ESUs.
During an Ideal development cycle, ESUs might be applied to the Dev
Environment, tested and played with by Programmers - and verified that their
created/modified objects work with the ESU. If the ESU doesn't work in DEV,
it should be backed out. But that is not real world, because ESUs require
the dozen programmers to check in what they are playing with (overriding the
environment's objects/circumventing why we have a SAVE environment)...
Programmers are, by nature, going to forget to check in objects and not want
to place a 'work in progress' to anything other than SAVE...
"- anyone got Merge Working with ESU, correctly???"
Once the ESU is tested (we are still talking dream world, here) and accepted
by the Programmer staff, It would be applied to the Prototype environment,
for the users to test... oh, but wait... wasn't it tested with checked in '
work in progress' objects in DEV (something to think about/OUCH). Once the
Users have OK'd it, the ESU gets pushed to Production...
There are so many issues / concerns regarding the Development Cycle with
ESU, I am getting sort of frightened... give me back a green screen and the
RPG cheat sheet...
Does anyone have their hands on some SOPs for the JDE Development Cycle? I
am looking for anything out there that would cover ... which environment
objects get check out from (even if they are to be copies) to what
environment ESUs should get applied to.
I am willing to do some big hike work to build a white-paper and throw it
back to the list... any helps you can provide will go an enormous way!
Thanks!
Daniel Bohner
[email protected]
www.existinglight.net
JDE - XE & AS/400
JDE - B7331 & MS SQL 7x
policy... But, even in a No Mod World, new objects are copied/created and
underlying business objects change when ESUs are applied....
We all live in the real world... so, I need some suggestions about the real
world JDE development cycle. So, here goes...
In a typical development cycle there should be three environments
(Development - where the programmers play, Prototype - where the users test
what the programmers played with & Production - where the programmers can't
play).
Now comes, that little monster I fear so much, ESUs.
During an Ideal development cycle, ESUs might be applied to the Dev
Environment, tested and played with by Programmers - and verified that their
created/modified objects work with the ESU. If the ESU doesn't work in DEV,
it should be backed out. But that is not real world, because ESUs require
the dozen programmers to check in what they are playing with (overriding the
environment's objects/circumventing why we have a SAVE environment)...
Programmers are, by nature, going to forget to check in objects and not want
to place a 'work in progress' to anything other than SAVE...
"- anyone got Merge Working with ESU, correctly???"
Once the ESU is tested (we are still talking dream world, here) and accepted
by the Programmer staff, It would be applied to the Prototype environment,
for the users to test... oh, but wait... wasn't it tested with checked in '
work in progress' objects in DEV (something to think about/OUCH). Once the
Users have OK'd it, the ESU gets pushed to Production...
There are so many issues / concerns regarding the Development Cycle with
ESU, I am getting sort of frightened... give me back a green screen and the
RPG cheat sheet...
Does anyone have their hands on some SOPs for the JDE Development Cycle? I
am looking for anything out there that would cover ... which environment
objects get check out from (even if they are to be copies) to what
environment ESUs should get applied to.
I am willing to do some big hike work to build a white-paper and throw it
back to the list... any helps you can provide will go an enormous way!
Thanks!
Daniel Bohner
[email protected]
www.existinglight.net
JDE - XE & AS/400
JDE - B7331 & MS SQL 7x