New User Experience: Configure Blueprints for Projects and Investments

ccppmop157
As an application administrator or PMO content designer, use blueprints to configure layouts for different types of projects, custom investments types. You can copy and configure blueprints that reflect the goals of each business unit in your organization.
You can associate project templates with project blueprints. When users create projects from these templates, the project details from the blueprint appear. The stakeholders for a business unit see only the sections, fields, visuals, and modules that are relevant to their projects.
Similarly, you can associate investments with custom investment types that share a common blueprint for their properties. Use blueprints to configure layouts for different types of custom investments in alignment with your organizational goals. When users create investment instances, the details from the associated blueprint appear. The stakeholders for a business unit see only the details that are relevant to their investments. For example, a marketing blueprint might appear different from an engineering blueprint.
Depending on your access rights as the application owner, you can configure the blueprinting capabilities in the 
New User Experience
. Verify that you have the appropriate rights for configuring blueprints. See New User Experience Access Rights in the Reference section.
 
2
 
 
HID_newux_admin_blueprints
Example: Using Project Blueprints
 
As an application owner, Ian is on-boarding a new Marketing business unit. The new business unit has unique requirements for capturing specific data when planning and executing projects. To facilitate their adoption of the new business unit, Ian copies the Standard Project blueprint to create the Marketing Blueprint. Based on the available options, Ian meets with various stakeholders to finalize the details. He tailors the marketing project details so that only the fields that are relevant to marketing projects appear. For example, Ian includes the Target Segments and Pilot Launch Date fields.
Ian configures the blueprint based on daily meeting results. After a week, Ian finally feels comfortable publishing the blueprint so that he can now associate templates to it. Theresa, a senior project manager, has created several templates for different project types in classic PPM. Ian associates the Marketing Tradeshow template with the new marketing blueprint. Nicole, the project manager for Marketing, creates a new project from the Marketing Tradeshow template. When Nicole views her new project, the project details show the fields that Ian configured for the type of projects she manages.
Feature Highlights: Project Blueprints
 
Feature Blueprints.jpg
 
 
c1.png
 
 
Navigate
: In the main menu, click 
Administration
 and then click 
Blueprints
.
 
c2.png
 
 
Copy a Blueprint
: You can view but cannot configure the default Standard Project blueprint; however, you can make a copy and then edit your copy. Click the Options menu to copy, rename, or delete a blueprint (you cannot delete the default blueprint). You can also make another blueprint the default blueprint. When users create new projects, they must select a template. The default blueprint determines the sections, fields, visuals, and modules they see.
 
c3.png
 
 
Move Templates
: You can drag-and-drop templates from one blueprint into another blueprint.
 
c4.png
 
 
Edit and Publish
: Open a copied blueprint and click Edit. You can define the layout details, visuals, and modules. When you click Publish, your changes appear in the templates that determine the functionality and appearance of current and future projects.
 
c5.png
 
 
Sections and Fields
: You can add and remove sections on the project layout. In this example, a user drags a field into a section and drops it near an adjacent field. You can adjust the position and resize the fields for an ideal fit.
 
c6.png
 
 
Visuals
: You can drag-and-drop up to three visual gauges that appear on the project tiles.
 
c7.png
 
 
Modules
: You determine at least one or multiple modules that appear when users open a project. The first four modules appear on the project tiles.
View Blueprints in a List
By default, the Standard Project blueprint is available with the product. Ian can configure extra blueprints either by copying the Standard Project blueprint or any other custom blueprint previously configured. The available and configured blueprints are listed with the following details:
  •  
    Last Used: 
    Specifies the date when a project was last created from a template that is associated with the blueprint. 
  •  
    Projects Using: 
    Defines the number of projects that are currently associated with the blueprint.
  •  
    Modified By: 
    Specifies the logged-in user that last configured the blueprint.
  •  
    Published: 
    Specifies the date when the blueprint details were published for use by project templates.
 
