OpenCRVS
v1.7
v1.7
  • 👋Welcome!
  • CRVS Systems
    • Understanding CRVS
    • Effective digital CRVS systems
    • OpenCRVS within a government systems architecture
    • OpenCRVS Value Proposition
  • Product Specifications
    • Functional Architecture
    • Workflow management
    • Status Flow Diagram
    • User roles & scopes
      • Examples
    • Core functions
      • 1. Notify event
      • 2. Declare event
      • 3. Validate event
      • 4. Register event
      • 5. Print certificate
      • 6. Issue certificate
      • 7. Search for a record
      • 8. View record
      • 9. Correct record
      • 10. Verify record
      • 11. Archive record
      • 12. Vital statistics export
    • Support functions
      • 13. Login
      • 14. Audit
      • 15. Deduplication
      • 16. Performance management
      • 17. Payment
      • 18. Learning
      • 19. User support
      • 20. User onboarding
    • Admin functions
      • 21. User management
      • 22. Comms management
      • 23. Content management
      • 24. Config management
    • Data functions
      • 25. Legacy data import
      • 26. Legacy paper import
  • Technology
    • Architecture
      • Performance tests
    • Standards
      • FHIR Documents
        • Event Composition
        • Person
        • Registration Task
        • Event Observations
        • Locations
    • Security
    • Interoperability
      • Create a client
      • Authenticate a client
      • Event Notification clients
      • Record Search clients
      • Webhook clients
      • National ID client
      • FHIR Location REST API
      • Other ways to interoperate
  • Default configuration
    • Intro to Farajaland
    • Civil registration in Farajaland
    • OpenCRVS configuration in Farajaland
      • Application settings
      • User roles
      • Declaration forms
      • Certified Copies templates
    • Business process flows in Farajaland
  • Setup
    • 1. Planning an OpenCRVS Implementation
    • 2. Establish project and team
    • 3. Gather requirements
      • 3.1 Mapping business processes
      • 3.2 Mapping offices and user types
      • 3.3 Define your application settings
      • 3.4 Designing event declaration forms
      • 3.5 Designing a certified copy
    • 4. Installation
      • 4.1 Quick start: Set-up a local development environment
        • 4.1.1 Install the required dependencies
        • 4.1.2 Install OpenCRVS locally
        • 4.1.3 Starting and stopping OpenCRVS
        • 4.1.4 Log in to OpenCRVS locally
        • 4.1.5 Tooling
          • 4.1.5.1 WSL Support
      • 4.2 Configure: Set-up your own, local, country configuration
        • 4.2.1 Fork your own country configuration repository
        • 4.2.2 Set up administrative address divisions
          • 4.2.2.1 Prepare source file for administrative structure
          • 4.2.2.2 Prepare source file for statistics
        • 4.2.3 Set up CR offices and Health facilities
          • 4.2.3.1 Prepare source file for CRVS Office facilities
          • 4.2.3.2 Prepare source file for health facilities
        • 4.2.4 Set up employee users, and scopes, for testing or production
          • 4.2.3.1 Prepare source file for employees
          • 4.2.3.2 Configure roles and scopes
        • 4.2.5 Set up application settings
          • 4.2.5.1 Managing language content
            • 4.2.5.1.1 Informant and staff notifications
          • 4.2.5.2 Configuring Metabase Dashboards
        • 4.2.6 Configure certificate templates
        • 4.2.7 Configure declaration forms
          • 4.2.7.1 Configuring an event form
        • 4.2.8 Seeding & clearing your local databases
        • 4.2.9 Countryconfig API endpoints explained
      • 4.3 Deploy: Set-up a server-hosted environment
        • 4.3.1 Verify servers & create a "provision" user
        • 4.3.2 TLS / SSL & DNS
          • 4.3.2.1 LetsEncrypt https challenge in development environments
          • 4.3.2.2 LetsEncrypt DNS challenge in production
          • 4.3.2.3 Static TLS certificates
        • 4.3.3 Configure inventory files
        • 4.3.4 Create a Github environment
          • 4.3.4.1 Environment secrets and variables explained
          • 4.3.4.2 VPN Recipes
        • 4.3.5 Provisioning servers
          • 4.3.5.1 SSH access
          • 4.3.5.2 Building, pushing & releasing your countryconfig code
          • 4.3.5.3 Ansible tasks when provisioning
        • 4.3.6 Deploy
          • 4.3.6.1 Running a deployment
          • 4.3.6.2 Seeding a server environment
          • 4.3.6.3 Login to an OpenCRVS server
          • 4.3.6.5 Resetting a server environment
        • 4.3.7 Backup & Restore
          • 4.3.7.1 Restoring a backup
          • 4.3.7.2 Off-boarding from OpenCRVS
    • 5. Quality assurance testing
    • 6. Go-live
      • 6.1 Pre-Deployment Checklist
    • 7. Operational Support
    • 8. Monitoring
      • 8.1 Application logs
      • 8.2 Infrastructure health
      • 8.3 Routine monitoring checklist
      • 8.4 Setting up alerts
      • 8.5 Managing a Docker Swarm
  • General
    • Community
    • Contributing
    • Migration notes
    • Releases and upgrades
    • Release notes
      • v1.7.2: Release notes
      • v1.7.1: Release notes
      • v1.7.0: Release notes
    • Product roadmap
