9 docs tagged with "reporting"

AI Assistant routes each conversation to an agent (domain). The Generic Agent and Reporting Agent are selectable. Task troubleshooting is launched from a failed task.

Release stores completed releases and reporting metadata in a separate archive database. For more information about the archiving process, see How archiving works.

See Configure Release and Trigger Settings.

This topic explains how to create a JDBC export hook in Release, allowing you to export data from the release system to a JDBC-compliant database. For more information, see Release export hooks.

You can use the export hook feature to configure Release to run a Jython script for every release that is about to be archived.

Navigate Digital.ai Release as an Engineering Manager and learn about monitoring delivery progress through dashboards, reports, and portfolio views.

Archiving in Digital.ai Release is a two-stage process that manages completed and aborted releases:

This topic covers the setup of a production environment in Digital.ai Release using an external clustered database for operational and archived data. It also includes configuring PostgreSQL in a hot-standby setup for high availability with standby servers ready to take over if the primary server fails.

The AI Assistant Reporting Agent answers data questions in natural language with charts and tables, and can add results to a custom dashboard.