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.
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.
|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.|
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:
Follow these steps:
Filter the blueprints list to manage the configuration workload in a focused effort. You can filter the list by the following criteria:
The filtering results are persisted for a user across all login sessions.
Use the Search field to search for blueprints using free form search.
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.
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.
The Standard Project blueprint includes the following visuals:
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.
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.
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.
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.
You can rename or edit the configuration of a user-defined blueprint. You cannot edit, rename, or delete the Standard Project 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. Seefor 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:
The following project attributes are not available to appear on the blueprint Fields list:
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.
Follow these steps:
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:
Follow these steps:
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:
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.
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:
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:
Referrer URLs must be comma-separated.
While configuring channel and referrer URL, the following errors can occur:
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).
The following visual treatments apply to blueprint components (fields, visuals, and modules):
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.
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.