Form Template Migration Checklist

During a Youreka implementation, it is very common to need to move Form Templates from one environment to another. And because Youreka's Form Templates (and related information) are Salesforce data rather than metadata, they cannot be moved through change sets, or any other dev ops applications. Instead, they must be moved by using Youreka's very own import/export feature.

Consider the following scenario...

You are utilizing several sandboxes as you are implementing Salesforce, and each of those Salesforce environments has a dedicated purpose (development, testing, etc.).

It is not uncommon during an implementation to build Youreka Form Templates in a developer sandbox, and then have to move them to higher environments. Below is a checklist that can be followed to ensure success every time this is done.

1. Testing - Test Your Form Templates in the environment where they were originally built. Make sure you are testing while logged in as a user that will be interacting with the forms (not a system administrator!). Items to test might be...
   1. Form Design / Layout
   2. Field Link Behavior
   3. Field Level Security
   4. Conditional Display Logic
   5. Discovery Logic
   6. Custom CSS
   7. Automation triggered before, during, and after form save/submit
2. Versioning - Ensure you are using the proper form template versions.
   1. Are you organized with your form versions in the current org?
   2. Consider deactivating old and outdated versions of your Form Templates before migrating.
3. Exporting - Export the Form Templates from the testing environment. This downloads them to your local hard drive as JSON files, which can be imported to your target environment.
   1. Consider saving these JSON files in a meaningful place on your hard drive (perhaps a dedicated folder for the project. This will ensure that, in the event data is erased in the environment, your Form Template/s are recoverable.
4. Importing - Import the Form Templates into the new environment. Follow the steps in the hyperlinked article to ensure the Form Templates are migrating properly.
   1. Verify that field links aren't broken during the import process
5. Edit the Form Templates - edit the Form Templates in the event any of the following situations apply:
   1. Template images do not migrate, so if you have template images, those need to be manually reconfigured in the Form Template Builder.
   2. Restore any broken Field Links
   3. Restore any broken Discovery Logic
6. Publish the Form Templates - publish the form templates so they are no longer in a draft state.
7. Testing - Create a Form record for each form template in the new environment. Ensure the forms look and feel the same way they did in the original Salesforce environment where they came from. Make sure you are testing while logged in as a user that will be interacting with the forms (not a system administrator!).
   
   1. Form Design / Layout
   2. Field Link Behavior
   3. Field Level Security
   4. Conditional Display Logic
   5. Discovery Logic
   6. Custom CSS
   7. Automation triggered before, during, and after form save/submit
8. Review Mobile Admin Settings - Ensure that the Mobile Admin settings in your original Salesforce environment match those of your target Salesforce environment.
9. Review New Form Buttons - If you are using Mobile Cards and New Form Buttons ensure that your New Form Buttons recognize the new versions of the forms
10. Form Generation / Creation - If you have processes that create new forms (either through automation, buttons, etc... ensure that these configurations are equipped to recognize the new versions of the Form Templates.

Depending on your implementation, there might very well be more steps for testing. Each project will have its own unique migration process. However, the steps above should provide a foundation for items to consider when moving Form Templates from one Salesforce environment to another.