To the specific issue at hand, what kind of tracing issues are you running into, and what kind of network are you building this on? There's every chance that this isn't actually the issue that it appears to be, and you're band-aid-ing an entirely different problem. It might be helpful to explain your current and planned architecture(s) a little bit more, first.
That said. Assuming the stated goal is valid for argument's sake, I see three approaches:
Approach 1:
My initial gut reaction here is to dig into Attribute Rules for this. I haven't gone down that rabbit hole enough to say whether they can trigger creation of a separate asset like this, but that would be my first stop. Though, a word of caution: Once you enable Attribute Rules in a Feature Class, that FC can no longer be opened in ArcGIS Desktop.
Approach 2:
If Attribute Rules can't do this, then you could theoretically do it with a standalone python script set up on a task scheduler with a listener component, but there's going to be a major issue of time delay, and it's a little clunky. In short:
- User creates Outfall Asset.
- [Some time interval passes]
- Python script on task scheduler triggers, and goes looking for new Outfall Assets; it finds our Asset from Step 1
- Script creates the linked Structure Asset.
Approach 3:
The most foolproof way to do this, though, would likely just be to make the user manually create both Assets and enforce a topology to make sure they don't miss one. The only thing the software is doing here is pinging an error if you have an Outfall floating unattached. Getting the topology to ping an error in the other direction (missing an Outfall Asset) is a bit more complex.
------------------------------
M Reed
"The pessimist may be right oftener than the optimist, but the optimist has more fun, and neither can stop the march of events anyhow." — Lazarus Long, in Time Enough for Love, by Robert A. Heinlein
