3.2.5 Set up application settings

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.

1. Prepare global functional settings

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.

Parameter

Description

APPLICATION_NAME

You can call your instance of OpenCRVS anything you like, such as "Farajaland CR"

BIRTH: {
    REGISTRATION_TARGET: 30,
    LATE_REGISTRATION_TARGET: 365,
    FEE: {
      ON_TIME: 0,
      LATE: 5.5,
      DELAYED: 15
    },
    PRINT_IN_ADVANCE: true
  }

These are your registration time periods and fees for birth, explained in more detail . 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.

DEATH: {
    REGISTRATION_TARGET: 45,
    FEE: {
      ON_TIME: 0,
      DELAYED: 0
    },
    PRINT_IN_ADVANCE: true
  }

These are your registration time periods and fees for death, explained in more detail . 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.

MARRIAGE_REGISTRATION

This cannot be amended later in the UI and must be configured here. 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 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 OpenCRVS v1.4. It is not yet production ready.

MARRIAGE: {
    REGISTRATION_TARGET: 45,
    FEE: {
      ON_TIME: 10,
      DELAYED: 45
    },
    PRINT_IN_ADVANCE: true
  }

These are your registration time periods and fees for marriage, explained in more detail . 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.

DATE_OF_BIRTH_UNKNOWN

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.

CURRENCY: {
    languagesAndCountry: ['en-US'],
    isoCode: 'USD'
  }

Fees due for collection and correction of certificates are calculated and displayed according to this value.

PHONE_NUMBER_PATTERN

This is a regular expression to evaluate if a supplied phone number minus country code is valid.

NID_NUMBER_PATTERN

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.

COUNTRY_LOGO

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]().

LOGIN_BACKGROUND: {
    backgroundColor: '36304E'
  }

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.

INFORMANT_SIGNATURE

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.

INFORMANT_SIGNATURE_REQUIRED

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.

FIELD_AGENT_AUDIT_LOCATIONS

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.

DECLARATION_AUDIT_LOCATIONS

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.

USER_NOTIFICATION_DELIVERY_METHOD

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"

INFORMANT_NOTIFICATION_DELIVERY_METHOD

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"

EXTERNAL_VALIDATION_WORKQUEUE

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. It is a legacy property that will likely be deprecated in OpenCRVS v1.4 due to relative underuse.

export const COUNTRY_WIDE_CRUDE_DEATH_RATE = 10

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.

2. Prepare javascript initialisation settings

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

window.config = {
  AUTH_API_URL: 'http://localhost:4040/',
  CONFIG_API_URL: 'http://localhost:2021',
  // Country code in uppercase ALPHA-3 format
  COUNTRY: 'FAR',
  LANGUAGES: 'en,fr',
  AVAILABLE_LANGUAGES_SELECT: 'en:English,fr:Français',
  CLIENT_APP_URL: 'http://localhost:3000/',
  COUNTRY_CONFIG_URL: 'http://localhost:3040',
  SENTRY: '',
  LOGROCKET: ''
}

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.9.1 Managing language content.

For example, if you wanted to support Spanish and English, with Spanish being the default this string should be:

es,en

AVAILABLE_LANGUAGES_SELECT: The app needs to populate available languages in a language select before it has had a chance to load any language content. This property allows you to customise the options & labels in the select. This value is a comma separated string of the following:

a) Firstly the ISO 639-1 language code for a single translation you have set up in step 3.2.7 Set-up language content followed by a colon.

b) After the colon, the displayName for the language.

For example, if you wanted to support Spanish and English, with Spanish being the default this string should be:

es:Español,en:English

The application can log errors to Sentry should it encounter any problems accessing the backend. LOGROCKET will be deprecated in OpenCRVS v1.4. Leave these options alone as empty strings as they are not used when running in localhost. They are populated dynamically from Github secrets in the server deploy step here.

Login app - server: login-config.prod.js

