Integrate CA PPM with CA Agile Central

Use the Agile add-in to integrate cappm with rally agile development software. The integration allows an organization to maintain the operational activity in rally and use cappm to focus on project status.
ccppmod1541
Use the Agile add-in to integrate 
Clarity PPM
 with 
CA Agile Central
 agile development software. The integration allows an organization to maintain the operational activity in 
CA Agile Central
 and use 
Clarity PPM
 to focus on project status.
 
 
2
 
 
Integration Components
The following integration components allow 
Clarity PPM
 projects and tasks to synchronize with 
CA Agile Central
 portfolio items.
  • A synchronization job that runs in the background to synchronize 
    Clarity PPM
     projects with 
    CA Agile Central
    .
  • Agile Summary project properties that link the 
    Clarity PPM
     project with 
    CA Agile Central
    .
  • Agile Summary task properties that link the 
    Clarity PPM
     task with 
    CA Agile Central
    .
  • An integration subpage for 
    CA Agile Central
     that allows you to configure integration options.
  • Embedded 
    Clarity PPM
     Timesheet portlet in 
    CA Agile Central
     
Integration Benefits
The project manager can answer the following questions for a release:
  • Has it been approved as part of the portfolio governance process?
  • How much is the cost?
  • Are we on track?
  • What gets delivered?
At the enterprise level, the integration provides the following benefits:
  • Portfolio visibility for business stakeholders so they are aware of investment benefits and delivery
  • Elimination of redundancy by seamlessly managing project artifacts between 
    Clarity PPM
     and 
    CA Agile Central
     
  • Project status information and visibility so budget, resource requirements, and deliverable status are available in 
    Clarity PPM
     
When you integrate with 
CA Agile Central
, projects in 
Clarity PPM
 correspond to portfolio items in 
CA Agile Central
. As a default you can integrate 
Clarity PPM
 projects with 
CA Agile Central
 initiatives or features (also known as portfolio items). An initiative can cross multiple features and releases, has a start and end date, and rolls up work beneath it. You can define features under the initiatives and can associate them with releases.
You can synchronize agile 
Clarity PPM
 projects with 
CA Agile Central
 in the following directions:
 
CA Agile Central
 to 
Clarity PPM
 Direction
  • The project manager links agile 
    Clarity PPM
     projects to corresponding agile systems. Each agile system is an integration configuration to 
    CA Agile Central
    .
  •  
    Clarity PPM
     projects are created as initiatives in 
    CA Agile Central
    .
  • Features under the 
    CA Agile Central
     initiatives are created as corresponding tasks under the linked 
    Clarity PPM
     projects. 
  • The project manager has access to status information imported from the 
    CA Agile Central
     portfolio items into the corresponding 
    Clarity PPM
     project and tasks.
 In this integration direction, the mapping of the 
CA Agile Central
 portfolio items to 
Clarity PPM
 projects does 
not
 have to be contiguous to the portfolio items mapped to 
Clarity PPM
 tasks.
For example, if your portfolio item hierarchy in 
CA Agile Central
 includes initiatives, epics, and features, then you can map the items as follows:
  •  
    CA Agile Central
     initiatives to 
    Clarity PPM
     projects
  •  
    CA Agile Central
     features to 
    Clarity PPM
     tasks
In this example, you can skip mapping anything to the epic level portfolio item in 
CA Agile Central
.
 
Clarity PPM
 to 
CA Agile Central
 Direction
  • The project manager links agile 
    Clarity PPM
     projects to corresponding agile systems. Each agile system is configured as an integration to 
    CA Agile Central
    .
  •  
    Clarity PPM
     projects are created as initiatives in 
    CA Agile Central
    .
  • Selected tasks under the linked 
    Clarity PPM
     projects are created as corresponding features under the 
    CA Agile Central
     initiatives.
  • The project manager has access to status information imported from the 
    CA Agile Central
     portfolio items into the corresponding 
    Clarity PPM
     project and tasks.
