4.2.5 Set up application settings
Last updated
Last updated
The next step is to configure some functional application settings. Some of these settings can be changed later using the OpenCRVS Functional Configuration UI by a National System Administrator. Others must be configured now during installation and cannot be changed in production.
You will be referring to the Config: Application Settings Excel sheet that would have been prepared in section 2: Gather requirements.
Prepare your application-config-default.ts source file. This is a Typescript file that is loaded in the application via an API explained in section 3.2.9 Countryconfig APIs explained.
Using our application-config-default.ts file as an example, update the settings according to your needs.
The OpenCRVS Core Login application loads the following config js files before connecting to the OpenCRVS backend to serve all the content. The Login app has not communicated with the backend yet and needs to know how to access it
Login app - localhost development: login-config.js
As you can see, the React Login application uses the URL values to understand how to connect to backend services such as the login authentication API and the country configuration API. Do not edit the URLs.
You must set some values:
COUNTRY: Set the Alpha 3 country code to be the same as the value you used when importing the set up files in step 3.2.5. The Login app needs to convert users phone numbers into MSISDN numbers using an Alpha 3 country code in case the user forgets their login details and requires an SMS reset.
LANGUAGES: This property allows you to customise the global language options. This value is a comma separated string of ISO 639-1 language codes for every translation you wish to set up in step 3.2.5.1 Managing language content.
For example, if you wanted to support Spanish and English, with Spanish being the default this string should be:
Login app - server: login-config.prod.js
As you can see, the server config file contains the same settings.
You may notice that localhost is replaced by your domain name dynamically in handlebars. Do not edit the URLs. We have taken care of this substitution for you in step 3.3.5 Deploy
You must set the COUNTRY & LANGUAGES values only.
Client app - localhost development: client-config.js
Following the same process as you did for the local development Login app config file, you must set the COUNTRY & LANGUAGES values, and can optionally uncomment LEADERBOARDS_DASHBOARD_URL, REGISTRATIONS_DASHBOARD_URL and STATISTICS_DASHBOARD_URL if you wish to run metabase dashboards locally. Refer to this step for more instructions.
Client app - server: client-config.prod.js
Following the same process as you did for the production Login app config file, you must set the COUNTRY & LANGUAGES values.
| Parameter | Description |
|---|---|
You can call your instance of OpenCRVS anything you like, such as "Farajaland CR"
These are your registration time periods and fees for birth, explained in more detail here. PRINT_IN_ADVANCE allows you to print certificates in advance for collection. You can disable this by setting it to false, if you operationally want to enforce an ID check from a recipient before printing a copy.
These are your registration time periods and fees for death, explained in more detail here. PRINT_IN_ADVANCE allows you to print certificates in advance for collection. You can disable this by setting it to false, if you operationally want to enforce an ID check from a recipient before printing a copy.
These are your registration time periods and fees for marriage, explained in more detail here. PRINT_IN_ADVANCE allows you to print certificates in advance for collection. You can disable this by setting it to false, if you operationally want to enforce an ID check from a recipient before printing a copy.
Fees due for collection and correction of certificates are calculated and displayed according to this value.
This is a regular expression to evaluate if a supplied phone number minus country code is valid.
If you configure your form to include a field to capture a user's National ID number, then this regular expression can evaluate if the string is valid.
You can always use our Farajaland logo by default and then upload this in the UI later, but if you look at the top of the file, you can see that this refers to a property that imports a copy of your country logo as a base64 image. Do not change this property but instead, locate your official logo/crest, convert it to base64 and you can replace our logo [here](https://github.com/opencrvs/opencrvs-countryconfig/blob/develop/src/api/application/country-logo.ts).
You can set the background of the login page to be a color of choice. You can always use the UI to change this color later, or use a tiled or full screen image.
This cannot be amended later in the UI and must be configured here. In application performance analytics, you can set the administrative level that you wish to aggregate field agent performance. We recommend that you leave this as DISTRICT as it refers to the FHIR "district" location level as opposed to your internal country name for location level 2. If your country is very small and has only 1 location level, set this to STATE.
This cannot be amended later in the UI and must be configured here. In application performance analytics, you can set the administrative level that you wish to aggregate field agent declaration completeness performance. We recommend that you leave this as DISTRICT as it refers to the FHIR "district" location level as opposed to your internal country name for location level 2. If your country is very small and has only 1 location level, set this to STATE.
This cannot be amended later in the UI and must be configured here. If you are using SMS or WhatsApp to send notifications to staff, set this to "sms". If you are using email, set this to "email"
This cannot be amended later in the UI and must be configured here. If you are using SMS or WhatsApp to send notifications to informants, set this to "sms". If you are using email, set this to "email"
This cannot be amended later in the UI and must be configured here. You will notice this separate property used by an API handler called by our analytics services. Whereas countries generally have crude birth rate ratios per area in their stastics, they tend to have a country-wide crude death rate. You can set this here in order to correctly calculate death registration completeness rates.
The following features can be enabled on and off in this block. We refer to this block as "Feature flags
This cannot be amended later in the UI and must be configured here. In some countries, the informant is required to sign the birth and death registration forms. In other countries uploads of supporting documentation is all that is required. Should you want the option for the informant to sign the birth and death form on the review page, set this to true.
This cannot be amended later in the UI and must be configured here. Should you wish to make the informant signature for birth and death described above a required field, set this to true.
This cannot be amended later in the UI and must be configured here. This field should be left as false. It is a custom property allowing a country to pause the registration process at the point of registration for 3rd party asynchronous validation. If you wish to use this property please get in touch with us at team@opencrvs.org. It is a legacy property that will likely be deprecated in OpenCRVS v1.4 due to relative underuse.
This cannot be amended later in the UI and must be configured here. In some countries, individuals do not know their date of birth. If you wish to enable that individuals are allowed to submit their ages in your declaration forms rather than a date of birth, set this to true. Please note that those individuals will have their days and months of birth automatically set to the 1st January in the system in that case.
Whether to enable the registration of death events in your OpenCRVS installation.
Whether to enable the registration of marriage events in your OpenCRVS installation. In OpenCRVS v1.3 we have released marriage registration in BETA. Set this property to true in order to demonstrate marriage registration as a proof of concept. Get in touch with us at team@opencrvs.org if you wish to use marriage registration in production. We require to complete marriage performance analytics and searching in order to release this feature in a future version. It is not yet production ready.
If enabled, you are able to print the review page of any declaration form including all the data entered by the applicant in an easy to read fashion. This can be a useful tool.