Do I need to build/deploy package for these objects?

jennifer_qiu

Active Member
Hello,

Our users created several menus, user overrides and versions(APPLVER and UBEVER) in a project in our develop environment. I promoted the project to our CRP environment. My question is: Do I need to build/deploy update package for this project in order for other users in our CRP environment to see the newly added menus, user overrides and versions?

Thanks for you reply!
Jennifer

Xe update 3 sp18.0
ES: AS400, DS: WIN2K, Citrix+Fat client
 
Jennifer :

You don't need update packages for menus, but you'll need them to
deploy new versions on CRP.

Sebastian
 
Jennifer, what I have found is that the very first time NEW versions are
created you don't need a package build, just promote them and they will be
seen. If you are modifying existing versions then you will need to build a
package to see the updates to the versions... Menus and user overrides
don't need a package build at all.

Hope this helps!!

:)



Our users created several menus, user overrides and versions(APPLVER and
UBEVER) in a project in our develop environment. I promoted the project to
our CRP environment. My question is: Do I need to build/deploy update
package for this project in order for other users in our CRP environment to
see the newly added menus, user overrides and versions?

Thanks for you reply!
Jennifer

Xe update 3 sp18.0
ES: AS400, DS: WIN2K, Citrix+Fat client




Lori
OW Xe SP16 Update 2
AS400 V5R1 NT
Citrix
email: [email protected]
 
Hello Lori/Sebastian,

Thank you for your help.

After promoting the menus/user overrides to my testing environment, I can
see menus but cannot see user overrides in my testing environment. That's
why I think about the package for user overrides.

Thanks, Jennifer Qiu




LoriStephens
<jdeperson@hotm To: [email protected]
ail.com> cc:
Sent by: Subject: Re: Do I need to build/deploy package for these objects?
owner-jdelist@j
delist.com


04/19/02 10:20
PM
Please respond
to jdelist






Jennifer, what I have found is that the very first time NEW versions are
created you don't need a package build, just promote them and they will be
seen. If you are modifying existing versions then you will need to build a
package to see the updates to the versions... Menus and user overrides
don't need a package build at all.

Hope this helps!!

:)



Our users created several menus, user overrides and versions(APPLVER and
UBEVER) in a project in our develop environment. I promoted the project to
our CRP environment. My question is: Do I need to build/deploy update
package for this project in order for other users in our CRP environment to
see the newly added menus, user overrides and versions?

Thanks for you reply!
Jennifer

Xe update 3 sp18.0
ES: AS400, DS: WIN2K, Citrix+Fat client




Lori
OW Xe SP16 Update 2
AS400 V5R1 NT
Citrix
email: [email protected]
--------------------------
 
Hello
Right Now We are in the same process. This is what I follow:---- For Menus and Apps version we do not build any package. for Batch version we build the package since Batch versions have specs. Hope this helps.

Thanks
Vivek Mohan
XE Update 3, SP18.1
Windows NT Enterprise Server
 
Hi Jennifer

One Modification from last reply. We do not build any package from any versions. We just need to check in Batch versions before promoting it to PY.

Thanks
Vivek Mohan
 
Hello all,

Thank you very much for your reply!
I think to menus, user overrides, no need to build pkg as they are just file records, to versions, especially Batch versions, I still think pgk is necessary.

Please correct me if I am wrong.
Thanks again, Jennifer
 
Jennifer,
it´s not really *necessary* to build packages for UBE versions either.
Once you build a version and checked it in, it is available right away
for everybody. You can even execute it on your ES. Try it out. Version
specs are automatically send to ESs when you submit a report. To WSs they
jiti down. For WTS you may want to build packages for versions in order
to avoid jiti.

There is one exception. If you have a new (custom) *report*, when you
build a server package with that report you should send at least one
version along with that package.

Another point would be changed versions. They should be send via package
as well to servers and/or workstations.

Thanks, Gerd
 
Back
Top