Developer Discussion - Recent Threads

Developer Meeting and Sessions Submissions Reminder

Shelly Xiong (they/she) — Wed, 03 Apr 2024 16:37:32 GMT

Hi everyone,

Reminder! This meeting is happening Friday!

You are invited to our next meeting on 5 Apr 2024, 10:30 AM - 11:15 AM Central Time (US & Canada).

Join us for our next Developers Tessitura Community meetup! Our guest speaker will go over the development lifecycle followed by some Q&A.

Presenter: Chris Hipschen (Director, Software Engineering Quality and Infrastructure)
Topic: Tessitura Core Application Software Development Lifecycle
Description: An overview of the Tessitura core application value stream mapping, described as the process to release new functionality or a defect resolution.

The presentation and Q&A will be in the first 30 mins but feel free to stay and chat afterwards and to join us in whatever way you feel most comfortable, whether with your camera on or off and through chat only.

Submit a presentation proposal for TLCC Washington, D.C.

There is still time to submit a presentation proposal for TLCC Washington, D.C.

Do you wonder what topics you might present this August? Anything you are doing with Tessitura to make your day-to-day and season-to-season life easier is guaranteed to interest others. Nothing is too small or too grand to propose.

Below is a list of topics to inspire your session proposal. If any of these sound familiar, then we’d love to hear from you. And if you have an idea that’s not on this list, we're happy to hear that as well!

How...

Your education or finance department uses Tessitura
You've transitioned activities and roles to Tessitura v16
Your website provides self-service opportunities
Your group sales process was made more efficient

What...

Integrations you've built with your Tessitura system
HTML templates you've customized
Customer journeys you've created for your organization
Dashboards you've built using the Interactions cube
Successful strategies you've used to combat fraud and/or chargebacks

Proposals may include one to two presenters, either from the same organization or from different organizations. Presenters and panelists selected for community-led sessions will receive a 25% discount on conference registration.

We’re actively seeking speakers who identify as Black, Indigenous, Latinx, or a person of color; gender-nonconforming or LGBTQIA+; having a disability; neurodivergent; and other historically excluded identities.

Session submissions are due by Wednesday, April 10 at 11:59pm PDT. Selected presenters will be notified by Friday, May 15.

Submit Your Idea

Next Developers Community Meetup (Tessitura Guest Speaker!)

Shelly Xiong (they/she) — Thu, 21 Mar 2024 19:53:53 GMT

You are invited to our next meeting on 5 Apr 2024, 10:30 AM - 11:30 AM Central Time (US & Canada).

Join us for our next Developers Tessitura Community meetup! Our guest speaker will go over the development lifecycle followed by some Q&A.

So please feel free to join us in whatever way you feel most comfortable, whether with your camera on or off and through chat only.

Best regards,

Shelly, Chris, and Marcus

TLCC Washington, D.C - Developer Track - Call for Presenters

Julie Rosenthal — Mon, 18 Mar 2024 20:39:36 GMT

Hello, Developers!

The call for presenters for TLCC Washington, D.C. is now officially open!

We invite everyone to submit presentation proposals, no matter your experience with Tessitura. Presenters will receive a 25% discount on the conference registration fee, and support will be available to help you in preparing your presentation.

TLCC Washington, D.C. will once again feature a Developer Track. When submitting a presentation proposal for the Developer Track, please select either IT and Software Development or Digital and Web as the primary interest area.

Session proposals are due by Wednesday, April 10th. Learn more and submit your ideas.

Pricing Rule Message Only Image Size

Jane Trembley — Wed, 28 Feb 2024 23:00:46 GMT

Has anyone had any luck changing the image size for message only pricing rules? Is this something based on your TNEW site templates? We are stuck with a rectangle that looks awful on mobile. Additional question - has anyone been able to have different image sizes based on mobile or desktop purchase path? For us, we cannot differentiate.

Removing Change Log Comments from Impresario SQL Objects

Julie Rosenthal — Wed, 31 Jan 2024 16:19:02 GMT

Tessitura will be discontinuing the maintenance of change log comments in SQL objects, and existing change log comments will be removed incrementally over the next year or so. Please note, that Description, Parameter, and Example comments will still be created and updated, and we do not intend to remove comments from custom/local objects.

This change aims to prevent inaccuracies and inconsistencies. The majority of SQL changes do not include change log comments and existing comments are often incomplete, incorrect or outdated, leading to confusion.

RE: Removing Change Log Comments from Impresario SQL Objects

Julie Rosenthal — Wed, 31 Jan 2024 16:42:11 GMT

Currently, there are no plans to publicly document changes beyond the existing comments available in release logs.

RE: Removing Change Log Comments from Impresario SQL Objects

John A. Moskal II — Wed, 31 Jan 2024 16:25:21 GMT

Or at least a central repository of documentation on the actual changes being made if not commentary on them? I also find looking at the changes to be useful when creating custom elements.

RE: Removing Change Log Comments from Impresario SQL Objects

Nancy Sheleheda — Wed, 31 Jan 2024 16:22:12 GMT

Hi Julie, Will there be a central repository accessible to members where we can continue to review these comments? I do find them occasionally useful when spinning off custom reports.

