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. 
ccppmop152
Use the Agile add-in to integrate
CA PPM
 with
CA Agile Central
 agile development software. The integration allows an organization to maintain the operational activity in
CA Agile Central
 and use 
CA PPM
 to focus on project status. 
2
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
    CA PPM
     and 
    CA Agile Central
  • Project status information and visibility so budget, resource requirements, and deliverable status are available in
    CA PPM
Integrated projects in
CA PPM
 correspond to portfolio items (initiatives and features) in
CA Agile Central
. You can also map any contiguous
CA Agile Central
portfolio items to
CA PPM
projects or tasks.
This article uses the following examples to explain how the integration works:
  • CA PPM
    projects that are integrated with 
    CA Agile Central
    initiatives
  • CA PPM
    tasks that are integrated with 
    CA Agile Central
    features
You can synchronize agile 
CA PPM
 projects with
CA Agile Central
in the following directions:
CA Agile Central
to
CA PPM
  • The project manager links agile
    CA PPM
     projects to corresponding agile systems. Each agile system is an integration configuration to
    CA Agile Central
    .
  • CA 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
    CA PPM
     projects. 
  • The project manager has access to status information imported from the 
    CA Agile Central
    portfolio items into the corresponding
    CA PPM
     project and tasks.
CA PPM
to
CA Agile Central
  • The project manager links agile
    CA PPM
    projects to corresponding agile systems. Each agile system is an integration configuration to 
    CA Agile Central
    .
  • CA PPM
    projects are created as initiatives in
    CA Agile Central
    .
  • Selected tasks under the linked projects are created as corresponding features under the initiatives.
  • The project manager has access to status information imported from the
    CA Agile Central
    portfolio items into the corresponding 
    CA PPM
    project and tasks.
Example: Manage a CA PPM Agile Project Using
CA Agile Central
At the Documentation Management company, the product development teams use 
CA PPM
 and a separate tool to track their software development projects. As more teams embrace agile methodologies, project management receives limited insight into the team efforts. Visibility is suffering both at the program and portfolio levels. Entering time twice in two different systems is leaving developers frustrated. The difficulty in tracking business value for these agile projects is leaving the portfolio leaders frustrated.
The company decides to integrate their 
CA 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
CA PPM
 as project and task agile summaries.  
Configure the 
CA Agile Central
Integration
The following integration components allow 
CA PPM
 projects and tasks to synchronize with 
CA Agile Central
 portfolio Items:
  • Agile Summary project properties that link the 
    CA PPM
     project with 
    CA Agile Central
    .
  • Agile Summary task properties that link the 
    CA PPM
     task with 
    CA Agile Central
    .
  • An integration subpage for 
    CA Agile Central
     that allows you to configure integration options.
  • A synchronization job that runs in the background to synchronize 
    CA PPM
     projects with 
    CA Agile Central
    .
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 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 beforehand:
  • 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 
    Compatibilities
     section in the 
    Release Notes
     for more information
    .
  • 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. When applying the views any existing configurations to the following views can get overwritten:
    • Project Properties
    • Rally Policy Details
    • Task Properties
  • The REST API Status is Enabled on your system so the Rally Synchronization 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
    CA 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 
Installing and Upgrading
 to learn how to install the Agile add-in. SaaS customers must open a request with the PPM SaaS team to get the add-in installed. During installation, attributes are created in the Project and Task objects. The new attributes are protected in CA PPM Studio and you cannot enable them for the data warehouse.
Define the Integration Attributes
As a 
CA 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. By default, the 
CA Agile Central
portfolio hierarchy is configured to include only two portfolio item types, feature (P1) and initiative (P2). The portfolio item types can be at any hierarchy level and they must be contiguous. Non-contiguous portfolio items and portfolio items with spaces in their names are not supported. The default integration setup and the documentation both reflect a
CA Agile Central
portfolio hierarchy that is supported. 
 
