Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-4975

Making Family name as Optional

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Should
    • Resolution: Fixed
    • Affects Version/s: Platform 2.0.1
    • Fix Version/s: Core 2.1.0
    • Component/s: None
    • Labels:
    • Complexity:
      Low

      Description

      Background

      Historically, OpenMRS requires names to contain a "Given" part and a "Family" part. But in the real world some places only use a single name. We should relax the constraint in OpenMRS to support this real-world use case.

      Recently this was raised here: https://talk.openmrs.org/t/can-i-set-family-name-as-non-required-field/

      Tech Notes

      Make changes in https://github.com/openmrs/openmrs-core/blob/2.0.1/api/src/main/java/org/openmrs/validator/PersonNameValidator.java so that only `givenName` is required (but `familyName` is allowed to be blank).

      Also make changes in the relevant messages.properties files so that the error key and message reflect the new validation.

      Scope and Testing

      After making this change, we also need to make a related change in the REST Web Services module. This is captured in a different ticket: RESTWS-629

      We expect that making this change in the core API will automatically just work in different UIs built on top of this, but as part of signing off on the work on this issue, please verify that the new behavior works correctly when used with the Legacy UI module.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                harisu harisu fanyui
                Reporter:
                sravanthi17 sravanthi naraharisetti
                Designated Committer:
                harisu fanyui
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 5 minutes
                    5m
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 days
                    2d