Bidirectional
  • The project manager links agile 
    Clarity PPM
     projects to corresponding agile systems. Each agile system is an integration configuration to 
    CA Agile Central
    .
  •  
    Clarity PPM
     projects are created as initiatives in 
    CA Agile Central
    .
  • Features under the 
    CA Agile Central
     initiatives are created as corresponding tasks under the linked 
    Clarity PPM
     projects.
  • Selected tasks under the linked 
    Clarity PPM
     projects are created as corresponding features under the 
    CA Agile Central
     initiatives.
  • The project manager has access to status information imported from the 
    CA Agile Central
     portfolio items into the corresponding 
    Clarity PPM
     project and tasks.
Example: Integrate an Agile Project in 
Clarity PPM
 with 
CA Agile Central
 
 
A product development team uses 
Clarity PPM
 and a separate tool to track their software development projects. As more teams embrace agile methodologies, project management receives limited insight into team effort. Visibility is suffering both at the program and portfolio levels. Entering time twice in two different systems is leaving developers frustrated. Leadership at the portfolio level finds it difficult to track the business value of these agile projects.
Management decides to integrate their 
Clarity PPM
 projects with 
CA Agile Central
 portfolio items. Project managers can now manage and track all agile projects as initiatives in 
CA Agile Central
. The scrum teams can create features, user stories, and tasks to define their work for the initiatives. The 
CA Agile Central
 initiative and feature status details are synchronized back to 
Clarity PPM
 as project and task agile summaries.  
Configure the 
CA Agile Central
 Integration
 Project data is integrated between the two systems based on the following setup:   
  • Integration object and its attributes that are defined to create the connection with 
    CA Agile Central
    .
  • An agile integration owner with access to projects, resources, and API.
  • Project level settings for synchronization.
  • A background job that runs to synchronize project data. 
As an 
Clarity PPM
 administrator, complete the following high-level steps to connect the product with 
CA Agile Central
:  
Verify the Prerequisites
To integrate with 
CA Agile Central
, verify that you have completed the following requirements: 
  • The compatible version of the Agile add-in is installed on your product instance. Installing the add-in allows you to save the integration information and populate default integration values. See the Release Notes for details
     
  • The Agile add-in content is installed successfully. Navigate to the Items tab for the Agile add-in under Administration, Content Add-Ins and verify that all the listed items display the 
    Installed
     status.
  • The REST API Status is Enabled on your system so the Synchronize Agile Central job can run. Navigate to Administration, General Settings, System Options page to verify the REST API status. The background job uses the REST APIs to synchronize data between the systems.  
  • An active 
    Clarity PPM
     user is identified as the Agile Integration Owner. The user needs the appropriate access rights to update the projects and tasks that are accessed using the integration.
 On-Premise customers can see Add-Ins and Integrations to learn how to install the Agile add-in. SaaS customers must create a support ticket to request the Agile add-in to be installed. During the Agile add-in installation, attributes are created in the Project and Task objects. The new attributes are protected and you cannot add, modify, or delete them from the data warehouse.
Define the Integration Attributes
As a 
Clarity PPM
 administrator, configure the integration attributes available with the Agile add-in to create the connection with 
CA Agile Central
. Define the information necessary for the integrated systems to work together. Also, capture the default integration information that is needed for transferring data. 
CA Agile Central
 allows you to configure up to five levels of portfolio items in the portfolio hierarchy. The lowest level is P1 and the highest level is P5. As per the default configuration, you can map to a maximum of two portfolio items at any hierarchy level. For example, you can map to feature at the P1 level and initiative at the P2 level. In 
Clarity PPM
, the P1 level item is mapped to a task and the P2 level item is mapped to a project.
The documentation reflects a 
CA Agile Central
 portfolio hierarchy that is available and supported by default. 
 
