We have followed best practices/recommendations to ensure strongly typed model classes are ONLY built in the Local environment, and no models are created in any other environment. This still creates an issue because there’s nothing preventing a user from adding/updating/deleting a document type in the other environments. This, more often than not, creates conflicts that can take hours to resolve, especially if the one resolving it was not involved in the changes that caused the conflict and has to track things down to get all environments into the correct state to resolve the issue.
Ideally, there would be some sort of configuration setting that would also prevent document type updates in a given environment, since it doesn’t make sense to allow that EXCEPT in the lowest environment (Local). We can’t be the only ones to encounter this issue, but for the life of me, I can’t find any documentation on how to prevent this, and I’m surprised there’s not a toggle in place already.
How does everyone else handle this scenario?
