Notifications
Clear all
Topic starter
Hello All,
I am trying to fix some issues with form slowness in a visit. Some button presses are slow particularly when there are other forms present. Specifically, one of the functions that runs when the button is clicked may add a problem to the problem list. This in turn makes everything that uses PROB_AFTER() run. I am looking at where I have PROB_AFTER() in forms in the visit and modifying or removing if I can. In my mel trace I have something like this:
MelTrace] Fire trigger: {global F03376158922416588048=PROB_AFTER() ""}
MelTrace] execute>>call PROB_AFTER()
MelTrace] results>>[PROBLEM LIST IS RETURNED HERE]
MelTrace] execute>>end
MelTrace] results>>""
MelTrace] execute>>Done with trigger
So it looks like somewhere I have defined a global variable that gets the value of PROB_AFTER(). The temporary variable name the emr uses isn't very helpful. Short of looking through every form in the visit is there a way for me to identify what the temporary variable F03376158922416588048 is actually called?
Thanks,
Brad
Posted : May 13, 2020 2:20 am
That's just how VFE compiles the form into a kit, in your form in VFE you would just find a reference to PROB_AFTER().
I would search for it by query, you should be able to run this and identify the form
SELECT * FROM FORMSET WHERE WATCHERS like '%F03376158922416588048%' and Active = 'D'
Posted : May 13, 2020 2:36 am
