The view settings for a navigator view can be modified in the View Settings dialog accessible by clicking the button when the Navigator View is open.
The General tab shows the name and description of the View Settings.
Select the Publish in Portal check box to have the view settings (hierarchy) selectable in the Navigator view of QPR Portal. This option is not applicable to SharePoint hierarchies.
To link the Navigator view settings to QPR Portal view settings, type in the QPR Portal view settings name in the Linked Portal View Settings field. The linked Portal view settings are then used by default when the published Navigator view is selected in QPR Portal. If the linked Portal view settings are not defined or a Portal view with the given name is not found, the default Portal view settings are used.
The Elements tab shows which elements are shown in the navigator views list. The tab is divided into two groups: Hierarchy and Additional Elements.
The Hierarchy group is used to select the shown hierarchy:
•Elements as list: selecting this will make the view show the element types selected in the Additional Elements group as a simple list, i.e. no hierarchy at all.
•Duplicate Element Management: selecting this will make the view show duplicate elements in the model.
•Custom relation hierarchy: selecting this will make the view show the element types and relation attributes (i.e. connectors and relation type custom attributes) selected in the Additional Elements group.
The Custom Relation Hierarchy supports drag and drop operations in the Navigator view for all other relations except Attached Elements, Attached to Elements, Incoming flows, Outgoing flows, From, To, Process steps (of an Organization item), Child process steps (of a subprocess), cardinality N attribute sets, and sub-attributes of cardinality N enumerated values.
When an element is dragged from an element to another element in the Custom Relation Hierarchy, all relations defined by the view setting from the original parent element to the dragged element are cleared. In addition, the Navigator view sets all possible relation attributes that have been defined in the view setting from the new parent element to the dragged element. If an element is dragged with the Shift key pressed, it is added to the new location, instead of moving it from its previous location to the new location. If an element is dragged under the root node of the hierarchy (without holding Shift key down), the relations from the original parent element to dragged element are removed without adding any new relations.
Elements can be dragged from other Navigator views to a Custom Relation Hierarchy. Drag and drop from another Navigator view to other than a Custom Relation Hierarchy is not supported.
If the Navigator view uses a cardinality 1 custom attribute, or a system attribute that can have only one value (Owner of a process step or a flow), and the attribute value has already been set for an element, another element cannot be dragged under it.
•SharePoint hierarchy: selecting this will make the view show the folder hierarchy and the documents in the SharePoint document site defined in the SharePoint settings group. Note that this will only show the hierarchy, documents are not created as information items until they are dragged and dropped to an element or the flow chart.
•System hierarchies: selecting one of these hierarchies will make the view show the elements of the corresponding fixed element types. See the topics Process Hierarchy, Organization Hierarchy, Notes Hierarchy, Resource Groups, Resource Pools and Information Hierarchy for more information.
•Custom hierarchies: selecting one of these hierarchies will make the view show the elements in the user defined element hierarchy.
The Additional Elements group is used to select additional leaf nodes for the hierarchy. The contents of the Additional Elements group depend on the hierarchy selected in the Hierarchy group:
•Elements as list: all element types available in the model.
•Relation hierarchy: all element types and relation attributes can be selected. There are three selection types. If the check box has a check mark, the item can be at root level in the hierarchy. If the check box is filled, the item can appear only as a child node in the hierarchy. If the check box is unchecked, the item is not shown on the hierarchy.
•Process hierarchy: any non-subprocess process step type, connector type, custom element type, store type and group instances are shown as leaf nodes for the process levels they exist in. Resources (allocated to), note (connected to) and organization item (belongs to) are shown as leaf nodes for the previously mentioned leaf nodes and subprocess nodes.
•Organization hierarchy: process step types and resources that belong to an organization item are shown as leaf nodes of the organization item.
•Information hierarchy: process step types, connector types and element types are shown as leaf nodes if an information item is connected to the element.
•Notes hierarchy: none
•Resource Group hierarchy: process step types, connector types and element types are shown as leaf nodes if the resource is used in the element.
•Resource Pool hierarchy: process step types, connector types and element types are shown as leaf nodes if the resource is used in the element.
•Custom hierarchies: connector types (incoming and outgoing flows), resources (allocated to), notes (connected to), information items (connected to).
The SharePoint Settings group is used to define the SharePoint site address and the way information items are created:
•SharePoint site's address: enter the URL of the SharePoint site to this field.
•Information item creation mode: this setting defines how information items are created when documents are dragged from the hierarchy to the elements on the flow chart. If the target element supports information items, the dragged items will be instantiated as information items under that element. Otherwise, they are created as information items that are not associated to any flow chart element. The creation mode of folders will always be 'Linked'.
The Base Model Settings group is used to define settings for seeing base model element usage in child models:
•Show child model instances: when this is selected and a base model element has been instantiated in child models, the child model instances are shown as sub-nodes of the element.
•Show child usage: when this option is selected and a base model element has been used in child models, the child models are shown as sub-nodes of the element. Here, the term "used" means that the child model element has a relation to the base model element, for example via a custom relation attribute or by using a base model information item in a child model activity.
For the child sub-nodes, the pop-up menu available via right-clicking an element has the Open selection available. Selecting it will open the child model in question in a new client, and if the child sub-node is a child model instance, the flow chart view will be opened with the instance selected.
The Base Model Settings selections are not used in QPR Portal or in Model Comparison.
The Elements Tab of the Navigator View Settings Dialog and Additional Elements Shown as Leaf Nodes in the Default Settings View
The Columns tab lists the columns that are shown in the navigator view. To add a column, click the Add button, type a name for the column in the Label field and select the attribute to be shown from the drop-down menu. To remove a column, select the column to be removed and click the Remove button. Note that the last column cannot be removed. To change the order of the columns, select a column and click the Up or Down buttons.
Note that the selections on the Columns tab do not have an effect in QPR Portal.
See the View Settings topic for instructions on how to delete or copy a navigator view or how to create a new navigator view.