The Custom Element Type dialog is used to view and modify the settings of custom element types.
The General tab shows the name, the symbol and the description of the custom element. These properties can be modified.
The symbol is a unique identifier for the custom element type. When a new custom element type is created, QPR Modeling Client will assign it a unique symbol by getting the model object id and adding "MO" to its beginning. It is also possible to edit the symbol for the custom element type. Allowed characters are alphanumeric characters in upper case and lower case.
The Behavior tab shows the predefined behavior options for the element and all custom element hierarchies in the model.
You can select the desired behavior options for the custom element by clicking a checkbox next to the behavior option. The behavior options are:
•Allow QPR Metrics linking: QPR Metrics measures can be linked to the custom element.
•Allow information item linking: information items can be linked to the custom element.
•Allow note linking: notes can be linked to the custom element.
•Allow resource linking: resources can be linked to the custom element.
•Allow element creation on flow chart: the custom element can be drawn on the flow chart, selecting this option will also enable content in the Symbol tab in the dialog and the "Allow instancing", "Allow elements with no instances", "Allow flow linking", and "Interface element" options.
•Hierarchy modeling: the element is shown in the process hierarchy.
•Hide subprocesses from process hierarchy: if you do not want subprocesses to be visible in the process hierarchy view, select this setting. By default, subprocesses are visible in the process hierarchy view.
•Allow instancing: multiple instances of the custom element can be created.
•Check for duplicates when instantiating: when this selection is enabled, creating instances of custom elements of this type can be done by selecting the name of an existing custom element from the drop-down menu displayed on a newly created element.
•Check for duplicates when pasting: when this option is selected, elements are checked for matching element type symbols when doing copy and paste operations for the custom elements. If a matching element type is found from the target model, but the custom attributes are not identical, the missing custom attributes will be added to the matching element type in the target model if the matching element type is not a base model element type and the user is an administrator in the model. If a matching element type is not found from the target model, the element type will added to the model if the base model allows the creation of new element types and the user is an administrator in the model. See the Transfer Model Elements via Clipboard topic for more information about copy paste and matching symbols.
•Allow elements with no instances: if this option is not selected, the custom element is deleted from the model when its last instance is deleted from the flow chart. When selected, the custom element remains in the model even if it has no instances on the flow chart.
•Allow flow linking: flows can be connected to the custom element.
•Allow attached elements: you can attach any element to the boundary of the element in the flow chart so that they together form a group. (See the attached elements section for more information.)
•Allow attaching to elements: the element can be attached to any element so that they together form a group. (See the attached elements section for more information.)
•Interface element: the custom element can be a Process Interface Element.
•Allow usage in child models: the elements of this type can be published to be used with child models. The elements can be published only if "Allow elements without instances" option is selected. In addition, if the "Allow element creation on flow chart" option is selected, the "Allow instancing" option must be selected too. Note that the model must be opened for exclusive editing in order for the element type to be published. What is more, the element type can be unpublished only if the base model doesn't have any child models, or, if the element type was published, the base model has not been saved after publishing. (This option is available only for base models.)
The element hierarchies can be used, for example, to model the structure of the process. The element hierarchies are visible in sub-tabs of the Processes tab in QPR Portal. In case the model containing the custom element hierarchy is a base model, the hierarchy is published if a custom element that is a part of the hierarchy is published. The "Custom hierarchies" list shows all the custom element hierarchies in the model. The list is used to define element hierarchy behavior for the custom element type. The list contains four parts:
•Checkbox: selecting a checkbox will make the custom element type a part of the hierarchy in question.
•Hierarchy: this column lists the names of the element hierarchies in the model.
•Part of branch: the drop down boxes in this column define if the custom element can be a part of a single branch (i.e. the custom element can have only one parent element) or multiple branches (i.e. the custom element can have multiple parent elements).
•Node type: defining the node type as a "leaf node" prevents the custom elements of this type from having child elements, whereas defining the node type as "any node" allows the custom elements of this type to have child elements.
To create a new element hierarchy, click the New button. To view and modify the properties of an existing hierarchy, click the View button. Clicking the Set as Default button will set the selected hierarchy as the default hierarchy for the custom element type. If a hierarchy has been set as a default hierarchy, that hierarchy is shown in the selection dialogs for the custom element type. If a default hierarchy has not been set, the custom elements are shown as a list in the selection dialogs. Clicking the Clear Default button will clear the default setting.
The selections on the Modeling tab are used to define quick modeling settings:
•Default connector type: defines which connector type is used when a new element of this type is created using quick modeling.
•Horizontal offset: defines the horizontal distance of the created element from the selected element in pixels. Allowed values are 10 to 1000. If the grid is enabled, the offset is rounded up to the next grid size.
•Vertical offset: defines the vertical distance of the created element from the selected element in pixels. Allowed values are 10 to 1000. If the grid is enabled, the offset is rounded up to the next grid size.
In addition, the following properties can be set:
•Icon that is used in the Navigator View Hierarchies and Portal views. To select the icon, click the button in the Icon for Hierarchies and Stencil Buttons group and choose an icon from the pop-up menu. You can also select a custom image by clicking Browse and choosing the image from your hard drive.
•Modeling direction of the process level (supported only for subprocess elements and elements that have the Hierarchy Modeling Behavior option enabled).
The default graphical properties of the element type are also shown. Click the Edit... button to modify the graphical properties.
The Default type group can also be selected if the process step is a subprocess element or if the Hierarchy Modeling Behavior option is enabled. Type groups are available with a separate license.
Custom Attribute Types
Custom attribute types can also be defined for the custom element type. On the Custom Attribute Types tab of this dialog, you can add custom attribute types by clicking the "Add" button and remove custom attribute types with the "Remove" button. You can also edit the custom attribute types. To change the order of the custom attribute types, use the upward and downward arrow buttons on the right side of the dialog. You can edit the name of the custom attribute type by typing it into the Name column. The cardinality can also be changed by clicking on the cardinality value and then selecting a new value from the drop-down list (either 1 or N). If you select 1, only one value can be defined for that attribute. If you select N, several values can be defined.
Note: If you delete a custom element type from a base model, you have to select a replacement for it.