Home / Portfolio Manager settings / Settings / Portfolio Manager settings
Portfolio Manager settings
Portfolio Manager settings apply to everyone who uses your repository, and they define how Portfolio Manager will work in your repository.
So, you will have one copy of them. We suggest that you store then in a package to which only model managers have access.
- The first time anyone tries to save the PM settings, they will be prompted to choose a location where the PM settings can be saved.
- Settings which can be safely changed once PM has been used, and which will not affect the structure of the repository, are highlighted.
If you change any of the other settings after you have started using PM, then you will need to make manual changes to all of your elements and connectors, which is outside the scope of this help.
- All values, except those in red, have default values.
- All values in blue are ones which you might change if you want element types and connectors to have non-English names.
| Attribute | Description |
| branchColor | Defines the color of the connectors which link an ‘implemented’ element with its branched element(s) |
| diffChangedColor | Defines color used in the ‘Differences’ tree, to show: A changed field/tagged value or connector |
| diffDeletedColor | Defines color used in the ‘Differences’ tree, to show: A deleted tagged value or connector |
| diffAddedColor | Defines color used in the ‘Differences’ tree, to show: An added tagged value or connector |
| linkToBaselineColor | Defines color for the connectors whihc linked from branched or planned elements back to ‘implemented’ elements. |
| copySuffix | String which is added to names of elements as they are branched. Helps to see where elements have been branched. Set to blank if you do not want this. Default = ‘*’ |
| baselinePackage | A package where some baseline elements are stored.
Only used to determine which menu options are available to users, so that, for example, only users with write access to this package are shown the ‘implement’ menu option. You may have multiple ‘baseline’ packages – this just needs to be one of them. |
| stagingPackage | Package in your repository where ‘planned’ elements will be placed when they are ‘promoted’ |
| statusLegend | Element which should be a Legend, which is added to generated diagrams, so that the ‘status’ of each element is clear. For an example, see the sample project. |
| archivePackage | Package where ‘archived’ elements are move to, when they are replaced by newer ones when the new elements are ‘implemented’ |