If I understand what you want to do, there are different ways of reaching your goal and opinions will vary on which is the best design. Perhaps the simplest would be via table-field that reads from your "questions" form with workflow to record (push) "answers" to wherever you like. So, it sounds like you need to open the "Workflow Objects Guide" (presume v7.6.04) and read: "Using active link guides in client-side table fields" (if you want to do this client-side) "Using a filter guide to loop through a table field" (if you want to do this server-side)
As for performance, unless you have a metric ton of answers to process in bulk/all-at-once (much more than 20), I don't think that the uncalibrated human eye-ball would notice any reasonably objectionable performance issues -- presuming your servers and network are decent. If the user is triggering workflow to push the answer separately for each question, then the performance would be about the same, whether it's one answer or a million (presuming they aren't writing a book in the answer field). -JDHood On Sun, Aug 28, 2011 at 5:20 AM, Shiju John <johns...@gmail.com> wrote: > ** > Hi Hood, > Thanks for your response. > Just a little bit more elaboration on the issue. > Just consider it as a checklist instead of the questions, for better > understanding :). Some options would be irrelevant based on the > application/release. In that case user wont be answering the respective > question. > Currently I am having a single back-end form (Form - A) which stores all > these Questions as a single record. So if we have 20 questions, and user can > enter values for n out of this 20 questions and the remaining (20-n) would > be left blank. And in future what if we need to add more questions? we have > to modify this form to accommodate the new questions. > What i am thinking of right now is to create single records (in a new form > - Form B) for each questions. So it doesn't matter, if in future new > questions are amended or if some are removed, thereby making it a bit > dynamic. > But for this I have to traverse through each questions (seperate fields) in > the respective record in Form A, and create individual records in Form-B. > Thus Form-B would be containing only Question, Answer and relevant composite > keys. > This would there by result in 'n' Push actions, degrading the performance a > bit (whether it be AL or Filter). I just want to know if we have any > shortcuts/tricks in remedy to traverse through the individual values within > a record, there by we can cut short this effort to some extend at least. > Please let me know your comments on this. > > Thanks, > Shiju... > > > > On Sun, Aug 28, 2011 at 11:56 AM, JD Hoodly <hood...@gmail.com> wrote: > >> ** John, >> >> >> If there is some user interaction that occurs as the result of each answer >> "pushed" before the entire record is saved, then active-links are >> appropriate -- even if you have to build one per question. >> >> If there is no user interaction that occurs from each push, then I would >> post-pone the push until all questions are answered and use filters. >> >> Whether you use one AL/Filter with 20 pushes or 20 ALs/Filters with a >> single push each -- you will still need to add or modify workflow each time >> you add a question (presuming each answer is in a separate field). I don't >> see this as a problem since you will already be in the dev-tool when you add >> the new question. >> >> Alternatively, if your questions & answers would fit on-screen gracefully >> then you might be able to do something with table-fields and use a guide to >> "walk" the answers. The UI would probably stink... >> >> Regardless, I would imagine users would complain about the number of >> questions they have to answer looooong before workflow performance became a >> serious issue. >> >> -JDHood >> >> >> >> On Sun, Aug 28, 2011 at 4:12 AM, Shiju John <johns...@gmail.com> wrote: >> >>> Hi, >>> I have a generic issue. The issue is as described below: >>> I have a form which stores 20 questions. These questions are not >>> mandatory, and the user might answer any "n" questions out of this 20. I >>> need to do a customization such that i need only the questions answered to >>> be pushed to a new form, which segregates each of these "n" questions to "n" >>> records in the new form. >>> The basic and easiest approach would be to create 20 activelinks which >>> checks if each question is answered or not, and based on that do a push to >>> the new form. But this would degrade the performance as there are chances >>> that the number of questions might increase in future. And this approach >>> would be a hard code( method of implementing 20 active links) , and not >>> configurable. Could some one suggest me a better approach to do this? >>> >>> Please pour in your thoughts !!! :) >>> >>> Thanks, >>> Shiju. >>> >>> >>> _______________________________________________________________________________ >>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >>> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" >>> >> >> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > > -- > > Thanks and Regards, > Shiju John > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