Follow these steps
  1. From Administration, select Integrations under General Settings.
  2. Click New.
  3. Complete the requested information. The following fields require explanation:
    •  
      Integration URL
      Defines the URL for the integration instance (for example, the 
      CA Agile Central
       instance URL). To determine what URL to use when connecting to 
      CA Agile Central
       from behind a firewall, refer to the Agile Central documentation for alternate URLs and associated IP addresses.
    •  
      Integration Instance
      Defines the integration instance to connect to such as a 
      CA Agile Central
       workspace ID. See Obtain Workspace, Owner, and Project ID in CA Agile Central.
       The Integration Instance field requires a value to create a successful integration with 
      CA Agile Central
      . The Synchronize Agile Central job uses the value in this field to synchronize 
      Clarity PPM
       projects with 
      CA Agile Central
       portfolio items. The job fails if a value is missing from the field.
    •  
      Referrer URL
      Defines the identity provider URL for use by the 
      Clarity PPM
       timesheet integration with 
      CA Agile Central
      . The value in this field is used only if you are not using the same URL as the 
      Integration URL
       field. See Configure SSO for CA PPM Timesheet Integration with CA Agile Central.
    •  
      Authentication Type
      •  
        Basic
        Select this authentication method to integrate with 
        CA Agile Central
         On Premise. Provide a username and password to use for authentication. When using this authentication type, you do not need to specify an API key.
         
       
       
      •  
        API Key
        Select this authentication method to integrate with 
        CA Agile Central
         On Demand. Provide the 
        CA Agile Central
         API Key that maps to the 
        Clarity PPM
         integration record. To obtain this key, follow the directions in this KB article. The article explains how to access the 
        CA Agile Central
         Application Manager and create the 
        CA Agile Central
         API Key. We recommend that you create a unique  
        CA Agile Central
         API Key for each Integration record in 
        Clarity PPM
        . The 
        CA Agile Central
         API Key is associated with a  
        CA Agile Central
         user that has the required privileges to update the 
        CA Agile Central
         workspace. Whenever you synchronize information from 
        Clarity PPM
         to 
        CA Agile Central
        , the updates appear for the 
        CA Agile Central
         user that is associated with the 
        CA Agile Central
         API Key. A username and password are not needed when using this authentication type.
  4. Optionally, to connect to 
    CA Agile Central
     using a proxy server in an 
    Clarity PPM
     On Premise environment, specify the following proxy server information. If you are accessing 
    CA Agile Central
     through a non-authenticated proxy, provide the proxy server and port details only. If you are accessing 
    CA Agile Central
     through an authenticated proxy, also provide the proxy username and password. After defining the proxy server information, restart the 
    Clarity PPM
     app and bg services.
    •  
      Proxy Server
       
      Defines the name of the proxy server. Provide the full URL starting with http or https.
    •  
      Proxy Port
       
      Defines the port for the proxy server.
    •  
      Proxy User Name
       
      Defines the user name for connecting to the proxy server.
    •  
      Proxy Password
       
      Defines the password for connecting to the proxy server.
      If you do not have the proxy server information, contact your network administrator. If the connection to 
      CA Agile Central
       is unsuccessful, review the proxy server logs to make sure the IP address is allowed.
  5. Click Save. A new Agile Central tab appears next to General. The new tab appears only if the Agile add-in is installed.
  6. Click Agile Central and define the policy details and the default project and task information for 
    CA Agile Central
    . The following fields require explanation:
    •  
      Portfolio Item Type Map (Project)
      Defines the 
      CA Agile Central
       portfolio item type to which the 
      Clarity PPM
       project maps to (for example, initiative). You can map a 
      Clarity PPM
       project to any level of the portfolio items in the 
      CA Agile Central
       portfolio hierarchy except the P1 level. We recommend that you do not change the value for this field after the initial synchronization. Changing this value can break the connection with 
      CA Agile Central
    •  
      Portfolio Item Type Map (Task)
      Defines the 
      CA Agile Central
       portfolio item type to which the 
      Clarity PPM
       task maps to (for example, feature). The portfolio item type must be at a lower hierarchy level. For the following integration directions, the portfolio item type has to be contiguous to the portfolio item type that you defined for the Portfolio Item Type Map (Project) field:
      • PPM to AC
      • Bidirectional 
      For the AC to PPM integration direction, the portfolio item type 
      does not
       have to be contiguous to the portfolio item type that you defined for the Portfolio Item Type Map (Project) field.
      We recommend that you do not change the value for this field after the initial synchronization. Changing this value can break the connection with 
      CA Agile Central
      .
      If the value for the Portfolio Item Type Map for both project and task is the same, then only one task is created in 
      Clarity PPM
      . The task has the same name as the project and all the details from 
      CA Agile Central
       are rolled up to that task during synchronization.
    •  
      Create and Sync Team
       
      Specifies whether to synchronize the 
      Clarity PPM
       project team with the users assigned to 
      CA Agile Central
       portfolio items. By default, the option is selected and team members are synchronized whenever the synchronization job runs
    •  
      Create and Sync Tasks
      Specifies whether to synchronize the 
      Clarity PPM
       tasks with the 
      CA Agile Central
       portfolio items. By default, the option is selected and tasks are synchronized whenever the synchronization job runs.
       When a parent PPM task has actuals, assignments, or both, the integration cannot add a child task under this parent. Instead, the integration adds the child task without a parent. The behavior complies with the rule that summary tasks in PPM cannot have actuals or assignments. The situation applies when synchronizing user stories from Agile Central to PPM tasks.
    •  
      Create Direction
      Defines the integration direction for synchronizing tasks.
      Select from the following options:
      • Agile Central to PPM. Depending on the Portfolio Item Type mapping, projects that you create in 
        Clarity PPM
         are created as corresponding portfolio items in 
        CA Agile Central
        . Child portfolio items that you create in 
        CA Agile Central
         are created as corresponding tasks in 
        Clarity PPM
        . If you do not select an integration direction, Agile Central to PPM is used as the default option.
      • PPM to Agile Central. Depending on the Portfolio Item Type mapping, projects that you create in 
        Clarity PPM
         are reflected as corresponding portfolio items in 
        CA Agile Central
        . Tasks that you create in 
        Clarity PPM
         are also created as child portfolio items in 
        CA Agile Central
        .
      • Bidirectional. Tasks are synchronized in either direction provided the Synchronize flag is checked at the task level. Any tasks that you create in 
        Clarity PPM
         are synchronized with 
        CA Agile Central
         features. Also, any features that you create in 
        CA Agile Central
         are synchronized with 
        Clarity PPM
         tasks.
      The Create Direction field works with the Synchronize option for tasks in a project that is integrated with 
      CA Agile Central
      . For each task marked as Synchronize, a corresponding portfolio item is created in 
      CA Agile Central
      .
    •  
      Default Agile Central Owner ID
      Defines the default owner ID to use when a portfolio item (for example, initiative) is created in 
      CA Agile Central
      . See Obtain Workspace, Owner, and Project ID in CA Agile Central for details.
    •  
      Default Agile Central Project ID 
      Defines the default project ID (the agile team ID) to use when a portfolio item (for example, initiative) is created in 
      CA Agile Central
      . See Obtain Workspace, Owner, and Project ID in CA Agile Central for details.
    •  
      Open for Time Entry (Team)
      Specifies whether the team members that are synchronized from  
      CA Agile Central
       are open for time entry in 
      Clarity PPM
      . Select one of the following options for the integration instance:
      • Yes: All the resources that are added to the 
        Clarity PPM
         project team from 
        CA Agile Central
         are open for time entry.
      • No: All the resources that are added to the 
        Clarity PPM
         project team from 
        CA Agile Central
         are not open for time entry.
      • Select: The Open attribute value on the Team Object is considered for determining whether the resources that are added to the 
        Clarity PPM
         project team from 
        CA Agile Central
         are open for time entry.
    •  
      Open for Time Entry (Task)
      Specifies that the tasks created in 
      Clarity PPM
       are open for time entry. If you do not select this option, the default setting from the task object definition takes effect. 
    •  
      Cost Type
      Defines the default cost type value to use when a task is created in 
      Clarity PPM
      . The default value is used only for task creation, not for updates.
    •  
      Charge Code
      Defines the default charge code value to use when a task is created in 
      Clarity PPM
      .
    •  
      Time Tracking Project Template
      Defines the default time tracking project template to use for creating time tracking sub tasks under a new task. When the Synchronization job runs, sub tasks are automatically created in 
      Clarity PPM
       in the following cases:
      • A task is added in 
        Clarity PPM
         from CA Agile Central.
      • A task is created within 
        Clarity PPM
        . Only those tasks that have the Synchronize flag checked have the new time keeping sub tasks created.
      The Time Tracking Project template includes tasks for the purpose of classifying time. The project template is available in both the Agile Central to PPM and the PPM to Agile Central integration directions.
      : You can synchronize 
      CA Agile Central
       user stories with 
      Clarity PPM
       tasks at the project level. After 
      Clarity PPM
       tasks are created for the user stories, you can track time against them. In this case, you can omit selecting a Time Tracking Project template for the integration. See Synchronize CA PPM Projects with CA Agile Central Portfolio Items for details.
