Option D could work, but creating a validation rule to prevent the same Apex component from being committed in different environments sounds like a lot of extra work. Option A is probably the simplest solution.
I'm not sure about Option B - it says to remove Apex classes from the Exclude From Auto Resolve field in the Pipeline record, which seems counterintuitive.
Option A seems like the right way to go. Activating the Online Conflict Resolution feature and removing Apex classes from the Exclude From Auto Resolve field should help prevent overwriting in separate environments.
I'm not sure, but I think D could also be a valid option. Creating a validation rule to prevent the same Apex component from being committed in different environments sounds like a good preventive measure.
I agree with Cheryl, it makes sense to activate the Online Conflict Resolution feature in the Promotion record to prevent Apex classes from getting overwritten.
Nancey
7 days agoCruz
8 days agoErick
9 days agoDalene
12 days agoSharan
7 hours agoShawnna
6 days agoHildred
19 days agoEvan
20 days agoEun
27 days agoCheryl
1 months ago