Moorgate Version 1.4.892.1010 available

A quick release on the back of the last one, build 1.4.892.1010 contains a couple of fixes and can be downloaded from the Twenty57 website.

Fixes:

• Initiate Market Action Proposed Unit error when the balancing entries are across multiple pages
• MSDTC check on install error when installing on Windows Server 2008.

There is no active development planned on Moorgate for the next while. Any critical bug fixes will be addressed and feature requests will be queued. Once the Failed Confirmations screen has been used for a few months we will look at automating the download from Finswitch.

Moorgate 1.4.890.1005 is available

Moorgate version 1.4.890.1005 is available for download from the Twenty57 website.

It contains the following features:

• Failed Confirmations screen Filter and Export to CSV
• User Maintenance role. A person assigned to this role only has access to the User Screen. They can create and edit all users except for Admin users. They cannot assign users to the admin role and they cannot edit their own role
• Static Data Maintenance role. Access to the Balancing Entry Type, Tag Type, Product Companies, Product, Fund Companies, Funds and Account screens only to maintain static data
• Included Market Action Status on the Internal Transaction grid of the Manual Recon screen and remove Market Action ID column
• New standard reports added: Last Closing Balance Report (Standard), Unresolved Transaction Report (Standard), Current Reconciliation Status Report (Standard), Current Reconciliation Status Report Per Fund (Standard)
• Order Product dropdown in the Account selector alphabetically

Minor bug fixes:

• Prevent duplicate Market Actions being created in the table
• Ensure Balancing entries are updated and deleted correctly when unreconciled and used in multiple reconciliations
• Remove Reconciliation. Don't show the remove pop-up if the transactions cannot be unreconciled (balancing entry is included in a Market Action which has already been authorised, submitted or completed)
• Edit Failed Confirmation Save error because of balances not matching due to rounding

We are working on a few more standard reports. As we identify others we will add them. Thanks to Jai and the development team for the work done

Moorgate 1.4.855.951 is available

Moorgate 1.4.855.951 is available for download from the Twenty57 website. It is the first version on .Net Framework 4 so please take note of the install instructions below. But with all install enhancements we have done I guarantee that it will be the easiest "Clean Install Upgrade" you have ever done.

New Features:

• .net Framework 4
• Clean Install now supports Windows Authentication
• Test Db Connection when installing. NB. On a clean install we only test the server and connection to the Master Db since at this stage we don't yet know if the database exists and must be updated or if it needs to be created. On Upgrade we test the entire connection. We can't stop you proceeding if it fails (yet) but you will get a warning that you have to dismiss to continue.
• Import definition performance improvements for large volumes of Data
• Standard Report Captured Confirmations Updated
• Include External Fund Code in the Account Selector ribbon
• Include External Fund Code in the Account Selector pop-up
• Allow the Account Selector pop-up to move in order to see long static data lists more easily

Bug Fixes

• Finswitch Import creating Opening and Closing Balance Records in the External Table
• Manual Recon Screen: Loading Internal Transactions into the Matched Section when the Last Tag and Last Tag Type columns are visible error
• dd/MM/yyyy format issue with days less than 13

.Net Framework 4 Install instructions

A clean install is much simpler but if for some reason you can't/don't want to do one let me know and I will provide you with the necessary config file changes. With all the msi enhancements though a clean install takes seconds!

1. Uninstall your existing version of Moorgate
2. Delete all the sub folders in your parent Moorgate directory (eg C:\Program Files\Twenty57 Moorgate)
3. Run the msi for build 1.4.851.945
4. Specify your install path. Default is C:\Program Files\Twenty57 Moorgate
5. Select all options except the Virtual Directory. Yes, you can now upgrade the Database in a clean install
6. Enter your Database credentials. Remember we can only check the server connection and that the credentials can log into the Master Db in clean install mode. 
7. Choose your authentication method and specify the user.
8. Click Finish and complete the install.
9. On your existing Virtual Directory change the Framework version from 2.0.50727 to 4.0.30319. In IIS7 and above you do this on the application pool and in IIS6 you change it on the Virtual Directory itself.

And Voila! you are done. The Database will be updated and your config files will have the right values. No need to run the database updater or edit your config files in anyway. 

Many thanks to Jai and the team for the fantastic install changes made (and everything else). We are busy adding some more Standard Reports as well as including some of the small feature requests.

Moorgate Release: 1.4.831.904

Moorgate build 1.4.831.904 is available for download from the Twenty57 website.

It contains the following features and fixes:

New Features:

