Configure user preferences

You can configure options for a Galaxy, including prompts for check-in comments and user defaults. These user options apply to the currently open Galaxy and do not change options for other Galaxies.

If you specify a security group, that security group must already exist. For more information about security and security groups, see Work with security.

To configure user information

1. From the ribbon, select Galaxy, then User, then Preferences. The Preferences pane appears. The pane has three tab pages.

   

2. On the Warnings page, select the check box for each option you want:

   • Ask for check-in comments to be prompted to type comments when checking in templates and objects.

   • Warn if check-in operation will block other users if you want to be warned if this occurs.

   • Editor for a read-only object to see a prompt that informs you if you are opening an instance or template as read-only. The prompt warns you if you open an instance or template while someone else is working on it. If someone else is working in the instance or template, you cannot make changes.

   • InTouchViewApp editor to see a prompt each time you attempt to edit an InTouchView application instance. You can edit the associated template or cancel the operation. If you do not select this check box, the request to edit the InTouchViewApp instance is automatically redirected to the associated template.

   • Linked content editor to see a prompt each time you attempt to edit a Visualization folder item, such as a graphic or layout, that is linked to an object. You can edit the linked content or cancel the operation. If you do not select this check box, the linked content opens in its editor (graphics in the Graphic Editor, layouts in the Layout Editor, etc.) without a warning, and you will be able to make changes to the content. If you then save the content, the item in the Visualization folder is updated with your edits, and the changes propagate to all objects that link to the content.

   • ViewApp in preview mode to restore the first warning message that appears after requesting a preview of a ViewApp. You need to select this prompt to display the message again after you select the check box on the warning message to hide the message.

   • Platform issues in preview mode to restore the warning message that appears after requesting a preview without the WinPlatform deployed. You need to select this prompt to display the message again after you select the check box on the warning message to hide the message.

   • Select the Warn for insufficient permissions to see a prompt that tells you if you have permission to create or modify InTouchView applications. These permissions authorize or prevent you from creating and modifying InTouchView Applications.

3. On the Scan page:

   • Select the Initial scan state for deployed objects. You can select On Scan or Off Scan. You can change this setting on an individual basis in the Deploy dialog box when you deploy.

   • Select the Scan state defaults when undeploying or redeploying instances. Force Off Scan will attempt to take the target object offscan when an already deployed object is redeployed. Don’t Force Off Scan does not force the target to go off scan when you deploy.

     Note: Redeployment of objects that are currently deployed on-scan will be canceled unless this option is selected.

   • Enable or disable Auto context selection. This setting is enabled by default:

     • When Auto context select is enabled (checked), an object selected in the Model, Derivation, or Deployment view remains selected when you switch between views.

     • When Auto context select is disabled (unchecked), the Model, Derivation, and Deployment views do not keep the same object selected as you switch between views, so a different object can be retained in each view.

   • In the Field Attributes section, select the Show Field Attributes check box to display the Field Attributes tab in the User Defined Object editor. By default, the Field Attributes tab is displayed only if field attributes are already defined for the object. You can override the default by selecting this option. For more information about working with legacy field attributes, see Field attributes, UDAs, and extensions pages in the Application Server help file

4. On the Defaults page, type the object names of the Framework objects you want to be the defaults with respect to assignment relationships.

   • Platform name.

   • Application engine name.

   • Area name.

   • View engine name.

   • Your Security group name, if any.

   Leave a field blank if you do not want a default for that type of object.

   Your changes are saved automatically.

5. When you are done, select OK.