Picture of What's New title image. What's New

 

Digitise Apps v10.10

 

Digitise apps can now run under iOS 18 and Android 15. For an existing app created using an earlier version of Digitise Apps (or its predecessor, MX), before you can run the app under either iOS 18 or Android 15, you will need to rebuild it using the latest version of the Digitise Apps Client software.

 

Load the app in the latest App Studio (updating the app if asked), then rebuild the app as normal, selecting the latest version of the software in the Codebase option under the General tab in either the Build Apple Standalone App or Build Android Standalone App dialog box. Once built, you can then redeploy your app to users' devices running iOS 18 or Android 15 in the usual way.

 

Improvements made to App Manager have significantly increased efficiency when working with large numbers of users and/or devices.

 

If you have lots of registered users and/or devices, loading the Users and Devices pages is much faster, as is adding and deleting users/devices and displaying a user's or a device's Properties.

  • There is no limit to the number of users or devices that can be registered with an App Server unless a limit is imposed by your licence.

 

The WriteFile Scripting Method now returns a value indicating whether the requested write operation has been successful or has failed. If the operation has succeeded, the Method will return "True". If it has failed, the Method will return "False". In addition, if the write fails, a call to GetLastError will now return the following error message: "Error reading/writing file".

 

E-mail notifications allow you to configure e-mails to be sent to specified people when specified messages are recorded in the audit and debug log. Notifications are configured in App Manager from the Server Properties page. When configuring e-mail notifications, the following fields now allow more characters to be entered:

  • Send To (max 3999 chars).
  • CC (max 3999 chars).
  • Sender Name (maximum 511 chars).
  • Subject (maximum 511 chars).
  • Content (max 3999 chars).

 

When requesting a build of a Standalone App for Android, the General tab in the Build Settings dialog box now allows you to choose from the following file formats for the generated install file:

  • '.apk' file signed with a 1024-bit signing key.
  • '.apk' file signed with a 2048-bit signing key.
  • '.aab' bundle file.

In addition, this option has now been added into the Build dialog for Android pre-configured Client build requests as well.

 

The version of SQLite used within the Android client has been upgraded to ensure compatibility with the latest Google Play Store requirements. To benefit from these changes, you will need to rebuild your application with the latest version of the Android client Codebase.

 

No changes should be required in your app to support this upgraded version, but if you encounter any issues, please contact the NDL Product Services Helpdesk.

 

An additional Disable Exit option has been added to the Settings tab of the Build Android Standalone App dialog box, aimed at preventing users from closing Android applications using the Back button, and eliminating the potential for unsaved data to be lost.

 

The option is set to No by default, meaning an Android application can't be exited using the Back button. Switching the option to Yes will enable the Back button to be used to close an Android application. Regardless of which of the two options is selected, the Back button can still be used to navigate through opened screens and return to the Home screen.

  • A message will be displayed if you attempt to exit an Android application using the Back button (on the Home screen) if the Disable Exit option is set to No.

For more information, see the Disable Exit section of the Build a Single app Standalone App topic.

 

 

For more information about using Digitise Apps refer to the Getting Started and User Guide sections of this online help.