I think what I may end up doing for the time being is create a new page, name it "Support" and add it as a client menu item, clone the html code that makes up the current support form I've created and paste it into the new page, and then copy the MySQL code from the account page (or create new) and toss it into the new Support page and code it so the fields will be populated, pass a unique identifier that can be set up in views/filters and then copy the same form action from the original support form.
By theory, this should work just fine and the submissions would appear within the form database named "Support", the client would have access to his submitted info only, and a fresh form populated with his info will appear by clicking on the "Support" link from the menu. But an unpopulated form will also appear under the Support submissions table > Add New, which might be a problem so I may need to look at views to see if this particular form (not the submissions table) can be excluded somehow from client views. Any suggestions would be helpful... I just haven't found a single day containing 48 hours worth of time to work on this yet...
Alternatively, the client doesn't really even need to see or keep a record of his own support submissions so I could set the views so Admin only can see them and this would eliminate the unpopulated form problem...
Or I could just look through open-source Support applications and see if there's some way that I could integrate it in with formtools... (probably making this more complex than it really needs to be)
The bottom line is that I want to make this work because FT has the ultimate potential to function as a fully-featured back office for my clients. I love its simplicity when compared to advanced CMS systems such as Joomla, Drupal, & PHP Nuke. With some modification, it even has the potential to be a simple CRM which would be much easier to manage than vTiger and SugarCRM.
By theory, this should work just fine and the submissions would appear within the form database named "Support", the client would have access to his submitted info only, and a fresh form populated with his info will appear by clicking on the "Support" link from the menu. But an unpopulated form will also appear under the Support submissions table > Add New, which might be a problem so I may need to look at views to see if this particular form (not the submissions table) can be excluded somehow from client views. Any suggestions would be helpful... I just haven't found a single day containing 48 hours worth of time to work on this yet...
Alternatively, the client doesn't really even need to see or keep a record of his own support submissions so I could set the views so Admin only can see them and this would eliminate the unpopulated form problem...
Or I could just look through open-source Support applications and see if there's some way that I could integrate it in with formtools... (probably making this more complex than it really needs to be)
The bottom line is that I want to make this work because FT has the ultimate potential to function as a fully-featured back office for my clients. I love its simplicity when compared to advanced CMS systems such as Joomla, Drupal, & PHP Nuke. With some modification, it even has the potential to be a simple CRM which would be much easier to manage than vTiger and SugarCRM.