You’re offline. This is a read only version of the page.
How do other organizations handle multiple development/configuration teams promoting solutions through environments without affecting each other? Our company has adopted a strategy to put every piece of configuration/dev into and solution and promote up from Dev > QA > UAT > Production environments. As a simple example. we are seeing problems with even a simple Form modification being affect by another teams work because they've made some changes to the fields on the same entity the Form was changed from.
What process to others employ to avoid these types of development/configuration collisions?
Regards,
James
Hi James ,
Maybe you can know about access teams:
The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.
Share
Report
All responses (
129
