V.12 in Consortia

Hi all,

We are a consortium that went live with v12 in January. Most of the issues we experienced were not necessarily related to being a consortium; however, here are two that I remember that may be worth looking out for:

1.       We spent some time mapping solicitors to workers.  I may have just made an error somewhere along the way, but somehow, all of our workers ended up tagged with both a control grouped worker type and one that was not control grouped. Consequently, until we fixed this, everyone in the consortium was seeing all workers – even those that did not apply to their company.

2.       We have had issues with some orders causing a Tessitura crash because the order had a control grouped email address linked to it, but it was an email address the particular person loading the order did not have access to. I can’t recall what the previous v11 behavior was, but it definitely was not a Tessitura crash. I believe those issues will be fixed in 12.1. If you are a consortium with some shared box office functions, this is one you may potentially run into.

If I think of others, I’ll post another reply to this thread.

Thanks,

David

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Eric Williams
Sent: Monday, May 12, 2014 12:06 PM
To: David Frederick
Subject: Re: [Tessitura Technical Forum] V.12 in Consortia

And we're very grateful for the help! 

My boss is asking me whether the issues we've encountered are attributable to our consortium environment...hence my query.  To complicate matters, our consortium has several control groups and we are also dealing with the results of past customization.   

Many of our problems appear to have been related to security objects....once permissions were assigned, it was possible to fix issues.  

Price types have had a few hiccups, some related to security and one issue still being diagnosed.   

Acknowledgement letter reports needed to be tweaked because "Mail Purpose" is replaced by "Address Purpose."  Not a difficult fix but necessary. 

We ran into a problem with v.12 playing well with TNEW and web sales went offline briefly....again, the problem was quickly dealt with but not without some angst. 

There have been some login and report server difficulties, quickly addressed by RAMP.  We've also encountered some problems with getting some pre-Tessitura legacy data (ticketing, contributions) to display.

We ran TIM several times and did a lot of testing prior to the upgrade.  We thought everything was ready for the upgrade.  We expected some glitches. Just wondering if our experience was because we're in a consortium.