kjjdelist
Well Known Member
My users have the ability to create their own versions of objects. They know that if they don't check them in when they create them, they will be lost during a full-package build/deploy, so they do a pretty good job of that. We've recently upgraded from B7332 to ERP8 and now have OMW.
If a user creates/mods a version, a new project is created named as their UserID and has them as the PVC administrator. I'm told by our consulting group that the check-in process places the version in DV and into the environment the user is logged in to when the version is made (usually PD). This leaves PY w/o the new/modded version.
What's the generally accepted practice here? Is there a way to make JDE a default PVC administrator for all projects? If so, that would make the promotion of these projects from 21 to 26 easier. Is promoting the project the only/best way to get these user modded objects to PY?
What if multiple users have modified the same version? How do you know which one to promote to keep the most recent one?
If a user creates/mods a version, a new project is created named as their UserID and has them as the PVC administrator. I'm told by our consulting group that the check-in process places the version in DV and into the environment the user is logged in to when the version is made (usually PD). This leaves PY w/o the new/modded version.
What's the generally accepted practice here? Is there a way to make JDE a default PVC administrator for all projects? If so, that would make the promotion of these projects from 21 to 26 easier. Is promoting the project the only/best way to get these user modded objects to PY?
What if multiple users have modified the same version? How do you know which one to promote to keep the most recent one?