Hi!
I have added KTL to Knack and I am noticing in all of my forms, every field is now sticky. Any help you can provide would be AWESOME! Thanks!
Dan
Hi @Dan3 - What do you mean “sticky”?
I’d recommend switching off all the Main Feature Switches expect the first three so essentially you are only using the loader. You should then be able to determine which switch is making things “sticky”. It could be the “Persistent From” option? There isn’t a sticky option?
Not sure of your experience but you might consider using the Configurator. The below video walks you through using it. 
1 Like
That was exactly it!!! Thank you very much! Quick question… what would be the use case for the Persistent Form setting to be true?
1 Like
Any data entered into the form is stored in a persistent manner, meaning that the form remembers the inputs across different sessions. For example, if you enter information into the form, close the application, and then return later, the form will be pre-filled with the previously entered data.
This feature could be helpful in scenarios like form-based surveys, applications, configuration settings, or user profiles, where users need to complete a form over an extended period, and it’s crucial not to lose progress.
In summary, Persistent Forms in the Cortex R&D KTL toolkit allows for forms that “remember” user input, making data entry more efficient and user-friendly by preserving the form’s content across sessions.
2 Likes
@Dan3 - Can you please mark this as the solution 
2 Likes
Just to shed a bit of light on this…
At Morbern’s industrial plant, we manage 72 kiosk-mode devices running 24/7 across two types: operator touchscreens for barcode scanning and data entry, and unattended dashboards displaying real-time production status.
With no downtime window available, when deploying software updates, all devices need to refresh simultaneously - we can’t wait for manual refreshes, especially for hotfixes or urgent features.
Initially, these forced refreshes would erase operators’ form data mid-entry, causing significant frustration.
The Persistent Form feature resolves this by:
- Automatically saving form data locally
- Only clearing saved data after successful submission, or when operators intentionally navigate away
- Preserving data through unexpected events (network issues, power failures, forced refreshes)
This solution maintains smooth operations while enabling immediate software deployment across all devices without risking unintended data loss or disrupting operator workflow.
Note: The _rlv (Reload Last Values) feature complements Persistent Form but serves a different purpose. While Persistent Form protects against data loss, _rlv speeds up data entry by automatically populating specified form fields with values from the previous submission - ideal for forms with repetitive data input.
Norm
2 Likes
Hi Normand, I have a question.
Is it possible to use the persistent form function for the same form across different pages?
So for example, assuming that I have the same form coming from the same object in different pages, is it possible that when I enter data without saving, it will show on the other forms in other pages?
1 Like
No, this is not possible because the data is saved per view ID.
Also, as soon as you navigate away from the page, the saved data is erased by design, so you wouldn’t be able to reload it in the next form.
1 Like