Follow these steps
:
  1. In classic PPM, click
    Administration
    ,
    General Settings
    ,
    Integrations
    .
  2. Click
    New
    .
  3. Complete the fields on the page:
    • Integration URL
      Defines the URL for the integration instance (for example, the 
      CA Agile Central
      instance URL).
    • 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 for details.
      The Integration Instance field requires a value to create a successful integration with
      CA Agile Central
      . The Rally Synchronization job uses the value in this field to synchronize
      CA PPM
      projects with 
      CA Agile Central
      portfolio items. The job fails if a value is missing from the field.
    • Authentication Type
      • Basic: 
        Select this authentication method to integrate with 
        CA Agile Central
        On Premise. Provide a username and password to use for authentication.
      • 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 
        CA 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 
        CA 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 
        CA PPM
         to 
        CA Agile Central
        , the updates appear for the 
        CA Agile Central
         user that is associated with the 
        CA Agile Central
         API Key.  
  4. Click
    Save
    A new
    Rally
    tab appears next to
    General
    . The new tab appears only if the Agile add-in is installed.
  5. Click
    Rally
    and define the following policy details and default project and task information for 
    CA Agile Central
    :
    • Portfolio Item Type Map (Project)
      Defines the 
      CA Agile Central
       portfolio item type to which the
      CA PPM
       project maps to (for example, Initiative). You can map a
      CA 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
      CA PPM
       task maps to (for example, feature). The portfolio item type must be at a lower hierarchy level and 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
      CA 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
      CA PPM
      project team with the users who are 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
      CA 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
        CA 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
        CA 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
        CA PPM
        are reflected as corresponding portfolio items in
        CA Agile Central
        . Tasks that you create in 
        CA PPM
        are also created as child portfolio items in
        CA Agile Central
        .
        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 Rally 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.
    • Default Rally 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.
    • Open for Time Entry (Team)
      Specifies whether the team members that are synchronized from 
      CA Agile Central
       are open for time entry in
      CA PPM
      . Select one of the following options for the integration instance:
      • Yes: All the resources that are added to the 
        CA PPM
        project team from 
        CA Agile Central
         are open for time entry.
      • No: All the resources that are added to the 
        CA 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 
        CA PPM
        project team from 
        CA Agile Central
         are open for time entry.
    • Open for Time Entry (Task)
      Specifies that the tasks that are created in
      CA 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
      CA 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
      CA PPM
      .
    • Time Tracking Project Template
      Defines the default time tracking project template to use when a task is created in 
      CA PPM
      from Agile Central. When the Synchronization job runs and a new task is added to 
      CA PPM
      from
      CA Agile Central
      , the tasks in the associated template are automatically created as sub-tasks under the new task. The Time Tracking Project template includes tasks for the purpose of classifying time. The project template is not available if you select the synchronize direction as PPM to Agile Central. The system ignores the template, in case you provide one.
Set the Agile Integration Owner
Define a 
CA PPM
 user as the Agile Integration Owner that the integration uses to run the following types of operations:
  • Running the Rally Synchronization job
  • Updating the 
    CA PPM
     project and task status from
    CA Agile Central
Assign the required access rights to the Agile Integration Owner so they can update the
CA 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. Open Administration, and from Project Management, click 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)
 See for information about access rights
.
Set Up the Rally Synchronization Job
The Agile Integration Owner (or the 
CA PPM
 administrator), can set up the Rally Synchronization job to run at scheduled intervals to synchronize 
CA PPM
 projects with 
CA Agile Central
portfolio items. The project manager can also run the job manually when needed. See 
.
The job reads through the
CA PPM
 projects that have the Synchronize option selected and a value that is defined for Agile System in their agile summary. Define the following job parameters to specify the projects that you want to synchronize with
CA Agile Central
:
  • Date Window
    Defines the date window for the updated projects that you want to synchronize. For example, if you select "Projects that are updated in the last 12 months", only the projects that were updated within the last 12 months are synchronized.
  • Project Status
    Defines
     
    the status of the projects that you want to synchronize. For example, if you select "All Projects", both active and inactive projects are synchronized.
The Rally Synchronization job logs error messages in English language only.
Note
: To learn how to synchronize an existing
CA 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
.
Synchronize
CA PPM
 Projects with 
