You can do a simple set fields in a filter to populate a field and then a 2nd
filter to check the contents of the field. No need to look at a table.
Example: Child form has Status and a Related_Parent_ID
Do a Set fields setting Display Only field on Parent = First
Matching Child_Entry_ID Where Child.Related_Parent_ID = Parent.Entry_ID and
Child.Status < "Closed" or Null if none found
If you get any value back then you know that there is still at least one open
child record.
Fred
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Brien Dieterle
Sent: Tuesday, October 06, 2009 2:19 PM
To: [email protected]
Subject: Re: send event after open window, midtier
**
Indeed I am getting directly to the child and may not even know about the
parent until I close the child. I was considering the push fields and using a
filter but I do not know how to perform the operations that I need within a
filter. I need to refresh a table and perform a colcount but those are purely
AL (client-side) operations right? I can't even use a filter to read column
fields from what I can tell. Thanks for any ideas.
Brien
Grooms, Frederick W wrote:
**
The Send Event is designed to send to an already existing window.
The question is how you are getting to this Child window. If you are coming
from the Parent window (and you open the child as a new window) then the send
event should do what you need. If you are coming directly from the child
(parent window Not open) then I would probably do something like a filter Push
fields to the Parent pushing something to a workflow field to trigger filters
set to check the count of open children and if 0 perform the close.
Fred
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Brien Dieterle
Sent: Tuesday, October 06, 2009 1:04 PM
To: [email protected]<mailto:[email protected]>
Subject: send event after open window, midtier
**
I'm hitting the open window, send event issue on the midtier. Couldn't find
much in the recent arslist to explain what to do exactly to get around it. The
workflow guide states:
"To solve this issue for the web client, create the workflow so that the parent
or child window is loaded, and then the send event action is executed."
That's a well and good suggestion, but I am not exactly sure how to actually
implement this. I have an AL that fires after-modify of a child form, that I
want to open a window to the parent form and THEN send an event to. I made
two separate ALs, one to open the window (exec order 0), and then another to
send the event (exec order 2)-- but it still doesn't work. It DOES work on the
user tool, and it DOES work on the midtier if I already have the parent form
open. Very frustrating. The only good thing is that the behavior is
consistent between Firefox and Internet Explorer :-).
Any ideas on how to implement this? My end goal is to have the parent ticket
modified such that when ALL children are closed the parent is also closed. I
couldn't think of a better way than to open the parent, send an event to
trigger an AL to: refresh a table field of open children and perform a colcount
and close the ticket if colcount=0
midtier 7.5p1
Thanks!
Brien Dieterle
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
