The Models tab is used to specify DataModel objects on which the Portfolio object will be based. This tab has a mini toolbar, a table, and the Requires all models for execution option buttons.
The mini toolbar buttons are used to manage the content of the Models table located below. These buttons are grouped according to their purpose. The following table provides descriptions of each of them.
TABLE Models tab mini toolbar buttons
|Add rows from lookup||Opens Select Data Model dialog box with the list of existing DataModel objects. You can select one or more objects to add them to the Models table|
|Add row||Adds a blank row to the end of the Models table for entering another DataModel object|
|Insert row||Adds a blank row above the selected row in the Models table for entering another DataModel object|
|Delete selected rows||Deletes selected rows from the table. This button is unavailable if no row is selected|
|Copy selected rows to clipboard||Copies selected rows to the Clipboard|
|Paste rows from clipboard||Inserts the content stored in the Clipboard as rows of the Models table|
|Move up selected row, Move down selected row||Moves a selected item up a row and moves a selected item down a row, respectively. These buttons are unavailable if two or more rows are selected|
|Edit selected Data Model||Opens the Data Model Setup screen where you can view or modify the properties of the DataModel object in the selected row. This button is available only if one row is selected|
The Models table has two columns: Model Name and Model Description. Initially, the table is empty. To populate it, use the buttons described in Table.
Note: If no row is added to the Models table (i.e. no DataModel object is associated with the Portfolio object), a warning message will appear because this Portfolio object cannot be saved in valid state.
Requires all models for execution option button defines the set of DataModel instances to be used by a Portfolio execution task. If ‘Yes’ is selected, instances of all the DataModel objects specified in the table will be used. If ‘No’ is selected, only instances of the DataModel objects required by the Portfolio execution task will be used.