Back to What's New
v6.00.03
What's New / New Features / Transaction Entry HTML Widget

Transaction Entry HTML Widget

Cloud New Feature

Overview

finPOWER Connect Cloud now ships with a dedicated Transaction Entry HTML Widget that mirrors the Transaction Entry form on Desktop. It enables bulk processing of Account Transactions — pick a Transaction Type, enter many account/amount rows, and commit them in one go.

Like the Bank Entry widget, the new Transaction Entry widget runs the commit step as a Background Process. Administrators can queue a large batch and continue working — or close the widget altogether — while the transactions process server-side. Progress can be reviewed later via the widget's Recent page.

This is a long-awaited feature: the original request goes back to October 2022 (J029911). It closes one of the biggest gaps between the Cloud and Desktop transaction-management toolset.

Prerequisites

finPOWER Connect Cloud is in use.
Web Services is configured and reachable. The widget commits via Background Processing, which runs through Web Services.
The user has the standard permissions required to enter Account Transactions and to use the relevant Transaction Types.
At least one Transaction Type is configured to allow Bulk entry (the widget filters the Transaction Type list using the new GetDataViewFilter_AllowTransactionBulk filter).

Setup & Configuration

The widget is built-in and works out of the box. No setup is required for default usage. However, sites that want to customise the widget — for example to apply branding, adjust validation, or add extra fields — can override it via the standard Cloud Configuration override path.

Default usage

The built-in widget HtmlWidget_TransactionEntry v1.00 (13/04/2026) is invoked automatically when the user opens Transaction Entry in Cloud. Nothing to configure.

Overriding the widget

1
Open Cloud Configuration

In Cloud, navigate to Administrator, Cloud Configuration (or open Cloud Configuration directly from Desktop).

2
Locate the Transaction Entry wizard slot

Navigate to Forms & Actions, Processes, Transaction Entry wizard. This is the override point that decides which widget Cloud will load when the user starts a Transaction Entry.

3
Point the slot at your custom widget

Set the wizard to use a custom HTML Widget you have authored. Save the configuration. From the next session, Cloud will load your widget rather than the built-in one.

Reusing the Transaction Type filter

If your custom widget needs to display the same list of Transaction Types as the built-in widget, call the new business-layer function finBL.TransactionTypes.GetDataViewFilter_AllowTransactionBulk. It returns a SQL WHERE string suitable for filtering the Transaction Types collection, so your widget shows exactly the same options as the standard widget.

Desktop form is not customisable

The override path applies only to the Cloud widget. The Desktop Transaction Entry form itself cannot be customised.

How to Use

1
Open Transaction Entry

In Cloud, navigate to Processes & Procedures, Transactions, Transaction Entry. The widget opens on its selection page.

2
Select a Transaction Type

The Transaction Type dropdown shows only those Transaction Types configured to allow Bulk entry. Pick the one that matches the work you are about to enter.

3
Enter rows

Move to the entry grid. Add a row for each transaction with the Account, Amount, Reference, and any other fields exposed for the Transaction Type. The grid supports paste-from-spreadsheet so a long list can be pulled in quickly.

4
Click Commit

Click Commit. The widget queues the work as a Background Process and switches to the Progress page. A live progress bar and event log show the work as it runs.

5
(Optional) Walk away

Close the widget if you wish — the commit will continue running on Web Services. Return later via the Recent page to see the final result.

Platform Differences

AspectDesktopCloud
Surface Native Transaction Entry form (unchanged in v6.00.03). New HTML Widget (HtmlWidget_TransactionEntry v1.00).
Commit model In-process — the user must keep the form open. Background Process via Web Services — the user can close the widget.
Customisation Not customisable. Overridable via Cloud Configuration, Forms & Actions, Processes, Transaction Entry wizard.

Tips & Best Practices

Use the supplied filter for custom widgets

If you write your own Transaction Entry widget override, call finBL.TransactionTypes.GetDataViewFilter_AllowTransactionBulk to get the same Transaction Type list the built-in widget uses. Building your own filter is brittle — the rules around which Transaction Types can be processed in bulk may evolve.

Background Process state lives on Web Services

The Recent page reads Background Process state from Web Services. If you re-deploy or restart Web Services partway through a commit, in-flight runs may be terminated. Plan large bulk runs to avoid Web Services restarts.

Knowledge Base References

Browse the live KB listings for v6.00.03 on the Intersoft support site:

The Knowledge Base articles consolidated into this release notes page: