Skip to content
CA PPM - 15.5
Documentation powered by DocOps

New User Experience: Configure Project Blueprints

Last update March 8, 2019

As an application administrator or PMO content designer, use blueprints to configure layouts for different types of projects that share a common template. You can copy and configure blueprints that reflect the goals of each business unit in your organization. You can associate project templates with 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.

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.

 


Example: Using 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

Navigate: In the main menu, click Administration and then click Blueprints.

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.

Move Templates: You can drag-and-drop templates from one blueprint into another blueprint.

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.

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.

Visuals: You can drag-and-drop up to three visual gauges that appear on the project tiles.

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 details. The following details require an explanation:

  • 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. Use the double arrows at the top to expand all or collapse all listed blueprints at once. In the expanded view, you can see all associated project templates for each blueprint. Use the single arrow next to a blueprint to expand or collapse that single blueprint and view the associated templates.
  4. Use the actions menu that appears to the right of the published date for a blueprint to copy, rename, delete, or make that blueprint the default one. You cannot rename or delete the Standard Project blueprint.

Filter and Search Blueprints

Filter the blueprints list to manage the configuration workload in a focused effort. You can filter the list 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.

The filtering results are persisted for a user across all login sessions.

Use the Search field to search for blueprints using free form search.

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 marked as the default blueprint.

With the blueprint edit right, you can associate project templates to the Standard Project blueprint. No investment edit rights are required to move or associate a project template to 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

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 any other user-defined blueprint. From the actions menu for the blueprint, click Copy. The new blueprint is created with a unique identifier through auto-numbering.

When you create a blueprint by copying an existing blueprint, the details, visuals, and modules from the existing blueprint are copied over. You can tailor the details and visuals in the new blueprint for specific templates for use when creating new projects.

Edit a Blueprint

You can rename or edit the configuration of a user-defined blueprint. You cannot edit, rename, or delete the Standard Project blueprint.

Add Project Fields to a Blueprint

To configure a project 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. Also, enable the fields for API access by specifying an API Attribute ID for them in the attribute details. See CA PPM Studio Objects and Attributes for details.

Adding the API Attribute ID to the following attribute types in Clarity PPM Studio is not supported. Also, 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

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.

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 modules for a blueprint so they display as icons on project tiles. 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.

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

Tip: 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 and Microsoft SharePoint:

Troubleshooting Tips for Administrators Configuring 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. 

Tip: 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 the page).


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 indicates an active component that is used in the blueprint.
  • A gray background and black font indicates an inactive component that is not used in the blueprint.
  • A gray background and gray font indicates 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.

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.

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.

Was this helpful?

Please log in to post comments.