A project decides once in the hub how it handles reports: whether final documents are kept, for how long, which formats exist and who approves templates. The build turns this into the configuration of CRMS. What differs per environment or is secret comes from environment variables. The data lives in the same database layer that CDMS uses.
Subject area
Set up and operate
The CRMS module of a project in the hub and its options, the environment variables, the database and, as an example, the reports of the hub.
Topics in this subject area
- 1.The CRMS module in the hub
What a project sets in the CRMS module, how the runtime decides the placement, and what each field does to the build and the environment.
- 2.Environment variables
Which variables CRMS reads, where a value comes from and which variables are required when: embedded, as a client and as a separate service.
- 3.The database
CRMS uses the same database layer as CDMS: the same variables, the same routing to system and tenant database, the schema from the entities, and tables that are only appended to.
- 4.Example: the reports of the hub
How the hub produces its project documents arc42, privacy and runbook through an embedded CRMS: shipped templates, TRANSIENT, an SVG diagram, PDF and DOCX.