Follow these steps:
 
  1. Click 
    Administration
    .
  2. Click 
    Blueprints
     to see all available blueprints.
  3. Expand a blueprint to view all associated project templates.
    1. Click the double arrows at the top to expand all or collapse all listed blueprints. 
    2. Click the single arrow next to a blueprint to expand or collapse only that single blueprint.
  4. Click the 
    ⋮ Actions
     menu to the right of the last published date for a blueprint to copy, rename, delete, or make that blueprint the default. 
    You cannot rename or delete the Standard Project blueprint; however, you can make a copy and edit your copy.
 
Visual Indicators for Blueprint Components
 
The following visual treatments apply to blueprint components (fields, visuals, and modules):
  • A white background and black font indicate an active component that is
     not
     used in the blueprint.
  • A white background and gray font indicate an active component that is used in the blueprint.
  • A gray background and black font indicate an inactive component that is
     not
     used in the blueprint.
  • A gray background and gray font indicate inactive components that are used in the blueprint. The inactive components are not visible to the users in the project details. 
  • Asterisks (*) indicate required fields.
Filter and Search Blueprints
You can filter the list of blueprints by the following criteria:
  •  
    Blueprint
    : Select one or more blueprints to display in the list.
  •  
    Template
    : Select one or more active templates that are associated with the listed blueprints. Only the selected templates display for the blueprints. You can only select active template names to filter for specific templates. You cannot filter for inactive templates by name. You can only filter for inactive templates by status.
  •  
    Template 
    active
     status
    : Select Active, Inactive, or both types of templates to display for the listed blueprints. By default, only Active templates are displayed.
  •  
    Blueprint Type
    : Select the type of blueprints (projects or custom investments) to display in the list.
You can also use the Search field to search for blueprints by name. The application preserves your filter selections across all your individual login sessions.
Standard Project Blueprint
The 
Standard
 Project blueprint is the pre-defined system blueprint that you cannot configure or delete. All existing templates are associated with the Standard Project blueprint. Initially, the Standard Project blueprint is also marked as the 
default
 blueprint. With the blueprint edit right, you can associate project templates with the Standard Project blueprint. No investment edit rights are required to move or associate a project template under a blueprint.
Standard Project Details
The Standard Project blueprint includes the following details. The same details appear on the details page for a project that is associated with Standard Project blueprint.
  • Project Summary details:
    •  
      Project Name
      Defines the project name.
    •  
      Project ID
      Defines the unique identifier for the project. The ID is auto-generated using auto-numbering.
    •  
      Project Type
      Defines the project type based on the template that was used such as Infrastructure Deployment.
    •  
      Work Status
      Defines the project status
    •  
      Start/Finish
      Defines the start and end dates for the project.
    •  
      Objective
      Defines the business goal for the project.
  • Stakeholders details:
    •  
      Manager
      Defines the stakeholder that manages the project lifecycle.
    •  
      Sponsor
      Defines the stakeholder that evaluates the functional and technical benefits and analyzes the cost benefits of the project.
    •  
      Project Management Office
      Defines the stakeholder that reviews and approves the project.
    •  
      Finance and Governance
      Defines the stakeholders that review aggregated views of all projects in the unit and make budget decisions.
  • Settings details:
    •  
      Track Mode
      Defines the time tracking mode for the project. Resources use the defined method for entering time spent on the project tasks.
    •  
      Open for Time Entry
      Specifies whether resources can track time against the project using timesheets
    •  
      Active
      Specifies whether the project is available for use in the system. You can only assign resources and perform financial processing for an active project.
    •  
      Banner Color
      Defines the color that appears at the top of the project tiles.
Standard Project Visuals
The Standard Project blueprint includes the following visuals:
  • Effort Spent
  • Budget Spent
  • Next Milestone
Standard Project Modules
The Standard Project blueprint includes the following modules. The same modules appear as clickable icons on the tile for a project that is associated with the Standard Project blueprint.
  • Conversations
  • Tasks
  • Links
  • Status
  • Financials
  • Risks
  • Issues
  • Changes
  • Documents
  • Details
  • Staff
  • Task List
