Tessitura Web Application usage in v16

We have a significant number of users whose Tessitura work is 90-100% defined by:

  • Constituent lookup
  • Lists
  • Extractions/Segmentations
  • Reports
  • Analytics
  • Reference Tables
  • Plans

Obviously I'm excited about the possibility of sending them to the Tessitura Web Application in v16.  The list of components now available is one thing, although the main thing that has prevented us from starting this in v15 was the lack of MFA login.

Has anyone on v16 been able to do this with a modest number of your users?  Any recommendations or pitfalls I should be aware of when planning for our upgrade?

Thanks,

Gawain

Parents
  • I am following because I am trying to get some of my users on. In my org I think only 2-3 people on staff could use web 100% of the time. The rest of us are too much in the day to day transactions and performance building to even try switching back and forth. 

    The biggest hurdle for us was a defect related to the Active Directory working on Tessitura Web (our staff that tried it kept getting an invalid credentials error). Also the MFA was a problem, but that's because my staff was trying to use DeepNet (their Citrix one) to open the web one. I use Google Authenticator for web to keep them separate, but that took my staff a while to figure out. 

  • I'm going to be polling people, but I'd say pretty much all senior staff using Tessitura, most of Development (only gift processing would require the client for them), most of Marketing (one user needs access to Production Elements from time to time), PR, Education, maybe Front of House (but they might need some Season Manager stuff). Box Office, Gift Processing, Finance and Systems would all continue to need client access for most work.

    Yeah, it looks like DeepNet doesn't work with it: my "fish" didn't, but my Google Authenticator account did.  Hopefully at the end of April I can start getting some users trying it out in our Dev environment to see if any other authentication problems crop up.

Reply
  • I'm going to be polling people, but I'd say pretty much all senior staff using Tessitura, most of Development (only gift processing would require the client for them), most of Marketing (one user needs access to Production Elements from time to time), PR, Education, maybe Front of House (but they might need some Season Manager stuff). Box Office, Gift Processing, Finance and Systems would all continue to need client access for most work.

    Yeah, it looks like DeepNet doesn't work with it: my "fish" didn't, but my Google Authenticator account did.  Hopefully at the end of April I can start getting some users trying it out in our Dev environment to see if any other authentication problems crop up.

Children
No Data