Hello,
I'm trying to understand what are the best practices when working on a project that has Omnistudio components (FlexCards, IP, Omniscript, etc.). Is it advisable to have a scratch org for every developer when doing their customisation or a common Dev Org or one dev box per developer? What is recommended? What are the challenges and considerations of different approaches especially from omnistudio point of view?
Thanks,
Neelesh
#Omnistudio #Deployment #SFDX CLI #Devops #Salesforce Developer
Recommended Approach - Development Org with Version Control:
Use a single Developer Org shared among your development team. This allows for:
Collaboration: Developers can easily share and test Omniscripts, FlexCards, and other components.
Consistency: Ensures everyone is working on the same codebase and avoids versioning issues.
Implement a robust Version Control System (VCS) like Git:
Track changes, revert to previous versions if needed.
Manage concurrent development and avoid conflicts.
Challenges of Scratch Orgs for Omnistudio:
- Limited Functionality: Scratch orgs lack features crucial for Omnistudio development, such as:
- OmniStudio Metadata API: This API allows deploying and retrieving Omniscript components between orgs. Not available in scratch orgs.
- DataRaptor Actions: DataRaptor actions are custom code snippets used within Omniscripts. Scratch orgs lack the security model to support them.
- Deployment Overhead: Frequent deployments from scratch orgs to a testing or staging org become cumbersome and inefficient.
Hope this helps