The Task List module has been introduced in 
Clarity PPM
 15.6.1. In previous versions of 
Clarity PPM
, the task list was available as the List layout on the Tasks page.
Set the Default Blueprint
Designate a blueprint as the default blueprint for your organization. All existing projects not associated with any blueprint are associated with the current default blueprint. After an upgrade, if a project is marked as a template and does not have a blueprint association, it is associated with the current default blueprint.
You can designate the Standard Project blueprint or any other blueprint as the default blueprint. From the blueprints list page, click the 
 actions menu for the blueprint and select Make Default. The Default banner appears next to the blueprint name. Only one blueprint can be a default.
When you mark another blueprint as the default, the existing blueprint is no longer the default blueprint.  
Associate Templates with Blueprints
A template is used to create projects. Project details are displayed to end-users based on the associated blueprint. You can associate a template with only one blueprint.
Initially, all existing templates are associated to the Standard Project blueprint by default. Depending on your business requirements, you can change a template association from one blueprint to another. Existing projects that are associated to a blueprint do not change. Only new projects use the new blueprint association to display details.
Use drag-and-drop to move a template from one blueprint to another.
Copy a Blueprint
Create a blueprint by copying the 
standard
 project blueprint or another user-defined blueprint. From the 
 
Actions
 menu for the blueprint, click 
Copy
. The new blueprint is created with a unique identifier through auto-numbering. The copy also includes the details, visuals, and modules from the existing blueprint. You can edit the copy and associate one or more project templates with it, instead of always using the standard blueprint. 
Edit a Blueprint
You can rename or edit the configuration of a user-defined blueprint. You cannot edit or delete the Standard blueprint for projects or custom investment types. You 
can
 rename the Standard blueprint for projects or custom investment types.
Add Project Fields to a Blueprint
You can add attributes to projects and custom investment type objects in Classic 
Clarity PPM
. The attributes are available for configuration on your project and custom investment type blueprints.
  • To configure a blueprint, verify that all required fields are available to the blueprint. For example, to configure a blueprint for marketing projects, verify that all marketing-related fields are added to the Project or Investment object in Classic 
    Clarity PPM
  • Enable the fields for API access by specifying an API Attribute ID in the attribute details. See 
    CA PPM Studio Objects and Attributes 
    for details.
  • You can also add OBS fields to blueprints and enable them for API access. See Configure an Organization Breakdown Structure for details on how to create an OBS and associate to the project object.
Adding the API Attribute ID to the following attribute types in 
Clarity PPM
 Studio is not supported. You cannot configure these attribute data types to appear on the blueprints Fields list:
  • Custom time-scaled value (TSV)
  • Attachment
  • URL
The following project attributes are not available to appear on the blueprint Fields list:
  • % Complete Calculation Method     
  • Actual Cost     
  • Approved
  • Blueprint Active ID     
  • Budgeted Capital Cost     
  • Budgeted Cost Finish (date)    
  • Budgeted Cost Start (date)     
  • Budgeted Cost Total     
  • Budgeted Operating Cost    
  • Currency Code        
  • EAC Sum for Labor Resources    
  • ETC Sum for Labor Resources     
  • Investments Using     
  • Last Used    
  • Page Layout
  • Planned Cost Total    
  • Priority   
  • Progress
  • Project Category
  • Status
  • Template
Remove Field Attributes from Project and Custom Investment Blueprints
To remove a custom attribute so that it no longer appears in the grid column panel or on blueprints, inactivate the custom attribute in Studio.
Edit Blueprint Details
 
