Integrate CA PPM with CA Agile Central (Rally)

Use the Agile add-in to integrate cappm with rally (formerly Rally) agile development software. The integration allows an organization to maintain the operational activity in rally and use cappm to focus on project status. Project data is integrated between the two systems based on an integration object and attributes. The integration also includes a background job to synchronize project level settings.
ccppmop151
Use the Agile add-in to integrate
CA PPM
 with
CA Agile Central
 (formerly Rally) 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. Project data is integrated between the two systems based on an integration object and attributes. The integration also includes a background job to synchronize project level settings.
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
When you integrate with
CA Agile Central
, projects in
CA PPM
 correspond to Portfolio Items in
CA Agile Central
. Out-of-the-box, you can integrate 
CA 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. Agile 
CA PPM
 projects are synchronized with
CA Agile Central
 as follows:
  • The project manager links agile
    CA PPM
     projects to corresponding 
    CA Agile Central
    Portfolio Items.
  • Features under the 
    CA Agile Central
    Initiatives create corresponding tasks under the linked
    CA PPM
     projects. 
  • The project manager imports status information from the 
    CA Agile Central
    Portfolio Items to the corresponding
    CA PPM
     project and tasks. 
Example: Manage an Agile
CA PPM
 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.  
 On Premise customers can see 
Installing and Upgrading
 to learn how to install the Agile add-in.
Configure the 
CA Agile Central
Integration
The following custom integration attributes allow 
CA PPM
 projects and tasks to synchronize with 
CA Agile Central
 Portfolio Items.
 
  • A synchronization job that runs in the background to synchronize 
    CA PPM
     projects with 
    CA Agile Central
    .
  • 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
     and lookup menus that allow you to select integration values.
As an 
CA 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 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
    Agile add-in content is installed successfully . On the Agile Addin items list page, verify that all the listed items display the
     
    Installed
     
    status.
  • The REST API Status is enabled on your system so the Rally Synchronization job can run. 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.