• Capture and Edit Transactions: Units are calculated if the amount and price are entered
• Capture Take-on Balances: Allow the Capture of a take-on balance from the Manual Capture and Failed Confirmations Edit screens for the first batch captured for an account
• Set up guidelines on Import Definition Screens: Open help box allows you to reference the information and work on the definition at the same time
• Finswitch File data in invalid format handling: Data in the FS file which we cannot resolve into valid batches is displayed to the User via a link 'Finswitch Records not Processed' on the Failed Confirmations Screen
• Failed Confirmations: Proper handling of the error Combination of codes cannot be mapped uniquely
• Failed Confirmations removed by the User are not deleted from the Database. Their Status is Updated to 3 (Removed) so that they can be reported on if necessary
• Include ReconID in the default filters
• Account Set up screen: Add columns Active and External and Internal Product and Fund Columns
• Import balance only records into Moorgate from the Finswitch File
• Process Details message: Pop up does not stop you working on with Moorgate and Confirmations message reordered to list failed batches first.

Bug Fixes:

• Imports failed unless all columns were specified even if the columns were not mandatory
• Import Definition error: Value was either too large or too small for an Int32
• Auto Match error when no transaction type is specified
• Account Selector: Allow selection of second account linked to the same Product and Fund.

With this release we should be handling all the exceptions that can appear on a Finswitch File. I will give it a while to be adopted and to ensure there are no other data exceptions which come to light and then we will look at automating the download of the Confirmation file directly from Finswitch.

This is the last build on Framework 3.5 (excluding critical bug fixes). We are upgrading to Framework 4 soon. We will also be including some standard reports going forward.

Thank you to the developers for the work done.

Moorgate Build 1.4.796.838 available

Please download  Moorgate 1.4.796.838 from the Twenty57 website.

It contains essential updates and fixes to the Finswitch Confirmation File import process and Failed Confirmations screen.

Moorgate version 1.4.792.824 available

Moorgate 1.4.792.824 is available for download from the Twenty57 website. It is a bumper release with a number of enhancements to the Finswitch Confirmation File import process and Failed Confirmations screen as well as additional features and fixes.

FS Import Enhancements

• Use Cycle Date rather than Value Date to determine Batches
• Show a 'Batch saved successfully' message when saving a Failed Confirmation batch
• Bug Fix: Error when first or second batch saved from the Failed Confirmation Screen
• Cancel Button on the Edit Failed Confirmation Screen
• Proper handling of duplicate codes on multiple funds/products on the Failed Confirmation Screen
• Balance Tolerance added for Opening Balance <> Previous Closing Balance and Opening Balance + sum(transactions) <> Closing Balance. Tolerance setting per Fund Company defaulted to 1 unit. If the difference is less than the setting, the batch is processed using Moorgate's balances. If it is more, then the batch fails and appears on the Failed Confirmation Screen.

Other Enhancements

• Streamlined install - only one option, remembers the install path, checks if the database exists and if yes then update it, else try to create it even on a clean install
• Balancing Entry Process change: When breaking a match, only delete the balancing entry if both sides are unreconciled.
• Dashboard: Only refresh the grid, not the entire page
• Import Definitions: Test button added
• Automatically assign users to a new Fund Company
• Order Products alphabetically in filters
• Default rule Group Internal and External by Account, TransactionType and ValueDate updated 

Bug Fixes

