Can some"Client Defaults" policies overridden by users?

[LLawton]

I'm interested specifically in the Check Out > Change Package option:

When it comes to creating/using Change Packages, I have users who want to always default to the last CP, and the rest want to be forced to choose.

Is it possible to set the policy to one (e.g. Active), and let each user set his/her choice?

Policy:

In individual Client Preferences, I can only find "Ask for Change Package" but that doesn't seem to do anything.

If this is not possible, we're on 10.4, so would 10.8 or 9 help?

[awalsh · Accepted solution]

As long as the server-side policy is not locked, then the user can override this in the client.  For the Change Package option on Check Out, the default is Active. It is easiest to leave the global preference "Active", and then have the users set the change package to "None" by using the following CLI command:

si setprefs --save --command=co ChangePackageID=:none

There is not a way to set this in the Integrity Client GUI.

The "Ask for change package" setting controls whether to prompt for a change package on the command line.  If you set the ChangePackageID=:none, and turn off Ask for Change Package, then the user would always have to use the --cpid option when running si co on the cli.