Server Configuration > Server Policies for SCM > PTC RV&S Client Defaults > Default Client Commands and Views
Default Client Commands and Views
In the PTC RV&S client, you set certain client-side preferences on the server so that they are unavailable for modification by the user and are instead populated by the server. In the CLI, options display with a (locked) message, indicating that the preference cannot be specified.
Users can circumvent the server enforced preferences by specifying their preferences while not connected to the server. However, once the server connection is established, the server enforced preferences override the client preferences.
* 
Clients cannot detect changes to the preferences until a new server connection is established.
The following table identifies the command options that can be enforced by the server. For command option descriptions, search the PTC RV&S Help Center.
Command
Options
Add Members
si add
Create Subprojects for Empty Directories
Save Working File Timestamp
Retain Working File
On Inconsistent Line Terminators
• Query User
• Normalize Line Terminators
• Cancel
On Existing Archive
• Query User
• Share Archive
• Create New Archive
• Cancel
On Existing Out Of Tree Archive
• Query User
• Share Archive
• Create New Archive
• Cancel
Check In
si ci
Branch if Variant
• Yes
• No
• Query User
Update Member Revision
Retain Working File
Save Working File Timestamp
On Inconsistent Line Terminators
• Query User
• Normalize Line Terminators
• Cancel
Check Out
si co
Change Package
• Active
• None
Move My Lock
Checkpoint
si checkpoint
Checkpoint Unchanged Subprojects
Create Development Path
si createdevpath
On Existing Development Path
• Share Development Path
• Query User
• Cancel
Creation Method
• Full
• Extendable
• Non-extendable with all subprojects configured as build
On Live Configuration
• Retain the existing live configuration of the subproject
• Create the development path on the subproject
Create Sandbox
si createsandbox
Compute Checksums of Working Files
* 
This policy is configured as a server-side default policy and is used for the Mathworks integration in order to reference file differences for code generation.
• Once the policy is configured for a project, PTC RV&S calculates checksums for both text and binary working files in all Sandboxes of that project created since the policy was set. If the current working file size is identical to the baseline, timestamps are compared.
• PTC RV&S calculates the current checksum if the file timestamps are identical. The checksum information is then used to calculate the working file deltas.
• As well as displaying the standard icon for a working file delta, PTC RV&S displays a detailed message in the Details panel on the PTC RV&S Server GUI and a detail message in the command line interface to indicate when the checksum is different from its base.
Automatically Resolve Potentially Modified Working Files
* 
• By default, this option is not selected. Selecting this option enables the --autoResolvePotentialModifications option on all new sandboxes.
• You can select this option only if the Compute Checksums of Working Files option is selected.
Lock
si lock
Change Package
• Active
• None
Restore Project
si restoreproject
Resulting subproject configuration
• On development path except explicitly configured subprojects (Legacy)
• On development path
• Lightweight (Build)
• Retain current configuration
Resynchronize
si resync
Restore Revision Timestamp
Move My Lock
Resynchronize Change Package
si resynccp
Restore Revision Timestamp
Revert
si revert
Restore Revision Timestamp
Downgrade/Remove Lock
si unlock
Break Lock
Downgrade Lock
• Query User
• Yes
• No
The following table identifies the client view options that can be enforced by the server:
View
Option
Revision Contents View
si setpolicysection
Keywords
• Expand
• Unexpand
• Do Not Expand
Update Archive Attributes View
si archiveinfo
Break Lock
There is an additional preference that can be set by the administrator that affects the Member History and the Project History views. This preference is set in the IntegrityClientSite.rc file.
Was this helpful?