• US: +1-800-476-7226

Software and services for the radio industry.

From the desk of Cory Smith

Modified: 2018/03/20 15:10 by admin - Uncategorized

Coming Soon




This is where we detail the features and capabilities we are actively working on.



Please understand that this page contains WORK IN PROGRESS information; as such, some of the information this page may be adjusted, changed and/or outright removed without notice.


Pending Release

Report Improvements

We added "Next Year" as a Period for the Annual Sales Review and Annual Sales Review Accrual reports:





Near Future

The following items are features and capabilities that we are going to be actively working on for inclusion in an upcoming update. Please remember, this list is "fluid"; it can literally change at any moment and nothing on this list is to be interpreted as a commitment feature availability or target release... in other words, this is just what we are "attempting to do" and if things go without any issues it might happen. With that said, you are very welcome to reach out to us regarding any comments/suggestions you might have related to these features so that we can provide you with the best possible result.

To put this another way... "Everybody has a plan until they get punched in the mouth." - Mike Tyson

  • Active/On-going...
    • Migrate RT from Dallas to Denver (traf.com, wiki, forum, services, updates, databases, etc.)
    • Migrate from .NET 4.5 to .NET 4.6.1 (security updates and Marketron services).
    • Trash and/or archive "everything"!
    • Merge nearly "everything"!
    • Multi-select capability on *all* Settings lists.
    • SQL Server performance tuning.
  • March 27
    • Add ability to multi-select, trash, un-trash, archive, un-archive, merge, view trashed, view archived to Voices. (.)
    • Add ability to multi-select, trash, un-trash, archive, un-archive, merge, view trashed, view archived to Taxes. (.)
    • Add "Next Year" as a Period for the Annual Sales Review report. (forum)
    • Modify the default behavior for Payments and Adjustments so as to not automatically display to "narrowing" fields; instead, allow a group option to specifically opt-in to having these fields visible to facilitate the optional narrowing of target invoice assignment. (.)
    • Allow Billing Read-Only role to print, email and/or export invoices. (forum)
    • Add ability to view the related contract when working with MakeGoods. UPDATE1 May consider delaying this in order to completely revamp/replace the existing MakeGoods windows into a single window experience more similar to the Contract View->Spot Details window. UPDATE2 This will be part of the revamp/replacement of the MakeGoods window. (forum)
    • Please allow for the "option" of seeing the update box on the dashboard; I'd prefer not to see it as I prefer to keep my dashboard clean as part of my work-flow. (.)
  • April 4
    • Add ability to multi-select, trash, un-trash, archive, un-archive, merge, view trashed, view archived to Plans. (.)
    • Add ability to multi-select, trash, un-trash, archive, un-archive, merge, view trashed, view archived to TaxOnTaxes. (.)
    • If a spot isn't written in when reconciling and need to add to the invoice via AR, would like the ability to differentiate between different order lines and dayparts. (forum)
    • Provide the ability to print the information on the PrintStatements tab. (forum)
    • When working with write on spots, it would be helpful if the spot(s) contained additional information so that specific spots from specific line items can be utilized.
  • April 17
    • Add ability to multi-select, trash, un-trash, archive, un-archive, merge, view trashed, view archived to Fees.
    • It would be nice to have an option to choose the way our statements format the aging information; would like to see "by month" (instead of 30/60/90/etc.). (forum)
    • Add ability to multi-select Contracts and print the selection. (forum)
    • Track when a contract was approved; in the PrintConfirmations window, add an Approved column so that contracts can be printed in the order they were approved. (forum)
  • April 24
    • When emailing invoices during billing, it would be awesome if multiple invoices going to the same target email address were attached to a single email. (forum)
  • May 8
  • May 22
    • Add ability to reorder the lines (line numbers) on a Contract. (forum)
    • When duplicating a Contract, would like the ability to re-target the lines to a specific station. (forum)
    • When duplicating a Contract, would like to specify whether or not to include the existing rotations. (forum)
    • When duplicating a Contract, would like to specify the end date in addition to the start date. (forum)
    • When adding a new rotation to a running contract, please take into account the state of the logs when determining the default start date of the new rotation. (forum)
  • June 5
    • Would like to have a new report, inspired by the Annual Sales Review report, called "Yearly Sales Review" that displays this year compared to (up to) the last 4 years (5 years in total). (forum)
    • Please add a "Cart #" report. (forum)
    • Please add a "Copy In-Use / Assigment" report. (forum)
    • Add date/time printed to the printed Invalid Copy tab in the Log. (forum)
  • June 19
    • Maintenance only...
  • June 26
    • Add optional "Garbage" tab to the Log providing the ability to see and un-trash previously trashed spots that could have targetted the currently working log. (forum)
  • July 10
  • Evaluating...
    • Would love to have the ability to "duplicate" an existing rotation (instructions) across multiple (one or more) stations instead of having to duplicate and change each time for every target station. (forum)
    • Modify Statements so that the automatic selection is based on "recent activity" instead of current "balance". (forum)
    • For OAR billing, would it be possible to bill clients at the end of a month instead of the 15th? Or at least closer to the end of the month. (forum)
    • When entering OAR could the calendar be the current month and not last month. Can be confusing. (forum)
    • Allow for the adding/modifying of Copy "everywhere". (forum, forum, forum)

NOTE: The above list is not all-inclusive, a commitment or a promise of delivery.


Far(ther) Future

The following list is areas that we are interested in working on; however, they are "further down the road".

  • Integrate RT Tickets with Marketron Customer Central with zero negative impact on existing client-facing features.
  • Migrate from "Forums" (external of RT) to Suggestions (internal to RT).
  • Integrate with Marketron Proof-of-Performance.
  • Integrate with Marketron Network Connect.
  • Integrate with Marketron PayNow. (forum)
  • Integrate with Marketron Electronic Orders and Invoices.
  • Integrate with Marketron Automation Manager.
  • Add "DocumentStore" - the capability to "file" externally created (electronic) documents directly within RT; possibly by integrating with one or more of the many cloud-based file sharing services.
  • Add "Credit Worthiness" information tab to Contracts. (forum)
  • Provide for detailed change tracking.
  • Add support for "Multi-level Approval".
  • Consider improvements (redesign) to Dashboard notifications.



  • Why do new releases occur "during the day"?

    There are pros and cons to every possible time where we could send out a release. Our experience has demonstrated that doing the updates during the day is in the best benefit of all. There are many reasons for this the first of which is having a full staff on hand to handle any possible issues that sometimes arise is far better than having no one. Given that RT is world-wide, there really isn't a day or time where someone is actively using the product; so no matter what, someone could be impacted if something goes wrong. One also has to remember that even if the update was done "overnight" if someone shows up before people are available at Marketron and there is a critical issue... that issue will have to go unresolved easily three or more hours. This, we feel, is unacceptable. Given how we currently approach this; if an issue arises, it's possible that given the number of people using the product that an issue is found and resolved by someone else before you experience the issue (power in numbers). The entire staff is on high alert and if any issues do arise, they handled with absolute #1 priority. Given that the update is typically less than a minute, we feel that the tradeoff is worth it.