In my previous blog, we explored how to set up a Route Template and configure a rule to automatically generate a Route when a Document's maturity state changes. 
In this case, a route is created only if a rule was configured for the specific maturity transition and the Document met the defined criteria. Otherwise, the Document could be promoted without restrictions.

In this blog, I will introduce a new setting that determines whether a Route is mandatory for a maturity transition when a rule is applied. 

The setting ‘Route mandatory for maturity change of all objects of a type on 
which rule applies’ is available under the ‘Route Management’ section in the ‘Collaborative Spaces Control Center’ app.

By default, this setting is set to NO, meaning a route is not required for a maturity transition with a rule. 

When set to YES, a route becomes mandatory for a maturity transition with a rule. 
If the Document does not meet the criteria defined in the rule, its promotion will be blocked.

The following diagram and video illustrate how the promotion of a document varies based on the presence of rules, criteria fulfillment, and setting configurations: