Blueprints for Roadmaps

As an application administrator or PMO content designer, you can use blueprints to configure layouts for roadmaps. You can copy and configure blueprints that reflect the goals of each business unit in your organization. Let's consider an example where multiple product management teams in the organization are using roadmaps to achieve different business outcomes. They have created multiple custom attributes. Some attributes are relevant to the New Banking Application Product Management roadmap while others are relevant to the Next-Gen AI roadmap. The administrator can create different blueprints for these teams so each team would only see information relevant to them.hi
includes a default roadmap blueprint. You can create a copy of the blueprint and edit it to suit your goals. For example, a marketing blueprint may be very different from an engineering blueprint.
The key steps you need to follow while editing blueprints are:
  1. Create a copy of the standard blueprint, rename it, and configure its Details layout (sections and fields).
  2. Add the relevant modules to the blueprint. In the current release, the blueprint includes the Investments and the Properties modules. Both modules will automatically be included in your blueprint.
  3. Publish the blueprint.
  4. (Optional): Mark a blueprint as the default blueprint for roadmaps.
Edit Blueprint Details
You can add various stock and custom attributes associated with Roadmaps to the Properties module in a blueprint.
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.
      You can only add a custom attribute to a blueprint if it is API enabled.
  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.
Associate a Blueprint with a Roadmap
You can navigate to the Roadmap page and use the Column Picker to add the Blueprint field to the grid. Then, associate the blueprint with the relevant roadmap.
Associating Processes with Blueprints
You can use the Actions tab to associate the relevant processes with the blueprint. You will only be able to associate a process when the following conditions are met:
  • The process is active.
  • The process is associated with the object, or it includes a custom script (GEL).
  • You have access to the process.
Follow these steps:
  1. Open the Administration page in Clarity and select
  2. From the blueprint list, click the name of the blueprint that you want to edit.
  3. On the Properties page that displays the currently published blueprint layout, click
  4. Select the
  5. Click
    Add Process
    to view a list of processes available for this blueprint.
  6. Select the relevant processes and click
  7. Use the
    field to set a manual value for this process. This value will determine the sequence in which the process is displayed when users want to execute them using the Actions button on the relevant object instance.
  8. Click
    to save your changes.
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).