Allow for Dirty Area Exceptions after a Reconcile

990
2
03-25-2022 11:21 AM
Status: Open
by Anonymous User
Not applicable

After completing an area of work we encourage our users to do the following:

  1. Save Edits
  2. Validate to ensure network is clean.
    1. Getting a totally clean area is a big deal for us. It is a good feeling to know you have a completely clean network after your edits.
  3. Reconcile and post

After the reconcile the dirty areas/ errors come back down. This leaves the editor to wonder if they in fact cleaned everything.  This leads to more explanation that dirty areas will continue to come back down until a full validate is run at night and a reconcile performed.

Ask: Allow the new Editor Inspection window to Ignore or Mark an area as an exception.  This will prevent editors from seeing so many dirty areas that we now just have to tell the editor to ignore.  With all the new technology the UN brings to the table--having to tell people to just ignore errors seems outdated.

 

2 Comments
AnneSanta_Maria1

100% agree. 

JakeJacobsAVA

In our workflow if the dirty area is purple (just dirty but not an actual error) then we know that we don't have to worry about it - when the batch validate topo runs, those will clear up. 

But to get fancier there could be a different status of dirty area if it came from a posted version vs if it was created in default. Or if the validate topology tool knew it was running against DEFAULT, it could set a flag?