We are experiencing an issue with simple visibility field. We have two fields stacked assessing a obsterm, one for a value of <= 129 and the other for a value > 129. If the value is 129 or below it will show the normal looking field. If the value is above it will show the red labeled field.
The EMR is giving us an ACCESS_VIOLATION (0xc0000005) at 0x20153643 when it transitions from one visibility condition to the other. Looking in the crash log it is specific to mlinform.dll. Has anyone experienced this with 9.10?
Try using a document variable instead of the obs term.
Have tried that as well and unfortunately, it does not work either . Narrowed it down a little further as well. It seems to happen when the field that will change has keyboard interaction. Weird I know, but I can take a dropdown with the same exact conditions and as long as I choose a value with my mouse off the list it works fine but as soon as I type a number or letter to get further down the list it crashes.
Out of curiosity is the obs term tied to an edit field or a drop down list? We found an issue where we have a drop down list that is populated by the patient's problem list. When the user clicks in the drop down list it works fine. If they type in the drop down list to search through the list of problems it searches fine but hangs for 5-10 seconds when the user tries to move to another item on the form. I ran mel traces using both workflows and they are exactly the same. Not exactly the same issue, but I'm wondering if there is a UI issue in CPS with keyboard interaction.
I have tried the same obs term on both a drop down and and edit field and they both have the issue. The only difference being two modes of interaction with a drop down. If I use my mouse to select a value for the drop down it is not crashing. When I use my keyboard to partially type the value to get closer to what I want to select and then select with the mouse or just type in full the value it will crash. I do believe 9.10 has a UI refresh issue. Not sure about CPS though.
Could you elaborate on the 9.10 UI refresh issue? We are in the process of upgrading our test environment to 9.10, but won't be able to actively test the environment under normal loads (600 concurrent users/ Citrix deployment).
We plan on using two JBOSS servers to mange the UI with a load balancing server and another JBOSS for interop. My hope is that the two UI JBOSS's will improve any UI lag that we currently experience in our 9.8.10 production environment.