Hi Marco,
I have checked this internally and below is is the official response:
"BOXI (CABI 4.1 SP3, 4.1.5) is no longer supported. The support was only till December 31st, 2018. Here is the screenshot of the note that is put up on the supportability matrix page.
Having said that, the matrix also should get updated to reflect the same. We will work on this to reflect the same on the portal."
------------------------------
===
Kind Regards,
Brian
------------------------------
Original Message:
Sent: 07-10-2019 10:18 AM
From: Marco Antonio Velazquez Aldama
Subject: Custom fields in CABI
Hi Brian
I comment you, that We are already working with integration of CA SDM with Jasper.
But because we still have reports in CABI, this inconsistency is an impact.
regards,
Marco Velazquez
------------------------------
ITSM Consultant
Dayset
Original Message:
Sent: 07-10-2019 08:21 AM
From: Brian Mathato
Subject: Custom fields in CABI
Hi Marco,
Much as we would like to assist you, checking the Supportability Matrix it does not look like CABI 4.1 is supported for r17.1. See below link:
r17.1 Supportability Matrix - Common Components
Any reason you are going full steam with this unsupported configuration, instead of using JasperReports?
------------------------------
===
Kind Regards,
Brian
Original Message:
Sent: 07-09-2019 12:15 PM
From: Marco Antonio Velazquez Aldama
Subject: Custom fields in CABI
Hi,
Currently, I am working with the CA Service Desk 17.1 and CABI 4.1 SP 5 Integration.
The Integration is working without problem. But I noticed a inconsistency in a new field "field z".
When run the report, The data is mixed, with other tenant using the same custom field
I attached information and screens in the attached document.
Regards,
Marco Velazquez
------------------------------
Regards,
Marco Velazquez
------------------------------