Web Services Application Pool Recycling

Friday, 13 May 2022 by Paul Hammond

Web Services should always be configured to use their own, separate Application Pool when installed under Internet Information Services (IIS).

IIS allows overlapped Application Pool Recycling to ensure that applications stay available (the overlapped part) when they are being recycled.

Recycling is recommended by Microsoft since most applications are not designed (or are just not stable enough) to run 24/7 indefinitely without at least some form of memory leak or other issues.

DocuSign OAuth 2.0 Implementation

Friday, 22 April 2022 by Gavin Huet

finPOWER Connect version 3.04.04 introduces OAuth 2.0 authentication for DocuSign.

This blog details the changes to DocuSign authentication implemented in finPOWER Connect.

Starting in October 2021, DocuSign began the end-of-life process for all API authentication flows except the recommended OAuth 2.0 flows.

WARNING: From October 2022, all REST non-OAuth 2.0 authentication flows will be fully deprecated in the production environment. After this date only OAuth 2.0 applications will be able to authenticate and make API calls.

To configure finPOWER Connect to use the OAuth 2.0 authentication flow, you will need to set up a new Integration Key in DocuSign, and add the details to the DocuSign Cost Centre within finPOWER Connect.

Script Debugging Enhancements

Tuesday, 5 April 2022 by John Rickard

finPOWER Connect version 3.04.03 introduced support for debugging scripts.

In version 3.04.04 we have made changes to how script debugging is enabled.

Having a debugger enabled is dangerous in a Production Environment. So, rather than enabling via a User Preference, it is now a session based option - with a Permission Key to allow for a User.

This means you have to specifically enable script debugging every time you open finPOWER Connect. Debugging is reset when you close finPOWER Connect or close a Database.

finPOWER Connect Version 4 and 5 Strategic Plan

Monday, 24 January 2022 by John Rickard

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.

Coding Best Practices Part 2

Friday, 14 January 2022 by Gavin Huet

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.

An Overview of Scheduled Processes

Friday, 14 January 2022 by Alex McAndrew

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

Scheduled Processes do not replace the existing manual methods of running these key system processes. They merely provide an alternative for Finance Companies which require these processes to be run with generic parameters on a repetitive basis.

A connected Web Services installation is required for Scheduled Processes to run.

Export Bank Transactions Scheduled Process

Friday, 14 January 2022 by Alex McAndrew

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.

This is supplemental Blog focusing on the Export Bank Transactions Scheduled Process. If you have not yet read the Scheduled Processes overview, we suggest you read it first to understand how Scheduled Processes work; see the Related Blogs section below.

Introducing Script Debugging

Thursday, 6 January 2022 by John Rickard

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.

Preparing for Release 3.04.02

Friday, 8 October 2021 by Paul Hammond

Important things you should prepare for in finPOWER Connect 3.04.02.

This Blog will continue to be updated up until this version is released.

Embedded Google Maps API

Friday, 18 June 2021 by Alex McAndrew

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.


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

<< Prev 123456789 Next >>