timallen
Well Known Member
(OneWorld Xe, Update 6, SP20, SQL Server, Windows 2000)
Problem: UBE/Version environment conflict when creating UBEs in RDA on PY7333
We have some functional consultants working in PY7333. They have their default OMW projects set to status 21. When they create new UBEs from RDA and check them in, OMW says these UBEs get stored in DV7333 (I suppose because the default project is in status 21-- is that why?).
When the consultants then create versions for the new UBE, these versions are stored in PY7333 (I suppose because the consultant is signed in to PY7333-- correct?).
This causes a problem when we go to check in the versions: the base UBE is in DV7333, and its versions are in PY7333. The only remedy we've found at this point is to move these UBEs out of the default OMW project into another project set to status 21, and advance this project to 26. Then both the UBEs and the versions exist in PY7333. Then the Versions can be checked in.
One workaround was to put the default OMW project to status 26. But I told another CNC about this and he winced. It seems to me that the default OMW project probably should stay at status 21. Is that right?
Ultimately what we want is for the functional consultants to be able to create UBEs with RDA and versions in RDA or Batch Versions and still be able to check everything in without intervention from the CNC (me).
How should this situation be resolved?
Problem: UBE/Version environment conflict when creating UBEs in RDA on PY7333
We have some functional consultants working in PY7333. They have their default OMW projects set to status 21. When they create new UBEs from RDA and check them in, OMW says these UBEs get stored in DV7333 (I suppose because the default project is in status 21-- is that why?).
When the consultants then create versions for the new UBE, these versions are stored in PY7333 (I suppose because the consultant is signed in to PY7333-- correct?).
This causes a problem when we go to check in the versions: the base UBE is in DV7333, and its versions are in PY7333. The only remedy we've found at this point is to move these UBEs out of the default OMW project into another project set to status 21, and advance this project to 26. Then both the UBEs and the versions exist in PY7333. Then the Versions can be checked in.
One workaround was to put the default OMW project to status 26. But I told another CNC about this and he winced. It seems to me that the default OMW project probably should stay at status 21. Is that right?
Ultimately what we want is for the functional consultants to be able to create UBEs with RDA and versions in RDA or Batch Versions and still be able to check everything in without intervention from the CNC (me).
How should this situation be resolved?