Mar 9th, 2010, 5:03 AM
Hi Ben, thanks for getting back on this.
You are correct in that I have created about 4 different "views" that filter the submissions based on criteria that forms our work flow. New, Pending, Confirmed, Deleted etc.
I also created a view called "paper applications" and allowed users to add submissions for here. We don't need to enter all of the data from the paper application into the form tools database, just enough to manage their application from "New" through "Confirmed" so, in this view I have limited the number of fields that are visible so as to make it easier for my staff to enter the data. So, that's the theory and here are the issues.
1. When logged in as Admin, I can select the "Paper Applications" view, click "add" and a blank form is immediately launched in the browser with the limited fields as I want it. When logged in as a User, you click "add" and seemingly nothing happens. It does create a new record set but doesn't launch the blank form... also you can't see it as the "paper applications" view is filtered based on the value of a field you haven't had a chance to select yet! In order to find the blank submission the user must now change views to "all submissions", find the blank submission and then click "edit". They are now faced with all of the fields (not just the ones that I need them to enter) so I have instructed them to only select the field that "paper application" view is filtered on, then update the submission, change views back to "paper application" re-open the submission and then enter the data! It's a pretty convoluted way to do it! I guess adding a submission from the "all submissions" view would cut down a couple of steps here yet it would be great if the user worked in the same way as the admin.
2. One other thing, currently you can only "add" a submission in a view when it already has a submission in it. When there are no submissions showing the "add" button is not viable. Not a big deal, yet in my application I really only created the "view" as a sort of substitute front end form, not to filter those submissions after they have been added.
Am I making any sense!
Mike
You are correct in that I have created about 4 different "views" that filter the submissions based on criteria that forms our work flow. New, Pending, Confirmed, Deleted etc.
I also created a view called "paper applications" and allowed users to add submissions for here. We don't need to enter all of the data from the paper application into the form tools database, just enough to manage their application from "New" through "Confirmed" so, in this view I have limited the number of fields that are visible so as to make it easier for my staff to enter the data. So, that's the theory and here are the issues.
1. When logged in as Admin, I can select the "Paper Applications" view, click "add" and a blank form is immediately launched in the browser with the limited fields as I want it. When logged in as a User, you click "add" and seemingly nothing happens. It does create a new record set but doesn't launch the blank form... also you can't see it as the "paper applications" view is filtered based on the value of a field you haven't had a chance to select yet! In order to find the blank submission the user must now change views to "all submissions", find the blank submission and then click "edit". They are now faced with all of the fields (not just the ones that I need them to enter) so I have instructed them to only select the field that "paper application" view is filtered on, then update the submission, change views back to "paper application" re-open the submission and then enter the data! It's a pretty convoluted way to do it! I guess adding a submission from the "all submissions" view would cut down a couple of steps here yet it would be great if the user worked in the same way as the admin.
2. One other thing, currently you can only "add" a submission in a view when it already has a submission in it. When there are no submissions showing the "add" button is not viable. Not a big deal, yet in my application I really only created the "view" as a sort of substitute front end form, not to filter those submissions after they have been added.
Am I making any sense!
Mike