Gateway-to-TIM Release Notes

Avatar
FreeWheel
Follow

 

Version 3.1.3 (8/13/2019)

  1. The Industry Type will now be set based on the Client Default when orders are imported via Gateway. This feature requires OneSUITE v6.3.0 or higher.
  2. Fixed a parsing issue with DAI/Dynamic Ad Insertion Network Code.
  3. Out of disk space error will now be handled in a way that will prevent corruption of entity cache file.
  4. Modify GW2TIM AQM to process and log OneTIM orders with no Lines (LineSet).

Version 3.1.2.4 (11/26/2018)

  1. MVPDINT-3085 : Modify GW2TIM AQM to process and log OneTIM orders with no Lines or LineSet.
Installation instructions for Gateway-to-TIM v3.1.2.4 as update to existing v3.1.2.3 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 3.1.2.3 (10/02/2018)

  1. MVPDINT-2960 : In addition to updating OneTIM order with the correct Advertiser, assign Default AE of that client to the Order's Primary AE.
Installation instructions for Gateway-to-TIM v3.1.2.3 as update to existing v3.1.2.1 and v3.1.2 install:
  1.  Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 3.1.2.2 (06/20/2017)

  1. MVPDINT-1521 : Market-specific mappings are not being updated in OneTIM after Gateway-imported order is created
Installation instructions for Gateway-to-TIM v3.1.2.2 as update to existing v3.1.2.1 and v3.1.2 install:
  1.  Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 3.1.2.1 (07/07/2016)

  1. MVPDINT-440 : Remove name/string look-up when mapping does not exist
  2. MVPDINT-302 : Users need logic for inactive agencies, rep firm, advertisers
Installation instructions for Gateway-to-TIM v3.1.2.1 as update to existing v3.1.2 install:
  1.  Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 3.1.2 (05/08/2015)

  1. OneTIM-compatible version
Installation instructions for Gateway-to-TIM v3.1.2. as full install for OneTIM V 4.4 or higher have been provided separately.