Follow these steps:
 
  1. From the blueprint list, click the name of the blueprint that you want to edit.
  2. On the details page that displays the currently published blueprint layout, click 
    Edit
    .
  3. Edit the blueprint details:
    • Drag-and-drop available fields from the Fields list onto an existing section within the blueprint. Use the Search to look for specific fields by label name. Resize any field in the layout using the shaded triangle that appears in the bottom-right of the field.
    • Drag-and-drop fields from a blueprint layout section to another section. 
    • Drag-and-drop fields from the blueprint layout sections back to the list of fields. You can also click the X on a field in a section to remove that field. The field goes back to being an available field.
    • Delete a section with or without fields. All fields within that section are removed from the layout and are available again to select from the Fields panel.
    • Drag an existing section up or down within the blueprint to rearrange the sections. All fields that are contained in the section also move to the new location.
    • Add a section by clicking Add Section or drag-and-drop the Add Section button to where you want to add a section.
  4. If you are unsure of the changes, discard the edits. The edits are deleted and the blueprint details view reverts to the currently published version.
  5. Click 
    Publish
     to save your changes and make the new layout available to projects. All projects associated with this blueprint display the new layout.
Edit Blueprint Visuals
Project tiles display visuals in the form of ring charts, date widgets, or icons. For each blueprint, you can show, hide, change, or reorder the visuals that display on the project tiles.
Configure visuals that align with the project goals for a specific business unit or theme.
 
