-
Notifications
You must be signed in to change notification settings - Fork 2
CHES and Notifications
The Forests Client Management System uses the BC Government's Common Hosted Email Service (CHES) to dispatch transactional emails to applicants and ministry staff.
CHES is an enterprise microservice provided by the BC Ministry of Citizens' Services that provides reliable, rate-limited, and audited email delivery over standard REST endpoints.
CHES endpoints require OAuth 2.0 Client Credentials authentication against a dedicated Keycloak realm. Configure connection details in your YAML profile:
ca:
bc:
gov:
nrs:
ches:
uri: ${CHES_API_URL:https://ches-dev.api.gov.bc.ca/api/v1}
tokenUrl: ${CHES_TOKEN_URL:https://loginproxy.gov.bc.ca/auth/realms/standard/protocol/openid-connect/token}
clientId: ${CHES_CLIENT_ID:your-ches-client-id}
clientSecret: ${CHES_CLIENT_SECRET:your-ches-secret}
scope: openidEmails are triggered at critical lifecycle milestones throughout the submission process:
-
Submission Received:
- Sent to: External Applicant (BCeID or BCSC).
- Content: Acknowledges receipt of application and provides reference tracking number.
-
Staff Review Alert:
- Sent to: Ministry Administrator Distribution List.
- Triggered by: Processor Channel #5 when potential duplicate matches require manual adjudication.
-
Application Approved:
- Sent to: External Applicant.
- Content: Confirms approval and delivers the official 8-digit Forest Client Number.
-
Application Rejected:
- Sent to: External Applicant.
- Content: Informs applicant of rejection, detailing reviewer notes and next steps.
For complete HTML and text template formatting specifications, refer to Mail Format Templates.
This wiki serves as the central documentation and knowledge base for the Forests Client Management System, maintained by the British Columbia Ministry of Forests.
Please Note:
- This wiki is a living document maintained by the development team and contributors.
- When making substantial architectural or code changes, remember to update the corresponding wiki documentation.
- Always verify critical environment configurations against team vaults and OpenShift secret managers.
Have questions, found a documentation discrepancy, or need clarification?
- Questions or Bug Reports: Open an issue in the GitHub repository
- Pull Requests: Submit code or doc improvements via Pull Requests
- Database Schema Reference: Explore our SchemaSpy ER Diagrams
Forest Client Wiki | GitHub Repository
- Architecture Overview
- Frontend Architecture
- Frontend Structure
- Backend Architecture
- Backend Structure
- Legacy Architecture
- Processor Architecture
- Data Model
- Development Overview
- Local Setup & Docker
- Frontend Setup
- Backend Setup
- Project Conventions
- Frontend Structure Guidelines