Test your extensions after uploading a user token
If you've submitted a user token to us and been prompted to remove our user ID from your app, this is a step you don't want to miss.
Over the years, Quickbase Extensions has used four important Quickbase features to integrate our extensions into customer apps: email notifications, automations, webhooks, and actions.
Since we've moved to a more secure method of processing our extensions (user tokens), we're requesting that all of our clients remove our service account, qbtools, from their apps.
As mentioned, we've used Quickbase's features to help configure extensions properly. By doing so, we became the owner of that specifically made feature in your app. (We could own multiple features in a single table.)
Before testing your extensions
Before testing your extensions, change ownership from qbtools to your account or a teammate's account. Learn about changing ownership.
Test extensions after changing ownership
Test your extensions in each app
Navigate to the page or pages where our extensions are installed.
Once you find the field that runs one of our extensions:
Exact Forms Plus, XL Docs, PDF Merger, PDF Stamper, Courier, and Docusign will likely have a button you select to run and test your extension. Run this with a test record so your client doesn't receive something by mistake.
For any extension triggered by an event, such as a change in a field elsewhere in your form that causes the extension to generate a result:
For these extensions, we likely set up one of the four features mentioned earlier (email notifications, automations, webhooks, or actions) to cause this change to trigger. If you followed the changing ownership steps correctly, you'll find that these triggers still work.
If you're unsure how to test your extensions, or where they're installed, submit a technical support case.