| | Categories: Blog, Software Updates

November software update

In the November 2018 software update there are two main changes that may be useful to you, and as always there are a number of other small changes which are documented within the ‘Release History’ which can be accessed from the home screen. 

The two changes that you may be interested in are:

 

Option to skip the report criteria screen when running reports

Do you have some reports that you always run for the same selection criteria?

To improve the efficiency of running these reports you can now tick a checkbox at the bottom of the selection criteria screen to tell Twinfield not to display the selection criteria screen next time you run the report:

Twinfield report criteria screen

Next time you run the report it will be displayed immediately without displaying the above screen. 

If you also create a shortcut to the report on your home screen, then you can effectively run the report with just a single click.

Twinfield single click reports

To revert back to displaying the selection criteria screen, simply click the ‘Criteria’ button at the top of the report and untick the checkbox.  The next time you run the report, you will then be prompted to enter selection criteria.

In addition, if you have multiple customised versions of the same report, the ‘Do not prompt for criteria the next time this report is opened’ checkbox relates to the specific version of the report.

Note: This is a user setting, meaning that whilst you may not want to see a report selection criteria, changes you make will not affect whether others users see that screen.

 

API change

If you use our open API to connect other software to Twinfield you may be interested to know that browse codes 130 (debtors) and 230 (creditors) has been improved to enable filtering on modification date and open amount.  For more information about these changes please refer to our API documentation.

 

Reminder: We’re retiring the “Classic” desktop

Later this month we will also be retiring the ‘Classic’ desktop.  Full details about this change can be found here, and a short video discussing the changes can be found in our knowledgebase here.  This change will be made without any downtime.

| | Categories: Blog, News, Software Updates

We’re retiring the “Classic” desktop

In November 2018, Twinfield’s “Classic” desktop will be deactivated and anyone logging into Twinfield will be automatically taken to the new desktop.  In this blog we explain why we’ve taken this decision and what it will mean for our users. 

Before we explain why we’re making this change, it’s important to say that we’re not removing the Classic functionalities – these can still be accessed via the new desktop.  And if you regularly use certain Classic functions, you can include these as favourites on your desktop.

Most users already use the “new” desktop, and have been for several years.  Even among those who still log in via the Classic desktop, we know that a large number regularly use the new desktop to perform daily work tasks as much of our new functionality developed in recent years is only available via the “new” desktop.

 

 

Why is the Classic desktop being deactivated?

Put very simply, the new desktop offers more possibilities.

Since the launch of the new desktop we’ve continued to support the Classic interface even though some new features were only available in the new desktop.  In the future we’ll be introducing a new and improved method of logging in which only works with the new desktop, and will be continuing to develop new functionality using new technology that will be incompatible with the old Classic desktop.  We feel that now is the right time to deactivate the Classic desktop.

Also, when it comes to providing support it is useful if everyone is using the same interface and looking at the same screens.  This provides consistency and clarity and all our training and webinars are provided utilising the “new” desktop.

When will this change be implemented?

The change will be implemented in November, but if you want to, you can switch to the new desktop immediately.  Simply click ‘Try the new Look & Feel of Twinfield’ in the upper right of the Classic desktop and then click the ‘Use this Look & Feel by default’ in the lower left of the new desktop to set that as your default.

 

 

 

 

 

 

 

What’s in it for me?

The new desktop provides an improved user experience.  You can create your own shortcuts to almost any area within Twinfield, open additional tabs, use the ‘Search’ function to find what you are looking for, and access both Neo and Classic functionality from the same menus.

You also have the ability to add your most frequently accessed companies into a ‘portfolio’ which makes access to these companies more efficient, and switching between companies is also much faster.

Can I return to the Classic desktop?

No.  Once we’ve made the change (in November), you won’t be able return to the Classic desktop.

Are there any additional costs?

No.  The new desktop is part of your current subscription and there will be no additional costs for using it.

Getting used to the new interface

