MENU
The AW Computing administrator team does significant amounts of work around process automation and ensuring data integrity. When an administrator created a new validation rule in production, the development team complained that their deployment to production failed.
What should be implemented to prevent this conflict from happening?
38 comments · newest first
ES
Essie
11 months ago
Definitely need to test changes before going live, no doubt!
OC
Octavio
11 months ago
Reviewing the setup audit trail is a good practice too.
BO
Bo
12 months ago
Surprised that they didn't have a shared testing environment already!
LU
Luis
12 months ago
I disagree, refreshing the sandbox daily seems excessive.
LE
Leonard
1 year ago
Testing changes in a shared sandbox is a must!
PA
Paul
1 year ago
I wonder if refreshing the sandbox daily would really help with this issue. It seems like a lot of work for something that might not be necessary.
IS
Isabelle
1 year ago
I feel like we practiced a similar question where testing in a sandbox was emphasized. It makes sense to do that here too.
AL
Alease
1 year ago
I'm not entirely sure, but I think reviewing the setup audit trail might help identify issues after they happen, not prevent them before.
EL
Elbert
1 year ago
I remember we discussed the importance of testing changes in a shared sandbox to avoid conflicts like this. It seems like the best option.
PU
Pura
1 year ago
I've seen this kind of problem before. Building automation and validation rules using screen flows could be a good way to avoid these conflicts.
DA
Darrel
1 year ago
I'm a bit confused on this one. What's the best way to ensure changes don't cause issues in production? Testing in a shared sandbox might be a good approach.
BE
Berry
1 year ago
Okay, let's see. I think the key here is to prevent the conflict between the admin team and the dev team. Maybe reviewing the audit trail could help identify the issue?
JA
Jamey
1 year ago
Hmm, this seems like a tricky one. I'll need to think through the different options carefully.
CA
Catina
1 year ago
Refreshing the full copy sandbox daily seems like it could help, but I'm not sure if that's the most efficient solution. I'll need to think this through carefully.
EM
Emelda
1 year ago
Relabeling, huh? I'm not totally confident that's the right answer. Maybe "Recategorizing" would be a better fit? I'll have to double-check the definitions to be sure.
CL
Clement
1 year ago
I think RDS doesn't allow direct access like that, but I'm not completely sure.
PE
Penney
1 year ago
Option C all the way! Testing changes in a shared sandbox is the equivalent of a dress rehearsal for your production deployment. That way, the admins and devs can work together to iron out any kinks before the big show. It's like the IT version of a musical theater production.
BR
Brandee
1 year ago
A: Totally, it's like a practice run before the real deal. Collaboration between admins and devs is key for a successful deployment.
PA
Paris
1 year ago
B: Yeah, testing changes in a shared sandbox seems like a smart way to ensure everything runs smoothly in production.
VI
Victor
1 year ago
A: Option C sounds like a good idea. It would definitely help avoid conflicts between the admins and devs.
CR
Cristy
1 year ago
I'm feeling option A. Reviewing the setup audit trail before making changes? Sounds like a great way to cover your bases and avoid those pesky deployment failures. Plus, it's like a little detective work, but without the danger of getting your code broken.
GI
Gianna
1 year ago
Hmm, Option B sounds like a lot of work. Refreshing the sandbox daily? Who has time for that? I'd rather just review the audit trail and call it a day. Less effort, same result, right?
JA
Jamal
1 year ago
D) Build automation and validation rules using screen flows.
GE
Geoffrey
1 year ago
C) Test changes in a shared sandbox.
TH
Theresia
1 year ago
B) Refresh the full copy sandbox daily.
LO
Loreta
1 year ago
A) Review the setup audit trail prior to changes.
JA
Jaleesa
2 years ago
Ah, the age-old battle between admins and devs. I'd go with Option D - build those automation and validation rules using screen flows. That way, everyone's on the same page, and the deployment shouldn't fail.
QU
Quentin
1 year ago
It's important for both teams to be aligned when making changes in production. Option D could definitely help with that.
FE
Felicitas
1 year ago
I agree, using screen flows for automation and validation rules seems like a smart way to prevent deployment failures.
YU
Yuriko
1 year ago
Option D sounds like a good solution. It would definitely help avoid conflicts between admins and devs.
AH
Ahmad
2 years ago
Option C is the way to go! Testing changes in a shared sandbox is the best way to catch conflicts before they hit production. Can't have those pesky developers ruining the admin's hard work, right?
SU
Sunshine
1 year ago
Testing changes in a shared sandbox can definitely help prevent conflicts between the admin and development teams.
HO
Howard
1 year ago
I agree, it's better to catch any issues in a shared sandbox rather than having deployment failures in production.
BA
Barney
1 year ago
Absolutely! It's important to catch any conflicts early on to prevent deployment failures.
RE
Rebeca
2 years ago
Option C is the way to go! Testing changes in a shared sandbox is the best way to catch conflicts before they hit production.
CA
Carrol
2 years ago
I agree with Beatriz. Option A seems like a proactive approach to preventing conflicts in production.
BE
Beatriz
2 years ago
I disagree, I believe option A is more effective. Reviewing the setup audit trail can provide insights into potential conflicts before making changes.
AM
Amie
2 years ago
I think option C is the best choice. Testing changes in a shared sandbox can help prevent conflicts.