Portfolio Definition: Root Node Setup

The first step in the Portfolio Definition is inserting the Root Node for the new Portfolio: On the new Portfolio Editor screen select the New Portfolio option from the Main Tool Bar or the File pull-down menu. The system inserts the Root node, naming it...

Portfolio Definition: Overview

There are two ways to start a Portfolio:  1. Save an existing Portfolio under a different name and modify it. This may be preferable if your new Portfolio closely resembles one already in use and only slight modifications are required.  2. Start from the very...

Portfolio Editor: Portfolio Structure tab

The Portfolio Structure tab is used to create a hierarchy of nodes or conditions for grouping the data from the DataModel instances. The nodes are organized as a tree that provides embedded or overlapping conditions. The tab is divided into two sections. The left, the...

Portfolio Editor: Toolbar

The toolbar is located below the menu bar. It displays the name of the open Portfolio object and provides quick access to frequently used functions. An asterisk next to the object name indicates that the object has unsaved changes.               The toolbar buttons...

Portfolio Editor: Models tab

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...

Portfolio Editor: Menu bar

The menu bar is located across the top of the Portfolio Setup screen. It provides a set of menus that contain commands to perform various functions.  The File menu is used to manage the Portfolio object.  New Portfolio creates a new Portfolio object on this Portfolio...

Portfolio Editor: Overview

A Portfolio object is a basic ControllerView® element that is used to group the customer data organized in DataModel instances according to specified business requirements. A Portfolio object contains a hierarchy of nodes that represent various inherited and...

Portfolio Editor: Levels tab

A Level is a Portfolio structural element that helps to group the data in the Portfolio execution process. Specifying levels on the Levels tab prompts the system to add as many columns in the resulting Portfolio instance as there are levels. The level names are used...

Portfolio Editor: Additional Fields tab

The Additional Fields tab is used to add and specify additional columns in the resulting Portfolio instance. After a Portfolio object is saved and executed, the resulting Portfolio instance is formed containing the additional columns specified on this tab.  The...

Portfolio Editor: Adjustment Validations tab

The Adjustment Validations tab is used to create validation rules against improper changes to the data on the Adjustments screen of the resulting Portfolio instance. For example, validation rule can disallow columns to contain ‘0’ or values surpassing a certain...