Comments on "when not revise all affected."
1. Need to carefully collect from the affected - as a CAD user familiar with the data. User who created the change request may have only added the drawing. May be models, WTParts to collect. May have to address family tables, envelope parts, skeletons, process assy's etc., etc. Wary of automated or programmatic revision, although less wary if collection is diligently done by a human first..
2.May not revise all in this particular case: Some objects being obsoleted at the same time as their replacement is being released. Objects to be obsoleted are moved from affected to resulting.
3. At times with family tables and tabulated drawings, may be necessary / desirable / policy to keep cerain Revisions in synch, so will have manually select to skip some Rev's.
May be more (I think we have had some over time) but can't think of any more at this point.