Extension SDK Best Practices/Tips and Tricks

qHubert · 2022-10-26T20:05:04+00:00

We have been working behind the scenes on the Extension SDK for a while now and there are a few things that have come up a number of times. This post will be geared towards aggregating best practices, so if you have any good tips or tricks while you are building, share them here with the rest of the community!Security:Security is our top priority and with the introduction of the SDK, we’re allowing you to integrate and introduce your own systems into the Qualtrics platform with relative ease. This means that we’re now sharing the security responsibilities. Be mindful of how your services are exposed and how you choose to show any embedded dashboards within your own systems. We support four authentication schemes: OAuth 2.0, Basic Authentication, API Key, and SFTP. Our recommendation is to use OAuth 2.0 as it has multiple advantages over the others. DevelopmentDuring development, use npm start or npm run build-dev because it generates unminified versions of your code. This makes it easier to walk through with break points. When you’re ready to submit, use npm run build. Develop against your sandbox brand, not production brand.Integration into QualtricsSince you’re building for the Qualtrics platform and other Qualtrics customers, you will need to abide by the Qualtrics Style Guide to maintain a common look and feel. Make sure you follow it!Certification:Certification is for our partners who intend to share their extensions with the community at large. If you’re reading this and don’t fall into that category, but are interested, let us know by filling out our survey!The policies really are a checklist. Make sure you are able to satisfy every one of the relevant policies. We’ve seen a few customers trip up on 4.18 specifically. Since the extensions are used as part of the Qualtrics platform, you need to ensure that the whole Qualtrics userbase can use your extension. This means additional compatibility tests you may not have needed to run in the past. It can take up to 4 weeks for you to reach the front of the certification line. Plan to have your extension certified well before your planned release date.

Extension SDK Best Practices/Tips and Tricks | Experience Community

Sign up

Login to the Community

Scanning file for viruses.

This file cannot be downloaded