Set the Agile Integration Owner
Define a 
Clarity PPM
 user as the Agile Integration Owner that the integration uses to run the following types of operations: 
  • Run the Synchronize Agile Central job
  • Update the 
    Clarity PPM
     project and task status from 
    CA Agile Central
     
Assign the required access rights to the Agile Integration Owner so they can update the 
Clarity PPM
 project and associated team and tasks. If the agile summary pages for the project and tasks are secured, assign the secure sub page rights to the Agile Integration Owner. 
 
Follow these steps:
 
  1. Click 
    Administration
    Project Management
    Settings
    .
  2. Select the Agile Integration Owner (for example, admin) and Save.
  3. Assign the following global access rights to the integration owner:
    • API - Access
    • Projects - Navigate
    • Resource - Navigate
  4. Depending on how you have implemented 
    CA Agile Central
     in your organization, assign the access rights to the agile integration owner for
    • Project - Edit Management (for specific projects, or for all projects)
    • Resource - View (for specific resources, or for all resources)
    • Resource - Hard Book (for specific resources, or for all resources)
Set Up the Synchronize Agile Central Job
The Agile Integration Owner (or the 
Clarity PPM
 administrator), can set up the Synchronize Agile Central job to run at scheduled intervals to synchronize 
Clarity PPM
 projects with 
