TAldemir
Member
Hi There,
After a version of a UBE that runs on the server is modified in DEV, and gets moved to PROD via PY (21 to 26 to 38 trip), I build an update pkg for the SERVER only containing this UBE along with its version and deploy it to the server. Since this UBE is executed only on the server, I do not build and deploy a CLIENT pkg. However, after the SERVER pkg deployment, when the end-users run the UBE/Version on the server they still execute the older (pre-modification version). When we go-ahead and check out the modified version to the specific workstation, then the execution of the UBE/version which still runs on the server executes the modified version. I am confused here. Why would a UBE/Version that is executed on the server require the workstation's version specifications to be refreshed? Am I missing something here?
After a version of a UBE that runs on the server is modified in DEV, and gets moved to PROD via PY (21 to 26 to 38 trip), I build an update pkg for the SERVER only containing this UBE along with its version and deploy it to the server. Since this UBE is executed only on the server, I do not build and deploy a CLIENT pkg. However, after the SERVER pkg deployment, when the end-users run the UBE/Version on the server they still execute the older (pre-modification version). When we go-ahead and check out the modified version to the specific workstation, then the execution of the UBE/version which still runs on the server executes the modified version. I am confused here. Why would a UBE/Version that is executed on the server require the workstation's version specifications to be refreshed? Am I missing something here?