You are viewing limited content. For full access, please sign in.

Question

Question

Forms Cloud Retention / Data Maintenance settings

asked on September 16, 2021

How do I see what the retention of Submission data / Uploads is set to in the Cloud Version of Forms

In On-Prem, this is under your Name, Administration, Data Maintenance

0 0

Replies

replied on October 27, 2022

Hi Chad,

We're looking into supporting data retention for Cloud Forms. If you could provide some detailed use cases, that'd be very helpful. 

0 0
replied on October 27, 2022

Hi Francis

 

Forms keeps a copy of every submission and attachment, so retention is needed since storage is not infinite.

Right now on-prem allows for a global retention of form data and attachments independently.

However most companies have different retention for different documents required by law and this applies to web forms as well (since they are just another form of a document).

It would be nice to have an option to pick retention plans per process. IE: 7 years, 5 years, 1 year etc.

1 0
replied on October 27, 2022

Have you considered saving form submissions to Laserfiche and applying retention there?

0 0
replied on October 27, 2022

Yes but I don't think there is an option to remove the data from Forms on archive. Right now it would just duplicate the data.

0 0
replied on October 27, 2022

Right. I'm just saying that we're unlikely to offer retention periods that long for process instance data.

0 0
replied on October 27, 2022

Oh you mean my 7 year, 5 year examples. Sure it makes sense that you could use the repository as a way to save longer term data and Forms for shorter term business processes. This is how it is done with on-prem.

The problem is that everyone who already purchased Cloud was told that Forms will keep all data forever. Technically it is impossible to keep things forever so I think that will be a problem in the long run.

Customers have to make a decision with each process how long they want to keep the data, but right now they don't have a limitation, so there is less reason for setting up a duplicate repository archive.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.