| The Rego Roadmap Conversion process provides the ability to create investments, from Roadmap Items. |
|
-
-
Converts one Investment type to another investment type. Functionality • One investment type instance converted to another investment type • Investment object level attributes are copied over by default • Investment sub-objects can be chosen to be copied • The attributes and sub-objects to be copied to must be api enabled • Can convert from non api enabled object like other work to api enabled Custom CIT • Attribute mapping does not support multivalued lookups yet • If auto-numbering is not enabled for target investment type of the sub-objects, an ID will be auto-generated. • Associated risks and issues will not be copied over • Target investment status will be "Unapproved" • If there are Mandatory target investment type attributes either o use a template to convert where having a value in the attribute is not mandatory or Have a default value in the mandatory field defined on the object • If effort task creation is enabled, the effort task will also be brought over. o The effort task will appear with custom code if a investment template is used for conversion • The allocations will extend to the finish of the new investment if investment template is used which has tasks • Almost 500 instances of sub-objects are supported at this point. • The values in lookups need to be active or the process will error out • All required attributes must be api enabled -
This portlet displays a Pie Chart of a Portfolio’s Realized Benefits partitioned into pie slices by the portfolio’s Investments’ Objectives. Clicking on any pie slice (Objective) drills-down into a portlet that lists the Investments that make up that slice. -
This portlet displays a Pie Chart of a Portfolio’s Realized Benefits partitioned into pie slices by the portfolio’s Investments’ Objectives. Clicking on any pie slice (Objective) drills-down into a portlet that lists the Investments that make up that slice.
-
This is a pie chart portlet to show realized benefits across the system by category, including a category for no category or unspecified. Pie chart shows categories of realized benefits in its slices. Available filters:- Portfolio (required)
- Manager
- Stakeholder
- Department
- Category Filter (default to all)
- Goal
- Objective
- Type
-
This is a pie chart portlet to show realized benefits across the system by category, including a category for no category or unspecified. Pie chart shows categories of realized benefits in its slices. Available filters:
- Portfolio (required)
- Manager
- Stakeholder
- Department
- Category Filter (default to all)
- Goal
- Objective
- Type
-
This is a pie chart portlet to show realized benefits across the system by category, including a category for no category or unspecified. Pie chart shows categories of realized benefits in its slices. Available filters:
- Portfolio (required)
- Manager
- Stakeholder
- Department
- Category Filter (default to all)
- Goal
- Objective
- Type
-
Pie Chart that aggregates Realized Benefit (Total Actual Benefit) by OBS for active projects. Only a Benefit Plan associated with the Cost Plan of Record will return data. The filter allows you to select which OBS filter you prefer to use for this pie chart, however, only an OBS associated with Projects will return data. -
Pie Chart that aggregates Realized Benefit (Total Actual Benefit) by OBS for active projects. Only a Benefit Plan associated with the Cost Plan of Record will return data. The filter allows you to select which OBS filter you prefer to use for this pie chart, however, only an OBS associated with Projects will return data.
-
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request. -
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
-
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
