Tessitura v16
Donate2 | Stream2 | Flex2 Forms are fully tested and 100% compatible with v16
Are you ready for v16? We are!
Tessitura Customer Service Issues
After an organization converts to v16, we sometimes see the following error:
Error: Origin (Subtype) is required for a customer service issue if origins are defined for the activity type
Work with your Tessitura migration team to ensure this is setup correctly.
Key Details & Impact
It is important to note that while this error flags a problem with the Customer Service Issue (CSI), it does not stop the transaction.
- Order Success: Orders will still process successfully into Tessitura even if this error occurs.
- CSI Failure: Only the specific CSI associated with the order will fail to generate.
- Data Recovery: The error message you receive is comprehensive; it contains all the original CSI content, allowing you to manually recreate or troubleshoot the issue.
Root Cause & Resolution
This error typically triggers when the Activity Type in Tessitura has been configured to require an Origin (Subtype), but that field was left blank during the data transmission.
To resolve this, ensure that:
- The mapping in your integration includes a valid Subtype.
- The Subtype provided matches the requirements set for that specific Activity Type within your Tessitura configuration.
Since your API URL will be changing, there are a few steps that you'll need to complete in order to maintain the integration between your 2Account and Tessitura.
After your organization has upgraded to v16, please make sure you've updated all of your REST permissions. The Tessitura REST Permissions article provides a list of the resources required and is updated as we release new features and functionality. There may be new tools that your organization would like to use, so we recommend taking the time now to check that you're up to date.
How to update your 2Account Integration
After you upgrade from Tessitura v15 to v16 you will have a new API endpoint URL. If any other information for your REST user needs to be updated, keep that in mind and update as needed. Most likely, it will just be the URL for the API Endpoint.
Navigate to your Tessitura menu
Select Live Environment
Update the API & Credentials screen as needed for your v16 environment. Most likely, it will just be the API Endpoint.
Error connecting to v16
For Tessitura hosted organizations, if you get an error connecting to your v16 environment, make sure that you have correct URL for the API Endpoint entered.
This looks like a v15 URL:
https://...........restprod.tnhs.cloud/tessituraservice
This looks like a v16 URL:
https://...........webprod.tnhs.cloud/Tessitura/api
Update the Tessitura Version Dropdown from 15 to 16.
Save the Credentials (Yes, this is one of the few areas in your 2Account that does not auto-save!)
Run Diagnostics and Refresh the Cache
After a few seconds, you should get 3 green smiley faces for Credentials, Resources, and Tessitura. If you get a red frowning face instead, something wasn't entered right. Please double check the information entered in the steps above (it is most likely the URL that needs to be updated to the v16 format), make any changes, and try again!
Thats all you need to do! All of your Forms, Recurring Subscriptions, Registrations, Add On Donations, etc... will work as expected.
Moving forward, our focus will be on building new features leveraging the functionality that comes with v16. We will continue to support v15 as needed for bugs and security.
We are excited for what's to come! The future is bright for cart-free transactions using 2Account Forms.