Thanks for the clarification. I've been reading that section; I guess I'll have to give it a try.
On Nov 4, 9:45 am, Thad Esser <[email protected]> wrote: > Table looping works pretty much as you described. Search for "Table Loop" > in the workflow objects guide. Page 134 of the 7.1 guide has a section on > "Using filter guides in server-side table fields" that might help. > Basically, when the workflow hits the filter guide, it "selects" the first > row in the table, processes all the filters in the guide using that row's > data, then selects the next row, processes all the filters in the guide > using the 2nd row's data, and so on. (technically, its not "selecting" the > row in the way you'd think of it on the client side, but you can > conceptually think of it that way.) > > Sorry to hear about you getting laid off. The good news is there's a fair > amount of Remedy job postings on the list these days. > > Thad > On Thu, Nov 4, 2010 at 8:00 AM, Christine <[email protected]>wrote: > > > > > > > Thad - Thank you for your detail. Perhaps I should state for aesthetic > > purposes that the form has quite a few Page Fields, with some embedded > > Page Fields so that only a small portion of the form is presented to > > the user at any one time. Each portion has sections for Oracle > > Responsiblities - such as those for Accounts Payables, Order > > Management etc. > > > As I have very limited Remedy training and no Remedy co-workers, > > perhaps you can clear up something for me. I see you mentioned the > > option of Table Loop in the filter. With my background a 'table' loop > > would search through each record in the table, searching for a > > matching parameter. Is this how a Table Loop in Remedy works, or does > > that search each field in one record? > > > I like the fact that this example is little maintenance. My company is > > laying me off the end of January and I'm trying to leave Remedy in a > > good state. I've been automating quite a bit of the admin work and > > looking for ways to reduce work once there is no full time Remedy > > person. > > > Thanks, > > Christine > > > On Nov 3, 1:31 pm, Thad Esser <[email protected]> wrote: > > > Christine, > > > > I love a good puzzle, although "many, many, hundreds of checkboxes" > > scares > > > me. Anyway, how about this: > > > > Create a New Form to hold information about the checkbox fields: > > > Field ID > > > Field Label > > > Field Name > > > > Create a Table on your Request form that references the new form above, > > with > > > the following columns: > > > col_fieldid > > > col_fieldlabel > > > col_fieldname > > > > Create some display only fields on your Request form: > > > char - ztmp_currentfieldid > > > char - ztmp_currentfieldvalue (for this example, we'll say this > > > field has a fieldid of 536870002) > > > char - ztmp_currentfieldlabel > > > > Create the filters and the guide to hold them: > > > Filter guide > > > Filter 1`!: (note the phasing override) > > > Action 1: (sets temp fields from your table of > > fields) > > > Set ztmp_currentfieldid = col_fieldid > > > Set ztmp_currentfieldlabel = col_fieldlabel > > > Action 2: Run Process: > > > Application-Copy-Field-Value > > > 536870002 $ztmp_currentfieldid$ (note: this takes the value from the > > field > > > that has the fieldid that is stored in $ztmp_currentfieldid$, and copies > > it > > > to the ztmp_currentfieldvalue) > > > Filter 2`!: (note the phasing override) > > > Run if: $ztmp_currentfieldvalue$ != $NULL$ > > > Action 1: set summary = summary + "|" + > > > $ztmp_currentfieldlabel$ + ": " + $ztmp_currentfieldvalue$ > > > > Create a filter to call the guide: > > > Run If: $record summary$ = $NULL$ > > > Action 1: Call guide, with Table Loop checked, and the new > > table > > > above selected. > > > > And then a final filter to do an LTRIM or substring to remove the intial > > > carriage return that will be there > > > > This has the benefit of little code to maintain, and makes the list of > > > checkboxes data-driven. When you add a new checkbox, you don't need to > > > update any code, just add a record to that first form. > > > > Hopefully that gives you some other options to think about. > > > > Thad Esser > > > Remedy Developer > > > > On Wed, Nov 3, 2010 at 11:33 AM, Christine <[email protected] > > >wrote: > > > > > I have a form with many, many checkboxes. When a person submits the > > > > form I want to walk just this record, evaluate each field for a value, > > > > if that value is != $NULL$ then I want to write the field title and > > > > the field value to a single, summary field I’m calling Record > > > > Summary. > > > > > Imagine a form with 4 checkboxes for color choices > > > > > Field names = Red, Blue, Green Black > > > > Field titles = “Color Red”, “Color Blue”, “Color Green” and “Color > > > > Black” > > > > The field attributes are correspondingly “Bright Red”, “Dark Blue”, > > > > “Faded Green” and “ReallyBlack”. This is the value that is written to > > > > the table when the checkbox is checked. > > > > > If the person submitting the record checks only the “Color Red” and > > > > “Color Black” boxes I want to write this to the summary field: > > > > Color Red: Bright Red > > > > Color Black: Really Black > > > > > I have a real kluge of this based on a filter working in dev. However, > > > > it is does not evaluate each field for a non-null value. I check to > > > > see if the Record Summary field is empty, if it is then I use this Set > > > > Field action on the Record Summary field: “$Red$ + "; " +”|” + $Blue > > > > $) + "; " +”|” + $Green$ + "; " +”|” $Black$ + "; " which > > > > results in: > > > > > Bright Red, > > > > , > > > > , > > > > Really Black > > > > > My form has hundreds of checkboxes for people to request AD Accounts, > > > > hardware, general software and Oracle Apps Responsibilities (this is > > > > the reason for the length of the form). As you can see using my kluge > > > > will result in an ugly text field for the help desk person to review. > > > > Many lines would just have the commas in them where the users didn’t > > > > make any choices. That is so even when I combine several checkbox > > > > field values on one line. > > > > > Plus, the processing just isn’t that elegant. > > > > > Can someone direct me to the correct process to use for this? Is there > > > > an example of this in a ACTL, Filter or Guide for me to review that > > > > might already be doing something like this? I keep reading the > > > > workflow manual about guides and looping and this just isn't clicking > > > > with me. (We have ARS 7.1.00, Change and Incident 7.0.03, and SRM 2.2) > > > > > Thanks, > > > > Christine > > > _______________________________________________________________________________ > > > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > > > attend wwrug11www.wwrug.comARSList:"Where the Answers Are" > > > _______________________________________________________________________________ > > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > > attend wwrug11www.wwrug.comARSList:"Where the Answers Are"- Hide quoted > > text - > > > > - Show quoted text - > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > attend wwrug11www.wwrug.comARSList: "Where the Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug11www.wwrug.comARSList: "Where the Answers Are"- Hide quoted text > - > > - Show quoted text - _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
