Server Configuration > Server Policies for SCM > Entering Project Paths > Example: Jumping to Variants
  
Example: Jumping to Variants
If you had the following project setup:
/projects/aurora/source_code/savings_tool/project.pj
where source_code is a subproject currently configured as beta_variant and savings_tool is a shared subproject currently configured as normal. The following jump would be allowed:
#/projects/aurora#source_code/savings_tool#d=beta_variant
The following jump would not be allowed:
#/projects/aurora#source_code/savings_tool#d=prod_variant
You can specify a jump to beta_variant from the subproject savings_tool because it is the same as the variant for source_code, and because as a shared subproject it is accepted as the local variant root (the configuration management project through which the development path was created). You cannot jump to prod_variant because it is different than the variant of source_code.