Do we need to raise use case approval for new defaulting and validation rules for redwood pages?

Summary:

Do we need to raise use case approval for new defaulting and validation rules for redwood pages?

Content (please ensure you mask any confidential information):

Earlier in autocomplete rules, if we had to create any new defaulting and autocomplete rules, we first used to submit use case with Oracle for approval and once approved only then we used to create the autocomplete rule.

We want to understand if that's the same case in VB. Since VB is not exact map from TDS and also the redwood process flow for pages have changed a bit, we need to create new defaulting and validation rules which were not existing as part of autocomplete approved use cases.