Subscription web help

Hi Dale,

If none of the types (fixed, super, flex, sub) are selected for a package in the setup, it’s a non fixed-seat package.  Essentially, this is the same as a flex package in the sense that it’s non-renewable and it has to be seated performance by performance, but it differs from a flex in that you do not go through the selection process to choose which performances the customer wants – it’s a fixed set of performances.

From the web side of things, NFS packages can be identified by looking at the super, fixed and flex indicators which will all be  ‘N’ for such a package.  Getting pricing and adding these to the cart is done in much the same way as flex packages.  The NFS package methods must be used.  So GetNFSPackageDetail would be used to retrieve pricing and AddNFSPackagePerformanceItem is used to add each performance in the package.  ValidateNFSPackages is then used to ensure the package has been completed before proceeding to checkout.  The key difference here is that the website would be ideally coded to not present the customer with the option to choose performances as they would have in a flex package.  Behind the scenes, it would simply loop through every performance in the package and add them in.  It sounds like your website may need to be recoded to handle that.  At the very least, I suppose you could have the website coded to recognize non fixed-seat packages like flex packages and send them down the same path, but the customer will be presented with the page to choose performances at which point they will need to choose them all which may be a little confusing.

From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Dale Aucoin
Sent: Thursday, July 28, 2011 6:45 PM
To: Gregg Stickney
Subject: [Tessitura Web Forum] Subscription web help

I have a number of 4 performance packages that are multi-venue where there are only 4 performances available.  Our web programmers are telling me they need to be coded as flex to make them work.  He're what the web guy says:

"The odd thing is that they are being reported as NOT flex, fixed, or super.  It’s like they have no package type which isn’t working correct via the API system.  We need these to be fully defined as either flex or fixed; prefer flex since we coded to this configuration." 

Am I missing something?  I mean I guess I can code them as flex but that adds an extra step for our box office that is totally unnecessary.

Any insights would be appreciated.

Thanks,
Dale 

You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hi Dale,

If none of the types (fixed, super, flex, sub) are selected for a package in the setup, it’s a non fixed-seat package.  Essentially, this is the same as a flex package in the sense that it’s non-renewable and it has to be seated performance by performance, but it differs from a flex in that you do not go through the selection process to choose which performances the customer wants – it’s a fixed set of performances.

From the web side of things, NFS packages can be identified by looking at the super, fixed and flex indicators which will all be  ‘N’ for such a package.  Getting pricing and adding these to the cart is done in much the same way as flex packages.  The NFS package methods must be used.  So GetNFSPackageDetail would be used to retrieve pricing and AddNFSPackagePerformanceItem is used to add each performance in the package.  ValidateNFSPackages is then used to ensure the package has been completed before proceeding to checkout.  The key difference here is that the website would be ideally coded to not present the customer with the option to choose performances as they would have in a flex package.  Behind the scenes, it would simply loop through every performance in the package and add them in.  It sounds like your website may need to be recoded to handle that.  At the very least, I suppose you could have the website coded to recognize non fixed-seat packages like flex packages and send them down the same path, but the customer will be presented with the page to choose performances at which point they will need to choose them all which may be a little confusing.

From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Dale Aucoin
Sent: Thursday, July 28, 2011 6:45 PM
To: Gregg Stickney
Subject: [Tessitura Web Forum] Subscription web help

I have a number of 4 performance packages that are multi-venue where there are only 4 performances available.  Our web programmers are telling me they need to be coded as flex to make them work.  He're what the web guy says:

"The odd thing is that they are being reported as NOT flex, fixed, or super.  It’s like they have no package type which isn’t working correct via the API system.  We need these to be fully defined as either flex or fixed; prefer flex since we coded to this configuration." 

Am I missing something?  I mean I guess I can code them as flex but that adds an extra step for our box office that is totally unnecessary.

Any insights would be appreciated.

Thanks,
Dale 

You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!