Hello all,
We are getting ready to run the iWave integration with Tessitura for our donor research data, but we're in a bit of a holding pattern at the moment due to the integration script being developed for individual organizations and not consortia members like us.
I'm curious to hear from anybody who might use the iWave integration in their daily use of Tessitura and get a sense of the pros and cons with how it's currently set up so that we can have these thoughts in mind before the integration happens and can be prepared for any weirdness that others may have experienced.
Appreciate any thoughts on this!
Thank you,
Brian
We simply created a local table where the iwave data is imported. We have a custom screen and custom devo header where the data is displayed, list elements, and nightly jobs where the information is considered while updating PLI and suggested asks for example.
Travis
**Dup post**
Hi Brian,
With the caveat that I'm new to iWave myself, the Seattle Rep does have the integration in place. Overall it's pretty user-friendly, but the biggest con I'm aware of is that accessing iWave within a constituent record automatically generates a new score for the patron and uses one of your screening credits, so should be approached with a bit of caution.
I inquired to iWave if the integration could be set up to manually screen constituents - in other words, to display the results of the last screening (if one exists) and only pull new data if we opt to do so. it doesn't sound like that's on the table, but if anyone else has other info or more experience with it I'm all ears!
Evan,
That is definitely good information to have about the integration using a screening credit automatically; at the moment our iWave use has been limited to our Managing Director (who has been using it for our current fundraising campaign) but we're wanting to expand our usage (and part of that involves integrating with Tessitura to have all the data under one digital roof).
Since the script for consortia users is currently being worked on, maybe there's some potential for us to mention the screening credit issue and find a workaround that makes it a little less tricky with regard to managing use of those credits.
Thank you!
Unknown said: We simply created a local table where the iwave data is imported. We have a custom screen and custom devo header where the data is displayed, list elements, and nightly jobs where the information is considered while updating PLI and suggested asks for example. Travis
Travis,
It sounds like this isn't the "official" integration for iWave and Tessitura; is your SQL for this available to be shared or not? (Completely understand if it isn't!)
Also, are you in a consortia setting or an individual organization?
Do you all run into a similar issue as articulated by Evan with regard to credits being used on every view in your setup? If your alternative setup doesn't have that downside, we might have to consider that over the official deal.
Hello,
Currently we have slated two upcoming updates for the iWave integration with Tessitura. The first which I am working on currently is to bring consortium capabilities into the integration. The second phase will bring the ability of bulk scoring , meaning that you will be able to send data out for iWave to be scored and once scored bring that data into Tessitura for use in lists and outputs. The last part of this phase 2 round will be an update to the custom screen so that each time you visit it a scoring credit is not deducted.
Currently when you visit the iWave custom tab on a customers record the scoring data is stored in a local table that can be used with the keywords for lists and output sets.
Thank you kindly,
Jon
Jon,
That sounds awesome; sounds like I'm getting us ready for iWave at exactly the right time!
I could get everything together for you, but it seems like it may not be worth it since Tessitura is catching up. Should you want it email offline.