window.config = {
  AUTH_API_URL: 'https://auth.{{hostname}}/',
  CONFIG_API_URL: 'https://config.{{hostname}}',
  // Country code in uppercase ALPHA-3 format
  COUNTRY: 'FAR',
  LANGUAGES: 'en,fr',
  AVAILABLE_LANGUAGES_SELECT: 'en:English,fr:Français',
  CLIENT_APP_URL: 'https://register.{{hostname}}/',
  COUNTRY_CONFIG_URL: 'https://countryconfig.{{hostname}}',
  SENTRY: '{{sentry}}',
  LOGROCKET: ''
}

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.6 Deploy

You must set the COUNTRY, LANGUAGES & AVAILABLE_LANGUAGES_SELECT values only.

Client app - localhost development: client-config.js

window.config = {
  API_GATEWAY_URL: 'http://localhost:7070/',
  CONFIG_API_URL: 'http://localhost:2021',
  LOGIN_URL: 'http://localhost:3020',
  AUTH_URL: 'http://localhost:4040',
  MINIO_BUCKET: 'ocrvs',
  COUNTRY_CONFIG_URL: 'http://localhost:3040',
  // Country code in uppercase ALPHA-3 format
  COUNTRY: 'FAR',
  AVAILABLE_LANGUAGES_SELECT: 'en:English,fr:Français',
  LANGUAGES: 'en,fr',
  SENTRY: '',
  LOGROCKET: '',
  // Use the values in comments when Metabase is running locally
  // http://localhost:4444/public/dashboard/acae0527-74be-4804-a3ee-f8b3c9c8784c#bordered=false&titled=false&refresh=300
  LEADERBOARDS_DASHBOARD_URL: '',
  // http://localhost:4444/public/dashboard/fec78656-e4f9-4b51-b540-0fed81dbd821#bordered=false&titled=false&refresh=300
  REGISTRATIONS_DASHBOARD_URL: '',
  // http://localhost:4444/public/dashboard/a17e9bc0-15a2-4bd1-92fa-ab0f346227ca#bordered=false&titled=false&refresh=300
  STATISTICS_DASHBOARD_URL: ''
}

Following the same process as you did for the local development Login app config file, you must set the COUNTRY, LANGUAGES & AVAILABLE_LANGUAGES_SELECT 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 step 3.2.5.1 Configuring Metabase Dashboards for more instructions.

Client app - server: client-config.prod.js

window.config = {
  API_GATEWAY_URL: 'https://gateway.{{hostname}}/',
  CONFIG_API_URL: 'https://config.{{hostname}}',
  LOGIN_URL: 'https://login.{{hostname}}',
  AUTH_URL: 'https://auth.{{hostname}}',
  MINIO_BUCKET: 'ocrvs',
  COUNTRY_CONFIG_URL: 'https://countryconfig.{{hostname}}',
  // Country code in uppercase ALPHA-3 format
  COUNTRY: 'FAR',
  AVAILABLE_LANGUAGES_SELECT: 'en:English,fr:Français',
  LANGUAGES: 'en,fr',
  SENTRY: '{{sentry}}',
  LOGROCKET: '',
  LEADERBOARDS_DASHBOARD_URL:
    'https://metabase.{{hostname}}/public/dashboard/acae0527-74be-4804-a3ee-f8b3c9c8784c#bordered=false&titled=false&refresh=300',
  REGISTRATIONS_DASHBOARD_URL:
    'https://metabase.{{hostname}}/public/dashboard/fec78656-e4f9-4b51-b540-0fed81dbd821#bordered=false&titled=false&refresh=300',
  STATISTICS_DASHBOARD_URL:
    'https://metabase.{{hostname}}/public/dashboard/a17e9bc0-15a2-4bd1-92fa-ab0f346227ca#bordered=false&titled=false&refresh=300'
}

Following the same process as you did for the production Login app config file, you must set the COUNTRY, LANGUAGES & AVAILABLE_LANGUAGES_SELECT values.

Previous3.2.3.2 Configure role titles Next3.2.5.1 Configuring Metabase Dashboards

Last updated 1 year ago