• Error in account selector when new Fund Company added
• Only show distinct values in Filter Account drop downs
• Allow use of quotations (") in static data names
• No paging on Market Action screen
• Duplicate Market actions show for Funds with 2 Internal Codes

Hopefully the changes make the FS Confirmation file import smoother, installs easier and provide benefit to the balancing entry process and the associated reporting. Thank you to Jai and the developers for the work done. As always, please send me your feedback and ideas.

Moorgate 1.4.754.751 is available

This build fixes a small bug. It will affect you if you are reporting on Deleted Transactions. Otherwise wait for the next build which will have more new features in it. As always, the build is available from the Twenty57 website.

External Deleted Transactions were being saved to the ExternalTransactionDeleted Table with the incorrect TransactionTypeID. We have amended that.

The next release will see substantial changes to the Moorgate install to make upgrades and new installs even easier: adding database checks and connection string tests and remembering your install path among other enhancements.

And then it is more enhancements to the Finswitch Confirmation File import and automation of the Finswitch processes.

Build 1.4.753.749 is available - Bug FIx

Moorgate version 1.4.753.749 is available from the Twenty57 website.

It contains a fix for the bug identified in released versions 1.4.750.743 and 1.4.715.689. If you are testing either one of these versions please upgrade to this build as soon as possible.

Bug Fix

• Negative confirmations (Repurchases, Switch Out etc) captured manually were displaying as positive values on the Manual Recon and View Confirmation Screens.

New Feature

• Details link included in the View Transactions and View Transactions Across Accounts screens.

Moorgate 1.4.750.743 is available

Moorgate 1.4.750.743 is available for download from the Twenty57 website.

It includes:

• Bug: Apostrophe in a filter value caused the filters to be 'lost'
• Apply Datetime mask to Manual Capture Dates
• Assign Users to Mancos. All existing users are assigned to all Mancos for their active Product Companies
• Use the default connection string supplied in the web.config file for auto recon rules- no need to specify it for each dataset in every rule
• Cancelled Recons are logged with a datetime stamp, user and reason.
• Save profiles on the View Transactions/Confirmations across accounts page
• Include Internal Fund Code on the Market Action screen

Moorgate.1.4.715.689 is available

There is a new version of Moorgate available from the Twenty57 website.

The main new feature is the significant changes to the Finswitch Confirmation File import and error handling. Moorgate will now import all the confirmations in a file that it can and provide you with a screen to handle those that failed.

• New screen 'Failed Confirmations' that lists all confirmations that could not be imported. This screen can be reached from the dashboard and the Transactions menu.
• Links to the Static data screens to update Moorgate data when mapping failed.(Confirmation File Import Missing Account Action setting on Product Company setup is set to Fail)
• New Setting on Product Company Setup: Confirmation File Missing Balances Action (default is Ignore). If set to Ignore Records on the Finswitch file with no balances are accepted automatically using the Moorgate balances. If set to Fail they will appear on the Failed Confirmation Screen for the user to follow up on.
• For missing Balances or Opening Balance on the Finswitch file does not equal Moorgate's previous Closing Balance the user can verify the batch and capture any missing transactions directly if needed.
• Failed Confirmations can be removed completely without fixing them. The user will then need to capture them manually.

Additional Features and Bug Fixes:

• Exclude Balancing Entries from the Unresolved Transaction Count on the Landing Page.
• Include the Static Data codes on the View Transactions across Accounts and View Confirmations across Accounts pages.
• Account selector breadcrumb: correct dependency of Product Company, Product, Fund Company, Fund and Account.
• Bug: Error when capturing first confirmation movement on an account.
• Bug: Match note was not populating with the Auto Match Rule name.
• Bug: Multiple matches were combined in one match.
• Bug: Balancing Entry Type ID was shown instead of the name in the matched section of the manual recon screen.

A very big thank you to Anand and the team for this build. There was significant development needed to change how the Finswitch file logic works.

Please send me all your feedback. The Failed Confirmation screen and Error Handling process are new concepts in Moorgate and need your input to become even more streamlined and useful.

Integration with Finswitch - the next step for Moorgate

Finswitch Trade Confirmation and Price files can be imported into Moorgate. But it is still a manual process. And Confirmation files can have a number of exceptions which currently need to be dealt with one by one - a very tedious exercise. So we are fixing that.

We are currently busy redesigning how the Confirmation file is processed in Moorgate. Instead of rejecting errors one by one, we will import the entire file, apply ordering to it to ensure the accounts and transactions are grouped together correctly and then process what we can and provide an interface within Moorgate to handle the exceptions - static data issues, balance issues and the like. Expect this functionality in the next 2-3 weeks, if not sooner.

Once that is done we will be able to automate the download of the Confirmation file from Finswitch using the available web services and automatically import it. The user will then just need to address any exceptions.

Price files are available at 6pm daily - using the web services we will automate the download and import of these too.

Finswitch is also now providing the ASISA generated Quarterly Asset Allocation Data through their system. Moorgate will be enhanced to download and import this data to minimise the need for manual capture and allow you to do your Asset Allocation Reporting more quickly.

And as a final cherry on the top of Finswitch integration we will provide a Finswitch format Transaction Request file from the Authorised Market Actions which can then be automatically uploaded into Finswitch if required.

These enhancements will make Moorgate the obvious choice for any company in the South African market looking for Unit Reconciliation software. And of course make the daily processing for our current users even simpler.

Moorgate Build 1.4.673.595 is available

The latest build of Moorgate available on the Twenty57 website contains bug fixes. Most of these are to the Market Action Process and Screens. The approach to dealing with Market Actions in Moorgate is very different to Unit Recon but I think we have ironed out all the kinks now.

Bug fixes are:

- Bug: Proposed amount is calculated in cents instead of rands in initiate market action screen.
- Bug: Incorrect values are displayed in proposed units field while initiating market action having units >= 1000. - Bug: When units column is placed anywhere except position 3, the wrong value is shown as proposed units in initiate market action screen.
 - Bug: Numbers on market action and initiate market action do not have space as the thousand separators.
 - Bug: When trying to remove confirmations, a datetime/string conversion error comes up when DateDisplayFormat is set as dd/MM/yyyy.
- Balance Check on Transaction Imports only looks at Import Batches and not at Balancing Entry Batches.

The next development work planned on Moorgate is better handling of Finswitch Confirmation file import errors (allowing all correct confirmations to be imported and providing an interface to edit the rejected lines) as well as the ability to reject an Authorised or Initiated Market Action.

Thanks to Anand and the team for all the development done.