Report a Data Entry Lag in Swimlane Records

occasionally a swimlane user will contact the swimlane support team to report data entry lags in swimlane record fields (typically single line text, multi line text, and comments fields) most of the time characters appear in the field’s display area as fast as you can strike the corresponding keys on the keyboard however, with a lag you can see that there are obvious delays between the time at which the keystrokes are made and the time at which the attendant characters appear in the display area these delays may be intermittent or ongoing this symptom has multiple root causes including too many fields, sections, tab controls in each record the easiest remedy for this root cause is to hide as many fields/sections as possible the more page elements are visible, the greater the memory required as each page element has its own javascript listener if possible, expose only the fields/sections that are needed at each phase of your work in the record memory leaks in swimlane’s ui code previously identified memory leaks have been fixed, but new ones may arise other, yet to be identified causes in order to identify the root cause, possibly find a temporary workaround, and bring about a permanent solution, swimlane support needs to understand clearly how and when the symptom arises, and how its severity may vary to provide support with this insight, make a screen capture video recording to document the steps that you take before and during the lag symptom to report a data entry lag in swimlane records open record x1 from application x change a value in selection field s1 so that section z appears (z happens to house a tab control with 4 tabs ) select each tab in z in turn, and then return to the first tab begin typing in the multi line text field m1 in the first tab of z at the highest possible speed, even if this creates nonsense text alternatively, and perhaps even better, press down one character key, such as the letter 'a', and hold it for 5+ seconds if a string of 'a's appear at a steady rate for the entire 5 seconds, then there is no lag if there are lapses when no new instances of 'a' appear on the current line, then this is the lag