CA Agile Central
Portfolio Items
After the integration is set up with
CA Agile Central
, the project manager can start synchronizing
CA 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 
CA PPM
 projects and tasks. The project manager has visibility into the work status information in
CA Agile Central
CA Agile Central
 to
CA PPM
Direction
In the
CA Agile Central
to
CA PPM
integration direction, the Rally Synchronization job ignores the Synchronize flag at the task level. The job does not create portfolio items for tasks. Hence, you may want to hide the Synchronize flag for tasks using
CA PPM
Studio.
Follow these steps
:
  1. Log in to classic PPM.
  2. Click
    Home
    ,
    Portfolio Management
    ,
    Projects
    .
  3. Open the project that you want to synchronize to
    CA Agile Central
    .
  4. Click
    Properties
    and select
    Agile Summary
    .
  5. Complete the following information:
    • Select the Synchronize check box.
    • Select the Agile System to use for synchronizing the project with
      CA Agile Central
      .
When the Synchronization job runs, it makes the following updates in the linked systems:
  • Creates top level 
    CA Agile Central
    portfolio items (levels P2-P5) based on the information in the
    CA PPM
     project. The job creates the portfolio items provided they do not exist for the linked projects. 
  • Creates
    CA PPM
     tasks from the lower-level 
    CA Agile Central
    portfolio items (level P1) based on the information in the 
    CA Agile Central
    portfolio items. The job creates the
    CA PPM
     tasks provided they do not exist. This depends on the selection of the Create and Sync Tasks option while configuring the 
    CA Agile Central
    integration settings in
    CA PPM
    .
  • Sets the initiative/feature ID of 
    CA Agile Central
    portfolio item on the synchronized project properties on the Agile Summary subpage of
    CA PPM
    .
  • Populates agile attributes from
    CA Agile Central
    to
    CA PPM
    on the Agile Summary subpage of integrated projects and tasks.
  • Creates
    CA PPM
    subtasks underneath the lower level 
    CA Agile Central
    portfolio item. Values are preset from the Open for Time Entry, Charge Code, and Cost Type fields based on the project template that is associated with the Integration settings in 
    CA PPM
    .
  • Synchronizes 
    CA Agile Central
    projects to
    CA PPM
    project teams provided 'Create and Sync Team' option is selected while configuring the 
    CA Agile Central
    integration settings in
    CA PPM
    .
CA PPM
to
CA Agile Central
Direction
In this integration direction, the Rally Synchronization job does not create 
CA PPM
sub tasks underneath the lower-level
CA Agile Central
portfolio item. Also, the Time Tracking Project Template option is not available for this integration direction. If you provide a template, it is ignored because you can use your regular project template for tracking time.
If you create a portfolio item in 
CA Agile Central
as part of a top-level portfolio item that is synchronized to
CA PPM
, a corresponding task does not get created in
CA PPM
. Hence, the project Agile Summary attribute reflects the data as rolled up and coming from
CA Agile Central
. The metrics are not calculated in
CA PPM
and hence they do not reflect the actual work breakdown.
Follow these steps:
  1. Log in to classic PPM.
  2. Click
    Home
    ,
    Portfolio Management
    ,
    Projects
    .
  3. Open the project that you want to synchronize with 
    CA Agile Central
    .
  4. Click
    Properties
    and select
    Agile Summary
    .
  5. Complete the following information:
    • Select the Synchronize check box.
    • Select the Agile System to use for synchronizing the project with CA Agile Central.
  6. Navigate to Tasks.
  7. For each task you want to synchronize, click task properties and select Agile Summary.
  8. Select the Synchronize check box.
