It sounds like you only need one notification for Child and Task for a unique Assignee Group and/or Assignee. What if you call your task Guide from within the child guide... Only have one button that calls the first guide. Write to the form immediately in the loops (use a tmp status so the notification goes on modify, not submit). Qualify your push fields so that records update if they are the same, they don't create new ones. Make sure an Assignee Group record with no Assignee doesn't overwrite a record that already has an assignee. Test to see if you are at the end of the loop in both tables and when you are, send a tmp status to notify, let the modify filter send the notification. HTH, Janie
_____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Frex Popo Sent: Saturday, January 10, 2009 5:19 AM To: [email protected] Subject: Re : Table Loop and Active Link Guides ** anyone has some thoughts on how to acheive this .... any help will be very much appreciated. --- En date de : Ven 9.1.09, Frex Popo <[email protected]> a écrit : De: Frex Popo <[email protected]> Objet: Table Loop and Active Link Guides À: [email protected] Date: Vendredi 9 Janvier 2009, 15h50 Dear all, I hope someone who tried this in the past or something similar can point me in the right direction. This is all workflow. In an incident form I have two tables, one for child incidents and one for tasks of these child incidents. I need to send a notification (email) to each group of these child incidents and their tasks if none have been assigned to a particular person. However if a child incident or task has been assigned to a particular person I ONLY need to send it to this person and not to the group. Here is what I did so far but can not get the sequence within the guides to work.. I have created the following active links which call a table loop guides. 1. One active link to calls the guide for the child incident table when a button is pressed with order 0. 2. One active link to calls the guide for the task table when the button is pressed with order 1. 3. One active link which writes a child incident request to a form, which is called from within guide 1. 4. One active link which writes a task request to the same form, which is called from within guide 2. I need to be able to, before I write a child incident or a task to the form, test if the group or the assigned person or both are duplicates within the table before I write them. If say in the task table (and this applies to child incidents as well) I have a task assigned to GroupA without an assignee and I have another task assigned GroupA but this with an assignee, I should only write the request for the latter and not the former, so that on the assignee will be notified and not the entire group. If say I have two tasks both assigned to GroupA and no person is assigned to these tasks I should only write one of the requests to the form so that each person in group will only be notified once. Similarly if I have two tasks with GroupA and one person is assigned to both of these tasks I should only write one of the requests to the form so that a filter can fire on submit and send the notification. I have tried adding two fields, one which holds the concatenated groups and one which holds an integer from a STRSTRC call which the Active links check before creating the requests in the from. Somehow I am not setting/checking these in the right sequence. Any help with this will be very much appreciate as I need to get this working by Monday :( Regards frex __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
