In-Memory Forms

In-memory forms, so named because data is only stored in the active memory of the user's device, differ from regular forms in that they will not be autosaved or saved as drafts, and will be submitted directly to the TrueContext server without being placed in the outbox or using the background upload process. This means that no data, image files, signatures etc. end up in the device file system after a form has been submitted.

In-memory forms are an ideal solution for sensitive use cases, such as when collecting personally identifiable information (PII) on shared devices.

Considerations

When a form is configured to run in-memory, the following limitations apply: 

• Saving a form as a draft and offline queuing is not supported
• Dispatched form data is not downloaded to the device on reconcile, but only as the form is opened which will require network connectivity at the time of form completion
• In-Memory forms cannot be submitted while a device is offline
• Once a form has been enabled to run in-memory, the form will be locked for editing and you will require assistance from TrueContext support to make further form changes

Limitations

When enabling in-memory functionality, all data entered into the form is stored in the device's active memory. As a result, performance may be limited by the memory available on your end-user devices. To improve performance, TrueContext recommends limiting the size of your form, especially as it pertains to image files. We recommend no more than 5 images or signatures per form.

Unsupported controls:

• Sketch Pad
• File Upload
• Audio Recording
• Document Editor

Implementation

Info:To enable a form to run in-memory, contact support@truecontext.com with the URL for the form you would like to enable the feature on.