It may take a little while to adjust to the new desktop, but we’re sure you’ll find the change worth it.  If you have further questions, please feel free to ask!

 

| | Categories: Blog, Software Updates

July and August software updates

The first half of 2018 has been focussed on many behind the scenes improvements to the Twinfield software, and those improvements are continuing during the remainder of this year.  This means that there is often very little to report when we release the monthly software updates.

In July we changed the Twinfield knowledgebase, and this is now being widely used.  If you haven’t yet had an opportunity to use the new knowledgebase, simply click the ‘?’ icon within the Twinfield toolbar and you will see the new and improved knowledgebase.  If you type ‘webinar’ in the search field and click on the ‘Twinfield webinar schedule’ article you can view a 10 minute demonstration of the new knowledgebase which was a part of our July monthly Q&A webinar.

This month, August, we have another small change that may be useful to you, and that is the ‘External Application Permissions’ overview screen.  This is available to all users from within the Access Settings screen, and displays a list of external applications that have access to your Twinfield data.

 

| | Categories: Blog, News

API support for TLS versions 1.0 and 1.1

Action Required for Web service / API Integrations

We’ll be retiring support for TLS versions 1.0 and 1.1 on all Twinfield sites, including Twinfield’s API. This change improves the security of the data sent between you and Twinfield, whether you’re accessing Twinfield through a browser or communicating directly with our API.

We strongly encourage any developers who are using the Twinfield API to ensure that their software supports negotiating TLS 1.2 connections, and to coordinate with their system administrators to update software to take advantage of newer TLS versions. In addition, we recommend proactively switching over to TLS 1.2 when communicating with Twinfield’s API by modifying your API client software to enforce TLS 1.2 negotiation.

Please refer to the compatibility guidelines below:

Platform or Library Compatibility Notes
Java (Oracle)

Compatible with the most recent version, regardless of operating system

Java 8 (1.8) and higher Compatible with TLS 1.2 by default.
Java 7 (1.7) Enable TLS 1.2 using the https.protocols Java system property for HttpsURLConnection. To enable TLS 1.2 on non-HttpsURLConnection connections, set the enabled protocols on the created SSLSocket and SSLEngine instances within the application source code. Switching to IBM Java may be an effective workaround if upgrading to a newer Oracle Java version isn’t feasible.
 
Java (IBM)
Java 8 Compatible with TLS 1.2 or higher by default. You may need to set com.ibm.jsse2.overrideDefaultTLS=true if your application or a library called it by it uses SSLContext.getinstance(“TLS”).
Java 7 and higher, Java 6.0.1 service refresh 1 (J9 VM2.6) and higher, Java 6 service refresh 10 and higher Enable TLS 1.2 using the https.protocols Java system property for HttpsURLConnection and the com.ibm.jsse2.overrideDefaultProtocol Java system property for SSLSocket and SSLEngine connections, as recommended by IBM’s documentation. You may also need to set com.ibm.jsse2.overrideDefaultTLS=true.
.NET

Compatible with the most recent version when running in an operating system that supports TLS 1.2.

.NET 4.6 and higher Compatible with TLS 1.2 or higher by default.
.NET 4.5 to 4.5.2 .NET 4.5, 4.5.1, and 4.5.2 do not enable TLS 1.2 by default. Two options exist to enable these, as described below.

Option 1:
.NET applications may directly enable TLS 1.2 in their software code by setting System.Net.ServicePointManager.SecurityProtocol to enable SecurityProtocolType.Tls12. The following C# code is an example:

System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

Option 2:
It may be possible to enable TLS 1.2 by default without modifying the source code by setting the SchUseStrongCrypto DWORD value in the following two registry keys to 1, creating them if they don’t exist: “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319” and “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319”. Although the version number in those registry keys is 4.0.30319, the .NET 4.5, 4.5.1, and 4.5.2 frameworks also use these values. Those registry keys, however, will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. It is thus advisable to test this change before deploying it to your production servers. This is also available as a registry import file. These registry values, however, will not affect .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.

