Clarity: Configure Blueprints for Projects

As an application administrator or PMO content designer, use blueprints to configure layouts for different types of projects. 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.
Depending on your access rights as the application owner, you can configure the blueprinting capabilities in
. Verify that you have the appropriate rights for configuring blueprints. See
Access Rights in the Reference section.
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
: In the main menu, click
and then click
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.
: You can drag-and-drop up to three visual gauges that appear on the project tiles.
: 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
  2. Click
    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
    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
    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
    : 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 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
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
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 Properties page for a project that is associated with the 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
  • Properties
  • Staff
  • Task List
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
project blueprint or another user-defined blueprint. From the
menu for the blueprint, click
. 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. You
rename the Standard blueprint for projects.
Add Project Fields to a Blueprint
You can add attributes to the project object in
Classic PPM
. The attributes are available for configuration on your project 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 in
    Classic PPM
  • Enable the fields for API access by specifying an API Attribute ID in the attribute details. See
    Classic 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
Classic 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
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 Blueprint
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.
Add Modules to Blueprints
If you have created a custom subobject for the Project object, add it as a module in the Project blueprint to make it available in
. For more information on custom subobjects, see Clarity Studio Objects and Attributes.
Follow these steps:
  1. Navigate to
  2. Click the name of the blueprint that you want to edit and click
  3. Select the
  4. Drag and drop the relevant modules into the blank boxes to add them to the blueprint.
    • You will only see custom subobjects that are API enabled as modules.
    • You will see the first-level custom subobjects as modules. The API-enabled, second-level subobjects are automatically added to the Details panel of the first-level subobject.
    • An object's blueprint can include a maximum of 50 modules, including default modules, custom subobjects, and channels. When you reach the limit of 50, you will no longer be able to add modules to the blueprint. Consider removing or combining the least used modules in such cases.
  5.   Click
    to save your changes and make the changes available to users.
  6. Open a project that is using the blueprint that you just edited. For more information on identifying the blueprint associated with a project, see Identify the Blueprint for a Project.
    You will see the custom objects appear as modules.
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
  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
    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.
: 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
  3. Click
    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
  • Properties
  • Financials
  • Conversations
Similarly, when a user creates a project in
, 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.
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
    main menu, click Projects.
  2. Switch to the grid layout and click the Columns panel.
  3. Search and select the Blueprint attribute.
    The Blueprint attribute is added as a column in the grid. You can now view the blueprints associated with each project
Projects with no value in the Blueprint field, do not have an associated blueprint. If you open one of these projects in
, it inherits the details, visuals, and modules defined in the
blueprint. After an upgrade from
15.2 and earlier releases,
automatically uses the
blueprint when you open your projects.
: 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.
: All four (4) projects below from 15.2 were upgraded to 15.3 or newer. Their
Blueprint Active ID
* is set to the current
blueprint. It was
Standard Project
immediately after the upgrade but has since been changed in
(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.
*Blueprint Active ID is an optional virtual attribute available in
Classic PPM
Use Channels to Embed External Content
Use channels to embed content from another source, such as an external site, application, or Classic PPM context-sensitive investment reports into Clarity. You can interact with the content and make informed business decisions without leaving an investment in Clarity.
As an administrator, you can add a channel to the blueprint, and configure a maximum of fifteen (15) channels. After you create a channel, you can find it in the Modules panel. After you publish the blueprint, the newly created channel appears as a tabbed page within the investment (Project, Custom Investment, Ideas) and Custom Objects.
After you add a channel, you need
drag and drop the new channel to the blueprint layout section, it's automatically added.
After you create 15 channels, you can no longer see the New Channel button.
This page contains the following sections:
Configure a Channel
Let's see how you can add a channel and embed content from another source into Clarity.
  1. Go to the
    and click
  2. From the
    tab, click
    New Channe
  3. Enter information in these fields:
    1. Channel Name
      : Enter the channel name
    2. Channel URL
      : Enter the channel URL
    3. Referrer URLs
      : Enter one or more comma-separated referrer URLs. Use Referrer URLs when your channel URL redirects you to another authentication link.
      For example, specify the authentication URL in the referrer URL if your channel URL requires SSO login.
  4. Click
    to test the channel.
    Remember, only concrete links can be previewed.
  5. Click
    to publish the blueprint.
    Your channel is created. Ask your users to refresh the browser session to see the new channel as a tabbed page within the investment.
Dynamic Parameters for Channels
  • You can use these parameters to construct dynamic content inside your channels
    • project id = ${_internalId}
    • projectCode = ${code}
    • project name =${name}
    • project manager =${manager}
    • logged in user =${_userId}
  • Channels also support custom attributes as input parameters, using attribute API Alias value, of the following attribute type:
    • Number
    • String
    • Single Value Lookup (Static and NSQL based)
Channels also support context-sensitive content with dynamic parameters. Content with dynamic parameters are not rendered in the Preview mode for channels in blueprints, but users can see them within the investment.
Use Relative Paths in a Generic Channel URL
When adding 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
Example 1:
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}&
Example 2:
A link to Rally investments would appear as follows:
Example 3:
The following example shows a link to a Jaspersoft report: %2Fca_ppm%2Freports%2Fproject_management%2FCSK_PRJ_ProjectStatusSummary &standAlone=true&ParentFolderUri=/ca_ppm/reports/project_management &populateProject=1&projectKey_1=${_internalId}
Channels That Link to
Classic PPM
with the Phoenix UI Theme Applied
If you create a channel that links to the
Classic 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
  4. To hide the project-specific menu items, append the following parameter:
  5. Save and publish your blueprint.
Video: Hide Navigation and Tool Bar in Channels when Phoenix UI Theme is Applied

Troubleshooting Tips for Administrators to Configure Channels
  • Before you preview a channel, refresh the browser page.
  • 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.
Known Issues for Channels
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 'self' data:”
To resolve this condition, refresh your browser. Refreshing forces Clarity 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. Whitelisting allows Clarity to display external applications in the Clarity framework, provided the other application does not have CORS restrictions built-in since Clarity 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 '' was loaded over HTTPS, but requested an insecure resource ''. 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.
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).
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.
Ian, the system administrator receives a request to define a project subobject called Compliance and configure the subobject for display in
. 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
. In
,  Ian selects a project blueprint and adds the new subobject as a module. He then creates a new project using this blueprint and verifies that the subobject 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
  2. Create a subobject (for example,
    ) for the Project master object.
  3. Select the
    API Enabled
    checkbox 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
  5. In
    , click a project blueprint and navigate to
  6. Click
    . Drag-and-drop the Compliance module to the blueprint modules section.
  7. Click
  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
    to open the new grid layout on its own dedicated page for working with instances and attributes of your custom Compliance subobject.