CA Agile Central
 portfolio items. The project manager can also run the job manually when needed. See Run or Schedule a Job 
.
 
The job reads through the 
Clarity PPM
 projects that have the Synchronize option selected and a value defined for Agile System in their agile summary. See CA PPM Jobs Reference.
 
Note
: To learn how to synchronize an existing 
Clarity PPM
 project with an existing 
CA Agile Central
 portfolio item, see 
Link an existing CA PPM Project to an Existing 
CA Agile Central
 Portfolio Item
.
 
Run the Synchronization Job from a Project
 
As a project manager, you can run the Synchronize Agile Central job directly from an active project using the Actions menu. Hence, you do not require the access rights to run jobs or view job outputs. You are granted instances access rights only to the job that you start from a project Actions menu.
Only the project from which you run the job is updated, not all projects. The project ID is included as part of the job name, for example: Synchronize Agile Central (Project2018-11). The admin users do not have access to the output of these jobs.
 
Note
: The Synchronize Agile Central action is not available by default from the Actions menu of a project. The action is available a part of the Agile add-in items install for the Project Properties - General content item.
 
Follow these steps:
 
  1. Click 
    Administration
    Studio
    Content Add-Ins
    .
    The Content Add-Ins page appears.
  2. Select 
    Agile Addin
     and click 
    Items
    .
  3. Filter for the 
    Project Properties - General
     content item and verify that the item is available for installation.
    When you install the Agile add-in, the item displays an 
    Upgrade Ready
     status. To protect any configurations that you might have made to the project properties view, the item is not automatically installed.
  4. Do one of the following:
    • If you do not have view configurations, select the 
      Project Properties - General
       content item and click 
      Install
      . The Synchronize Agile Central action becomes available from the main project properties page and subpages for users with edit access to the project.
    • If you have view configurations, manually configure the project properties view in Studio to include the Synchronize Agile Central action in the Actions menu. To configure the Actions menu, see CA PPM Studio Menus and Links.
  5. Open the project properties and click 
    Actions
    Synchronize Agile Central
    .
Synchronize 
Clarity PPM
 Projects with 
CA Agile Central
 Portfolio Items
After the integration is set up with 
CA Agile Central
, the project manager can start synchronizing 
Clarity PPM
 projects with 
CA Agile Central
. By default, the synchronization allows initiative and feature status information from 
CA Agile Central
 to flow back to the 
Clarity PPM
 projects and tasks. The project manager has visibility into the work status information in 
