What is the best practice and number of environments for the ACS service? Does the development need to be deployed so workflow testing can be done in that environment? What is the standard flow to develop, test, and migrate the programs and workflow between environments?
Solved! Go to Solution.
Views
Replies
Total Likes
@Kevin_Lo, It's a best practice to keep stage environment, and prod environment. Stage environment where you can setup everything (profile extension resource, custom resources, programs, workflow templates, import templates, delivery templates etc.) and test with non-prod data to make sure everything looks good. One thing to remember make sure you use custom id's on the objects that you create on stage (for example: wkfImportData instead of WKF123). So that when you export and import a package in between environments it won't fail.
Take a look at this documentation page on how you can migrate data between stage and prod.
@Kevin_Lo, It's a best practice to keep stage environment, and prod environment. Stage environment where you can setup everything (profile extension resource, custom resources, programs, workflow templates, import templates, delivery templates etc.) and test with non-prod data to make sure everything looks good. One thing to remember make sure you use custom id's on the objects that you create on stage (for example: wkfImportData instead of WKF123). So that when you export and import a package in between environments it won't fail.
Take a look at this documentation page on how you can migrate data between stage and prod.
Hi Kevin,
Typically you should have 2 stage environments and 1 production. Where one of your stages should be dedicated for developments/PoC and the other for UAT or marketers to test complex/advanced before doing it in production
Views
Likes
Replies
Views
Likes
Replies