Child table update does not trigger launch point for main object

Question

I have an automation script with the launch point SAVE, ADD, UPDATE, BEFORE SAVE of WORKORDER object.

When I make a change to any child table related to my work order and only the child tables, the launch point is not triggered. Its only if I have an update on the WORKORDER table itself that will trigger this launch point to run. This seems the same for custom objects or out of box objects.

Its deceiving because when I have modified my related tables, the save button for my work order opens up, making it seem like it will save the WORKORDER object, and not just the related tables.

What am I missing here? Is there a UI trick I should be doing? Should I just be moving my launch point to my related tables?

Thanks in advance!

Eric

Accepted Answer

Hi Eric,

When you update a child is added or updated, it does not cause the parent to be updated i.e. a change to the rowstamp. So you can't have a generalised script. So, yes you're fooled by the save icon.

You can have a script cause a change on the parent to then fire off the other script, but be careful that you are not causing a loop.

Maximo Open Forum