Skip to content

29th November 2024

Major update to underlying system

This version is a major change and should be tested thoroughly on a test system before being moved to production. We always test on a number of different systems and configurations but it is always possible for something to behave slightly differently on your setup.

Major

[OA-307] [IMPROVEMENT] Full redesign of the underlying architecture to allow the screen to be used across multiple clients in the same session

[OA-337][OA-318] [IMPROVEMENT] Full implementation of legal entity function to allow the system to integrate with different queues for different entities

[OA-215] [IMPROVEMENT]Add a logging tab to the system for cloud users so you can see SOME of the logging information without the need to get a logfile from Unit4.

Minor

[OA-334] [IMPROVEMENT] Allow a role to be added to the admin clear flags which will let people in this role, see the clear flags button

[ISD-149] [IMPROVEMENT] Deleted items never have their status updated to completed to allow for easier tracking.

[ISD-143] [IMPROVEMENT] Allow for document index refresh if indexes are changed on an exiting document type.

[OA-339] [BUG] Fix issues with saving password against legal entities

[OA-340] [IMPROVEMENT] add additional message on failure to get a statement license, further up in the logfile

[OA-343] [IMPROVEMENT] Improvements to retrieval of statement queue information

[OA-346] [BUG] Resolve issue where admin_clear_flags still had a lingering form.client in it and so caused an issue when it was on and a report was being run.

[OA-347] [BUG] Resolve issue where if absolutely no entity parameters were on in the system, a null was returned rather than a blank table causing the screen to crash

[IMPROVEMENT] Small fix to the installation script to correct an error

New System Setup Values in this release

NONE

New Invoice Flags introduced in this release

NONE

Known Issues

  • We are aware with an issue with the indexing fields where a manual update is not possible on some fields, this appears to be a browser issue and we are working to resolve it. Index fields which are automatically filled and updated by header fields are not affected and updating the header field manually will result in the index field updating.