Reporting Question - new Reporting API

[Cristi Mitrana]

Hello,

with the 17.4 RU4 release, a new Reporting API has been introduced, slated to replace the exiting CA BI application (TIBCO JasperSoft). I have a question regarding the new API

 Are the PdmDowntime/PdmAddDays/etc. functions that were available for dates and SLA calculatons in the previous ODBC/JDBC drivers included or planned to be included ? Withouth the Downtime related functions, it's almost impossible to calculate the correct downtime-in-SLA interval for tichets/periods of time.

[Mounika Prasad Kombathula]

Hi Cristi,

The Reporting APIs do not have support for the PDM functions at the moment, however, we are reviewing the requirement currently and shall provide an update.

Thanks.

[Cristi Mitrana]

Did you reach a decision ?

[Mounika Prasad Kombathula]

Hi Cristi,

We are considering this functionality for the next release of the reporting API, however, we do not have an ETA at this point.

Please follow our product management updates during our CA SM Office hours sessions. 

Thanks,

Mounika.

-------------------------------------------

[Peter Schmidt]

Hi Mounika,

in last CA Service Management Office Hours 10th July 2025 - Artefacts | CA Service Management  Broadcom showed what is planned for the future according CASM Reporting.

Question 1: Do you also think about including PDM functions in CASM Reporting?

Question 2: Next CASM Office Hour session on Thursday, 11th September 2025 - will Broadcom talk about REST-Reporting and additional/planned features?

Regards,

Peter

-------------------------------------------

[Richa Pathak]

Hi Peter, 

Please see my responses below:

Question 1: Do you also think about including PDM functions in CASM Reporting?

Yes, we have considered the PDM functions and it will be available in a future release. I will be able to share more details about timelines in the next Office Hour session.

Question 2: Next CASM Office Hour session on Thursday, 11th September 2025 - will Broadcom talk about REST-Reporting and additional/planned features?

We will continue to share updates/progress related to Reporting capabilities in the upcoming sessions of Office Hour so that customers are aware of what to expect in future versions. 

-------------------------------------------

[Peter Schmidt]

Hi Richa,

many thanks for your fast answer.

Regards,

Peter

-------------------------------------------

[Jakub Kolacny]

Hi Cristi,
Have you considered using spel to pre‑calculate the SLA times you need? We've been using this approach for years, and it removes any dependency on ODBC or a reporting tool. It's fast: you calculate once and store the results in the database as additional ticket attributes/tables.

With this approach we compute all management‑level metrics, for example:
- Time from ticket open to first/last resolution
- Time to first assignment
- Total time the ticket spent on hold
- Time spent in any given status / assigned group / assignee / category

Each metric is stored both as pure elapsed time and SLA or category work‑shift time.

For example, instead of PdmDownTime(slaName, workshift, startDate, endDate), you can use a similar spel function workshift_abs2work(workshift, startDate, endDate);

Regards,
Jakub

-------------------------------------------

[Chi Chen]

while this idea is a great one, you can't use the Rest Reporting API for the data stored in database. The API supports in,cr,pr,nr,chg and iss factories only.  As you pointed out, this would remove the dependency of the odbc or reporting api/tool and you would need to access the stored data using classic web interface(which, by itself, is not a graphic reporting tool).  Again, this is some great idea that will allow you to access some needed metric data.

-------------------------------------------