Details
-
Task
-
Status: Closed
-
Must
-
Resolution: Fixed
-
None
-
Undetermined
-
Sync 2.0 Sprint 9, Sync 2.0 Sprint 10
-
Description
Before this ticket implementation will start, we should define the scope of this issue. What exactly means catchment areas ? How should we handle this ?
Acceptance Criteria:
- Gather requirements, define the scope of this issue and update ticket description
- Support for handling different catchment areas should be added - allow to configure what is synced where through configuration
UPDATE 08.10.2018
What exactly means catchment areas?
Catchment area means some additional conditions which objects must fulfill to be pulled from parent server (for instance we want to pull only patients from the specific department).
How should we handle this?
I think the best solution is creating strategies for different catchment areas. The strategy will help us choose which objects are interesting for us.
Acceptance criteria:
- Support for handling different catchment areas should be added - allow to configure what is synced where through configuration
- Update documentation
Gliffy Diagrams
Attachments
1.
|
Create the generic interface for the catchment area strategy |
|
Closed | Arkadiusz Lalo |
|
||||||||
2.
|
Create the configuration for catchment areas |
|
Closed | Arkadiusz Lalo |
|
||||||||
3.
|
Create a default strategy |
|
Closed | Karol Cissewski |
|
||||||||
4.
|
Create service for handling catchment areas |
|
Closed | Oskar Hinc |
|
||||||||
5.
|
Fix issues related to filtering functionality |
|
Closed | Arkadiusz Lalo |
|