Encounters Rework and core fixes. #3517
Conversation
- targetElement won't work with buttons.
This reverts commit 2371eb2.
- Minor fix to portal home not formatting correctly. - fix set POS events auto encounters. - fixup follow up encounter feature - fix encounters to scan today events to default new encounters settings - add provider pull down to encounter form - fix POS on facility change. - some restyles for normally off features
|
Darn git. It pulls this history c$^% ever now and then. I shouldn't have to rebase but sometimes git forces it. Anyway... I really need @eyalvo-matrix or @matrix-amiel or anyone at Matrix to look this over. I tried to keep original follow up encounter feature true to original logic but it needs testing. Anyone else that may have some ideas on further integration of follow up feature please share here. |
|
Bringing this in (ignoring any travis build errors) so I can move on. Looks like nobody from Matrix is interested in giving me feedback so, I'll deal with their issues if they find any down the road. I still can't find a good reason for follow up feature and if we don't have one by time of v5.0.3 release, i'm going to push for pulling it out of Globals as a feature. It's confusing unless now i've added a reference in the encounter to parent encounter proves useful. |
sjpadgett
changed the title
|
Thanks @sjpadgett !
|
Short description of what this resolves:
Encounters work flow rework
Bug fixes as I find them.
Changes proposed in this pull request: