• US: +1-800-476-7226

Software and services for the radio industry.

From the desk of Cory Smith

Modified: 2018/06/21 13:10 by admin - Uncategorized

Coming Soon




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

Please note that RT follows the philosophy of "release early, release often" through a "continuous delivery" approach. This means that we are extremely enthusiastic to get any completed improvements into your hands as soon as possible so that you can take advantage of these capabilities NOW!.

This means that it is extremely important that you keep an eye out for our release notes and if you have any questions (or need additional in-depth assistance) with any of the improvements that you do not hesitate to ask one of our customer service individuals to spend a little time with you. As always, if you have any questions, comments, or suggests you can always begin the process by using the Send a Smile tool available under the Feedback menu located on your Dashboard.



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

Log Improvements

  • Bump Spots by Owner

It is now possible to open up the Context menu and remove spots by Owner.


  • Bump Spots that are Make Goods

It is now possible to open up the Context menu and remove spots by Make Goods.


EC You will only see this highlighted if you have placed any Make Goods on the Log and they have not been rescheduled.

  • Added
    • It is now possible to "bump by owner" when working the Log.
  • Modified
    • Fix: When exporting an invoice to PDF (if available), the additional copy pages included as part of a coop invoice have issues with formatting if the customer name is "too long".
    • Improve: The Bump All Make Good Spots tool in the Log is only enabled if there is at least one "make good" on the Log. Note: Once the log is saved, any make good spots on the log are now "rescheduled"... meaning they are no longer "make good".
    • Fix: When exporting to a Maestro automation system, it is possible to specify the type of event through adding an LS, LR, etc. to the avail type name using a pipe character; however, this pipe character is used with the composite avails feature causing the avail to no longer be visible in the selection list when trying to assign the avail type to a contract line item. To address this, the character used is being changed from a pipe character to a backslash character.


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 to 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 (Scott Traffic, LLC) to Denver (Marketron Broadcast Solutions, LLC) (traf.com, wiki, forum, services, updates, databases, "master database", etc.)
    • SQL Server performance tuning.
  • May 22
  • June 5
    • Please add a "Copy Assignment" report. (forum, forum)
    • Would like a "Rescheduled" report showing what spots are rescheduled for a specific date range. Please include the ability to show the original target date and rescheduled date if possible. Having this facility will assist us in quickly identifying agency spots that might be an issue because we incorrectly rescheduled them. (.)
    • 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)
  • June 19
    • Maintenance only... (ie. Cory's on vacation.)
  • June 26
    • Modify the Log so that the loading of the make good information is gracefully loaded after the "Log" so that work can begin immediately without having to have to load "everything" before doing so (as it is now). (.)
    • Modify the Log so that the loading of the "must fill" information is gracefully done in the background so that work on the Log can begin immediately without having to have to load "everything" before doing so (as it is now). This will delay the ability to lock the log until the information has been loaded. (.)
    • Modify the Log so that the loading of the information related to determining "copy assignment" is gracefully loaded in the background; this will delay the displaying of the copy assignment preview, the determination of invalid copy and ability to lock the log. (.)
    • Add ability to make the make good list "optional".
    • Add ability to bump by owner in Log.
  • July 10
    • Add date/time printed to the printed Invalid Copy tab in the Log. (forum)
    • 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)
    • Add ability to leverage multi-select to approve the selected item(s) in Contracts. (forum)
  • July 24
    • Add optional "Bonus" tab to the Log providing the ability to place Copy directly on the Log without having to create a Contract. (.)
    • 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)
  • Evaluating...
    • 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 duplicating a Contract line item, would like to specify the "end date" in addition to the "start date". (.)
    • 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)
    • "Would it be possible to add Created to the available options for the Period drop down for the Contract report?"

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 My Marketron.
  • 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 adding the ability to add multiple spots as a single action directly to invoices from both within the invoice and spot detail.
  • Consider creating a target invoice to manually place spots directly to an invoice if the invoice for the target billing cycle doesn't already exist; need to evaluate the pros/cons further.
  • Consider adding a tool that will (at the very least) allow a support person to "catch up" the generated logs for new station(s) due to delays in "getting started"; removing the need to manually lock and reconcile all of the logs up to a particular date.
  • Consider adding a prompt to either launch ticket or URL for notices on the dashboard for ticket replies that clearly contain a URL (launching the default web browser).
  • Consider duplicating the functionality of "Batch Invoices" in AR in Contracts for Confirmations.
  • "Would like to be able to X out of a station in templates and not have to go completely out and select "templates" again, would like to be able to X out of a station and then be able to select another station to work in without getting completely out. I hope that makes sense! Thank you!"
  • "Would like the ability to pre-print confirmations where these "pre-confirmations" include the projected billing section."
  • "Would like to be able to see and possibly un-trash Log Templates."



  • 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.