To help our finPOWER Connect Users plan for the future we have developed an outline of what the next two major finPOWER Connect versions will look like. We have reviewed a number of options for the future of finPOWER Connect and decided on a cautious approach that should provide many benefits in the long term.

Every few years we seem to have major shifts in the technology environment that we rely upon, whether its moving from DOS to Windows, Access to SQL Server, VB6 to .NET or Desktop to Cloud.

With this in mind and looking at where technology is headed we thought we'd give an update on our strategic plan for finPOWER Connect over the next few years. Our plan covers the next two major versions, culminating in version 5.0 in 2024.

This blog outlines coding practices that any professional developer using the finPOWER Connect API should adhere to.

finPOWER Connect is written entirely in VB.NET. All sample scripts are also written in VB.NET. Although C# is an option, Intersoft Systems does not provide support for this.

2019 saw the introduction of "Scheduled Processes" to finPOWER Connect. This allowed key system processes (which could be long-running) to be configured on a schedule within finPOWER Connect, and then automatically executed (via a connected Web Services installation) where manual User interaction is not required.

Up until recently the only supported Scheduled Processes were Account Processes and running of a Script. 2021 saw a major enhancement of this area of the system, and as of writing this Blog the following processes can be configured for finPOWER Connect's Scheduled Processing (where licenced):

• Account Processes
• Disbursement Account Payments
• Export Bank Transactions
• Pending Service Requests
• PPSR NZ Update
• PPSR B2G AU Update
• Process Direct Debit Payments
• Retrieve SMS Status Updates and Replies
• Script
• Securitisation Allocations

The purpose of Exporting Bank Transactions is to generate a file which is then sent to a bank.

When run as a Scheduled Process, i.e., run from Web Services on a Web Server, the file system may not be the appropriate place for a file to be exported to. Therefore, the Export Bank Transactions Scheduled Process gives the User some flexibility on how this file is generated. Because of this, the parameters which can be configured differ somewhat from those in the existing Export Bank Transactions form.

finPOWER Connect version 3.04.03 introduces support for debugging scripts.

This is very useful to delve into script code whilst it is running, and then, for example, trace code and examine variables.

Important things you should prepare for in finPOWER Connect 3.04.02.

Version 3.04.00 introduces support for Google's Maps Embed API embedded map.

Traditionally, embedding an interactive Google map onto a website was done without the need for any authentication or API keys. You would create an iFrame with the source looking something like the below URL, and you would get a fully interactive Google Map placed on your website.

http://maps.google.com/maps?q=19+Marine+Parade,Bluff+Hill,Napier,New+Zealand&output=embed

finPOWER Connect uses this to display the Client map in the Client Key Details Summary Page.

Google now prefers the new embedded map approach, which requires an API Key. They are pushing this method so much so that they have removed any reference to the old method in their documentation. More information about the new API can be found in the Google documentation here:

The Maps Embed API overview

Version 3.04.00 introduces the Positive Commercial Bureau Data Update for Centrix in New Zealand.

Centrix uses the data provided in this uploaded file to add additional information within the Commercial Report Product. For more information see Centrix NZ Commercial Report; updated to include Positive Bureau Data.

Important things you should prepare for in finPOWER Connect 3.04.00.

This blog outlines coding practices that any professional developer using the finPOWER Connect API should adhere to.

finPOWER Connect is written entirely in VB.NET. All sample scripts are also written in VB.NET. Although C# is an option, Intersoft Systems does not provide support for this.