RE: Swagger definition file empty for v16

Gerald Stockinger — Wed, 06 Dec 2023 14:45:30 GMT

Amazing!! Thanks.

Swagger definition file empty for v16

Gerald Stockinger — Wed, 06 Dec 2023 11:54:14 GMT

Hi everyone,

We are relying on the swagger definition for creating our client for Tessitura v16.

Unfortunately the swagger file provided in the API documentation seems to be empty (0 bytes): https://www.tessituranetwork.com/REST_v160/Tessitura/SWAGGER/16_0_10/SWAGGER.JSO

Who should we contact about this?

Thanks a lot,

Gerald

RE: Swagger definition file empty for v16

Cyrus Collier — Wed, 06 Dec 2023 14:34:45 GMT

Good news! I got a quick reply from Michael Flaherty-Wilcox on Slack that this should be fixed in v16.0.11, due to be released later this month.

RE: Swagger definition file empty for v16

Cyrus Collier — Wed, 06 Dec 2023 14:11:48 GMT

Yep, that's the same error I'm getting in our v16 test environment.

RE: Swagger definition file empty for v16

Gerald Stockinger — Wed, 06 Dec 2023 13:25:06 GMT

Thanks Cyrus Collier.

I tried in on our v16 test environment but run into another error there:

"Ambiguous HTTP method for action - Tessitura.Controllers.BookingsController.Download (Tessitura). Actions require an explicit HttpMethod binding for Swagger/OpenAPI 3.0"

RE: Swagger definition file empty for v16

Cyrus Collier — Wed, 06 Dec 2023 13:09:54 GMT

I also have this issue, and can't work on generating a v16-compatible client yet because of it. The v16 OpenAPI schema URL was working a year ago, but then has been broken since April or May of this year. I currently have a support ticket open about it, but there has been no movement on it since May. However, I was told that in order to access the v16 schema, you need to use an actual org host instead of the generic public link, i.e. abcorg.tnhs.cloud/.../swagger.json. However, in my case this generates an error and hasn't been address yet.

I'm going to follow up on my ticket today, since it's encouraging to know I'm not the only one who cares! Feel free to submit your own support ticket too. I'll also start a chain on Slack to see if that might get the attention of Tessitura devs.

RE: CORS errors when accessing the API

Alex Gorski — Wed, 15 Nov 2023 20:23:57 GMT

Think about making the API call from your WP server using PHP instead of directly from the client's front-end.

CORS errors when accessing the API

Josh Bell — Wed, 15 Nov 2023 20:16:52 GMT

Greetings,

