Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Must
-
Resolution: Fixed
-
Affects Version/s: HTML Form Entry 3.9.2
-
Fix Version/s: HTML Form Entry 3.10.0
-
Labels:None
Description
Background
Currently the <uiIclude/> tag does not support picking up fragment parameters. These parameters are in some instances required by the FragmentController making it currently impossible to include many fragments into HFE forms.
An example of such a fragment is ConditionsFragmentController:
public class ConditionsFragmentController { public void controller(.., @FragmentParam("patientId") Patient patient) { ... } }
In this case the fragment params is a reference to an instance of Patient.
Developer Notes
- Changes should be made in the UiIncludeTagHandler
- The attribute fragment should be able to accept URL parameters, example use:
<uiInclude provider="coreapps" fragment="conditionlist/conditions" fragmentParams="patientId=$patient.patientId¶m2=value" />
Additionally we could make this URI-like syntax work as well:
<uiInclude provider="coreapps" fragment="conditionlist/conditions?patientId=$patient.patientId¶m2=value" />
- Also take note that the tag handler should be able to pickup and parse velocity expressions from the URL parameters, i.e. "patientId=$patient.patientId" should result to "patientId=2" if patient Id is 2.
Gliffy Diagrams
Attachments
Issue Links
- is related to
-
HTML-686 Allow passing params when including fragments and saves as a observation
-
- Closed
-