Browser based Custom Tab

Hi folks!

We are looking to try and 'integrate' specific CMS editable areas within the custom tab.

After asking around, I found that it is possible to have our CMS do this, but what I'm trying to figure out now is the limitations from Tessitura on what can be passed in the URL to the CMS.

According to some of the documentation I'm reading about the CMS, I can only pass:
* current constituent id
* current tessitura usergroup
* current tessitura userid
* company name from t_defaults
* current sql login
* a report server url (not sure what this is for)
* ssrs folder path

Since we are looking to try to implement this in the custom tab for performances only (at this time), I see the need to also be able to pass at the least:
* the performance code or id
* the production id
* production season
(I mention production because of the way we are organizing our programs in tessitura, production/production season/performance all have a one-to-one relation in our setup. )

Is anyone aware if I can pass any of this information along as well as part of the querystring in the URL?

Parents
  • The <key> token will get you the appropriate value, depending on where in the system you are.  So, for example a custom screen in performance setup will substitute perf_no, whereas a custom tab in production season setup will substitute prod_season_no.  So if your url looks like this: http://www.mysite.org/season/performance.aspx?id=8863, then put this in TR_CUSTOM_TAB: http://www.mysite.org/season/performance.aspx?id=<key>

  • Thanks for getting back to me so quick Chuck.  Great to hear that I can pass the id from the performance custom tab, but is it solely limited to the performance id?  Is there any way to get the production id associated to the performance pushed to the URL?

    Being that we are setting up our production and performances on a one-to-one relationship, each performance would only ever have one production.

  • If you have to go to the database for other data for you custom tab page, you can always get the production number there:

    select    prod_no = b.prod_no
    from    t_perf a
        JOIN t_prod_season b ON a.prod_season_no = b.prod_season_no
    where    a.perf_no = <your perf_no>

     

  • Thanks Chuck.  It was pointed out to me a bit before your post that there is a SP that handles the pre-processing of the URL and that I might be able to use that to gather additional info for my querystring. 

    I guess I was wondering if there was something already pre-built but that works just as well.

    Now, I still have this other problem from my last post re: the error messages that I'm getting when trying to utilize the << >> keywords that tessitura uses as the replacement keywords.  Is this a known issue?  I'm posting here a sample of what I actually have set up in t_custom_tab table.

Reply
  • Thanks Chuck.  It was pointed out to me a bit before your post that there is a SP that handles the pre-processing of the URL and that I might be able to use that to gather additional info for my querystring. 

    I guess I was wondering if there was something already pre-built but that works just as well.

    Now, I still have this other problem from my last post re: the error messages that I'm getting when trying to utilize the << >> keywords that tessitura uses as the replacement keywords.  Is this a known issue?  I'm posting here a sample of what I actually have set up in t_custom_tab table.

Children
  • Nevermind, I spoke with Fran Hoylman and she finally cleared up the issue with using this feature.  Based on that info, I think the documentation for the custom tab browser feature needs to be re-written perhaps to be much clearer.

    It turns out (at least based on her example) that I can't enter in the full URL with querystring containing replacement keywords and that I need to setup a partial identifier of some fashion like .. www.92y=<<key>> as an example and that I should utilize the lp_preprocess_url sp in order to then take that further to generate the final URL that I need to pass on to the inline browser.