I'm trying to access the API from my wordpress site using PHP and AJAX. Our client has setup a TNEW site and we have a live and staging tessitura instance. Whenever I hit the API I get a CORS error. Here's the error:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at... (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 405.

I'm trying to hit the /api/Diagnostics/Status endpoint which shouldn't require any authentication. I don't want to print the entire url for security purposes. I'm sending this from a local instance on my machine with the same domain name as our live site. I've been told my domain has been whitelisted. Is there anything else I need to do to send the request? I've also tried using an "Authorization: Basic ..." header with the hashed key following this format "admin:admin:location1:pwd123", but from my understanding I don't need that header when accessing this endpoint.

I'm using this ajax code:

$.ajax({
 url: url,
 headers: {
 'Content-Type': 'application/json',
 },
 crossDomain: true,
 xhrFields: {
 withCredentials: true
 },
 }).done(function( data ) {
 if ( console && console.log ) {
 console.log( "Sample of data:", data.slice( 0, 100 ) );
 }
});

Custom Screens - v15 - ability to change token keys

Vivek Mittal — Wed, 15 Nov 2023 00:40:25 GMT

Hi,

I'm trying to implement a browser based custom screen onto the constituent pages to show information from an external system. The external system is a vendor provided out of the box solution that takes in a Sync_ID key with the value being the constituent id. The Tessitura docs specify that they pass in "key" in the query string with the constituent id as the value. Is there any way to rename key to sync_id?

The solution also requires an oauth token to be passed in that expires every 20 minutes. Is there any way for Tessitura to generate that token and also pass that in as part of the URL to the browser based custom screen?

Regards,

Vivek

RE: Custom Screens - v15 - ability to change token keys

Vivek Mittal — Wed, 15 Nov 2023 01:14:59 GMT

Thank you. That was a simple answer. I was thinking the URL was customwebapp.com/?key=xxxx. I thought the parameter key was key; not that the value was <<key>>.

For the second part, I'm thinking along the same lines as you. Have a middleware component that generates the token every x minutes and then updates the URL in the DB with the token. However, not sure how that would be impacted by things like caching on the Tessitura app side - would it reload the URL every time the screen is refreshed so that a new updated token would be used.

An alternative I was thinking was to develop an intermediary web app hosted somewhere locally that will receive the request from Tessitura and then, retrieve the token and invoke the final end-point. Something like a proxy app... but that adds complexity in terms of another hop and finding somewhere to host it.

Cheers,

Vivek

RE: Custom Screens - v15 - ability to change token keys

Graham Wright — Wed, 15 Nov 2023 01:06:26 GMT

Your first question should be fairly straightforward. You can specify whatever query parameter you like when you pass the key to your web app by just putting a uri like customwebapp.com/?sync_id=<<key>> in the custom screen setup panel.

I'm not aware of a way to generate and pass an Oauth token via the custom screen feature. My first thought would be that you might need to build a custom middleware app between Tess and your external system to handle Oauth, but I'm also fairly new to working with the custom screens, so others might know more.

Graham

Webinar this week: Overview of Tessitura's developer landscape

Gill Tasker (she/her) — Mon, 23 Oct 2023 15:54:01 GMT

Calling all developers! This session will provide an overview of how you can (and cannot) customize and extend a Tessitura system. We'll describe the architecture of a Tessitura system. Next, we'll review which functions to use when developing apps, screens, reports and other custom utilities.

After this session, you will understand:

The high-level architecture of a Tessitura system
The ways in which developers can customize the Tessitura platform
Which other customization options are discouraged, deprecated, or not allowed

This is the first in a series of six webinars reprising our popular Developer track presentations from TLCC Orlando in 2023. The series will introduce current and aspiring developers to the most common methods of creating Tessitura customizations. Learn about using the API for custom websites or integrations, developing web-based custom screens and creating SSRS custom reports.

Register Now for the Wednesday webinar (12-1pm EDT) - we look forward to seeing you there!

Developers Community Meetup (Sept 27, 2023) - Casual Networking

Shelly Xiong (they/she) — Mon, 25 Sep 2023 16:56:47 GMT

Reminder! This meeting is happening tomorrow!

You are invited to our next meeting on Wednesday Sep 27, 2023 11:00 AM Eastern Time (US and Canada).

Register For The Event

Please join us for a casual networking event. We will give updates on group activities and afterwards break out into small groups to get to know each other.

We look forward to seeing you!

Shelly, Chris, & Marcus

July 19th - Developer Community Meetup Follow-up

Julie Rosenthal — Fri, 28 Jul 2023 18:10:40 GMT

I just wanted to thank Dmitry for a great presentation last week and point the Developer Community to some resources Tessitura offers on a few of the items Dmitry talked about. Please let me know if you have any questions.

Session Sharing –

Documentation
- V16 - https://www.tessituranetwork.com/Help_System_v160/TNEW/Admin/Configuration/Shared-Session.htm
- V7 - https://www.tessituranetwork.com/TNEW_7/TNEW.htm#Topics/Shared_Session.htm
Shared Session Solution - https://bitbucket.org/TN_WebShare/webpro-session-sharing-sample

Instruction and examples on how to style TNEW –

Training Video - https://www.tessituranetwork.com/en/Items/Videos/Training/TNEW_Templates
Documentation
- V16
  - Site Templates - https://www.tessituranetwork.com/Help_System_v160/TNEW/Setup/Self-Hosted_Templates.htm
  - Site Map: https://www.tessituranetwork.com/Help_System_v160/TNEW/Site_Map.htm
- V7
  - Site Templates - https://www.tessituranetwork.com/TNEW_7/TNEW.htm#Topics/Self-Hosted_Templates.htm
  - Site Map : https://www.tessituranetwork.com/TNEW_7/TNEW.htm#Topics/Site_Map.htm

Thanks,

Julie Rosenthal

Software Engineering Manager, Tessitura Network

Next Developers Community Meetup (Tessitura API) July 19th

Marcus Johnson — Fri, 23 Jun 2023 12:51:39 GMT

You are invited to our next meeting on Jul 19th, 2023, at 01:00 PM Eastern Time (US and Canada).

We will have Dmitry from FiveJars will be presenting on his experience utilizing the Tessitura API. This presentation is intended to cover the following.

How the Tessitura API can be utilized to create a customized ticket purchase path
Mount Vernon migration process to TNEW
The open-source solutions utilized
How an open-source community is key to advancing any closed ecosystem.

We look forward to seeing you! Register here.

Shelly, Chris, & Marcus

RE: Next Developers Community Meetup (Tessitura API) July 19th

Gill Tasker (she/her) — Wed, 12 Jul 2023 10:50:11 GMT

Thanks Dmitry - for anyone wanting to join the meetup next Wednesday 19th, please RSVP in advance here. Looking forward to it!

RE: Next Developers Community Meetup (Tessitura API) July 19th

Dmitry Drozdik — Wed, 12 Jul 2023 10:37:46 GMT

Hello everyone,

I will be speaking in front of the community next week. Welcome, everyone, to listen and hopefully learn something new. Today, I would like to share some additional details:

During this session, I will be sharing my experience working with Tessitura on the Mount Vernon ticketing system and how we successfully integrated it using the Tessitura API.

I will provide examples of how the Tessitura API can be utilized to create a customized ticket purchase path. Additionally, I will discuss our migration process of a portion of the ticketing system to TNEW and the valuable lessons we learned throughout this migration.

Furthermore, I will delve into the current state of the project, the open-source solutions we utilized, and why I strongly believe that an open-source community is the key to advancing any closed ecosystem.

Thank you, and welcome.