Portfolio Item Query Changes


Portfolio items were introduced in CA Agile Central Portfolio Manager as a new object to track initiatives and features in your organization’s portfolio. Initially, this object was implemented with a field that specified type (such as Theme, Initiative, Feature).

We are changing the way CA Agile Central references portfolio items of different types. Now you will be able to treat each type as its own object, and CA Agile Central will create dynamic typeDefs for each new type of Portfolio Item that you create.

Web Services API changes

1.37 is the earliest version of the Web Services API that will support the new references for portfolio item types.

Changes to the ordering of levels in the hierarchy

The Ordinal field is used to associate a portfolio item type with the position that a portfolio item type has in the portfolio item hierarchy. It is also used to determine the type of work item or portfolio item allowed for parents and children. The Ordinal field value starts with 0 for the lowest level of portfolio item (such as Feature), and increments by 1 for each portfolio item type as you go up in the hierarchy. This is a change from the old numbering, which started at 1.

Querying for all portfolio item types


will change to

/slm/webservice/1.37/typedefinition.js?query=((Parent.Name = "Portfolio Item") and (Creatable = true))

Querying for portfolio items with a specific portfolio item type

A user would previously have to hit the portfolioitem endpoint with one of 4 possible queries for type. These are listed below, along with how the query will change:

Basically, anything that references the Type field should change to PortfolioItemType, and any reference to type/123.js in an object ref should change to typedefinition/123.js.

However, the simplest (and preferred) way to change the query would be to just hit the endpoint for the individual type:


Querying for portfolio items with a specific Kanban state

The State field has been moved from the portfolio item typedef to the individual typedefs. Any query that looks like this will no longer work:

Users will now need to hit the endpoint for the individual type with that same query:


Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.