CA Agile Central
See CA PPM Jobs Reference for details about how the Synchronize Agile Central job updates 
Clarity PPM
 and 
CA Agile Central
 for each integration direction.
 
 
CA Agile Central
 to PPM Direction
 
 
Follow these steps
:
  1. Open Home, and from Portfolio Management, click Projects.
  2. Open the project that you want to synchronize to 
    CA Agile Central
    .
  3. Click Properties and select Agile Summary.
  4. Complete the following information:
    • Select the Synchronize check box to link the 
      Clarity PPM
       projects to 
      CA Agile Central
       initiatives or features.
    • Select the Create and Sync Stories check box to bring over user stories from 
      CA Agile Central
       into 
      Clarity PPM
       for time tracking purposes.
    • Select the Agile System to use for synchronizing the project with 
      CA Agile Central
      .
: In the 
CA Agile Central
 to 
Clarity PPM
 integration direction, the Synchronize Agile Central job ignores the task Synchronize option. The job does not create portfolio items for tasks.
 
PPM to 
CA Agile Central
 Direction
 
 
Follow these steps:
 
  1. Open Home, and from Portfolio Management, click Projects.
  2. Open the project that you want to synchronize to CA Agile Central.
  3. Click Properties and select Agile Summary.
  4. Complete the following information:
    • Select the Synchronize check box to link the 
      Clarity PPM
       projects to 
      CA Agile Central
       initiatives or features.
    • Select the Create and Sync Stories check box to bring over user stories from 
      CA Agile Central
       into 
      Clarity PPM
       for time tracking purposes.
    • Select the Agile System to use for synchronizing the project with 
      CA Agile Central
      .
  5. Navigate to Tasks.
  6. For each task you want to synchronize, click task properties and select Agile Summary.
  7. Select the Synchronize check box.
 
Bidirectional Synchronization
 
In the Bidirectional integration, features and user stories from 
CA Agile Central
 are brought in as tasks and sub tasks in 
Clarity PPM
. Also, tasks from 
Clarity PPM
 are pushed to 
CA Agile Central
 as portfolio items. 
In 
Clarity PPM
, select the Synchronize check box for both projects and tasks that you want to synchronize with 
CA Agile Central
.  To synchronize user stories with tasks, select the Create and Sync Stories check box at the project level.
The following diagram shows how the Synchronize Agile Central job updates 
Clarity PPM
 projects with latest status details from 
CA Agile Central
 in the the Agile Central to PPM integration direction:
The image shows how the Synchronize Agile Central job updates CA PPM projects with status details from Agile Central
The image shows how the Synchronize Agile Central job updates CA PPM projects with status details from Agile Central
Synchronize Tasks
The following diagram shows how the Synchronize Agile Central job updates 
Clarity PPM
 tasks with latest status from 
CA Agile Central
 in the Agile Central to PPM integration direction:
The image shows how the Synchronize Agile Central job updates CA PPM tasks with status details from Agile Central
The image shows how the Synchronize Agile Central job updates CA PPM tasks with status details from Agile Central
The 
Clarity PPM
 task start and finish dates are populated based on the actual start and end dates of the corresponding 
CA Agile Central
 portfolio item. If the actual start and end dates of the 
CA Agile Central
 portfolio item are not defined, the 
Clarity PPM
 task start and finish dates match the planned start and end dates of the 
CA Agile Central
 portfolio item. If both the actual and planned dates are not defined for the 
CA Agile Central
 portfolio item, then the 
Clarity PPM
 project start and finish dates are used to define the 
Clarity PPM
 task start and finish dates.
 
Synchronize Agile Central User Stories to 
Clarity PPM
 Tasks
 
You can synchronize 
CA Agile Central
 user stories with tasks in 
Clarity PPM
 to reflect the work progress. With user stories available as tasks in 
Clarity PPM
, you can assign team members to the tasks and have them report time against these tasks.
Select the Create and Sync Stories check box on a project Agile Summary page to bring in 
CA Agile Central
 user stories to 
Clarity PPM
 as tasks. The user stories show as sub tasks to the parent portfolio item (for example, feature) tasks in 
