| 57216 |
Support for creating custom aggregations via tags has been added. Previously, users could create tags for objects but were unable to use those tags to build custom views with grouped nodes. With this fix, it is now possible to create custom views that aggregate objects based on their associated tags (e.g., grouping objects under nodes like TG_TABLES or TG_VIEWS). |
| 57254 |
An issue was identified where source file paths were truncated when retrieving object details using object tools, particularly for cases involving long file paths. This has been resolved, and full source file paths are now returned without truncation. |
| 57324 |
An issue was identified where the objects endpoint did not differentiate between standard COBOL Programs and COBOL Transactional Programs, returning all such objects under a single type ("Cobol Program"). This also prevented accurate filtering for transactional programs, despite their distinction in the architectural graph. This has been enhanced by introducing support for multiple filtering operators, including equals, starts with, and ends with, in addition to the default contains operator, enabling more precise and flexible queries. |
| 57236 |
An issue was identified where callers and callees of an object were partially returned due to a pagination limitation, restricting results to the first 100 entries. This led to incomplete dependency information when using MCP tools, even though the full dataset was available via the API. This has been fixed by improving pagination handling, ensuring that all callers and callees are now fully retrieved without truncation. |
| 56956 |
A discrepancy was observed between the transaction counts returned by MCP and those displayed in Imaging. This was due to the Imaging APIs service counting only transactions that have both a start point and an end point, while the UI displays all transactions, including those without endpoints. This difference in logic led to mismatched counts. A fix has been introduced to align the API behavior with the UI by including all transactions in the count, ensuring consistency across both. |
| 57276 |
An issue was identified where relationships between nodes could not be extracted for static custom views when using MCP tools, resulting in incomplete or missing data when querying such views. This has been resolved, and MCP now correctly retrieves and returns the relationships between nodes within static custom views, enabling accurate analysis and reporting. |
| 57421 |
An issue was identified where quality insights retrieved via the MCP tool application_quality_insights were truncated, returning only a subset of results (e.g., 20 patterns out of 50) due to limitations in nested pagination handling. This has been resolved by improving the nested pagination logic, ensuring that all available quality insight patterns are now fully retrieved and returned in the response. |