# Global Settings A complete description of the Global Settings available for Designer. {% hint style="danger" %} **Designer Admin Rights Required** You need Designer Admin rights to change global settings. {% endhint %} Designer provides an easy method to configure Global Settings for all users. To access the Global Settings menu: 1. Launch the Diagram view. 2. Select the 3-line menu (hamburger) button and select **Settings**. This option is only visible for Designer Admins. ![designer-global\_settings1.png](/files/5t3UYJS3NKqHTWDh3PFE) Your browser will take you to the Global Settings menu, each setting includes a short header explaining its function. ## General Settings Key features of the Designer application are configured in this tab. ![designer-global\_settings2.png](/files/tUKaXHuVCjynIK93sQ57) In summary, the menu items have the following effect: | Setting | Effect | Note | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Block Approved Diagram** | Toggle this option on to prevent further editing of an approved Diagram. With this button on, users must clone approved diagrams if they want to make changes. | Designer supports versioning of approved and non-approved diagrams automatically. You can distinguish between different versions on the same Diagram. Switch off this option to use the default feature providing higher flexibility. | | **Delete Diagram** | Specifies who can delete diagrams, options include: Any User, Diagram Owner, Admin only | | | **Create preview image of diagram** | This feature creates a preview of the Diagram in the x\_inpgh\_des\_diagrams table. Since Version 5.0 Designer provides live previews of diagrams. | Deactivating this option decreases the amount of time required to save a diagram | | **Automatic Zoom** | Sets the diagram to zoom to fill the screen by default. | | | **Auto Checkout** | Enable this so that users automatically checkout diagrams when editing | With this enabled only the user with the diagram checked out can edit it. | | **Auto Checkout Time** | Specify the duration for how long a user can have a diagram checked out | | | **Autosave Time** | Specify the amount of time between autosave | The user must have autosave enabled during their Designer session for this option to have an effect. | | **Export Image scale** | Sets the default resolution for all PNG exports. The larger the scale the greater the file size. | A 200% scale provides sufficient resolution for screen and print presentations for small to medium size diagrams. The scale can be changed by the user for each export. | | **Landing Page** | Toggle this setting on and add a landing page to the text box in order to show when initially loading diagrams | | | **Parent field(s) priority for hierarchy** | Set a comma-separated list to represent a hierarchy for custom parent fields | E.g. `u_parent` instead of `parent`. | ## Commit Settings Options related to committing changes are available in this tab. ![Designer Global Settings Commit Settings](/files/dW1jIlPM4OXiE6aGA79p) In summary, the menu items have the following effect: | Setting | Effect | Note | | ------------------------------------ | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Commit Duplicate Elements** | Toggle this option to allow Designer to commit duplicate elements. | For more information on committing elements, see Committing Elements & Relationships. In general, Designer checks the Class Definitions form to prevent duplicate elements based on the "Display Name" settings. See Class Definitions and Cross Scope Privileges for more information | | **Commit Duplicate Relationships** | Toggle this option on to enable Designer to commit duplicate relationships | By default Designer checks if a relationship is a duplicate based on the relationship type. For more information on the relationships see Relationship Fields and for more information on committing changes to relationships see Committing Elements & Relationships | | **Auto commit after final approval** | This option automatically commits all approved elements and relationships with cross-scope privilege. | For further information see Class Definitions and Cross Scope Privileges | {% hint style="info" %} **Application Cross-Scope Privileges** Use the hyperlinked text within the Settings page blue information box to quickly open the ServiceNow table to set the cross-scope privileges. {% endhint %} {% hint style="warning" %} **Manually Committing Elements & Relationships** Be aware that the Auto commit can be bypassed by any user being part of the "Designer Commit" Group/role. {% endhint %} ## Approvals Settings Options in this tab relate to workflow approval steps and options. ![designer-global\_settings3.png](/files/YrkQuCifO4ir3NGQqA23) In summary, the menu items have the following effect: | Setting | Effect | Note | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | **Contributor review** | This setting enables the Contributor review workflow step, where selected Contributors perform the approval | See further details here: Approval Workflow | | **Assessment review** | Activate this option to enable the second step of the workflow, which is performed by the group members of the Design Assessment Group. | See further details here: Approval Workflow | | **Architecture review** | Disabling the Architecture review workflow step will disable all other steps. Enable the Architecture review to drive the final approval of a Diagram by the Architecture Committee Group members | See further details here: Approval Workflow | | **Allow Creator Approval** | Toggle this to enable diagram creators to approve their own diagrams. | The creator must be a part of the assessment group or architecture committee for this to work | {% hint style="info" %} Select the checkbox next to each option to enable multiuser approval. {% endhint %} ## Data Panel Options in the Data Panel tab toggle activation and additional fields on the Shape/Relationship Data form. In summary, the menu items have the following effect: * **Show Notes**: Activate to show Notes field. This field content will not be committed and is only available within the Diagram. * **Show Expected dates**: Activate the Expected dates option to show the Expected Start & Expected Stop dates for planning purposes. * **Show Tooltip**: Activate to show the Tooltip field. * **Show Link**: Activate to show the hyperlink to the form for committed elements & relationships. * **Show SysID**: Activate to show the SysID for committed elements & relationships. {% hint style="info" %} **Fields Visibility** All fields are shown on the Shape/Relationship Data Form (CTRL+M), and on the Data Form on the right hand panel. The above mentioned editable fields are not part of the commit feature! {% endhint %} ## Custom Fields Custom fields are user-defined fields added to x\_inpgh\_des\_diagrams. They supplement pre-defined fields, which cannot be changed by users. After you have added some user-defined fields to the Dictionary in service now, these fields will appear in the Custom Fields tab in Global Settings. Here you can show or hide these field or select the check box to make them read-only. ![designer-global\_settings5.png](/files/tQCG1FXwquUIH2Abau4Q) ## Custom Buttons Adding custom buttons provides an easy way to add new buttons, which add further UI actions, to the Designer Form view. Such actions include triggering a value change to initiate additional logic e.g. triggering a business rule, or a workflow. ![designer-global\_settings6.png](/files/aiooo1OMhiiVGzpLt9kB) | Setting | Effect | Note | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ---- | | **Button Layout** | You can change the background color and font color. | | | **Visible if user has role** | Select the role the user needs to have to see the button. This can be combined with Visible if User member of group | | | **Visible if User member of group** | Select the group membership the user needs to have to see the button. This can be combined with the previous role selection. | | | **Visible if Diagram field** | Select the field and value when the button is visible. | | | **Click action** | Select the field and target value the button click action should perform. | | When ready to add the button: select **Add New Button**. ## Licences ![designer-global\_settings7.png](/files/HqBwnLwKe7dGd66gAriq) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ins-pi.com/designer/configuration/enhanced-configuration/global-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.