Clarity PPM
. If the parent task has assignments, then the story tasks show at the same level as the parent task (not as sub-tasks) in 
Clarity PPM
.
 To synchronize user stories to tasks, map the lowest-level item in the Agile Central portfolio items hierarchy to a PPM task.
The following rules apply to the user story tasks:
  • The user story dates are used as the task start and finish date.
  • The user story dates come from the parent portfolio item dates.
  • If the user stories have sub stories, then the sub stories are also brought in to 
    Clarity PPM
     as tasks.
See  CA PPM Jobs Reference for details on how the Synchronize Agile Central job synchronizes user stories with tasks for each integration direction.
Synchronize Teams
If you select the Create and Sync Team option for the integration instance, 
CA Agile Central
 users who are assigned to initiatives, features, and all child components of features are brought over to 
Clarity PPM
 when the Synchronize Agile Central job runs. If the 
CA Agile Central
 users are existing 
Clarity PPM
 resources, they show up directly on the project team staff page. If the 
CA Agile Central
 users are not existing 
Clarity PPM
 resources, they appear listed on the Missing Resources portlet. The administrator can add these users as 
Clarity PPM
resources and run the Synchronize Agile Central job to make them appear on the project team staff page. Users with the same first and last names but different email IDs in 
Clarity PPM
 and 
CA Agile Central
 are listed in the Possible Matching Resources column on the Missing Resources portlet. The administrator can either create new resources for these matching resources or use the existing resources by modifying the email ID. All changes to team are reflected in 
Clarity PPM
, only after the Synchronize Agile Central job runs.
: The Missing Resources portlet does not appear by default on any application page. You can configure Overview: General page or any other page to add the Missing Resources portlet using the Manage my Tabs option. See  for more details.
Once the 
CA Agile Central
 resources are synchronized with the 
Clarity PPM
 project team, they are not removed from 
Clarity PPM
, even if the corresponding resources are removed from the corresponding 
CA Agile Central
 portfolio items or from 
CA Agile Central
.
Similarly, once the 
CA Agile Central
 features are synchronized with the 
Clarity PPM
 project task, they are not removed from 
Clarity PPM
, even if the corresponding features are removed from the corresponding 
CA Agile Central
 portfolio items.
The following diagram shows how the Synchronize Agile Central job updates the 
Clarity PPM
 project team with the latest user details from 
CA Agile Central
 in the Agile Central to PPM integration direction::
The image shows how the Synchronize Agile Central job updates CA PPM project teams with status details from Agile Central
The image shows how the Synchronize Agile Central job updates CA PPM project teams with status details from Agile Central
: If you import a linked 
Clarity PPM
 project using XOG, the project remains linked to the 
CA Agile Central
 portfolio item. To unlink the project from 
CA Agile Central
, unselect the Synchronize check box for the 
Clarity PPM
 project.
Review Integration Status for Synchronized Projects
To verify that data is successfully transferring to 
CA Agile Central
 and back to 
Clarity PPM
, review the Synchronize Agile Central job details and the 
Clarity PPM
 Background (bg) services log file. For more information about how to access the bg services log file, contact your system administrator. 
Unsuccessful integration can indicate one or more of the following issues:
  • The 
    CA Agile Central
     connection information is incorrectly defined in the 
    Clarity PPM
     Integration settings under Administration, General Settings. 
  • The Agile Integration Owner is not set up as a dedicated resource for updating integrated 
    Clarity PPM
     projects and tasks. 
  • The REST API Status is disabled. Verify that the REST API Status appears Enabled on the System Options page under Administration. Search 
    REST APIs
     for more information.
  • The 
    CA Agile Central
     server is down.
Try integrating again after entering the correct values or completing the setup, and running the Synchronize Agile Central job. 
You can also review the project integration status. Sometimes an integration error happens because a linked initiative is deleted in 
CA Agile Central
. In this case, an error message appears when you run the Synchronize Agile Central job. In the 
Clarity PPM
 project, the Synchronize check box gets unchecked and the sync status indicates a failure in the synchronization. Relink the project to a new 
CA Agile Central
 initiative to renew the connection.
: When a 
CA Agile Central
 feature is moved to a different initiative, the corresponding task in 
Clarity PPM
 project is not deleted. However, the task is no longer synchronized with 