.NET 4.0 .NET 4.0 does not enable TLS 1.2 by default. To enable TLS 1.2 by default, it is possible to install .NET Framework 4.5, or a newer version, and set the SchUseStrongCrypto DWORD value in the following two registry keys to 1, creating them if they don’t exist: “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319” and “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319”. Those registry keys, however, may enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. We recommend testing this change before deploying it to your production servers.

These registry values, however, will not affect .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.

.NET 3.5 and below Not compatible with TLS 1.2 or higher encryption
 
Python

Compatible with the most recent version when running on an operating system that supports TLS 1.2.

Python 2.7.9 and higher Compatible with TLS 1.2 by default.
Python 2.7.8 and below Not compatible with TLS 1.2 or higher encryption
 
Ruby

Compatible with the most recent version when linked to OpenSSL 1.0.1 or higher.

Ruby 2.0.0 TLS 1.2 is enabled by default when used with OpenSSL 1.0.1 or higher. Using the :TLSv1_2  symbol with an SSLContext’s ssl_version helps ensure that TLS 1.1 or earlier is disabled.
Ruby 1.9.3 and below The :TLSv1_2 symbol does not exist in 1.9.3 and below, but it is possible to patch Ruby to add that symbol and compile Ruby with OpenSSL 1.0.1 or higher.

 

| | Categories: Blog, Software Updates

February 2018 Software update

Before I take you through the changes in this month’s software update, you may be interested to know that due to popular demand we are bringing back our monthly webinars in 2018.  The format of these webinars will change slightly however, and will become an opportunity for you to ask questions in a live Q&A session on a monthly basis. 

The webinar presenters will also change from time to time.  Rather than just me presenting the webinars, there will be other members of our team sharing their knowledge with you. 

We will continue to demonstrate the changes in each month’s software update, but we encourage you to use these webinars as an opportunity to ask questions about anything to do with your use of Twinfield.  Full details are available by searching for ‘webinar’ and selecting ‘Twinfield webinar schedule’ within the Twinfield knowledgebase.

 

What’s in the February software update?

In our first software update for 2018 we have four changes that I wanted to document for you.  These are:

  • New Audit Trail listing
  • New report: VAT overdue invoices
  • Neo sales invoices VAT in base currency
  • New VAT list screen

 

Audit Trail

The new Audit Trail is a list view that initially enables you to list all changes to supplier bank accounts.  This will be enhanced in the future to enable reporting on other changes within Twinfield.

To run the Audit Trail, click the new ‘Audit Trail’ icon on the Reports screen:

In this release the listing will display all supplier bank account changes made within the last 12 months.  This can be filtered in many ways:

We will advise when more functionality is added to this new screen.

 

New report: VAT overdue invoices

Due to a change in Dutch VAT legislation a new report has been added to the VAT category which may be of interest to other users as well.

The new report enables you to report on the VAT content of outstanding sales and purchase invoices as follows:

  • Select the new VAT Overdue Invoices report from the VAT reports menu
  • Enter selection criteria:
  • The result will be a list of both sales and purchase invoices which meet the specified criteria, grouped by VAT code:

This report is available to all users in Level 1, 2, 3, and 4 roles.

 

Neo sales invoices VAT in base currency

If you process a sales invoice in a foreign currency and the invoice includes VAT, the VAT Summary section now displays the VAT exclusive and VAT amounts in both base currency and transaction currency as required by European law.

 

New VAT list screen

As a part of our ongoing work to update our list screens we have now updated the VAT rates screen to bring it into line with other screens.  Please see example below:

 

 

The above is all I wanted to cover this month.  Don’t forget our monthly webinars which start on the 23rd February.  Search for ‘webinar’ within the Twinfield knowledgebase for full details and links to register.

 

Richard McChesney
Product Manager for Twinfield and Basecone in the UK and Ireland