si copypolicysection
copies the policy settings from an existing policy section (global or project) to a new project policy section
Synopsis
si copypolicysection [--source=value] [--hostname=server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]] policy section name
Description
si copypolicysection copies the policy settings from an existing policy section (global or project) to a new project policy section. You specify the global or project policies you want to copy and then specify the registered project you want to copy those policies to.
|
• You can copy policy sections from the global policy section to a new project policy section, or from an existing project policy section to a new project policy section. You cannot copy existing project policy sections to global policies.
• The ViewPolicy and EditPolicy permissions are required.
• Global policies contains some policies that only apply at the global level, for example, Windchill RV&SManagerEnabled. If :global is specified as the source, these policies are not copied.
|
For example, to create a new policy section for /newProject/project.pj and copy any policies that are not global-specific from the global policy, type the following:
si copypolicysection --source=:global /newProject/project.pj
Options
This command takes the universal options available to all
si commands, as well as some general options. See the
options reference page for descriptions.
• --source=value
specifies the policy section to copy.
• policy section name
specifies the new project policy section to copy the policy section to, where policy section name is of the form:
◦ :global for a global policy.
◦ project for a project, for example, /demo/project.pj.
◦ project ; development path for a development path on a project, for example, /demo/project.pj;Variant1.
◦ development path for all projects that are configured on the development path at the top level, for example, ;Variant1.
|
You may need to escape the ; in your command line environment, for example, enclose it in "" or escape the individual character with a /.
|
Diagnostics
See the
diagnostics reference page for possible exit status values.
Preferences
Using
si setprefs or
si viewprefs, you are able to set or view the preference keys for this command.
See Also