-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Validate search scope when scheduled event created [DHIS2-17335] #19457
Merged
muilpp
merged 3 commits into
master
from
DHIS2-17335-validate-search-scope-scheduled-event
Dec 13, 2024
Merged
fix: Validate search scope when scheduled event created [DHIS2-17335] #19457
muilpp
merged 3 commits into
master
from
DHIS2-17335-validate-search-scope-scheduled-event
Dec 13, 2024
+67
−17
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
muilpp
force-pushed
the
DHIS2-17335-validate-search-scope-scheduled-event
branch
from
December 12, 2024 13:32
43a1a6f
to
c44e588
Compare
enricocolasante
approved these changes
Dec 12, 2024
Comment on lines
2
to
32
"importMode": "COMMIT", | ||
"idSchemes": { | ||
"dataElementIdScheme": { | ||
"idScheme": "UID" | ||
}, | ||
"orgUnitIdScheme": { | ||
"idScheme": "UID" | ||
}, | ||
"programIdScheme": { | ||
"idScheme": "UID" | ||
}, | ||
"programStageIdScheme": { | ||
"idScheme": "UID" | ||
}, | ||
"idScheme": { | ||
"idScheme": "UID" | ||
}, | ||
"categoryOptionComboIdScheme": { | ||
"idScheme": "UID" | ||
}, | ||
"categoryOptionIdScheme": { | ||
"idScheme": "UID" | ||
} | ||
}, | ||
"importStrategy": "CREATE", | ||
"atomicMode": "ALL", | ||
"flushMode": "AUTO", | ||
"validationMode": "FULL", | ||
"skipPatternValidation": false, | ||
"skipSideEffects": false, | ||
"skipRuleEngine": false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
"importMode": "COMMIT", | |
"idSchemes": { | |
"dataElementIdScheme": { | |
"idScheme": "UID" | |
}, | |
"orgUnitIdScheme": { | |
"idScheme": "UID" | |
}, | |
"programIdScheme": { | |
"idScheme": "UID" | |
}, | |
"programStageIdScheme": { | |
"idScheme": "UID" | |
}, | |
"idScheme": { | |
"idScheme": "UID" | |
}, | |
"categoryOptionComboIdScheme": { | |
"idScheme": "UID" | |
}, | |
"categoryOptionIdScheme": { | |
"idScheme": "UID" | |
} | |
}, | |
"importStrategy": "CREATE", | |
"atomicMode": "ALL", | |
"flushMode": "AUTO", | |
"validationMode": "FULL", | |
"skipPatternValidation": false, | |
"skipSideEffects": false, | |
"skipRuleEngine": false, |
} | ||
], | ||
"relationships": [], | ||
"username": "system-process" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
"username": "system-process" |
Quality Gate passedIssues Measures |
This was referenced Dec 12, 2024
ameenhere
approved these changes
Dec 13, 2024
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.
We currently validate the capture scope when creating an event. This works for
ACTIVE
andCOMPLETED
events. However, forSCHEDULE
events, it should also be possible to create them using the user's search scope. This PR addresses that issue.