You've just completed your TaroWorks training and you're ready to start setting up your Jobs and Forms. You know you'll go through some iterations before handing them over to your mobile users, so you may wonder whether you should set everything up in a Sandbox or in Production environment. While it is always a best practice to test functionality in your sandbox org, it is recommended to build out your Jobs and Forms in Production when possible.
When you create Jobs and Forms using TaroWorks in Salesforce, you are not creating metadata, but rather object records. This means that TaroWorks Jobs cannot be copied into sandboxes or migrated to production via changesets. If you first create your Jobs in a sandbox, you will eventually need to migrate that data into production using a third party tool.
When building and testing in Production, you can assign test records only to your test mobile user(s) so that you can ensure that no live production records are affected. You can also use Assigning Jobs to Groups to ensure that only the testers have visibility to your Jobs until they are ready for launch.
- Jobs and Forms cannot be deleted. When Jobs and Forms are closed they no longer appear on mobile devices, however they can still be found in Salesforce and can be cloned.
- If you're uncomfortable with any automations in your org, and how they may behave as a result of syncing a TaroWorks Jobs, you may want to test these Jobs in a Sandbox before migrating to Production.
If you have any questions please reach out to firstname.lastname@example.org