How to filter trace configuration features by LifecycleStatus?

[Andy_Morgan]

I must admit I'm confused on how to design trace configurations if you only want them to apply to water lines/devices/junctions that have LifecycleStatus = "In Service". I see you can filter Condition barriers, but what about simply filtering the whole set of what's used for the trace by an attribute?

Is there any way to exclude all the Abandoned/Removed/Out of Service and other Lifecycle status features, or are they somehow already excluded and I don't need to do anything? 

We were hoping to add a new Lifecycle status domain value for "Deleted". This would store special cases where we want to know historically that it was deleted. In any case we don't want trace to run on anything other than "In Service" features.

[RobertKrisher · Accepted solution]

Use a condition barrier to stop the trace, then add an output condition to only return the in-service features:

The Solutions team also has some tools available if you want to maintain your retired/abandoned/deleted features in a separate layer in case you only want in-service features in the network and all other features in the GIS but non-traceable.

[MobiusSnake]

Hi Robert, I'm curious about these tools you reference in your last paragraph, could you share some links?  Thanks.

[Andy_Morgan]

Ah, it's that simple. OK, thanks, I was focused on input rather than "output" conditions.

Does this mean we're filtering only the lines being traced? What about the water valves, in this case? What if we have a few LifecycleStatus = Removed valves, will those be ignored, too? 

[RobertKrisher]

Condition barriers apply to all the features in your trace unless you specify otherwise, so it is used to stop the trace at ALL out-of-service features. The output filter applies to ALL the features returned by the trace, so it will filter out the proposed features where the tracing stopped.

You can control which lifecycle status values are included and excluded by modifying your conditions.  You'll likely set it up to only include things that are in service or pending removal (if that's in your workflow/model).

[RobertKrisher]

@MobiusSnake you can find them, along with their documentation, in this GitHub repo: arcade-expressions/attribute_assistant at master · Esri/arcade-expressions · GitHub. For any questions, please follow up with @MikeMillerGIS from the Solutions team.