How to retrieve internal interface draft data?

RE: How to retrieve internal interface draft data?

cedric02 — Sat, 22 Oct 2022 06:38:30 GMT

I can't view these tasks anymore, but I was naively thinking that a tool or plugin could extract or display data from .Kdb files...

RE: How to retrieve internal interface draft data?

Chris — Fri, 21 Oct 2022 21:28:49 GMT

Can you obtain it from just viewing the task yourself? Assuming this is a small/single case.

RE: How to retrieve internal interface draft data?

cedric02 — Fri, 21 Oct 2022 20:52:20 GMT

Thank you Mike. I will suggest the customer to implement its own custom draft use case.

RE: How to retrieve internal interface draft data?

cedric02 — Fri, 21 Oct 2022 20:50:29 GMT

Thank you for the tip Chris, but initially I just need to get old draft data (if possible).

but Ok I understand there is no way.

RE: How to retrieve internal interface draft data?

Mike Schmitt — Fri, 21 Oct 2022 18:34:32 GMT

There are no ways that I know of or have heard about here. That data is considered to be stored basically as internal "cache" type data in the appian engine, up until the form is submitted. Many of us prevent the use of this feature and instead implement our own.

RE: How to retrieve internal interface draft data?

Chris — Fri, 21 Oct 2022 18:34:28 GMT

To my knowledge we cannot access any data "saved" in memory with the OOTB save function. What I typically do here is disable this built-in save function on the User Input task, and create my own "Save For Later" type button within the form layout. This will bypass validation, and technically submits the form to only chain through a Write to DS node, and chain back to the same form, typically with a custom "Data has been saved" type message, where they can X it closed and re-access from their Tasks List later. This will persist the current values to the database where we can access them for reporting.