Enhancements coming soon

1. For the next release, we are looking at changing the way the program works when both Trade IDs and R codes are used.

2. It is time to re-visit the pricing model that was developed a year ago but put “on ice”.  We want to see if it can be developed
into a truly superior model.  One goal is to get a better curve fit so that fair values in the Matrix come closer to actual market
prices.  Another goal is to develop a model that accurately anticipates changes in the shapes of the skew curves in response to
possible market moves.  Don’t worry, the pricing model in the software now will be kept and given a name, perhaps “the golden
oldie”, and users will be allowed to switch between this and the new model.  At the same time, we want to improve upon the
current volty skew graphics and add the ability to show IV skews of different dates, current and past.

3. As of January 1st, we will begin storing BackTrader data on 15 minute intervals.

Information about the new Trade IDs

A new “Trade ID” field was added to the Trade Log (on the far right) in version 8.10. It can be used to help group a series of
trades that are meant to be considered a single “campaign”. Trade IDs can be used just like R codes except that a Trade ID
can be up to 40 characters in length. Also, unlike R codes, Trade ID’s can be used to group two or more separate trades even
if those trades were not contemporary.

We are hoping that users will switch to recording all of the transactions that take place in a single brokerage account in a single
OptionVue account, or at least all of the transactions in that brokerage account during a calendar year.  That way the user can
make use of OptionVue’s aggregate performance reporting, including a historical graph of account value and an analysis of
how various trading approaches, as coded using the Strategy and Class fields, have performed.

In the Matrix, there is a new drop-down for choosing a single Trade ID to be displayed.  By default this is set to “ALL”, in which
case all existing, open positions are displayed.  This new Trade ID selector is only visible if the user is making use of the Trade
ID field when recording transactions.

OptionVue groups trades primarily by Trade ID and secondarily by R code.  In the same way, when selecting a particular trade
to be displayed in the Matrix, the program selects primarily by Trade ID and secondarily by R code.  If a user never begins
using the new Trade ID field, OptionVue will behave exactly as it did before with respect to the R codes.  Trade ID selectors are
also available in the T.Log and in Reports.

Trade ID is available to be displayed in a new column in Account Status and Reports.  To cause it to be displayed, open the
Report Formats form by clicking the Format button in the upper left area of Account Status or Reports, find Trade ID in the list
and checkmark it.  You may also move it into the desired position among the other columns of the report. Users accustomed to
how Trade IDs work in ONE may have a bit of an adjustment as they begin to use them in OptionVue.  In OptionVue, a Trade ID
is just another “tag” that can be attached to individual trade records as you add them to the T.Log.  It is optional.  Other optional
tags are R code, strategy, and class.  These tags are useful for selecting certain trades to be shown in the Matrix or included in
various Reports, and are also used for automatically grouping trades in Account Status and Reports, and for determining what
previously realized G/L’s should be included when looking at a trade in the Matrix.

Trade ID is basically just a better version of the R code that allows you to use a string of characters when naming a trade.  It
works just like the R code except that it has precedence over R codes if you ever want to use both.  The following table shows a
breakdown of this logic.
OptionVue version 8.12 started shipping December 23, 2016.

Enhancements

1. In Graphic Analysis, there is a new (3rd) choice for how the line legend is displayed:  DTE (number of days till expiration).  
This can be selected in Preferences | Graphic Analysis.

2. The snap-to-dot mode in Graphic Analysis would be reset with every auto-update unless the checkbox “Persist T+0 line snap
to Graham dot” was checked.  We changed this, and now auto-updates never reset the snap-to-dot.

3. Also, the snap-to-dot mode in Graphic Analysis would be reset whenever the user clicked to highlight a different line or
changed the number of lines.  We realized this was unnecessary and we stopped it from happening.

Problem Fixes

1. There was a “memory leak” in the program that could cause the system to display the “Out of memory” message after a
couple of hours of collecting real-time quotes while a matrix was open.  This was solved.

2. There was also a “memory leak” associated with just opening and closing a Matrix.  This was solved as well.

3. When opening and closing transactions were recorded in the T.Log using separate and distinct R codes, the G/L displayed
in the Summary section of the Matrix could be wrong.  This long-standing problem was solved.
Phone: 847-816-6610
You're The Options Expert