Not sure why it does this, but it doesnt make sense that the software processes when these are changed although they are disabled.
To aid in productivity, especially for large corridors, the corridor should check if the Point Control / Parametric Constraint is enabled before sparking a Corridor process.
Agreed - the software clearly knows what is enabled or disabled, so just check that setting before starting to process again.
And frankly, the Process/Do Not Process should be a very, very top level Toggle. It should not be a "rule" to try and find where it can be locked or unlocked, or broken or ignored..... this whole rules business makes simple things overly complex sometimes.
Just right up there on the Corridor ribbon, there should be a simple yes/no or on/off toggle for Automatic Processing. Let the user decide with a single click if every change they are making needs to be processed right away, or if it can wait. They already have a button there to force process it on-demand.
Similarly, the corridor will reprocess with a simple name (description) change of a Point Control or Parametric Constraint.