Powered by GitBook
On this page
  • OpenCRVS core v1.7.2
  • OpenCRVS Country config template v1.7.2
  1. General
  2. Release notes

v1.7.2: Release notes

OpenCRVS 1.7.2 is a hotfix release that introduces minor improvements and bug fixes based on the identified needs of countries using OpenCRVS.

PreviousRelease notesNextv1.7.1: Release notes

Last updated 1 day ago

OpenCRVS core v1.7.2

New features

  • TimeField component with AM/PM support: The TimeField component now supports both 12-hour (AM/PM) and 24-hour formats through a new prop, use12HourFormat: boolean. The logic has been refactored into two separate components, TimeInput24 and TimeInput12. The TimeField component automatically selects the appropriate component based on the prop.

  • Configurable Scopes: Introduce a new syntax for scopes which provides more customizability to the SI's via scopes. Two new scopes user.create[role=a|b|c] & user.update[role=d|e|f] are getting included in this release which can be used to restrict what the role of a newly created or updated user can be set to by the user of a particular role. Gradually most of the existing scopes will be migrated to use this new syntax.

  • New Full Honorific Name Field: An optional fullHonorificName field has been added to the user management page to capture the complete name of a user including their title or honorific. This field can be used for display purposes, including rendering the name appropriately on certificates.

Bug fixes

  • Filter out inactive locations in the Organisations menu

  • Improve quick search results when searching by name

  • Fix practitioner role history entries from being created with every view and download

  • Fix a child's NID form field cannot be added eithe rmanually or via ESignet. A father section cannot be placed before a mother section if you wish to use a radio button to control mapping addresses from one individual to aother to make data entry easier

  • Fix the role of the certifier unable to get resolved for new users which in turn caused the download of the declaration to fail

  • Fix one failing unassign blocking all other unassign actions from continuing

  • Fix record not getting unassigned when validating an already validated record again

OpenCRVS Country config template v1.7.2

Bugfixes

  • A configuration example of how to use middle names in a supported way has been added, inspired by [#9369((https://github.com/opencrvs/opencrvs-core/issues/9369))

partial write: max-values-per-tag limit exceeded (100000/100000)

New features

  • {
      name: 'time',
      custom: true,
      type: 'TIME',
      use12HourFormat: true,
      ...otherProp
    }
  • Control over allowed user creation/update: user.create[role=role_a|role_b] & user.update[role=role_a|role_b] can be used to control users of which role can be created/updated by users of a certain role.

Breaking changes

  • Roles with the following scopes: USER_CREATE, USER_CREATE_MY_JURISDICTION & USER_UPDATE, USER_UPDATE_MY_JURISDICTION need to have the user.create[role=role_a|role_b] & user.update[role=role_a|role_b] scopes added to them (replace role_a|role_b with the role IDs of your selection) in order to work as expected. If you are using custom roles, please make sure to update them accordingly.

InfluxDB max-values-per-tag is now set to unlimited to temporarily fix the following error when clearing data from a deployed environment

Added user.update:my-jurisdiction scope to Local System Admin to allow editing of users in jurisdiction

Time field 12-hour format: To enable the 12-hour (AM/PM) format of the TimeField, set the use12HourFormat property to true.

#8336
#8782
#9272
#9462
#9582
#9643
#9651
#9648
#393
#732
#8336