patient.gsp’s controller fetches extensions whose extensionPointId are either "patientDashboard.firstColumnFragments" or "patientDashboard.secondColumnFragments" to then dispatch them in the appropriate part of the view.
AppFrameworkService service = Context.getService(AppFrameworkService.class);
service.disableExtension("org.openmrs.module.coreapps.patientHeader.secondLineFragments.activeVisitStatus");
Do you mean how to customise the overall actions menu that is on the right hand side?
If yes, then I believe your HFE forms should show up as soon as there is an active visit.
@mksd Thanks, now I get how to manage fragments on the dashboard.
On the forms my question is how to register the forms without going through Configure Metadata -> Manage Forms then adding each form to the UI as is currently the case - I am trying to have my module configure everything for the installation so that a user just has to create new users and they are off.
The idea is that all HFE forms that are in omod/src/main/webapp/resources/htmlforms/ are scanned by the above code.
Ans so we have added new attributes in their header specifying the defaults for what you would otherwise do manually in Configure Metadata \ Manage Forms:
<htmlform formUuid="5743bf01-7879-40a0-ab26-95fc2446e510" formName="Triage" formEncounterType="5235f7da-194e-4278-afbd-a473bb430857" formVersion="0.6"
formAddMetadata="yes"
formUILocation="patientDashboard.visitActions"
formOrder="1"
formIcon="icon-medkit"
formShowIf=""
formDisplayStyle="Standard"
>
...
</htmlform>
```
The above code comes from, amongst others, [our triage form](https://github.com/mekomsolutions/openmrs-module-lfhcforms/blob/dev/omod/src/main/webapp/resources/htmlforms/triage.html#L2-L7).
-----
Feel free to dig in there and ask more questions about our implementation's details.
Just seeing this now… (thanks @ssmusoke for pointing this out to me)… would be good to add this to the reference app somewhere, would have to think about where it should live… @darius
@mksd Coming back to this solution, have you had any need to show the form in two different locations - there are cases when I need the same form in both registrationSummary.overallActions and registrationSummary.overallActions.
@darius There is a Form UI Location tag which was holding a single extension for the form, which may be updated to take a comma delimited list of extensions as a quick fix.