KNOWLEDGE BASE ARTICLE

Preparing to Upgrade to Version 25

Upgrading from Umango version 23 to version 25 introduces several significant changes that enhance functionality and improve user experience. This article outlines the key considerations and steps to ensure a smooth transition.

Compatibility Considerations


Metadata References for Source Data

In Umango version 25, the logic for referencing source document data has been updated. Previously, metadata references were structured as:

<<EmailSubject>>

In version 25, the new structure is:

<<ImportConnectorName.Data[KeyName]>>

For example:

<<EmailOffice365.Data[EmailSubject]>>

This change allows for more flexible and precise metadata referencing. Detailed instructions on using this new approach can be found in the Umango Metadata Referencing Guide.

Watched Folder Jobs

A critical change in version 25 is the handling of watched folder jobs. These jobs do not automatically upgrade and must be deleted before upgrading to avoid issues. In version 25, watched folder jobs are replaced by more flexible and feature rich Classifiers. Ensure all watched folder jobs are removed prior to the upgrade process.

Email/Folder Sources to Source Connectors

Version 25 introduces source connectors, which replace the previous email and folder watching settings. During the upgrade, these settings in version 23 jobs are automatically converted to their corresponding source connectors in version 25. This transition is designed to be seamless, but it is advisable to verify the settings post-upgrade to ensure accuracy.

Device Sources Assigned by Serial Number

In version 25, device sources are no longer assigned using the device's IP4 address. Instead, they are assigned based on the device's serial number. For TWAIN sources, the serial number is provided by the new Umango Scan Actuator desktop app. This change enhances the reliability and consistency of device assignments.

History Log Source/Destination Description Changes

Version 25 includes subtle changes to the descriptions in history logs, making them more informative and logical. These changes are intended to improve clarity and understanding of the logs, aiding in better tracking and troubleshooting.

Conclusion

Transitioning to Umango version 25 involves several important changes that enhance the application's capabilities. By understanding and preparing for these changes, users can ensure a smooth upgrade process. It is recommended to review all settings and configurations post-upgrade to confirm that everything is functioning as expected. For further assistance, refer to the Umango support resources or contact the support team.

Link to this article https://umango.com/KB?article=146