Wednesday, 18 June 2014

Moorgate 1.4.1017.1237 is available

Moorgate 1.4.1017.1237 is available for download from the 
Twenty57 website. It contains the following feature

    New Feature

    • Allow for a tolerance (for rounding errors) on internal transactions when checking opening balance + nett transactions = closing balance.  This is set up on the import definition - Balance Check Tolerance.

    Thursday, 17 April 2014

    Moorgate 1.4.1016.1235 is available

    Moorgate 1.4.1016.1235 is available for download from the 
    Twenty57 website. It contains the following features and fixes

    New Features
    • New standard report - User Activity Report.
    • New standard report - Failed Confirmations Action Report.
    • Management Companies now have a new setting Confirmation Source which specifies where the confirmations will come from.  Options are Finswitch and Confirmation Import Definition.  Only data from the selected source will be processed for the management company.
    • Transaction Imports will now show all failures and not just the first one.
    • Audit Trail for Static Data Changes.
    • The new Holdings Balance message type on Finswitch Confirmation file will be ignored.
    • The entire Finswitch Confirmation import can now be rolled back.
    • Added Created by and Created Date to the Market Action screen.
    • Instruction Date displayed on Failed Confirmation Screen.
    • Cycledate is now mandatory on Transaction Import Definitions.
    • Consolidated report logic changed to calculate closing balances from opening balance + sum(transactions) on both transactions and confirmations.
    • Email notification on saving a tag.
      Need to add the following config settings after upgrade.
    <add key="EmailHost" value=""/>
      <add key="EmailPort" value="25"/>
        <add key="EmailLoginUserName" value=""/>
          <add key="EmailLoginPassword" value=""/>
            <add key="EmailEnableSSL" value="false"/>
            • Removed the results limit on the unresolved Transactions Screen.
            • Allow for internal names to be displayed on the Failed confirmations page.
            • Allow filtering on the dashboard page.
            • Update Reports to report viewer 2012.
            Update your web.config file as follows:
            Replace the reference to the old version of ReportViewer
             <Reference Include="Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL">
               with:
                 <Reference Include="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=MSIL" />
                  In your <system.web> section, add the line
                     <trust legacyCasModel="true" level="Full"/>
                       this speeds up export of reports to Excel.

                          Existing reports will need to be upgraded in VS 2012

                              Repercussions of upgrade

                                • SQL Server Reporting Services 2005 is no longer supported - must use 2008 +
                                • Local mode reports will have to be upgraded to 2010/2012.
                                • Reports are generated a bit differently by this DLL, especially when it comes to HTML formatting. Size of report controls may differ. Table layout of generated reports will definitely differ. If you run a web test suite using Watin, this might affect your tests.

                                      Prerequisites for users may include
                                        Microsoft Report Viewer 2012, which in turn has a prerequisite of SQL System CLR types, http://www.microsoft.com/en-za/download/details.aspx?id=35580
                                          All standard reports will need to be opened in a 2010/2012 VS Reporting Project and saved to upgrade them.


                                            Bug Fix:
                                            • Manual Recon Account selector was empty under certain conditions.
                                            • Recon balancing entry "disappearing" from manual recon screen.
                                            • Prevent the Object reference error on matching a single confirmation where there is no transaction batch.  An empty transaction batch will be created and the balancing entry will be put in it.
                                            • Prevent rerunning a transaction import while once it has been started.