When the Rally Synchronization job runs, it makes the following updates in the linked systems:
  • Creates top level 
    CA Agile Central
    portfolio items (levels P2-P5) based on the information in the 
    CA PPM
    project. The job creates the portfolio items provided they do not exist for the linked projects.
  • Creates lower level 
    CA Agile Central
    portfolio items (level P1) based on the information in the 
    CA PPM
    tasks. The job creates the 
    CA PPM
    tasks provided they do not exist. A corresponding portfolio Item is created in
    CA Agile Central
    only for tasks marked as Synchronize. This also depends upon the selection of the Create and Sync Tasks option while configuring the
    CA Agile Central
    integration settings from
    CA PPM
    .
  • Sets the Initiative/Feature ID of the 
    CA Agile Central
    portfolio item on the synchronized project properties on the Agile Summary subpage of
    CA PPM
    .
  • Populates Portfolio Item Name, Planned Start Date, and Planned End Date agile attributes from 
    CA PPM
    to
    CA Agile Central
    portfolio items. At the task level, Planned Start Date and Planned End Date are based on the task start and finish dates. If these dates are modified in
    CA PPM
    , the job overwrites the Planned Start Date and Planned End Date agile attributes in 
    CA Agile Central
    .
  • Populates agile attributes from
    CA Agile Central
    to 
    CA PPM
    on the Agile Summary subpage of integrated projects and tasks. At the task level, the task ID is not overwritten by the portfolio item ID.
  • Synchronizes 
    CA Agile Central
    projects to 
    CA PPM
    project teams provided the Create and Sync Team option is selected while configuring the 
    CA Agile Central
    integration settings from
    CA PPM
    .
The following diagram shows how the Rally Synchronization job updates 
CA PPM
 projects with latest status details from
CA Agile Central
:
This diagram shows how the Rally Synchronization job updates CA PPM projects with the latest status details from CA Agile Central
This diagram shows how the Rally Synchronization job updates CA PPM projects with the latest status details from CA Agile Central
Synchronize Tasks
The following diagram shows how the Rally Synchronization job updates 
CA PPM
tasks with latest status from
CA Agile Central
in the Agile Central to PPM integration direction:
This diagram shows how the Rally Synchronization job updates CA PPM with task details from CA Agile Central
This diagram shows how the Rally Synchronization job updates CA PPM with task details from CA Agile Central
The
CA 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
CA 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 
CA PPM
project start and finish dates are used to define the 
CA PPM
task start and finish dates.
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 
CA PPM
when the Rally Synchronization job runs. If the 
CA Agile Central
users are existing 
CA PPM
resources, they show up directly on the project team staff page. If the 
CA Agile Central
users are not existing 
CA PPM
resources, they appear listed on the Missing Resources portlet. The administrator can add these users as 
CA PPM
 resources and run the Rally Synchronization job to make them appear on the project team staff page. Users with the same first and last names but different email IDs in 
CA PPM
and 
CA Agile Central
are listed in the Possible Matching Resources column on the Missing Resources portlet. The administrator can either create resources for these matching resources or use the existing resources by modifying the email ID. All changes to team are reflected in
CA PPM
, only after the Rally synchronization 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
CA PPM
project team, they are not removed from
CA 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 
CA PPM
 project task, they are not removed from 
CA PPM
, even if the corresponding features are removed from the corresponding 
CA Agile Central
portfolio items.
The following diagram shows how the Rally Synchronization job updates the
CA PPM
project team with the latest user details from
CA Agile Central
:
This diagram shows how the Rally Synchronization job updates CA PPM project teams with status details from CA Agile Central
This diagram shows how the Rally Synchronization job updates CA PPM project teams with status details from CA Agile Central
: If you import a linked 
CA 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
CA PPM
project.
Review Integration Status for Synchronized Projects
To verify that data is successfully transferring to 
CA Agile Central
and back to 
CA PPM
, review the Rally Synchronization job details and the 
CA 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
    CA PPM
     Integration settings under Administration, General Settings. 
  • The Agile Integration Owner is not set up as a dedicated resource for updating integrated 
    CA 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 Rally Synchronization 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 Rally Synchronization job. In the
CA 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 
CA 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 
      CA 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
CA 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
CA 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
CA PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 2:
In this example, the
CA 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
CA PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 3:
In this example, the
CA 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
CA PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 4:
In this example, the
CA 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
CA 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
CA PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 5:
In this example, the 
CA 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
CA PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015
Example 6:
In this example, the 
CA 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
CA PPM
Project Start and Finish Date
March 20, 2015
August 5, 2015