(Program Rule) Cross-event scope for program rules

Registered by Markus Bekken on 2016-03-01

In Event Capture, some program rule variables needs to get values from events other than the active event. This can be getting values from the newest previous event, the latest event in the program, and so forth.
The source types of "DATAELEMENT_PREVIOUS_EVENT", "DATAELEMENT_NEWEST_EVENT_PROGRAM" and "DATAELEMENT_NEWEST_EVENT_PROGRAM_STAGE" should be able to get the value from the other events in the same orgunit. The maximum number of events to be concidered should be specified on each variable, and will default be set to 100 events. This means that when running variable population of a variable that gets the newest value in a program, maximum the 100 newest values will be considered. The model for programrulevariable will be extended with a property for the number of events to concider part of the scope.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Markus Bekken
Direction:
Needs approval
Assignee:
Markus Bekken
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 2.23
Started by
Markus Bekken on 2016-04-11
Completed by
Markus Bekken on 2016-04-11

Related branches

Sprints

Whiteboard

Implemented. Note that a default scope of 10 events is not made configurable in the way originally planned. The default was made more adaptive, so running a rule with a DATAELEMENT_NEWEST_EVENT_PROGRAM variable will run the rule on the 10 latest data values collected on the orgunit. Running a rule with DATAELEMENT_PREVIOUS_EVENT variable will run the rule on the 10 events that is preceding the current event date. If there are variables with both these types, the union of these two gropus will be used.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.