Examples
: An IT department manages complex projects and typically likes to see gauges that reflect traditional cost (Budget Spent) and schedule (Effort Spent) metrics. A Marketing department manages product launches and trade shows and prefers progress-oriented visuals such as Days Remaining. 
The following visuals are available:  
  •  
    % Complete
    Defines the percentage of the project work that is completed. The chart is based on the % Complete field that you can configure for the project details page.
  •  
    Budget Remaining
    Defines the amount of budget remaining for the project calculated as Total Remaining Cost/Total Budgeted Cost.
  •  
    Budget Spent
    Defines the amount of budget spent for the project calculated as Total Actual Cost/Total Budgeted Cost.
  •  
    Days Remaining
    Defines the number of days remaining on the project. If the current date is before the project start date, then days remaining are the project finish date minus the project start date. If the current date is past the project start date but before the project finish date, then days remaining are the project finish date minus the current date. In all other cases, the value is zero.
  •  
    Days to Start
    Defines the number of days until the project starts (project start date - current date provided the project start date is later than the current date. If the current date is past the start date or if the start date is undefined, then the value is zero.
  •  
    Effort Remaining
    Defines the hours remaining on the project calculated as Total Remaining Units/Total Budgeted Units or (EAC - Actual)/EAC. If the estimate at completion (EAC) is zero or null, the effort remaining value is zero. If Actual is greater than EAC, then the effort remaining value is negative.
  •  
    Effort Spent
    Defines the hours spent calculated as Labor Actuals/Total Effort. Labor Actuals is the sum of all actuals posted for labor resources. Total Effort is the total EAC for the project.
  •  
    Finish Date
    Defines the project finish date.
  •  
    Next Milestone
    Displays the next milestone date after today. If no milestones exist or if all milestones are from the past, the product uses the project Finish date.
  •  
    Start Date
    Defines the project finish date.
 
Follow these steps:
 
  1. From the blueprints list, click the name of a blueprint.
  2. On the details page, click 
    Visuals
    .
  3. Click 
    Edit
     to configure visuals for the project tile layout:
    • Select at least one and up to three visuals.
    • Drag an available visual from the Visuals list and drop it on an existing visual in the project tile to replace that visual.
    • Use the Search box to look for specific visuals by label name.
    • Drag-and-drop visuals from the project tile back to the list of visuals. You can also click the X on a visual in the project tile to remove that visual from the tile. The visual goes back to being available.
    • Rearrange the visuals with the project tile by dragging and dropping.
  4. Discard edits or publish to save your changes.
Edit Blueprint Modules
You can configure up to four (4) blueprint modules to appear as icons on the bottom of each project tile. The icons allow users to go directly to a module such as Conversations or Tasks without having to first navigate a module and then to another module.
When a user clicks an area on the project tile that is not a module link (for example, the banner color or one of the gauges), the product takes the user to the first module that you configure for the blueprint. For example, if you configure the following modules for a blueprint in left to right order, the user lands on the Status Report module for the project:
  • Status Report
  • Details
  • Financials
  • Conversations
Similarly, when a user creates a project in the 
New User Experience
, after entering the project name, the product navigates them to the first module based on the blueprint configuration.
At least one module is required for displaying on the project tile.  A maximum of four modules appears on the project tiles in the order of their configuration. The remaining modules appear as tabs inside a project.
Publish a Blueprint
When you publish a blueprint, all edits in progress for the details, visuals, and modules are published at once. All projects that are associated with the blueprint display the latest layout that is configured for the blueprint.
 The New User Experience currently supports 25 modules, 25 visuals, and 200 attributes for the project blueprint.
Delete a Blueprint
With the appropriate access rights, you can delete any user-defined blueprint. If you delete a blueprint that is not the default, all templates and projects that are associated with the blueprint are then re-associated with the current default blueprint. If the Standard Project blueprint is the default blueprint, all templates and projects are associated with this blueprint. If you delete a user-defined default blueprint, then the associated templates and projects are also re-associated with the Standard Project blueprint. The Standard Project blueprint becomes the new default blueprint. You cannot delete the Standard Project blueprint.
Identify the Blueprint for a Project
As you work on blueprints, templates, and projects over time, you might want a quick way to identify and change the blueprint associated with a project.
 
Follow these steps
:
  1. In the 
    New User Experience
     main menu, click  
    Administration
    .
  2. Click 
    Blueprints
    .
  3. Open a blueprint. (You cannot edit the 
    standard
     blueprint; however, you can make a copy and then edit your copy.)
  4. Click 
    Edit
    .
  5. On the 
    Details
     tab, from the list of 
    Fields
     on the left, drag the 
    BLUEPRINT
     field to the layout on the right.
  6. Click 
    Publish
    .
Project managers and other users with sufficient access rights can now open a project, click the 
DETAILS
 tab, and view or edit the value of the 
BLUEPRINT
 field. 
 In the Project grid, users can also click 
CONFIGURE
 to add the 
BLUEPRINT
 field to the 
DETAILS
 pane.
 The following image shows the 
BLUEPRINT
 field on the project 
DETAILS
 page (left) and on the project 
DETAILS
 pane or flyout (right).
 
image2019-5-20_12-49-24.png
 
You can also view the associated blueprint for each project in Classic PPM.
 
Follow these steps
:
  1. In the 
    New User Experience
     main menu, click  
    Classic PPM
    .
  2. In the Classic PPM main menu, click 
    Home
    Portfolio Management
    Projects
    .
  3. On the 
    Projects
     list page, click 
    Options
     and select 
    Configure
    .
    image2019-5-20_13-25-40.png
     
  4. Select the Blueprint field. 
  5. Click the RIGHT arrow to move it from Available Columns to Selected Columns.
  6. Click Save and Return.
The following image shows examples of blueprint associations for a list of projects.
 
image2019-5-20_13-13-1.png
 
Projects with no value in the Blueprint field, do not have an associated blueprint. If you open one of these projects in the 
New User Experience
, it inherits the details, visuals, and modules defined in the 
default
 blueprint. Blueprints were introduced in 15.3. After an upgrade from CA PPM 15.2 and earlier releases, Clarity PPM automatically uses the 
default
 blueprint when you open your projects.
 
Options
: You can decide to allow that default loose association to continue or you can set the project to subscribe to a different template or blueprint. If you create a blueprint and mark it as the default, we recommend that you also move your templates to that default blueprint before your users create new projects. If your templates do not appear under a blueprint, new projects won't have a blueprint association and revert to the layout of the currently defined default blueprint.
 
Example
: All four (4) projects below from 15.2 were upgraded to 15.3 or newer. Their 
Blueprint Active ID
* is set to the current 
default
 blueprint. It was 
Standard Project
 immediately after the upgrade but has since been changed in the New User Experience to 
(Copy of) Standard Project
. Whenever you change the default blueprint or create a new blueprint and mark it as the default, those projects continue to adopt the look-and-feel of the default blueprint. To end this loose association with the default blueprint, you set the Blueprint for the first project (Automated Security Enhancements) to Standard Project. The application immediately updates the Blueprint Active ID to match. If you change the Project Template (for example, you change a blank value to Major Project Template), the loose association to the default blueprint still prevails, even if the default blueprint does not include the Major Project Template.
 
image2019-5-22_14-11-54.png
 
image2019-5-22_14-38-26.png
 
*Blueprint Active ID is an optional virtual attribute available in Classic PPM
Configure Links to External Content With Channels
To provide project team members with easy access to external sites, other applications, or even classic PPM links, add a channel to the blueprint. You can configure links to external applications as channel modules in a blueprint. The user gets access to all the business decision-making capabilities without leaving a PPM project. You can configure a maximum of five (5) channels.
 
Example
: Configure links to your Agile Central projects, classic PPM pages, SharePoint links, or a Google Drive for your projects.
 
Follow these steps:
 
  1. Navigate to the custom blueprint and click 
    Edit.
     
  2. Once the custom blueprint is in editable mode, drag-and-drop Channel # to the blueprint modules section.
  3. Click the Channel icon and enter the Channel Name and Channel URL.
  4. Enter one or more comma-separated referrer URLs. Referrer URLs are used when your channel URL is redirected to another authentication link. For example, if your channel URL requires SSO login, specify the authentication URL in the referrer URL.
  5. Click 
    Preview
     to test the channel link. Refresh your browser to view the preview.
  6. When you are ready for other users to begin using the new channels inside an open project, click 
    Publish
  7. Before users can see the content, advise them to refresh the project page in their browser window. 
Channels support the same context-sensitive links with dynamic parameters that you can use with the Links module and Links page. Links with dynamic parameters are not rendered in Preview mode for channels in blueprints, but you can see them in projects. Only concrete links can be previewed.
The following image shows how you can configure channel URLs in a blueprint. In this example, the blueprint administrator configures channels that enable users to navigate to CA Agile Central. 
 
Channels.gif
 
You can use the following parameters to construct dynamic links inside your channel modules:
• Project Code: ${code}
• Project ID: ${internalID}
• Project Manager: ${manager}
• User Name: ${userName}
• Project Name: ${name}
Blueprint Channels That Link to Classic PPM Pages with the Phoenix UI Theme Applied
If you create a channel that links to the Classic Clarity PPM user interface and the optional Phoenix UI theme is applied, users see two main menus along the left edge of the page. To show just one main menu, follow these steps:
  1. Edit the blueprint.
  2. Open the channel module.
  3. Add the following parameter to the 
    Channel URL
     field:
      &puiFullscreen=on 
     
  4. To hide the project-specific menu items, append the following parameter:
     
      &puiHidePPMTabs=on 
     
  5. Save and publish your blueprint.
 
image2019-3-19_19-26-6.png
 
Use Relative Paths in a Generic Channel URL
When building a channel to link back to Classic PPM, replace the server URL with the HTML dot-dot-slash syntax for relative rather than fixed absolute path references. If the data is restored to another server, your channel continues to function.
Original URL
Generic Channel URL
http://my_clarity.ca.com/niku/nu
./../../../../niku/nu
 
Channel URL Example 1
: You are building a link in a channel from the New UX to the properties page of a project in Classic PPM as shown below:
https://helloworld.ca.com/niku/nu#action:projmgr.projectProperties&id=5039001
You want to use the optional Phoenix UI theme in Classic PPM. Format your Channel URL as follows:
./../../../../niku/nu#action:projmgr.projectProperties&id= ${internalID}&puiFullscreen=on&puiHidePPMTabs=on
Without leaving the page, users can interact with Classic benefit plans from inside the project in the New UX.
The following image demonstrates what your users see:
 
image2019-3-19_19-51-13.png
 
 
Channel URL Example 2: 
In this example, you define a link in a channel to the Classic PPM Project Processes Page:
./../../../../niku/nu#action:projmgr.projectProcessInstances&id=${internalID}&object_type =project&object_id=${internalID}&ui.page.space=mainnav.work&ui.page.template=union.appPage
 
image2019-3-19_19-57-36.png
 
Channel URL Example 3: 
A link to Rally (formerly CA Agile Central) investments would appear as follows:
https://rally1.rallydev.com/#/investments
 
Channel URL Example 4: 
The following example shows a link to a Jaspersoft report:
https://clarityserver.ca.com/reportservice/flow.html?_flowId=viewReportFlow&reportUnit= %2Fca_ppm%2Freports%2Fproject_management%2FCSK_PRJ_ProjectStatusSummary &standAlone=true&ParentFolderUri=/ca_ppm/reports/project_management &populateProject=1&projectKey_1=${internalID}
Troubleshooting Tips for Administrators to Configure Blueprint Channel Modules
  • Refresh the browser page before you preview a channel.
  • Advise users to refresh their browser after publishing a blueprint with new or changed channels.
  • Avoid spaces, semicolons, and special characters in referrer URLs. 
  • Referrer URLs must be comma-separated.
While configuring channel and referrer URL, the following errors can occur:
  •  
    Refused to Frame
    : You might see a Refused to frame error when you click Preview for a given channel URL because it violates the following Content Security Policy directive: "frame-src app.pendo.io cdn.pendo.iodocops.ca.com 'self' data:".
    Resolution
    : To resolve this condition, refresh your browser. Refreshing forces CA PPM to white list the domain in compliance with the Content Security Policy directive. The new blueprint channel feature has a built-in ability to white list a domain after you define it in the channel. Refresh your browser to white list a domain before you can preview it. White listing allows CA PPM to display external applications in the PPM framework, provided the other application does not have CORS restrictions built-in since CA PPM cannot overwrite an external security policy.
  •  
    Mixed Content
    : You might see the following error if you configure a link with HTTP inside a domain that requires a secure HTTPS connection: 
    Mixed Content: The page at 'https://MY-PPM-SERVER.ondemand.ca.com/pm/#/admin/blueprints/blueprint/edit/5000043' was loaded over HTTPS, but requested an insecure resource 'http://OTHER-SITE.domain.org'. This request has been blocked; the content must be served over HTTPS.
    Your browser might show an alert asking you to confirm before loading unsafe scripts. In Chrome, a security shield icon and prompt appear asking you to confirm that you want to open an insecure channel. 
     
    Resolution
    : To resolve this condition, edit the channel in the blueprint to use HTTPS and then publish the blueprint, or, if you know the HTTP content is safe, preview the HTTP content in another browser. 
On-premise administrators can also white list a domain using admin system options. See CSA: Service and Admin Command-Line Utilities (near the bottom of that page).
Video: Hide Navigation and Tool Bar in Channels with Phoenix UI Theme for Clarity PPM
 

 
Configure Custom Project Subobjects as Modules
You can add a new module to appear as its own tabbed page along with the other project pages.
To configure your project pages to accurately reflect your organizational business processes, define custom project subobjects. API-enable the custom subobjects for use with blueprints. When an end-user creates a project using the blueprint, a new tab corresponding to the subobject name appears on the project. 
 
Example:
 Ian, the system administrator receives a request to define a project subobject called Compliance and configure the subobject for display in the 
New User Experience
. In Classic PPM Studio, Ian creates the subobject and makes it API-enabled. On the Attributes tab of the subobject, Ian specifies an API Attribute ID so that the attributes are available for selection in the new 
New User Experience
. In the 
New User Experience
,  Ian selects a project blueprint and adds the new sub object as a module. He then creates a new project using this blueprint and verifies that the sub object appears as a tab and the grid contains the selected attributes.
You can API-enable both new and existing project subobjects. After you API-enable a subobject, you cannot disable it for the API.
 
Follow these steps:
 
  1. In classic PPM, click 
    Administration
    Studio
    Objects
    .
  2. Create a subobject (for example, 
    Compliance
     or 
    Opportunities
    ) for the Project master object.
    image2018-11-19_14-1-59.png
     
  3. Select the 
    API Enabled
     check box for the subobject. When you API-enable a new or existing project subobject, an API Attribute ID is generated for the subobject using the subobject ID and prefixing it with "cust" (for example "custoOpportunities"). You can see this ID on the objects list page.
  4. Create attributes for the subobject. Specify a value for the 
    API Attribute ID
     for all attributes.
    The subobject dynamically creates the Compliance module and views in the project blueprints in the 
    New User Experience
    .
  5. In the 
    New User Experience
    , click a project blueprint and navigate to 
    Modules
    .
  6. Click 
    Edit
    . Drag-and-drop the Compliance module to the blueprint modules section.
    image2018-11-19_14-4-39.png
     
  7. Click 
    Publish
    .
  8. Create a new project based on a template that uses the blueprint you just edited and published.
  9. Verify that your new custom subobject module appears as a tab. Click 
    COMPLIANCE
     to open the new grid layout on its own dedicated page for working with instances and attributes of your custom Compliance subobject.
    image2018-11-19_14-7-46.png
     
Create Blueprints for Custom Investment Types
You can define different blueprints for your custom investment types. Blueprints allow the configuration of the custom investment screens to more accurately reflect the business processes at your organization.
 
Follow these steps:
 
  1. In classic PPM, click 
    Administration
    Studio
    Objects
    .
  2. Create a custom investment object (for example, Demand) and select 
    Investment Extension
     for 
    Object Extension
    .
  3. Click 
    Save
    .
    When you create a custom investment object, the following gets automatically generated:
    • An API Attribute ID for the object using the object ID and prefixing it with "cust" (for example "custDemand"). You can see this ID on the objects list page.
    • A Standard custom investment type blueprint with the name of the object in the 
      New User Experience
       You cannot delete or edit the standard custom investment blueprint.
    • A Details view with default attributes for the custom investment type blueprint. When end users drill into a custom investment instance from the 
      New User Experience
      , they see the details.
  4. Create attributes for the custom investment object. Specify a value for the 
    API Attribute ID
     for all attributes.
  5. When end users create custom investment instances in the 
    New User Experience
    , they see the attributes as fields on the grid. Each new custom investment instance is associated with the blueprint that you have designated as the 
    Default
     blueprint.
  6. To change the associated blueprint, add the Blueprint attribute to the grid from the Column Panel. You can then select a custom investment blueprint for the investment instance.
Configure Custom Investment Type Blueprints
Create a copy of the 
Standard
 custom investment type blueprint. You can then rename the copy and configure it to match your specific business requirements. When end-users create custom investments that are based on the configured blueprint, they see the details that are relevant to them. 
You can configure the custom investment type blueprints as follows:
  • Create a copy of the 
    standard
     blueprint, rename it, and configure its Details layout (sections and fields).
  • Mark a blueprint as the 
    default
     blueprint. 
  • Publish the changes in a blueprint to update each associated custom investment.
  • Delete a user-defined blueprint.
 
Example: Using Custom Investment Type Blueprints
 
You want to provide unique screen layouts for different work types at your organization. Create the following custom investment objects in Classic PPM:
  • Enhancement Requests
  • Business Cases
  • Customer Contracts
Next, in the 
New User Experience
, copy the three standard blueprints that were generated for the custom investment objects. Associate the first blueprint with the Enhancement Request custom investment type and name the blueprint 
Simple Enhancement v1.0
. Edit the blueprint details to display only some of the default fields.
Associate the second blueprint with the Business Case custom investment type and name the blueprint 
Finance Department Business Case
. Edit the blueprint details to display 25 financial fields broken out into 3 sections. Repeat the process with the appropriate configuration for the third blueprint for the Customer Contracts custom investment type. Once published, all the new blueprints are available for stakeholders to create three types of custom investment instances.
Your portfolio managers can now create an instance of the Business Case custom investment type. The application offers the option to use a blueprint. When users select the Finance Department Business Case blueprint, they land on the details page that was configured for that blueprint.