NewViews 2.08
Released - April 21, 2006
This is a version change, not just a service pack. The service pack number is reset to zero. After installing this version, each workstation, server, or application database will be automatically processed the first time you open it. You will be asked for comfirmation before any processing is performed, and as a precaution, a backup is made automatically before each conversion.
What's New
-
Less memory consumption under some important conditions
Under certain conditions memory grew to "unmanageable" levels, resulting in virtual memory thrashing and reduced performance, or eventually an out of memory error, or a similar error triggered by the inability to allocate more memory. These conditions always involved either a major operation on a very large set of books, or a long-running server.
The NewViews internal memory management system has been revamped. As a result, these conditions no longer occur, regardless of the size of the set of books, or how long a server has been running.
See the Problem/Bug Fixes for a description of each NewViews functional area affected by this change.
-
Speed improved for printing when templates are used
Users should notice a significant performance improvement when printing documents that use print templates (i.e. checks, invoices, etc).
-
Added the Tools>Totalto>Graph Above command.
The previous release, i.e. version 2.07, introduced the Tools>Totalto Graph command which displays a graph of the total-to structure below any selected account. This version, i.e. 2.08, renames the command, as described below, and also introduces a similar command, Tools>Totalto>Graph Above, which displays a graph of the total structure above any selected account. The new command lets you see everything an account totals to, as shown below.
In the figure above, the Tools>Totalto>Graph Above command was issued while positioned on 1060, a bank account. As a result, the total-to structure above the account is displayed in a graph.
You can change the graph fonts, colors, styles, and so on, and decide what information to display in graph nodes. In the example above we display the account name and description, as well as the description of the account's report. This makes it easy to see that the bank account affects other accounts on several reports including the balance sheet, and two statements of changes in financial position, one based on working capital and another on cash.
Now you can now explore the total-structure both below and above any account.
-
Tools>Totalto Graph command was renamed to Tools>Totalto>Graph Below.
With the introduction of the Tools>Totalto>Graph Above command it seemed appropriate to rename the Tools>Totalto Graph command to better reflect its purpose, i.e. to display the graph below any total account.
-
Added the Tools>Totalto>Orphan Search command.
This command lets you search for orphan accounts.
The command helps to determine why a proof account is non-zero, that is, why books appear to be out of balance. Note that books are never really out of balance as debits/credits always balance. They only appear to be out of balance, almost always due to omitting to total an account; hence the term orphan.
Position on a so-called proof account, issue this search command, and all accounts that do not total to the proof account are displayed. Although the majority of accounts listed in the search results can be explained by those with knowledge of the total-to structure of the set of books, others will be very suspicious and often represent omissions in the total-to's, resulting in the balance problem.
Note: Only users granted access to the root account (or any object above it) can use this command. Otherwise this would be a breach of the security system since lists of accounts to which the user has not been granted access could be displayed.
-
Added the Tools>Totalto>Semiloop Search command.
This command lets you search for semiloops in the total-to structure of a set of books.
A semiloop occurs when you total one account to another more than once. Position on a total account high in the total-to structure, such as a balance sheet or trial balance proof account, issue this command, and a list of semiloops occurring below the account in the total-to structure, if any, is displayed. Each semiloop is displayed in graphic form as shown below.
In the example above, INCOME totals to EQUITY and also to LE, i.e. liabilities and equity. This is unnecessary because EQUITY already totals to LE, and therefore there is a semiloop.
Semiloops are not particularly harmful because NewViews automatically eliminates duplication on accounts that are totalled-to more than once. However, they do reflect a degree of sloppiness in the total-to structure, and they can also lead to amounts on reports that do not seem to add up correctly. Therefore you should use this command to identify and remove all semiloops from your total-to structure.
-
You can now print checks directly from a bank account ledger.
In prior versions checks had to be printed when positioned on a payment journal (pink table). Now you can mark a block of checks directly on a bank ledger (green table) and print them.
-
You can now print invoices directly from a customer account ledger.
In prior versions invoices had to be printed when positioned on an invoice or order journal (pink table). Now you can mark a block of invoices or orders directly on a customer ledger (green table) and print them.
-
You can now print purchase orders directly from a vendor account ledger.
In prior versions purchase orders had to be printed when positioned on an purchase order journal (pink table). Now you can mark a block of orders directly on a vendor ledger (green table) and print them.
-
Refined editing of expressions in numeric fields.
Whenever you enter a value into a numeric field you can instead enter an expression. Users unaware of this feature typically use a calculator to perform an operation such as calculating an after-tax amount, and then manually enter the result into the numeric field in NewViews. But you can enter an expression such as (5+6)*1.07 directly into the field and as a result 11.77 is automatically calculated and entered.
However, prior to this version the expression evaluator treated any number without a decimal point as an integer and automatically performed integer truncation or rounding. For example, entering 3/2 resulted in the value 1.00 instead of the expected 1.50.
Technically this was not a bug, but it certainly was an oversight. In this version, the expression evaluator treats all numbers as real numbers. Integer truncating and rounding have been completely eliminated and the resulting numbers are exactly as you would expect.
The only rounding that still occurs is the automatic rounding of dollar amounts to the nearest cent. Note that rounding to the nearest cent does not occur on quantity fields or other non-dollar fields.
-
The [F4] and [F5] keys are now available on settings prompts and similar windows.
Many settings prompts and similar windows require you to press a button to dismiss the window or to perform the relevant operation. You can now instead use the [F4] and [F5] keys for this purpose. This lets you perform operations without taking your hand off the keyboard to use the mouse.
-
Payroll pay period restrictions were removed.
Monthly pay periods were required to be calendar months, and semi-monthly pay periods were required to either start on the 1st of a month, or end on the last day of a month. This restriction has been removed to allow for non-standard monthly or semi-monthly pay cycles.
-
The symbol @P can now be used in the description paycode.
The symbol @P can now be used in the description paycode. The @P symbol is replaced with the perpetual balance of the earnings/deduction account when a pay check is processed.
- Iowa state income tax table included for Apr 01, 2006
Problem / Bug Fixes
-
A number of problems related to memory management have been fixed.
Under certain conditions, generally when operating on very large sets of books, or when running a server over a long period, memory grew beyond manageable levels and the revamped memory management in this release eliminates these conditions. Below, we list and describe several functional areas where problems related to memory management had occurred in the past, and the affect of revamped memory management on them. -
Long-running NewViews servers.
The memory management problem was an issue when running a NewViews server continuously, i.e. never shutting it down, over an extended period of time. Memory would eventually grow and result in virtual memory thrashing, accompanied by a significant reduction in performance.
With this release, a server can run be continuously, without intermittent shutdowns, for an unlimited period, without encountering problems related to memory management.
-
nvreorganize
On very large sets of books, when running nvreorganize, memory consumption would eventually reach unmanageable levels and nvreorganize would eventually thrash to death on very large sets of books. This is no longer the case. Memory consumption is now contrained to a manageable level and a set of books can be reorganized regardless of it's size.
-
nvcheck
On very large sets of books, when running nvcheck, memory consumption would eventually reach unmanageable levels and nvreorganize would eventually thrash to death on very large sets of books. This is no longer the case. Memory consumption is now contrained to a manageable level and a set of books can be checked regardless of it's size.
-
Decompressing transactions.
When transactions were imported from NV1 with compression enabled, problems could subsequently occur when decompressing too many of the compressed transactions in one operation. This situation was avoided by NewViews by limiting the number of the compressed transactions that could be decompressed in one operation.
With this release, any number of compressed transactions can be decompressed in one operation, and NewViews no longer prohibits the decompression of too many compressed transactions.
-
Large imports from NV1.
The memory management problem occurred when importing very large sets of books from NV1. These very large sets of books could only be imported by setting reasonably small batch limits (say 10000) for the import. This had the effect of shutting/restarting NewViews periodically, resuming where the import left off.
Other reasons for using import batch limits, such as resuming after power failures and so on, remain. However, an import should now succeed regardless of the size of the books or the batch limits specified.
-
Huge default window setups.
-
Some field changes were not signalled under multiuser access.
Field changes in various settings prompts and notes views were not being signalled to other users, although the changes were properly updated to the database. This bug was introduced in version 2.07 and occurred in that version only.
-
A bug occurred when deleting sub-accounts.
A bug occurred under the following relatively rare circumstances. First, you had to be adding and using sub-accounts. Second, you had to change the name of an account that had sub-accounts. Third, you had to attempt to delete the account and/or its existing sub-accounts.
This bug is fixed in this release and any problems it may have introduced into existing books are fixed during conversion.
-
NewViews sometimes reported that a computer was not properly registered when in fact it was.
This problem only occurred on a computer with multiple network interface cards. Furthermore, it occurred only when NewViews was registered when one card was active, and then NewViews was subsequently run when a different card was active. This release fixes the problem.
-
NewViews version 2.07 would not run more than once.
When NewViews was already running it could not be run again. This problem only applied specifically to version 2.07 and was the result of a dynamic load library conflict. Microsoft Windows silently shut the application down so the second attempt to run NewViews mysteriously did nothing. This release fixes the problem.
-
EFT (Electronic Funds Transfer) problems occurred for some banks.
The EFT data generated for CIBC and the ROYAL BANK contained a glitch that resulted in their rejection by the banks. This release fixes the problem.
-
Employee EFT status inconsistency.
An employee EFT status was sometimes displayed as empty under multi-user access but the supposedly same value was instead displayed as non-empty under single-user access. Also, the EFT status for new employees was set to empty instead of inactive. This release fixes the problem.
-
Payrun processing error if employee born on Feb 29.
This bug applies to Canada only. If an employee's date of birth is Feb 29th then an error prevented the processing of the payrun. This release fixes the problem.
-
Employee payroll deduction accounts sometimes had an empty normal balance.
This problem applies only to employee deduction accounts that were imported from NV1. Employee deduction accounts that were not correctly a-typed before exporting from NV1, could show up in NV2 with an empty normal balance field. This release fixes the problem for data imported in the future. Employee deduction accounts that have already been imported and that have an empty normal balance must be set manually, i.e. to presumably credit in this case.
-
Problem occurred when remitting payroll liabilities using the Tools>Pay Wihholdings command.
If any of the five remittance categories (i.e. cpp, ei, tax, etc) were not filled in, then none were paid. This release fixes the problem.
-
Employer ppip contribution was posted even though employee deduction was zero.
This bug applies to Canada payroll only. An employer ppip contribution was posted even though an employee has reached their limit for the year. This release fixes the problem.
-
Data might be exported incorrectly from a purged NV1 set of books.
This bug applies only to books that were exported from NV1 and only if the books had been purged in NV1. When the NV1 purge audit count ended in the digit 0, the exporter ignored the fact that the books had been purged. Consequently, Transactions older than 10 years could have the wrong date and lead to the NV2 books being out of balance for these periods. This release prevents this problem from occuring in the future.
-
Problem occurred when a fatal error was encountered when exporting from NV1.
When a fatal history error was encountered at the end of exporting the accounts from NV1, the NV1_NV2 file was not deleted. Some users ignored the fatal error and subsequently attempted to import the partially complete NV1_NV2 file. With this release the file is automatically deleted when a fatal error is encountered.
-
An error occurred during printing for French versions of Excel.
Users of French versions of Excel would receive an error that no Print Area had been defined on their print templates, and that the range Zone_D_Impression was an invalid size. This was caused by the fact that French Excel uses the name Zone_D_Impression for the print area. NV2 has been updated to recognize this name as well as the English version.
-
Several block operations did not work when a table was sorted in backward order.
Several block operations, including printing and copying of blocks, only processed the first row of the block when the table containing the block was currently sorted in backward order. This release fixes the problem.
-
Phone and fax numbers were not printed on customer statements.
This release fixes the problem.
-
Rows sometimes did not keep their order when copied and pasted.
Blocks were copied using their creation order and therefore were also pasted in that order. This would not keep the order of the interactive index, i.e. the sort order when the line number order is selected. This release fixes the problem.
-
Invoices and checks printed incorrectly when printed from their table of details.
When you attempted to print an invoice or check while positioned on the invoice or check details, only the current single row representing the current detail was printed. Now the entire invoice or check is printed correctly.
-
Bug occurred when setting up columns and moving back and forth using [F4] and [F6].
This release fixes the problem.
NewViews 2.08 - Service Pack 18
Released - June 21, 2007
What's New
-
Includes Canadian July 01, 2007 tax calculation update.
Payroll update is the primary reason for this service pack. All Canadian payroll users will require this service pack to process payroll after July 1st, 2007.
NewViews 2.08 - Service Pack 17
Released - April 30, 2007
Problem / Bug Fixes
-
Enables NewViews to run under Microsoft Windows Vista
NewViews was not able to install on Microsoft Windows Vista. This release fixes the problem.
NewViews 2.08 - Service Pack 16
Released - January 23, 2007
Problem / Bug Fixes
-
Corrects a problem that occurs when re-totaling.
A speedup algorithm fails when there are semiloops in the totaling structure of a database. The speedup has been removed which means re-totaling will be slower. However this is temporary as future versions will eliminate semiloops and restore re-totaling efficiency.
NewViews 2.08 - Service Pack 15
Released - December 22, 2006
What's New
-
Includes Canadian January 01, 2007 tax calculation update.
Payroll update is the primary reason for this service pack. All Canadian payroll users will require this service pack to process payroll after January 1st, 2007.
-
Includes United States January 01, 2007 tax calculation update.
Payroll update is the primary reason for this service pack. All United States payroll users will require this service pack to process payroll after January 1st, 2007.
-
Includes new check templates.
Check templates have been added for printing CPA (Canadian Payments Association) compliant checks. The new templates are in the same folder as other templates previously shipped with NewViews, i.e. c:/nv/nv20.dat/object/newviews (where c:/nv is assumed to be the installation folder).
NewViews 2.08 - Service Pack 14
Released - November 6, 2006
Problem / Bug Fixes
-
Collision checking was too aggressive.
Recent service packs addressed the invalid index record problem and part of the solution was an adjustment to the collision checking algorithm. However, there was one situation, where new objects were being added, say by two users active on the same journal, where the modified collision checking algorithm turned out to be too aggressive. This caused the detection of collisions when no collision should have occurred. This service pack fixes the problem.
NewViews 2.08 - Service Pack 13
Released - November 2, 2006
Problem / Bug Fixes
-
Corrects a bug in nvreorganize.
The previous service pack eliminated a performance bottleneck of the nvreorganize utility that occurred under some rare circumstances but in the process introduced a bug. This service pack fixes the bug.
NewViews 2.08 - Service Pack 12
Released - October 30, 2006
Problem / Bug Fixes
-
Eliminates a problem that occurs when changing a database's company description.
The previous service pack, 2.08.11.20061027, fixed the invalid record problem but also introduced a problem that occurs when changing the root account .address.company field. This field of the root account object also serves as the description of the database root object. This release fixes the problem.
NewViews 2.08 - Service Pack 11
Released - October 27, 2006
Problem / Bug Fixes
-
Eliminated a server memory leak.
A memory leak caused server memory to grow steadily without limit and performance eventually degraded significantly. This leak has been eliminated.
Note that this memory leak motivated users to periodically shut down and re-start the server for the purpose of reclaiming the memory. Elimination of this leak has helped the situation and periodic restart may no longer be necessary, or at least, it will not be necessary to re-start as often. Which is the case is yet to be determined conclusively.
-
Fixed a rare but serious bug that caused invalid index records.
In circumstances that were rare, but which did occur, it was possible to cause the creation of invalid index records. Because NewViews continually performs a series of checks on all records this bug would occasionlly surface as a error message that reported a bug and which would shut NewViews down. Invalid records introduced by this bug were detected by the nvcheck diagnostic tool, and could be fixed by the nvreorganize tool.
The bug occurred under relatively rare circumstances that required several database conditions to coincide. These circumstances involved the number of objects loaded and the order in which they had been loaded, so the bug depended on the dynamics of database usage. It also required that a transaction's header fields such as it's account, reference, or date, were changed either more than once before committing, or else changed several times and then the changes were aborted using the Edit>Quit command. It also occurred only on transactions with a number of transaction line items. Although the set of circumstances was rare, it was less rare in a multi-user environment where the object loading conditions were more likely to occur.
The point is that because this set of circumstances was so rare, and subtle, no user or Q.W.Page staff member was able to reproduce the bug, despite repeated efforts. That made the source of the bug very difficult to track down. However, information gathered over time allowed Q.W.Page staff to finally home-in on the bug, and once found, to reproduce it at will, and therefore eliminate it.
This release should not introduce additional invalid index records. However, the bug could still be reported due to invalid records already created by previous versions. In that case, run nvreorganize to eliminate the pre-existing invalid records.
NewViews 2.08 - Service Pack 10
Released - September 20, 2006
Problem / Bug Fixes
-
Allows NewViews to register and run on XP64.
NewViews ran on XP64 but could not be registered.
-
Fixed an error in numeric data entry.
This fix was reported in the previous service pack but was not actually included in the previous service pack due to an administrative error.
-
Fixed an error in the totalto semiloop search command.
The Tools>Totalto>Semiloop Search command was broken in the prior service pack due to another fix related to processing special characters. This release fixes the problem.
-
Fixed an error in the record import command.
The Tools>Import Records command was broken in the prior service pack due to another fix related to processing special characters. This release fixes the problem.
NewViews 2.08 - Service Pack 9
Released - September 14, 2006
Problem / Bug Fixes
-
Fixed an error in numeric data entry.
The previous service pack fixed numeric entry for numbers that were completely enclosed in parentheses but broke numeric entry for numbers containing internal minus signs.
This service pack fixes that problem, and also enhances the range of numeric entry formats that can be recognized and successfully collected. For example, an entry such as ( 123,456.78 )- previously reported an invalid entry error because it contained internal spaces and a trailing minus after enclosing parentheses.
As a result it is easier to flip the sign of most numbers, regardless of how they are formatted, by simply pressing [Escape] to start editing and then the minus key to flip the sign.
-
Fixed an error preventing multi-user login.
Under rare circumstances a user would receive an error such as "Server XXX encountered duplicate workstation serial number YYY." when the workstation was not in fact connected to the server. This resulted from the server failing to remove the serial number during a disconnection or logout.
-
The orphan search tool could generate errors when encountering special characters.
Special characters in name or description fields could result in errors when generating HTML for the resulting orphan reports. The characters & [ ] $ " \ < > { and } are "special" in this context because they can conflict with underlying tcl evaluation or HTML markup. This version fixes the problem.
-
The record import tool had an error importing distributions with mixed amounts.
The record import tool, invoked by the Tools>Import>Records command, had a error when both positive and negative amounts were encountered on a distribution. Although this case is common, the error was inadvertantly introduced as a side-effect of a recent fix to another record import problem.
NewViews 2.08 - Service Pack 8
Released - August 1, 2006
Problem / Bug Fixes
-
Fixed an error in number data entry.
Numbers completely enclosed in parentheses were not interpreted as negative numbers. As a result of this error, numbers were also being displayed in incorrect columns on the trial balance report.
-
Fixed an error with nvreorganize.
Nvreorganize would not complete on some sets of books.
NewViews 2.08 - Service Pack 7
Released - July 17, 2006
Problem / Bug Fixes
-
Fixed an error with nvreorganize.
Nvreorganize would not complete on some sets of books.
NewViews 2.08 - Service Pack 6
Released - July 14, 2006
Problem / Bug Fixes
-
Fixed an error in the Edit>Quit command.
This was a serious error that could affect the integrity of an accounting database and in that case could be corrected only by running the nvreorganize utility on that database. This service pack fixes the problem.
-
Now allow printing through French version of Excel.
Corrected several problems that did not allow printing when using a French version of Excel.
-
Fixed an error in the calculation of USA payroll deductions.
Prior to this release, the ability to round federal, state, and local tax deductions did not work properly. This problem occurred only in USA payroll.
-
Fixed an error in the Arizona state tax table.
Prior to this release, Arizona state tax was not calculated correctly and an amount of zero was used. This problem occurred only in USA payroll.
-
The "Shrink to fit" Excel attribute is now recognized.
When printing checks, the template TEXTAMOUNT cell for the amount in words is examined to see if the words fit in the cell. An error was displayed if the cell is too small. The test now also checks to see if the cell alignment property "Shrink To Fit" is enabled, and if so, then no error is displayed because Excel will automatically reduce the point size of the cell as necessary to contain all of the text.
-
Checks were sometimes printed with negative amounts.
Checks entered in a bank account using a general journal (instead of a bank payment journal) were printed with negative amounts.
-
An error occurred in Quebec payroll when processing July 2006 checks.
This error occurred only for Quebec payroll and only for checks dated on or after July 01, 2006.
-
Fixed an error that occured when importing NV1 books.
During the import of an NV1 set of books, descriptions of all postings are examined to see if the beginning of the description contains a number. If so, then it is assumed to be a quantity and the quantity field of the NV2 posting is set to that number. In rare cases, a description would contain a number at the front, but the number was too large to be used as a quantity. This would cause the import to fail. The testing for numbers in descriptions has been improved to eliminate this error.
-
Fixed a problem that occurred when importing NV1 books with Canadian payroll and non-cash taxable benfits.
When importing an NV1 set of books containing Canadian payroll, benefits accounts with the codes B=T440, B=T441, B=T442, etc. are assumed to be non-cash benefits accounts. Since the accounts and postings are "non-cash", they were not included in the converted employee setup. This posed a problem for users who used these codes for actual cash amounts that totalled into financial amounts in their books.
This version checks the totalling of the benefits accounts, and leaves the accounts and postings in the employee setup, if the accounts appear to total to financial statements. The test is if the benefit account's totalling intersects with any of the employee's earnings or deduction accounts totalling. In other words, if by following the totalling of a benefit account and any of the earnings or deduction accounts, the same total account can be reached, then the benefit account is considered to be a "cash" benefit and is left in the NV2 books.
NewViews 2.08 - Service Pack 5
Released - July 7, 2006
What's New
-
Service Pack 2.08.5.20060707
This service pack was not released and was used for internal testing purposes only.
NewViews 2.08 - Service Pack 4
Released - June 13, 2006
What's New
-
Includes Canadian July 01, 2006 tax calculation update.
This is the primary reason for this service pack. All Canadian payroll users will require this service pack to process payroll after July 1st, 2006.
Problem / Bug Fixes
-
A problem occurred when copying payroll accounts to a new employee.
This applies only to Canadian payroll. When copying the accounts to a new employee the T4 and/or Releve 1 boxes were set incorrectly.
-
Quebec provincial tax calculation enforces minimum claim amount.
This applies only to Canadian payroll. The claim amount used for tax calculations will use the current minimum amount even in cases where the employee's amount is below the minimum.
-
Fixes a problem when converting some databases.
A small number of databases could not be converted from pre-2.08 versions to 2.08. This service pack fixes the problem.
-
The Tools>Totalto>Orphan Search command did not work.
A minor enhancement to this command introduced an error. This service pack fixes the problem.
NewViews 2.08 - Service Pack 3
Released - May 15, 2006
Problem / Bug Fixes
-
The "invalid record" bug has been fixed.
Prior to this service pack it was possible for an invalid amount to be stored in an index record. NewViews has continuous integrity checking and this integrity checking would subsequently encounter the invalid amount and would report it as a bug. The particular bug that was reported depended on the operation currently being performed, but the underlying cause was always the same; on-going integrity checking had detected the invalid amount that was originally stored in the index record during some previous operation.
Typically the bug was reported when deleting a transaction, when re-totaling an account, or sometimes, just by displaying a table. The integrity of index records is checked under all of these circumstances so the problem would appear to occur under different circumstances.
The invalid index record amount would also be detected by nvcheck. Either the third (index record integrity) or the fourth (index record references) check might detect different variations of invalid index records.
nvcheck may still detect the problem if invalid amounts were introduced into a database when running a version of NewViews prior to service pack 3, since the invalid amounts will still be in the database. Running nvcheck will determine if this is the case.
nvreorganize will fix the problem.
The problem did not compromise the integrity of accounting data. Invalid amounts introduced by the bug were limited to index records which are auxiliary to the original data entered into the database.
-
Fixes a problem in nvreorganize.
The problem was relatively rare and would make nvreorganize appear to hang near completion of either the first or second progress bar. In fact, nvreorganize had encountered an exceedingly large block paste buffer and was taking an inordinately large amount of time to process it due to a correct but inefficient algorithm. This algorithm could also result in failure due a memory problem in underlying software.
This problem in nvreorganize has been fixed and should not recur.
-
Fixes a problem with internal minus signs in numeric data entry.
Entering 36-12 resulted in value -3612 instead of the expected 24. NewViews negated the number each time a minus was encountered regardless of where or how many were encountered, except in more complex expressions. Now the number is negated in this way only when encountered at either end of the entered value and the result returned in the example above is 24 as expected.
NewViews 2.08 - Service Pack 2
Released - May 5, 2006
What's New
This service pack introduces the ability to make an object a sub-object of a different parent object.
This was required for several NewViews users who had time-dependent needs for this functionality.
This functionality is not being offered to all users at this time because it is not complete or fully tested.
DO NOT try to use this feature until version 2.09 is released.