The assetid will increase from any asset being created anywhere in the instance. If you set āLog Submissionsā to āNoā then the form wonāt create any form submission assets, but if thereās any custom actions or triggers that create assets based on the form submitting then the asset id will still increase in response to the form being submitted.
The form does not create any instance on Matrix, and the Log Submissions is turned off. Weāve setup āCall Rest Resourceā Submission Action that sends the form data to AutoPilot via CURL API.
Would this count as instance? I canāt see anything else that is creating an instance on the system.
I meant the form does not create any instances (trigger action or any assets) in the system and there are no triggers. I have tested it on a live system (matrix 5.4.3.1) and also on my private Matrix build (v5.4.0.0) which is just a barebone build with no interaction internally or the outside world.
Here is an example with submission log turned off.
Test 2 folder #1049 created after the form submission
Another test #1050 created after Test 2 folder
#Another test 2 after form submission
As you can see each time after a form submission the Asset ID is being skipped in the folder creation which means somewhere in the system or in the database it is logging the asset ID or there is some sort of bug.
So with submission turned off, it looks like the form submission does get created in the database, and then it gets Trashed?
Is there anything I need to do apart from turning submission log off?
I can replicate in the latest version of 5.4.5.0. I think that form submission assets are created temporarily if you have something like multi step form, but seems like the asset ID is incrementing even with single step forms and form submissions turned off. There might be an underlying reason as to why this is, but Iāll create a Squizmap ticket to investigate further.
We will eventually get to the 6 digit mark in about 2-3 years time. However now we know the system increments the IDās it will be within the next 6-12 months.
As for the second point, we just need re-assurance that the form submission data is not logged somewhere in the system when submissions logging is turned off. Weāre currently working to mininize the risk of getting on the wrong side of GDPR.