Feature/client feedback #33
Merged
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
ifoche
approved these changes
Oct 7, 2020
xurxodev
pushed a commit
that referenced
this pull request
Jun 27, 2023
* Update HomeActivity.kt * Adding managestockViewmodel as param to checkVisbility * check size of the data in the table * Adding variables to check the table content * Update paperwork.json * Code style * Update HomeScreen.kt Co-authored-by: Andrés Miguel Rubio <[email protected]>
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.
📌 References
⚙️ branches
app:
Origin: :feature/client_feedback Target: develop-psi
dhis2-android-SDK:
Origin: develop-eyeseetea
dhis2-rule-engine:
Origin: android_2.0.1
🎩 What is the goal?
The goal is to apply the feedback of the client after the last release:
📝 How is it being implemented?
💥 How can it be tested?
Use case 1: - the indicators icon and menu should not be visible in the event capture screen for the psi flavor
Use case 2: - changes in the event should realize live updates in the toolbar according to TitlePattern of the program stage
💾 Requires DB migration?
🎨 UI changes?