Customizing PCR360

Customizing PCR360 Application Settings

PCR360 application settings (branding, billing, GLA, E911, Crystal Reports, etc.) are controlled through a custom ini file that you manage. Changes to this file take effect after restarting the web service.

Where the File Lives

Environment	File
Production	`config/prod-custom.ini`
Test	`config/test-custom.ini`

These files live in your PCR360 installation directory (typically /opt/pcr360).

How the File Gets Created

If you installed PCR360 by importing an existing bare-metal installation, config/prod-custom.ini was generated automatically during the deploy process — your settings from the old install were imported into it. You can edit it at any time to make further changes.

If you did a fresh install, the file does not exist yet. Create it from the example:

Bash

cd /opt/pcr360
sudo cp config/prod-custom.ini.example config/prod-custom.ini

Editing the File

Bash

cd /opt/pcr360
sudo vi config/prod-custom.ini

The file uses standard ini key-value syntax. Do not include section headers like [pcrprod] — the installer adds those automatically.

; Example entries
constants.CUSTOMER_NAME = "Your Organization"
theme.REPORT_HEADER_ALT = "Your Org PCR-360"
constants.CREATE_GLA_INVOICE_NUMBERS = true

For a full list of available settings with examples, see config/prod-custom.ini.example.

What Belongs Here

Any application-level setting from your original pcr360.ini belongs in this file — except the settings that Docker manages automatically:

Encryption keys and license key
Email transport, host, and port
Database connection details
File paths (import, export, PDF converter)
AI service configuration (python360, compose360)
MongoDB connection

Those are set in .env and should not be duplicated here. Everything else — branding, billing, GLA format, E911, Crystal Reports JDBC, auth settings — goes in prod-custom.ini.

Applying Changes

Changes require a restart of the web container:

Bash

cd /opt/pcr360
sudo docker compose restart web-prod

For the test environment:

Bash

sudo docker compose restart web-test

The container re-reads prod-custom.ini at startup. Allow 30–60 seconds for it to become healthy before testing your changes.

To confirm the container restarted cleanly:

Bash

docker compose ps   # web-prod should show "healthy"

Common Settings

Branding

constants.CUSTOMER_NAME = "Your Org"
theme.REPORT_HEADER_IMG = "/media/images/print/YourLogo.png"
theme.REPORT_HEADER_ALT = "Your Org PCR-360"
theme.REPORT_HEADER_LINK_WIDTH = "450px"

Email display name

email.DISPLAY_NAME = "ITS Billing"
constants.ERROR_REPORT_EMAIL = "pcr360-errors@yourorg.edu"

GLA / Billing

constants.CREATE_GLA_INVOICE_NUMBERS = true
constants.GLA_FORMAT_DEFAULT = "WORKDAY"
constants.GLA_TYPE = "COMPONENT"
constants.GLA_PRICING_MODEL = "billing_group"

E911

constants.USE_E911_NENA2_FIELDS = true
constants.DEFAULT_STATE = "VA"

Crystal Reports JDBC

crystal.jdbc.type = mysql
crystal.jdbc.host = your-db-host
crystal.jdbc.username = pcr360
crystal.jdbc.password = 'your-password'
crystal.jdbc.dbname = pcr360_yourorg
crystal.jdbc.port = "3306"

For a complete reference of all available settings, contact PCR360 support or refer to your original pcr360.ini from a bare-metal installation.