Hi Ben,
Thank you for your reply. I am pretty sure you'll find the best solution and will fix the bad error.
What did I notice...
Case 1.
When you are on the submissions list view there is an Add button. Now when the client hits it they create a new submission and are redirected to the submission edit page. Lets assume the form has some required fields that shouldn't be left blank but the client suddenly decides to leave the page let's say to check something else on the site (no matter what). In this case the submission is saved with all the fields blank or partially filled.
Case 2.
The client wants to add a new submission. They hit the add button and they are redirected to the submission edit page and the submission already has been created but the client doesn’t know it. They fill in the fields and start looking where to hit to add the record. For them the record hasn’t been created yet and the option to hit the update button doesn’t sound as a logic one. More likely they would choose to hit the Add button to save their information, but then actually they save the current record and create a new one – blank. For them everything is OK and they navigate to some other page, but in this way they leave one more blank record in the database.
How have I solved the issue? I've removed the Add button from the submission edit page (in the template file) and renamed the Update button to SAVE button. Of course it's not the best solution because the problem when the client leaves the page remains.
In my opinion it would be more intuitive if when the client hits the Add button on the submissions list view not to create a new record but to be redirected to the blank form (the record hasn't been created yet). There they should have buttons let’s say “SAVE” and “CANCEL”. Then they know – when hit Save they’ll create the record (and the fields check will be performed). When they hit cancel or leave the page they won’t leave a record with blank fields.
The buttons Update and Delete should appear only on the submission edit page (connected to the edit icon on the submission list view page).
I might not be right but I think that it’s a little bit more intuitive procedure.
I would be very thankful if you would help me to solve my problem mentioned in my previous post. I need to set the system in a way that the clients are able to view, edit, delete only their own submissions.
Thank you for the link above! I’ve read the article and I think it would be a good solution. As far as I understand if I find a way to put the account id as a value in some field I would be able to set the client map filter in a way that the particular filed equals the account id. Then the issue should be solved I think.
If I’m on the right direction would you help me with a few words how to get the account id in one of the form fields? If not, would you propose the best solution in your opinion?
With my best regards,
Yavor
Thank you for your reply. I am pretty sure you'll find the best solution and will fix the bad error.
What did I notice...
Case 1.
When you are on the submissions list view there is an Add button. Now when the client hits it they create a new submission and are redirected to the submission edit page. Lets assume the form has some required fields that shouldn't be left blank but the client suddenly decides to leave the page let's say to check something else on the site (no matter what). In this case the submission is saved with all the fields blank or partially filled.
Case 2.
The client wants to add a new submission. They hit the add button and they are redirected to the submission edit page and the submission already has been created but the client doesn’t know it. They fill in the fields and start looking where to hit to add the record. For them the record hasn’t been created yet and the option to hit the update button doesn’t sound as a logic one. More likely they would choose to hit the Add button to save their information, but then actually they save the current record and create a new one – blank. For them everything is OK and they navigate to some other page, but in this way they leave one more blank record in the database.
How have I solved the issue? I've removed the Add button from the submission edit page (in the template file) and renamed the Update button to SAVE button. Of course it's not the best solution because the problem when the client leaves the page remains.
In my opinion it would be more intuitive if when the client hits the Add button on the submissions list view not to create a new record but to be redirected to the blank form (the record hasn't been created yet). There they should have buttons let’s say “SAVE” and “CANCEL”. Then they know – when hit Save they’ll create the record (and the fields check will be performed). When they hit cancel or leave the page they won’t leave a record with blank fields.
The buttons Update and Delete should appear only on the submission edit page (connected to the edit icon on the submission list view page).
I might not be right but I think that it’s a little bit more intuitive procedure.
I would be very thankful if you would help me to solve my problem mentioned in my previous post. I need to set the system in a way that the clients are able to view, edit, delete only their own submissions.
Thank you for the link above! I’ve read the article and I think it would be a good solution. As far as I understand if I find a way to put the account id as a value in some field I would be able to set the client map filter in a way that the particular filed equals the account id. Then the issue should be solved I think.
If I’m on the right direction would you help me with a few words how to get the account id in one of the form fields? If not, would you propose the best solution in your opinion?
With my best regards,
Yavor