Feature-related P4V properties
You can set a value of On
or Off
for properties that can disable or enable certain P4V features. P4V reads the property values from the first Server to which P4V connects.
Off overrides On
If you deactivate a feature by setting its property to Off
on the server, that feature becomes unavailable in P4V. Even if that feature property might be visible in the P4V Preferences
dialog and shown as enabled, the P4V user cannot use that feature.
The server Admin and the local P4V each have a mechanism to disable certain features.
For example:
-
If the P4V user enables the Markdown option in the local preference, the Admin can override that choice and disable the feature with
p4 property -a -n P4V.Features.Markdown -v Off
-
If the P4V user disables the Markdown option in the local preference, although the Admin can enable the feature in a general sense with
p4 property -a -n P4V.Features.Markdown -v On
a local P4V user's choice to disable the feature remains in force locally.
Server properties
The following Server properties can change the value of a P4V feature that is On by default to Off.
Property |
P4V > Edit > Preferences |
Default Value |
Description |
P4V Version Introduced |
---|---|---|---|---|
|
Administration Tool |
|
If |
2013.1 |
P4V.Features.AllowDirectStreamEdit
|
N/A | On
|
If |
2022.1 |
P4V.Features.CheckForUpdates
|
Automatically check for Helix P4V updates. |
|
If |
2013.2 |
|
Set Up Connection Wizard |
|
If |
2013.1 |
|
Custom Tools |
|
If |
2013.1 |
|
N/A |
|
If |
2013.1 |
|
N/A |
not set |
If set, specifies the file limit for the Dashboard's Workspace Folder view. This setting overrides the the user-specified data preference on the server side. |
2017.2 |
|
DVCS - Distributed Version Control |
|
On by default, but governed by the |
2017.1 |
|
N/A |
Off |
If On, P4V displays full user names in the Pending, Submitted, and History tabs. |
2018.4 |
HTML Tools |
|
If |
2019.2 |
|
|
Merge, Copy and Branch Dialogs |
|
If |
2013.1 |
|
Jobs |
|
If |
2013.1 |
|
Labels |
|
If |
2013.1 |
|
Description fields |
|
If |
2021.3 |
P4V.Features.MaxAllowedVersion
|
N/A |
<int value> that determines the maximum version hint when checking for updates. Setting the version does not restrict the user from using a newer version of P4V against the server, but the checking for an update will not report a newer version than the one set in the hint. The value should be a changelist number equal to the maximum allowed version. If that value is set to 60000 and the latest current version is 65000, the user will get the message that there is no available update if the user is already at version 60000. If the user is at 60000 and the current live version is 70000, but the admin has set the max value to 65000, then the user will get a message that there is a newer version available, but an administrator has set a different maximum, and they should contact their administrator for the proper version. |
2013.2 |
|
P4V.Features.PromptWorkspaceName |
Prompt for name when creating new workspace |
|
If On, P4V prompts the user for the workspace name when creating a new workspace. P4V runs the p4 client -o command, allowing a form-out trigger to modify the default form. P4V supports overwrite of the following attributes: Client:, Root:, View:, Owner:, Description:, Host:, AltRoots:, ChangeView:, Options:, SubmitOptions:, LineEnd:, and Type:. |
2018.3 |
P4V.Features.Repos | Repos | On
|
If Off, repo-related icons and menus do not appear. | 2020.2 |
|
Revision Graph |
|
If |
2013.1 |
|
Streams |
|
If |
2013.1 |
|
Time-lapse |
|
If |
2013.1 |
|
Unload/Reload |
On
|
If |
2013.2 |
P4V.Features.UnshelveSideways | N/A | On
|
If |
2013.1 |
|
N/A |
|
If |
2013.1 |
For example, the administrator of a site that does not want to use the Helix Core Server built-in defect tracking system called "jobs" can disable access to jobs from within P4V by running:
$ p4 property -a -n P4V.Features.Jobs -v Off
A new property is added/updated (-a
), it is named
(-n
) P4V.Features.Jobs
, and it
is assigned the value (-v
) of Off
.