SavePulse for Qlik

Automatically saves compatible Qlik Cloud comments when you leave a changed note field.

SavePulse for Qlik was created to solve a very real and frustrating problem: losing completed work because a Qlik comment or note was updated but never saved. The developer experienced this multiple times firsthand. Time was spent updating comments and notes in Qlik, only for a missed Save action followed by a refresh or navigation to cause that work to be lost. The comments then had to be recreated from scratch. Similar experiences have also been reported by other Qlik users, suggesting the problem may affect more people than the developer alone. SavePulse was built specifically to help prevent that from happening. Instead of relying on you to remember to manually press Save every time, SavePulse watches compatible Qlik Cloud comment and note workflows. When you change a supported note and leave the field, SavePulse checks whether the content actually changed and, when it can safely identify the correct existing Qlik Save control, automatically triggers that Save action for you. The goal is simple: Update the note. Move on. SavePulse handles the Save. Clearing all text from a previously populated supported note also counts as a change and can be saved when the correct Qlik Save control is safely available. WHY SAVEPULSE EXISTS Updating comments and notes can be repetitive, especially when working through many records. It is easy to finish typing, move on to something else, refresh the page, navigate away, or simply forget that one final Save click. If the change was never saved, the work may be lost and have to be recreated. SavePulse adds a safety layer to that workflow by automatically performing the existing Qlik Save action after a supported changed note is left. It was originally created for the developer's own real-world Qlik Cloud workflow after experiencing lost comments more than once. MAIN FEATURES • Automatic save after leaving a changed compatible note/comment field • Helps prevent unsaved Qlik comment or note work from being lost • Premium READY / SAVING / SAVED status panel • Detection details showing the active compatibility method • Known Mode for validated layouts • Learned/Teach Mode for user-mapped layouts • Guided three-step Teach Mode: open editor, select note field, select Save control • Teach selections identify controls without activating the selected note field or pressing the selected Save button • Conservative Smart Detection for compatible layout variations • Safe fallback when the correct Save action cannot be identified confidently • Draggable full-size SavePulse panel • Draggable compact minimized status panel • Bright synchronized green save pulse in the full panel, minimized panel, and on-page SAVING alert • Optional movable on-page SAVING alert • Locally remembered UI preferences and selector-based taught mappings COMPATIBILITY AND TESTING SavePulse was originally created specifically for the Qlik Cloud workflow used by its developer. That original environment is the layout against which SavePulse has received its most extensive real-world testing. Qlik environments and workflows can be customized, and the developer does not have access to other organizations' Qlik environments or accounts for direct testing. To support compatible variations, SavePulse uses this compatibility order: Known → Learned/Teach → Smart → Safe Fallback Known Mode handles layouts SavePulse already recognizes. Learned/Teach Mode allows a user to identify the note field and Save control used by their own compatible Qlik workflow. Teach Mode uses a guided three-step process: 1. Open the note editor 2. Select the note field 3. Select the Save control After the editor is opened, the selection steps are designed to identify those controls without activating the selected note field or pressing the selected Save button. Conservative Smart Detection can recognize some additional compatible layouts automatically. If SavePulse cannot safely determine the correct Save action, it stops instead of guessing. Teach Mode is specifically designed to help SavePulse adapt to compatible Qlik layouts that have not been directly tested by the developer. However, because the developer does not have access to every organization's Qlik environment, universal compatibility with every Qlik configuration cannot be guaranteed. PRIVACY AND LOCAL OPERATION SavePulse operates locally in Chrome. SavePulse v1.2.3 has no SavePulse backend, analytics, telemetry, advertising, or remote-code system. To provide its auto-save function, SavePulse temporarily reads the active supported Qlik note/comment value in browser memory so it can determine whether the field changed. SavePulse does not intentionally store, log, or transmit the text of your Qlik notes or comments. Chrome local storage is used only for SavePulse preferences and selector-based Teach Mode mappings, such as: • SavePulse panel position • Minimized or expanded state • Saving-alert preferences and location • Selector mappings created through Teach Mode Teach Mode does not intentionally store the text contained inside the note field. SAFE BY DESIGN SavePulse is intentionally conservative. If there are multiple equally plausible Save controls, if a Save control cannot be safely identified, or if a layout does not meet SavePulse's confidence requirements, SavePulse does not guess. Runtime SavePulse will not intentionally click a disabled Save control. During Teach Mode, a disabled Save control may still be selected so SavePulse can learn where the correct control is located, but teaching that control does not intentionally press it. The goal is to automate one repetitive Save action while avoiding unsafe clicks elsewhere in Qlik. INITIAL PUBLIC SCOPE SavePulse v1.2.3 is designed for supported standard HTTPS Qlik Cloud tenant URLs under: *.qlikcloud.com Different Qlik applications, customizations, workflows, permissions, and future Qlik interface changes may affect compatibility. NEED HELP WITH YOUR QLIK LAYOUT? If SavePulse does not recognize your compatible workflow automatically, try Teach Mode first. For additional help, visit: https://jbrcollection.com/savepulse/support Support email: savepulse@jbrcollection.com If you provide a screenshot for compatibility assistance, remove or obscure customer information, names, VINs, account numbers, email addresses, phone numbers, financial information, internal business information, or other confidential data before sending it. SAVEPULSE FOR QLIK Protect your work. Reduce repetitive Save clicks. Keep moving. SavePulse for Qlik is an independent third-party product by JBR Collection. SavePulse is not affiliated with, endorsed by, sponsored by, or an official product of Qlik.