Define the Integration Attributes
As an 
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. Out-of-the-box, the 
CA Agile Central
portfolio hierarchy is configured to include only two Portfolio Items, Feature (P1) and Initiative (P2). The default integration setup with 
CA Agile Central
and the documentation both reflect the out-of-the box configuration of the 
CA Agile Central
portfolio hierarchy. 
 
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).
    • Integration Instance
      Defines the integration instance to connect to such as a 
      CA Agile Central
      workspace ID.
      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.
      To obtain the workspace ID, complete the following steps:
      1. Log in to the 
        CA Agile Central
        workspace (for example, rally1.rallydev.com) with your credentials.
      2. Access the following URL:
        https://
        rally1.rallydev.com
        /slm/webservice/v2.0/workspace
        A JSON response appears.
      3. Copy the _refObjectUUID from the JSON response and use it as the workspace ID.
        The following code shows a sample JSON response with the workspace ID bolded.
        {    "QueryResult": {        "_rallyAPIMajor": "2",        "_rallyAPIMinor": "0",        "Errors": [],        "Warnings": [],        "TotalResultCount": 1,        "StartIndex": 1,        "PageSize": 20,        "Results": [            {                "_rallyAPIMajor": "2",                "_rallyAPIMinor": "0",                "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/workspace/40681926241",                "_refObjectUUID": "
        6e99c9d5-95ff-4046-9155-e7384d6f353a
        ",                "_refObjectName": "ITC Development",                "_type": "Workspace"            }        ]    }
    • Authentication Type
      • Basic
        Select this authentication method to integrate with 
        CA Agile Central
        On Premise. Provide an 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
        l 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
    CA Agile Central
    Rally 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
      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 the lowest level (P1) in the  
      CA Agile Central
       portfolio hierarchy. 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 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.
    • Default Rally Owner ID
      Defines the default owner ID to use when a Portfolio Item (for example, Initiative) is created in  
      CA Agile Central
      . To obtain the value for this field, complete the following steps:
      1. Log in to the  
        CA Agile Central
         workspace (for example, rally1.rallydev.com) with your credentials.
      2. Access the following URL:
        https://rally1.rallydev.com/slm/webservice/v2.0/workspace
        A JSON response similar to the following appears:
        {    "QueryResult": {        "_rallyAPIMajor": "2",        "_rallyAPIMinor": "0",        "Errors": [],        "Warnings": [],        "TotalResultCount": 1,        "StartIndex": 1,        "PageSize": 20,        "Results": [            {                "_rallyAPIMajor": "2",                "_rallyAPIMinor": "0",                "_ref": "
        https://rally1.rallydev.com/slm/webservice/v2.0/workspace/40681926241
        ",                "_refObjectUUID": "6e99c9d5-95ff-4046-9155-e7384d6f353a",                "_refObjectName": "ITC Development",                "_type": "Workspace"            }        ]    }
      3. Open a separate browser tab and copy and paste the following URL from the JSON response:
        https://
        rally1.rallydev.com
        /slm/webservice/v2.0/workspace/40681926241
        After accessing the URL, you get the default Rally owner ID in a JSON response. The following code shows a sample JSON response with the owner ID bolded:
        {  "Workspace": {    "_rallyAPIMajor": "2",    "_rallyAPIMinor": "0",    "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/workspace/40681926241",    "_refObjectUUID": "6e99c9d5-95ff-4046-9155-e7384d6f353a",    "_objectVersion": "3",    "_refObjectName": "ITC Development",    "CreationDate": "2015-08-06T15:57:42.093Z",…..……      "_type": "Subscription"    },    "Children": {      "_rallyAPIMajor": "2",      "_rallyAPIMinor": "0",      "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Workspace/40681926241/Children",      "_type": "Project",      "Count": 5    },    "Description": "Sandbox workspace for ITC development to play around with to better understand Rally and the integration with PPM",    "Name": "ITC Development",    "Notes": "",    "
        Owner
        ": {      "_rallyAPIMajor": "2",      "_rallyAPIMinor": "0",      "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/user/42778241050",      "_refObjectUUID": "
        f8d849a9-1691-44ef-bc90-5fadb8392709
        ",      "_refObjectName": "ITC Admin Portfolio Manager",          "_type": "User"    },    "Projects": {      "_rallyAPIMajor": "2",      "_rallyAPIMinor": "0",      "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Workspace/40681926241/Projects",      "_type": "Project",      "Count": 15    },….….    },    "WorkspaceConfiguration": {      "_rallyAPIMajor": "2",      "_rallyAPIMinor": "0",      "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/workspaceconfiguration/40681926241",      "_refObjectUUID": "dca55e6e-5db2-49a0-aaf3-4409391270b6",      "_type": "WorkspaceConfiguration"    },    "Errors": [],    "Warnings": []  }}
    • 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
      . To obtain the value for this field, complete the following steps: 
      1. Log in to the  
        CA Agile Central
         workspace (for example, rally1.rallydev.com) with your credentials.
      2. Obtain the  
        CA Agile Central
         workspace ID. See the description for the
        Integration Instance
        field for details.
         
      3. Access the following URL using the workspace ID value you obtained in Step 2: 
        https://
        rally1.rallydev.com
        /slm/webservice/v2.0/workspace/
        <workspace id>
        /projects
        A JSON response appears containing workspace projects.
      4. Use the project UUID as the default Project ID of the  
        CA Agile Central
         integration instance. The following code shows a sample JSON response with the project ID bolded:
        {  "QueryResult": {    "_rallyAPIMajor": "2",    "_rallyAPIMinor": "0",    "Errors": [],    "Warnings": [],    "TotalResultCount": 15,    "StartIndex": 1,    "PageSize": 20,    "Results": [      {        "_rallyAPIMajor": "2",        "_rallyAPIMinor": "0",        "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/project/40681926325",        "_refObjectUUID": "c6f9155c-ee45-4fa7-b82f-c04399437c13",        "_objectVersion": "2",        "_refObjectName": "Sample Project",        "CreationDate": "2015-08-06T15:57:42.135Z",        "_CreatedAt": "Aug 6, 2015",        "ObjectID": 40681926325,        "ObjectUUID": "c6f9155c-ee45-4fa7-b82f-c04399437c13",        "VersionId": "2",        "Subscription": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/subscription/32868941812",          "_refObjectUUID": "fc3c31fd-4761-401c-9851-d825709e6ec6",          "_refObjectName": "Tech Partner - CA Technologies",          "_type": "Subscription"        },        "BuildDefinitions": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Project/40681926325/BuildDefinitions",          "_type": "BuildDefinition",          "Count": 1        },        "Children": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Project/40681926325/Children",          "_type": "Project",          "Count": 0        },        "Description": "",        "Editors": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Project/40681926325/Editors",          "_type": "User",          "Count": 5        },        "Iterations": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Project/40681926325/Iterations",          "_type": "Iteration",          "Count": 1        },        "Name": "Sample Project",        "Notes": "",        "Owner": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/user/34854539788",          "_refObjectUUID": "65bd754e-42b0-45fe-93ce-3359060a5f76",          "_refObjectName": "team-ppm-rad-admin",          "_type": "User"        },        "Parent": null,        "Releases": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Project/40681926325/Releases",          "_type": "Release",          "Count": 0        },        "RevisionHistory": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/revisionhistory/40681926326",          "_refObjectUUID": "29e6f0b0-5b5f-49cf-b89e-b6a816fc324c",          "_type": "RevisionHistory"        },        "SchemaVersion": "093898709ed1969ccd44bf5b936e9c5b",        "State": "Open",        "TeamMembers": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/Project/40681926325/TeamMembers",          "_type": "User",          "Count": 1        },        "Workspace": {          "_rallyAPIMajor": "2",          "_rallyAPIMinor": "0",          "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/workspace/40681926241",          "_refObjectUUID": "6e99c9d5-95ff-4046-9155-e7384d6f353a",          "_refObjectName": "ITC Development",          "_type": "Workspace"        },        "_type": "Project"      },      {        "_rallyAPIMajor": "2",        "_rallyAPIMinor": "0",        "_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/project/42778749224",        "_refObjectUUID": "ca3ca519-49b5-421b-a08d-e2532227bed1",        "_objectVersion": "49",        "_refObjectName": "
        Learn Rally
        ",        "CreationDate": "2015-09-10T17:13:30.964Z",        "_CreatedAt": "Sep 10, 2015",        "ObjectID": 42778749224,        "ObjectUUID": "
        ca3ca519-49b5-421b-a08d-e2532227bed1
        ",        ......      },…………..…………..     ]  }}
       
    • Create and Sync Team
      Specifies whether to synchronize the
      CA PPM
      project team with the users assigned to  
      CA Agile Central
       Initiatives, Features, and all the child components of Features. By default, the option is selected and team members are synchronized whenever the synchronization job runs.
    • 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.
    • 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
      .
    • Open for Time Entry (Task)
      Specifies that the tasks 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. 
Configure Multiple 
CA PPM
Integration Records
To control what default  
CA Agile Central
 owner and project values are assigned when  
CA Agile Central
 Initiatives are created, configure and maintain multiple
CA PPM
 integration records. You can configure multiple 
CA PPM
 Integration records either for the same  
CA Agile Central
 Workspace or different workspaces. However, you can map a 
CA PPM
 project to only a single  
CA Agile Central
 workspace or instance. 
 To synchronize a
CA PPM
 project with a  
CA Agile Central
 Portfolio Item, you select the appropriate integration record in the Agile System field of the project. After synchronization, a  
CA Agile Central
 Initiative is created for the
CA PPM
 project. The new initiative is populated using the following default values that you defined in the
CA PPM
 integration record:
  • Rally Owner ID
  • Rally Project ID  
Link a 
CA PPM
Project to a  
CA Agile Central
 Portfolio Item 
To link an existing
CA PPM
 project to an existing  
CA Agile Central
 Portfolio Item, update the project Agile External ID attribute with the  
CA Agile Central
 Portfolio Item object ID. The Agile External ID attribute is used internally to link 
CA PPM
 projects to 
CA Agile Central
Portfolio Items. As an administrator, update the custom information element in the Project XOG schema with the following information:
  • The object ID of the 
    CA Agile Central
    Portfolio Item with which the project is synchronizing.
  • The 
    CA Agile Central
    Portfolio Item with which the project is synchronizing (for example, Initiative or Feature).
  • The ID for the 
    CA Agile Central
    integration instance.
  • The option to initiate the synchronization with
    CA Agile Central
    .
 See the following example:
<CustomInformation> <ColumnValue name="agl_ext_id">39345976308</ColumnValue> <ColumnValue name="agl_id">I1</ColumnValue> <ColumnValue name="agl_system">rally1</ColumnValue> <ColumnValue name="agl_sync">true</ColumnValue></CustomInformation>
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
.
Connect Projects to
CA Agile Central
As a 
CA PPM
project manager, complete the following high-level steps to synchronize agile
CA PPM
 projects with 
CA Agile Central
Portfolio Items:
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
Set up the
CA PPM
 Project for Synchronization with
CA Agile Central
Set up a
CA PPM
 project to synchronize with 
CA Agile Central
so Initiative and Feature status information can flow back to the project. 
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.
    • Select the Agile System to use for synchronizing the project with
      CA Agile Central
      .
Run 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 as and when needed. See for more information
.
The job reads through the
CA PPM
 projects that have the Synchronize option selected and a value 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 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 job runs to make 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 already exist for the linked projects. This depends upon the selection of 'Create and Sync Tasks' option while configuring the 
    CA Agile Central
    integration administration settings from
    CA PPM
    .
  • Creates
    CA PPM
     tasks from the lowest 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 already exist.
  • Sets the Initiative/Feature ID of 
    CA Agile Central
    portfolio item on the synchronized project properties on the Agile Summary subpage of
    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 administration settings from
    CA PPM
    .
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
.
The following 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 status details from CA Agile Central
This diagram shows how the Rally Synchronization job updates CA PPM projects with status details from CA Agile Central
The following diagram shows how the Rally Synchronization job updates 
CA PPM
tasks with latest status details from
CA Agile Central
:
This diagram shows how the Rally Synchronization job updates CA PPM task details from CA Agile Central
This diagram shows how the Rally Synchronization job updates CA PPM task details from CA Agile Central
The following diagram shows how the Rally Synchronization job updates the
CA PPM
project team with 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.
CA PPM
 and 
CA Agile Central
Attribute Mapping
When you create a new 
CA Agile Central
Portfolio Item from a
CA PPM
 project, the following information is populated from
CA PPM
:
  • Portfolio Item Name (based on the
    CA PPM
     project name)
  • Planned Start/End dates (based on the
    CA PPM
     Project Start/Finish dates)
  • Owner ID: This 
    CA Agile Central
    field is populated based on the Default Rally Owner ID value from the integration instance that is specified on the
    CA PPM
     project, Agile System field. Leaving Default Rally Owner ID field blank while configuring 
    CA Agile Central
    Integration Instance from 
    CA PPM
     would result in the blank Owner ID for the corresponding Portfolio item present in
    CA Agile Central
    .
  • Project: This 
    CA Agile Central
    field is populated based on the Default Rally Project ID value from the integration instance that is specified on the 
    CA PPM
     project, Agile System field)
    If the Default Rally Project ID field is left blank while configuring 
    CA Agile Central
    Integration Instance from 
    CA PPM
     then the Project field of corresponding Portfolio item present in 
    CA Agile Central
    will be set to the first project ( in the alphabetical order of the projects) of the workspace.
Once the 
CA Agile Central
Portfolio Item is created, you can change these values in
CA Agile Central
. When the Rally Synchronization job runs next, it does not overwrite the recently updated values except for the Portfolio Item Name.
The job keeps the 
CA Agile Central
Portfolio Item Name synchronized with the
CA PPM
 project name.
Scrum teams can define Features, User Stories, and Tasks under the 
CA Agile Central
Portfolio Item. When you next synchronize with
CA Agile Central
, the status details from the 
CA Agile Central
Portfolio Item are updated in the corresponding
CA PPM
 project. The 
CA Agile Central
Feature details are brought over as
CA PPM
 tasks. The following
CA PPM
 task fields are populated with default values based on the specified Agile System (integration record):
  • Cost Type
  • Charge Code
  • Open for Time Entry
At any time during the agile project lifecycle, you can synchronize the 
CA PPM
 projects and tasks with status details from
CA Agile Central
. Alternatively, the 
CA PPM
 administrator can set up the Synchronize job to run at scheduled intervals. 
See the 
CA Agile Central
documentation
for information about Initiatives, Features, User Stories, or Tasks. 
The following table lists the 
CA Agile Central
Initiative attributes that are synchronized back to the 
CA PPM
 project agile summary. Not all status attributes from 
CA Agile Central
are synchronized back to the project. See the
 
CA Agile Central
documentation
for descriptions of the 
CA Agile Central
attributes.
CA Agile Central
 Attribute (Initiative)
CA PPM
Project Attribute
State
Agile State
Preliminary Estimate
Preliminary Estimate
% Done By Plan Estimate
% Done By Agile Plan Estimate
% Done By Story Count
% Done By Story Count
Value Score
Agile Value Score
Risk Score
Agile Risk Score
WSJF Score
WSJF Score (SAFE scoring attribute)
Actual Start Date
Agile Actual Start
Actual End Date
Agile Actual Finish
No specific field. The value is dynamically calculated based on user story status and rolled up to the
CA PPM
project.
Estimated Story Points
No specific field. The value is dynamically calculated based on user story status and rolled up to the
CA PPM
project.
Estimated User Stories
No specific field. The value is dynamically calculated based on user story status and rolled up to the
CA PPM
project.
Accepted User Stories
No specific field. The value is dynamically calculated based on user story status and rolled up to the
CA PPM
project.
Accepted Story Points
The following table lists the 
CA Agile Central
Feature attributes that are synchronized back to the 
CA PPM
 task agile summary. Not all status attributes from 
CA Agile Central
are synchronized back to the task. See the
 
CA Agile Central
documentation
 for descriptions of the 
CA Agile Central
attributes.
CA Agile Central
 Attribute (Feature)
CA PPM
Task Attribute
Name
Task Name
ID (feature)
Feature ID
State
Agile State
Preliminary Estimate
Agile Preliminary Estimate
Risk Score
Agile Risk Score
Value Score
Agile Value Score
WSJF Score
WSJF Score (SAFe scoring attribute)
Planned Start Date
Agile Planned Start
Planned End Date
Agile Planned Finish
Actual Start Date
Agile Actual Start
Actual End Date
Agile Actual Finish
Total Story Points
Estimated Story Points
Accepted Leaf Story Points
Accepted Story Points
% Done by Plan Estimate
% Done by Agile Plan Estimate
Total User Stories
Estimated User Stories
Accepted Leaf Story Estimate
Accepted User Stories
% Done by Story Count
% Done by Story Count
Populating Task Dates in 
CA PPM
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.
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
Synchronizing Team Members from 
CA Agile Central
to
CA PPM
If you select the Create and Sync Team option for the integration instance, 
CA Agile Central
users assigned to Initiatives, Features, and all child components of Features are brought over to 
CA PPM
when 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 new 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.
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 subpage 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 API Attribute ID value has changed for project attributes. The API Attribute ID field can be edited for the attributes that the Agile add-in adds to the Project object. If you change the default API Attribute ID value for these attributes, the Rally Synchronization job does not work properly.
  • 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 in 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.