Version 2.7.4 (5/07/2015)

  1. TIM Entity Searches by name with square brackets return no results (#55320)
  2. Entity Search should fail when entity is not found in TIM (#55425)
Installation instructions for Gateway-to-TIM v2.7.4 as update to existing v2.7.1 through 2.7.3 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.7.3.1 (04/02/2015)

  1. Additional logging was added to troubleshoot errors around SearchAgency during the EntitySearch in TIM. Additional exception handling was added to resolve the issue.

Version 2.7.3 (02/13/2015)

  1. Update AE in TIM if AEID is present in the SCX2 (#54059)
  2. Add NetPack AE and assignment if order is flagged as a NetPack (#52764)
Installation instructions for Gateway-to-TIM v2.7.3 as update to existing v2.7.2 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Add the following new key to the TIM_GatewayActionMonitor app config file:
  1. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.7.2 (01/16/2015)

  1. Add new GAM configuration setting for populating the Estimate Description in TIM using the description from the SCX or current logic (inbound est desc]-[inbound (agency/rep) advertiser name]-[yyyy-mm-dd]) (#53024)
Installation instructions for Gateway-to-TIM v2.7.2 as update to existing v2.7.0 or v2.7.1 install:
  1. Stop the TIM_GatewayActionMonitor service
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Add the following new key to the TIM_GatewayActionMonitor app config file:
false - Estimate Description populated based on ([inbound est desc]-[inbound (agency/rep) advertiser name]-[yyyy-mm-dd]) 
true - Estimate Description populated based on SCX /AAAA-Message/campaign/estimate/desc field
  1. Restart the TIM_GatewayActionMonitor service

Version 2.7.1 (10/13/2014)

  1. "The given key was not present in the dictionary" error for some orders that already exist in TIM. (#52167)
Installation instructions for Gateway-to-TIM v2.7.1 as update to existing v2.7.0 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.7.0 (07/18/2014)

  1. Update GAM and AQM for TIM WS 5.3.0 (new ImportSCX functions) (#48590)
  2. Display System Order Comments in email notification (#39709)
Installation instructions for Gateway-to-TIM v2.6.3 as update to existing v2.5 or v2.6.1 or v2.6.2 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.6.3 (04/15/2014)

  1. Follow-up fix for: GetAirStartDate calculation fails in some scenarios (#46519)
Installation instructions for Gateway-to-TIM v2.7.0 as update to existing v2.6.x install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.6.2 (04/02/2014)

  1. Gateway import failed after mapped client name was changed in TIM - Reported by Colleen Manning / NCD (#47073)
Installation instructions for Gateway-to-TIM v2.6.2 as update to existing v2.5 or v2.6.1 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.6.1 (03/11/2014)

  1. Additional fix for - Allow STRATA AEInbox/ACE integration: Separate FROM_TP value from Agency BusinessKey (#45622)
Installation instructions for Gateway-to-TIM v2.6.1 as update to existing v2.5 or v2.6 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.6 (01/21/2014)

  1. Allow STRATA AEInbox/ACE integration: Separate FROM_TP value from Agency BusinessKey (#45622)
  2. Null values for Product from NCC is causing product mapping issues (#45639, #44043)
  3. GetAirStartDate calculation fails in some scenarios (#46519)
Installation instructions for Gateway-to-TIM v2.6 as update to existing v2.5 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.5 (09/20/2013)

  1. Trade orders from NCC will be indicated in the new order email with "Trade order" (NOTE: This will be coordinated with NCC and is not currently available)
  2. Another new field in the new order email, Air Date Range, which indicates the first and last possible dates where spots can run.  This is different than the flight dates.  This represents is the first and last dates that spots can run based on the weeks where spots have been ordered and the eligible days on the order lines.
  3. Orders set to "Rejected to agency" status in TIM will not result in a Rejection message being sent to NCC
  4. Store agency and client mappings based on TIM ID instead of TIM name
  5. Allow agency and client mappings by market based on config setting (EnableEntityMappingByMarket)
  6. When a new syscode is added to an order that has already been imported into TIM, the failure email will be sent to the AE distribution list for the market with details about the order and new syscode that was added
  7. Improved performance by reducing number of calls to the TIM WS
  8. Improved logging for email distribution lists
  9. Most failure emails now include order details as available
Installation instructions for Gateway-to-TIM v2.5 as update to existing v2.4 or v2.4.1 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIPs to the corresponding folder (overwrite all)
  3. Add the following new key to the TIM_ActionQueueMonitor app config file:
  1. Add the following new key to the TIM_GatewayActionMonitor app config file:
false for the previous functionality
true to start storing all mappings by market
  1. Copy the statusMap.xml over the existing file
Copy the custom file (statusMap.xml) received from STRATA the TIMeBusDir/TIM_eBusiness/statusMap folder on the TIM web server.
  1. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.4 (07/27/2012)

  1. Define email distribution lists by market
  2. Support for bookend orders (Eclipse)
  3. Include broadcast month dollars breakout in email body
  4. Include flight start date and client name in the email subject line
  5. Include agency address info in email body (NOTE: This will be coordinated with NCC and is not currently available)
Installation instructions for Gateway-to-TIM v2.4 as update to existing v2.3 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.3 (10/03/2010)

  1. Updates to demo handling in GAM when demo does not exist in TIM (replace with Households, include demos in notification emails)
Installation instructions for Gateway-to-TIM v2.3 as update to existing v2.1 or v2.2 install:
  1. Stop both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services
  2. Unzip the respective ZIP to the corresponding folder (overwrite all)
  3. Restart both the TIM_GatewayActionMonitor and TIM_ActionQueueMonitor services

Version 2.2 (05/05/2010)

  1. Updates to Estimate Description field in TIM for NCC orders
  2. Updates to New Order and Revision emails for NCC orders
Installation instructions for Gateway-to-TIM v2.2 as update to existing v2.1 install:
  1. Stop the TIM_GatewayActionMonitor service
  2. Unzip the respective ZIPs to the corresponding folder (overwrite all)
  3. Restart the TIM_GatewayActionMonitor services

Version 2.1 (04/21/2010)

  1. Added support for orders from NCC
Installation instructions for Gateway-to-TIM v2.1 as update to existing v2.0 install:
  1. Stop both the TIM_ActionQueueMonitor and TIM_GatewayActionMonitor services
  2. Unzip the respective ZIPs to the corresponding folders (overwrite all)
  3. Open the TIM Database Manager.  Under the Setup left-hand menu, select Application Settings.  Select the radio button for Gateway Action Monitor.  Use the "..." button beside the Config File Location text box to browse to the location of the TIM_GatewayActionMonitor\bin\GatewayActionMonitor.exe.config file.
  4. Set EncryptionLevel to LOW. Click Save. Close the TIM Database Manager.
  5. Manually edit the TIM_GatewayActionMonitor\bin\TIM_GatewayActionMonitor.exe.config file in Notepad.  Add the following lines after the line with this value: ErrorEmailNotificationActive
   
   
   

   
   

   
   

   
   

   
  1. Populate values for the new keys (added in Step 5):
The values from the existing keys AEs.Email.To, TIM_Username and TIM_Password should be populated in the equivalent Marketing keys.  For example, copy the value of the AEs.Email.To key and paste that as the value of the Marketing.AEs.Email.To.
The Regional keys can be left empty for this version.
The Rep Key need to be populated as appopriate for orders from NCC.  This includes setting the email distribution list (Rep.AEs.Email.To) for NCC orders and using an existing or creating a TIM user account (Rep.TIM_Username and Rep.TIM_Password) for importing NCC orders.  If creating a new TIM user account, please remember that the user must be associated to at least 1 Account Executive in TIM and be a member of the Sales group.
  1. REMOVE the following lines from the same file (TIM_GatewayActionMonitor\bin\TIM_GatewayActionMonitor.exe.config file):
AEs.Email.To
TIM_Username
TIM_Password
  1. Restart the TIM_ActionQueueMonitor and TIM_GatewayActionMonitor services

Version 2.0 (02/03/2010)

  1. Added support for TIM WS 3.7 which resolves issue with opening orders in View32 from TIM
  2. Fixed issue with processing Revision and Cancellations when spaces exist in GAM installation folder path
  3. Fixed issue with mapping when Product is not mapped in TIM
Installation instructions for Gateway-to-TIM v2.0 as update to existing install:
  1. Upgrade TIM WS to version 3.7 (follow pre-requisites and instructions from STRATA)
  2. Stop both the TIM_ActionQueueMonitor and TIM_GatewayActionMonitor services
  3. Unzip the respective ZIPs to the corresponding folders (overwrite all)
  4. Manually edit the TIM_ActionQueueMonitor\bin\TIM_ActionQueueMonitor.exe.config and TIM_GatewayActionMonitor\bin\TIM_GatewayActionMonitor.exe.config files in Notepad.  Add the following 2 lines after the line with this value: TimWS.Service.Url

  1. Restart the TIM_ActionQueueMonitor and TIM_GatewayActionMonitor services

Version 1.3 and 1.3R2

  1. Fixed issue with supporting EncryptionLevel when set to LOW

Version 1.2

  1. Added ServiceAccount key to AQM and GAM application configs to support Windows 2000 or 2003 servers

Version 1.1

  1. Fixed issue with long advertiser name
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk