This article is intended to help those who are interested, or have made the decision to upgrade their current Forms for Salesforce forms to our updated Native version. There are things to consider before making the move and this will provide you with a readiness checklist you can go through to make sure your upgrade experience is as smooth as possible and leads to no down time for your organization.
NOTE: Using the tips below will help reduce and prevent downtime.
- Once your account is upgraded to one of our Native tiers, all new forms you create will use our Native architecture.
- Forms created in your account prior to upgrading to a Native tier must be upgraded to Native individually.
- You do not need to upgrade all your forms at once. Forms on our non-native architecture will keep working as they were before the upgrade.
- You can leave a specific form to our non-Native offering if it depends on a functionality not currently available in Native.
- We strongly recommend duplicating your form before upgrading your form to Native.
- You must update any system embedding your form to use the new URL.
Readiness checklist:
If your form has an integration with Formstack Documents -Specifically, we refer to the integration configured through the “Document” tab in your form configuration.
- The Formstack Document integration must be rebuilt using our Documents For Salesforce package. You will need to save all data to Salesforce fields and then trigger the document to be generated after the data is saved.
- I understand that read-only fields behave differently in Native.
- Read-only fields in Native are not getting submitted with the rest of the form data. We recommend hiding the field but unchecking the read-only property of your field or building another automation to preserve the same behavior.
- You do not need to upload files larger than 2.5MB
- We offer a native-compatible integration that supports files up to 25MB. If you need these activated, please open a support case.
- Your payment provider is currently supported
- We currently offer Native support for PayPal and Stripe.
- If you wish to use our Paypal integration, know that you will need to update your account. You can find more information in our help article.
- Your payment field configuration uses a formula
- We recommend you do not upgrade your form to Native at this time.
- You can follow the progress of this project on our roadmap.
- You are using another provider (Authorize.net, IATS)
- We recommend you change your provider to Stripe or Paypal.
- If you cannot change provider, we recommend not upgrading your form to Native at this time.
- Native does not currently support Advanced Prefill.
- You can follow the progress of this project on our roadmap.
- We recommend you do not upgrade your form to Native at this time.
- I understand that the document generated using Native might differ from the document generated in our non-native version.
- Custom style and rules are not executed when generating the document in our Native edition. We recommend that you evaluate the results before proceeding with the upgrade.