Let's say I want to create an internal support form for all of my clients but I want them to see only whatever support info they submit. Once created, I would edit the views so some field on the form would = the same input from some field from their account form. I would make the form available for all clients to see.
Unless I'm doing something wrong, it's not working the way I'd like it to. By selecting a view filter where field = field, the support form submissions box shows up but the "add new" form doesn't show up for the client. When I remove the field = field, the client can see the form and also all of the submissions from all other clients but I don't want this client to see them.
What's needed is a field that's automatically populated with some info from the client's account. Currently, ID is the only unique identifier for a particular client and can't be changed unless the client's account is deleted. A different unique id could also be created through the add-account-field module and it'll show up where field = field in views. If this field is added to the internal support form, it's still useless because the client can enter anything he wants into the field and won't be able to see his submissions (but another client might). So what's needed here are 3 things:
-The ability to see the form even though no submissions have been made.
-A field that's populated with a unique identifier from the client's account that'll be used where field = field in views for whatever form and its submissions we'd want the client to see.
-The field must be "readonly" so it may be visible but can't be changed by the client, either that or just hidden (I know FT has similar controls over form fields).
Being able to create a form with populated fields based on the user's account info would be very helpful. If one were to create a form to be used for some type of communication between client and admin, admin would need to know who's sending the info. It would be convenient for the client if he didn't have to fill out his info every time he wants to communicate with admin.
I think what this may involve is a system based on relationships. If I were to set up the support form to work for every client based on the clients' unique id, they should be able to log into their accounts and see the form as if it's customized specifically for themselves. The only way to do this is if the form itself connects to the database and pulls data from the row containing the client's id. Is it possible to create {$placeholders} for field values similar to those FT has available for email? Would the placeholders be related to the client account so when he logs in and sees the form, his name, his email, his phone, etc shows up on his form?
Thanks!
Unless I'm doing something wrong, it's not working the way I'd like it to. By selecting a view filter where field = field, the support form submissions box shows up but the "add new" form doesn't show up for the client. When I remove the field = field, the client can see the form and also all of the submissions from all other clients but I don't want this client to see them.
What's needed is a field that's automatically populated with some info from the client's account. Currently, ID is the only unique identifier for a particular client and can't be changed unless the client's account is deleted. A different unique id could also be created through the add-account-field module and it'll show up where field = field in views. If this field is added to the internal support form, it's still useless because the client can enter anything he wants into the field and won't be able to see his submissions (but another client might). So what's needed here are 3 things:
-The ability to see the form even though no submissions have been made.
-A field that's populated with a unique identifier from the client's account that'll be used where field = field in views for whatever form and its submissions we'd want the client to see.
-The field must be "readonly" so it may be visible but can't be changed by the client, either that or just hidden (I know FT has similar controls over form fields).
Being able to create a form with populated fields based on the user's account info would be very helpful. If one were to create a form to be used for some type of communication between client and admin, admin would need to know who's sending the info. It would be convenient for the client if he didn't have to fill out his info every time he wants to communicate with admin.
I think what this may involve is a system based on relationships. If I were to set up the support form to work for every client based on the clients' unique id, they should be able to log into their accounts and see the form as if it's customized specifically for themselves. The only way to do this is if the form itself connects to the database and pulls data from the row containing the client's id. Is it possible to create {$placeholders} for field values similar to those FT has available for email? Would the placeholders be related to the client account so when he logs in and sees the form, his name, his email, his phone, etc shows up on his form?
Thanks!