I was actually going down this route but I didn't want the child form to be "hard-coded" with a table field pointing to the parent, because there may be a variety of different parent forms that create these children. However, since you mentioned this it dawned on me that I can use Sample Data as the table data source and use the field I already have for the "related-to form name". Duh! Thank you all, I will most likely use this advice along with a push-fields active link to close the parent. Regarding the EULA, that was mostly tongue-in-cheek but I worry about inadvertently using a filter that does a push fields fields to another form-- it just seems like it is rarely *required*, as Active Links seem to be a sensible alternative and you never have to worry about the EULA when using them.

Brien

Carey Matthew Black wrote:
Brien,

If this is the business logic that your application needs....
"
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
"
then I think a push action is your best approach.

However, if you really have some need to check for other children (or
siblings if you prefer) then you could from the child record have a
table field of all children of the same parent. You could refresh that
table field (during After Modify Active Links) and see if any of the
children are "not closed". If so then you could do a push to the
parent record to close it.

So I really see no good reason to open the other record(or form) for
the user. The business logic sounds "automatic" to me.


Now if you are trying to force the user to decide/choose if the parent
needs closed then you could also open the parent and give the user a
message action explaining the condition.


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to