eddie
Active Member
that whenever a new version was created (eithere copied or added) it would=
need to be included in a package build/deploy in order for others users to=
access it. Just recently I've seen a user copy dozens of versions, check t=
hem in via OMW, add them to menus, and then (without me building a package =
with these versions) other users can use and see these new versions.</P>
=
How is this? I always thought all versions and objects needed to be built a=
nd deployed in a package for all users to see them without checking them ou=
t and overriding local specs. Why didn't a package need to be built? =
Is it because spec files weren't modified for the versions?</P>
&nb=
need to be included in a package build/deploy in order for others users to=
access it. Just recently I've seen a user copy dozens of versions, check t=
hem in via OMW, add them to menus, and then (without me building a package =
with these versions) other users can use and see these new versions.</P>
=
How is this? I always thought all versions and objects needed to be built a=
nd deployed in a package for all users to see them without checking them ou=
t and overriding local specs. Why didn't a package need to be built? =
Is it because spec files weren't modified for the versions?</P>
&nb=