B) Activate the Online Conflict Resolution feature by removing Apex classes from the Exclude From Auto Resolve field in the Pipeline record. That's the way to go, I'm sure of it!
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.
Janet
1 days agoNancey
16 days agoCruz
17 days agoErick
18 days agoDalene
21 days agoRasheeda
24 hours agoAlida
3 days agoEdna
4 days agoSharan
9 days agoShawnna
15 days agoHildred
28 days agoJarvis
23 hours agoEvan
29 days agoEun
1 months agoCheryl
1 months ago