Deploying Ad Hoc Reports into Another Environment

If your agency wants to create ad hoc reports in a staging environment and then move them to a production environment for use, follow the process described below. Note that the process assumes that you already created the ad hoc report before moving it. For information about creating an ad hoc report, see “Designing a New Report” in the Ad Hoc Reporting chapter of the Accela Civic Platform User Guide.

Note:

To deploy ad hoc reports from one environment to another, you must use a 3rd party database application to access to both the source database and the target database. Civic Platform does not provide the ability to work with databases.

  1. Use a database application such as MS-SQL or Oracle, to access the source database.

    • In the RADHOC_REPORTS table, locate the XML for the ad hoc report you are migrating to production and copy the XML contents for the report.

  2. Access the target database.

    • Add a new row to the RADHOC_REPORTS table, and enter a group and name for the report.

    • Paste the XML contents you copied from the source database into the target database.

    • Locate and change the serv_prov_code in this table (serv_prov_code=TENANTID) so it shows the current agency serv_prov_code.

  3. Open Civic Platform and navigate to Report Manager.

    • Set permissions as needed for the DB_views used in the report you just moved.

    • If you want to associate a report with a portlet or report list for users to access by clicking a button, add the report in Report Manager, associate it with the portlet or report list portlet, and set appropriate permissions.

    For more information, see the Report Manager chapter of the Accela Civic Platform Administrator Guide.