Super User options
The Administrator may configure the Super Users
and Super
Group Leaders. The
various super user access modes allow a user to modify, version or otherwise
use any component in the system regardless of ownership. This
feature enhances several individual features of the base VA Java including
versioning, releasing, loading and creating new editions, changing
ownership of components, adding and deleting classes, user administration,
and package management.
Note: Once Super User status is invoked, it remains in effect for a
specific workspace until it is turned off (even if the current user is
changed for that workspace). This is done intentionally in order to allow
a (super) user to better get their work done. In order to invoke Super
User status, a user must have the ability to become a user with Super User
privilege and then invoke that privilege. If they have a need to switch
users to get their job done, they need to be able to keep Super User
status turned on. If Super User mode is turned off while acting as a
non-super-user-privileged user, it can't be turned on again until they
change user back to a user that has the Super User privilege.
Super User mode always off at startup for all users
This ensures that
Super User mode is always off when a user starts up
their workspace. They must consciously turn it on during each session in order to use it.
Super Group
Access options
The Administrator may configure Super Groups. The
various super access modes allow a user to modify, version or otherwise
use any component in the system regardless of ownership. This
feature enhances several individual features of the base VA Java including
versioning, releasing, loading and creating new editions, changing
ownership of components, adding and deleting classes, user administration,
and package management.
Note: information about the Super Group status of the projects and
packages in your workspace is read from the repository during startup and
stored in a library cache. If the Administrator changes the status of any
of those projects or packages, the library cache can get out of date. You
can either shut down VA Java and re-start, or click the "Clear
Library Cache" button on the "VA
Assist | Layout" options page.
Allow auto-join/auto-manage of package
groups
With these options enabled, creating a new edition of a super package
group will automatically add the current user to the group list and
optionally make them the owner of the package. Also, any time a Super User
creates a new edition of any package or adds a type to an existing
package, they will automatically be added to the group list and optionally
made the manager of the package..
Allow nested Solutions (VA Java 3.5 Only)
Allows all users
connected to the repository to created nested
Solutions. This allows a Solutions to contain other Solutions in
addition to individual projects. Nested Solutions should be thought of as
required/pre-requisite Solutions for the selected Solution.
Use global version name template
When a global version name template is in effect, individual users
will not be able to specify their own version name template. Version
name templates allow the developer to specify the scheme used for
generating new version names from prior releases.
Disable VA Assist version check task for all users
This prevents the
automatic check for new versions of VA Assist from occurring. Note that the new version check may still be run
manually. By default, the Version Check task is scheduled to execute once
a week at startup to send a message to the Instantiations web site looking
for a newer version of VA Assist than what is currently loaded in the
workspace.
Disable version renaming
This disables version renaming except by either the Administrator or
by the Administrator and Super Users. Version renaming allows a
developer to change the version name on an item after it has been
versioned. This is very useful for baselining components for release. An
option is provided to rename all subcomponents as well. This command is
available for items in the workbench and in the repository.