CA Agile Central
. A new task is created in the project that now corresponds to the 
CA Agile Central
 initiative where the feature moved. The new task is created provided the project is enabled to synchronize with 
CA Agile Central
. During synchronization, this new task is updated from 
CA Agile Central
. The old task remains but never gets updated.
The following procedure describes how to review the project integration status.
 
Follow these steps
  1. Open Home, and from Portfolio Management, click Projects.
  2. Open the project, and from the Properties, click Agile Summary. 
  3. Review this information:
    •  
      Last Agile Sync Date
      Displays the last time the 
      CA Agile Central
       portfolio items were synchronized with the 
      Clarity PPM
       project.
    •  
      Last Agile Sync Status
      Displays the status of the Sync job as successful or failed. Even if the job status is successful, we recommend that you check the job logs to see if there are any warnings.
Examples: Populating Task Dates in 
Clarity PPM
 
The following examples describe how task dates in CA PPM are populated based on actual or planned dates of the portfolio items in 
CA Agile Central
.
 
Example 1
:
In this example, the 
Clarity PPM
 task start date is May 15, 2015 and the finish date is June 28,2015 based on the 
CA Agile Central
 actual start and end dates:
Start Date
End or Finish Date
 
CA Agile Central
 Actual Start and End Date
May 15, 2015
June 28, 2015
 
CA Agile Central
 Planned Start and End Date
May 10, 2015
June 25, 2015
 
Clarity PPM
 Project Start and Finish Date
March 20, 2015
August 5, 2015
 
Example 2:
 
In this example, the 
Clarity PPM
 task start date is May 15, 2015 based on the 
CA Agile Central
 actual start date. However, the task finish date is June 25, 2015 based on the 
CA Agile Central
 planned end date because the actual end date is not defined.
Start Date
End or Finish Date
 
CA Agile Central
 Actual Start and End Date
May 15, 2015
Null
 
CA Agile Central
 Planned Start and End Date
May 10, 2015
June 25, 2015
 
Clarity PPM
 Project Start and Finish Date
March 20, 2015
August 5, 2015
 
Example 3:
 
In this example, the 
Clarity PPM
 task start date is May 15, 2015 based on the 
CA Agile Central
 actual start date. The task finish date is August 5, 2015 based on the project finish date because the 
CA Agile Central
 actual and planned end dates are not defined.
Start Date
End or Finish Date
 
CA Agile Central
 Actual Start and End Date
May 15, 2015
Null
 
CA Agile Central
 Planned Start and End Date
May 10, 2015
Null
 
Clarity PPM
 Project Start and Finish Date
March 20, 2015
August 5, 2015
 
Example 4:
 
In this example, the 
Clarity PPM
 task start date is March 20, 2015 and the finish date is August 5, 2015. The task dates are based on the project start and finish dates because the 
CA Agile Central
 actual start date is later than the 
Clarity PPM
 project finish date.
Start Date
End or Finish Date
 
CA Agile Central
 Actual Start and End Date
October 15, 2015
Null
 
CA Agile Central
 Planned Start and End Date
May 10, 2015
Null
 
Clarity PPM
 Project Start and Finish Date
March 20, 2015
August 5, 2015
 
Example 5:
 
In this example, the 
Clarity PPM
 task start date is March 20, 2015 based on the project start date. The task finish date is June 28, 2015 based on the 
CA Agile Central
 actual end date.
Start Date
End or Finish Date
 
CA Agile Central
 Actual Start and End Date
Null
June 28, 2015
 
CA Agile Central
 Planned Start and End Date
Null
June 25, 2015
 
Clarity PPM
 Project Start and Finish Date
March 20, 2015
August 5, 2015
 
Example 6:
 
In this example, the 
Clarity PPM
 task start date is May 10, 2015 based on the 
CA Agile Central
 planned start date. The task finish date is June 28, 2015 based on the 
CA Agile Central
 actual end date.
Start Date
End or Finish Date
 
CA Agile Central
 Actual Start and End Date
Null
June 28, 2015
 
CA Agile Central
 Planned Start and End Date
May 10, 2015
June 25, 2015
 
Clarity PPM
 Project Start and Finish Date
March 20, 2015
August 5, 2015