Active Link guides work just fine on the web (I think since 6.3)
Fred From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Brien Dieterle Sent: Wednesday, November 19, 2008 3:44 PM To: [email protected] Subject: employee setup form best practices? I'm building a custom form to handle changes for new/existing employees-- things like account creation, email setup, shared group folder permissions, new computer setup, office phone setup, furniture and even name changes. I am duplicating an existing form from a different system that did all of this on one form using dynamic html to hide and show fields as selections are made. I was wondering if anyone had any suggestions as to how to handle a big form like this, or if this is the wrong approach entirely (should it be split up into smaller forms?). My first problem is that the form starts with a basic information gathering: Select employee type: New or Existing. Now, depending on what you select there are different fields available to fill out (by hiding/showing different page holder tabs). The pain comes when certain fields are required only when a certain choice is made. (If you select "New", well, you better provide a first and last name, right?) It doesn't seem like you can change a field to be required on-the-fly using "change fields" (is that correct?). So I am left with leaving them blank and using filters to check the required fields, or using activelinks to set the unneeded "required" field to bogus values like "N/A". Not a pretty picture. My gut says when something is difficult it is probably wrong. Active Links Guides look like an idea but this needs to be web-based (ALGs don't work on web?). Thanks for any tips! ARS 7.1 patch 003 MS-SQL Tomcat Brien _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
