(fix) Add a check for customConceptAnswers when configuring coded person attribute fields #996
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
denniskigen
changed the title
denniskigen
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requirements
Summary
This PR addresses an issue discovered while configuring the Patient Registration form. After adding customized concept answers to a patient attribute
format org.openmrs.Concept, the errorThe person attribute field 'nextOfKinRelationship' is of type 'coded' but has been defined without an answer concept set UUID. The 'answerConceptSetUuid' key is required.is displayed. This has been resolved by addingcustomConceptAnswersto the check that determines whether the error should be shown.Screenshots
Related Issue
N/A
Other
Error displayed should include customConceptAnswers