||Permits access to any user who is assigned this access right
||Commas between access codes that are outside of brackets signify an 'or' syntax, whereas
commas between access codes within brackets signify 'and'. In this case, access is
granted only to those users who have both DEV and QA access rights, or have MGR access right.
|Transfer route activations
||+Latest or Latest
||Activates the object version at this location
||De-activates the object version at this location
||Commas signify 'and'. In this case, the object version is activated in the 'Tested'
location and de-activated from the 'Sandbox' location. All activations are applied
first (in collating sequence), followed by all deactivations.
|Transfer route dependencies
||Permits the transfer only if the object version already exists at this location. If
the location is single-version, existence of a successor version also satisfies the
||Validates the transfer only if the object version does not already exist at this location.
For single-version locations the presence of a successor version is ignored. To consider
successor versions, use $$%NotAt("Latest")
||Commas signify 'and'. In this case, the transfer is only validated if the object version
exists in the location called 'Tested' and if it does not exist in the location called 'Library'.
||Specifies a dependency function
||Shorthand notation for specifying a dependency function. For this to work, the ^%vcvc("customDependencyRoutine") global needs to have been
set to the name of the routine where this function's line label exists.
||Shorthand notation for specifying a pre-built dependency function. The line label of any function in %vc1xvf.int can be specified in this way.
||Permits the transfer only if the exact object version already exists at this location.
Unlike for a normal positive dependency (see above) the existence of a successor version
does not satisfy the dependency for a single-version location.
See Also: Managing Users and Access Controls, Managing Transfer Routes