IN THIS PAGE

v2020.1.1 (12.1.1)
What's New in MOVEit Transfer 2020.1
Release Notes are available in the following languages:
You can download the 2020.1 release of MOVEit Transfer from the community products page.
Microsoft SQL Server 2019
You can now deploy MOVEit Transfer to use the newest version of MS SQL Server (MS SQL Server 2019) for your database platform. See supported databases for full database support options.
If you do not have an existing database, you can also choose MySQL at install time to install a free database bundled in the installer. For details, see Supported Databases and the MOVEit Transfer Install Guide.
ADFS 4.0 and 5.0 Support
We tested Windows Server 2019 AD FS (also referred to as "ADFS 5.0") and Windows Server 2016 AD FS (also referred to as "ADFS 4.0") with MOVEit Transfer. For details, see the MOVEit Transfer Administrator Guide.
Tip You can leverage ADFS as an external authentication source. Additionally, within a Single Sign-on model, you can use ADFS as a trusted identity provider.
Mobile and Desktop Single Sign-on
You can now use enterprise credentials or custom identity providers (IdP) for friction-free sign-on to MOVEit Mobile and MOVEit Client by authorized users. For details on how to configure SAML message passing with a trusted identity provider, see the Administrator Guide.
MOVEit Mobile Single Sign-on
If Single Sign-on (SSO) is enabled for your organization, an SSO link displays. From there, users can choose an Identity Provider (IdP) (assuming more than one is configured for their organization).
Specify Server |
Single Sign-on Option |
MOVEit Client Single Sign-on
Single Sign-on Option (MOVEit Client) |
Multi-Org Gateway
If you are using MOVEit Gateway 4.1 or newer, you can use the MOVEit Gateway Admin UI to specify a different endpoint (in other words, sign-on URL) for each organization (Org) in your MOVEit Transfer deployment. For more details, see the MOVEit Gateway documentation.
To define Org-specific MOVEit Gateway, you must apply configuration details (including the MOVEit Transfer Org ID) at the MOVEit Gateway Admin UI. For details, see the MOVEit Gateway documentation.
RESTful API Improvements
The following new capabilities were added for the 2020.1 release of MOVEit Transfer.
Feature |
Description |
Endpoint |
Return logs current user can view Return specific log data |
|
|
Allow a SysAdmin to create and define a new Org |
||
Create and apply password aging policies to user classes. |
||
Create and apply user expiration policies to user classes. |
||
Specify how long system and org logs are kept |
||
Import custom report definitions. |
Fixed Issues
This section outlines issues tracked and fixed by the MOVEit product team for the 2020.1 release. Not all changes suggested by customers or uncovered in usability testing are tracked as issues or defects. See the What's New section for a broader view of these improvements.
ID |
Category |
Fixed Issue |
4210 |
Web Farm Pattern |
Fixed issue in Webfarm deployment where the Gateway tab (MOVEit Transfer Config Utility) was replicated for each MOVEit Transfer Server node. |
4248 |
Download Wizard |
Fixed case where using Azure Blobs for the MOVEit Transfer filestore and opting for MOVEit Transfer encryption could result in download failures (or validation check failures) when downloading large (> 10,000,000 byte) files. |
4364 |
SSH Module |
Fixed issue where after upgrade from 2019.2, the SSH server reported a fault, possibly due to server load. |
5237 |
Legacy Uploader |
Fixed issue where if using the legacy uploader (pre 2019.2), MOVEit Transfer could block a file upload based on X-Forwarded-For header leveraged to identify proxy traffic. |
5287 (10525) |
Sign-on/MFA |
Fixed customer reported issue found when using MOVEit Transfer MFA with MOVEit Gateway. |
7027 |
Security |
Fixed SSRF vulnerability where an authorized admin user could view recently-downloaded filenames. |
7065 |
Security |
Fixed X-FRAME-OPTIONS setting to ensure security best practices when handling HTML frames. |
7167 |
HA Service |
Fixed small memory leak. |
8683 (382921) |
Security |
Fixed a security error that could allow an authorized user to view another user's default directory, under certain unusual circumstances. |
4213 |
WebUI |
Fixed issue where downloading a saved report file using the WebUI could result in a partial copy of the file (and fail file validation). |
4740 |
WebUI |
Fixed issue where GroupAdmins could grant Folder Sharing permissions to a Regular User, but at a later time the UI did not provide controls to remove the privilege. |
11537 |
WebUI |
Fixed issue where typing in Create User As a Clone of field failed to auto complete with a list of current users to clone. |
4943 |
Silent Install |
Aligned with .NET dependency that triggered install of 2020 to fails with "Could not encrypt the responses" error message. |
6067 |
Admin Guide |
Fixed issues and updated Settings > Security Policies > Password topic in Administrator Guide. |
4159 (12239) |
Download (Security) |
Fixed case where file not downloaded when at the same time the platform allowed filenames comprised of quotation mark characters. CVE-2020-XXXXX. Fix for 4159 also addressed XSS illegal filename vulnerability. Version affected: 2020 (and earlier). Version fixed: 2020.1 Credit: Mark Galea |
5316 |
Security |
Resolved file information disclosure that could be possible when certain folder inheritance settings were met. |
4396 |
DMZOrgCopy |
Fixed issue where a previous version of DMZOrgCopy utility did not copy MOVEit Transfer Group table record. |
11540 |
Ad Hoc Message/security |
Fixed case where script tags need to be removed from Ad Hoc messages. |
11644 |
Logging/WebUI |
Fixed issue where blank log entry is written after blank client key is uploaded. |
30646 |
Sign-on |
Fixed issue where a new user account could not sign-on from MOVEit Automation. |
30736 |
REST API |
Fixed case where Multi-threaded clients could run into database layer exceptions under high load. |
30648 |
REST API |
Aligned behavior with WebUI so REST API client is routed to the correct identity provider based on current or default org. |
Upgrading
This section explains how you can upgrade from an earlier version of MOVEit Transfer.
Upgrade Paths
Reasons you should upgrade:
- Get the latest features. Full-featured mobile app integration, simplified Gateway deployment configuration, REST API, and much more.
- Ensure your product is up-to-date. Get ongoing improvements, fixes, the latest support of the MOVEit teams, and take advantage of the improvements and wins requested by the rich ecosystem of Progress users.
- If you have a support subscription, upgrades are free. Read this community article for evaluators and check your product license.
MOVEit Transfer 2020.1 supports "direct upgrade" (upgrade by way of running the MOVEit Transfer installer) for existing MOVEit Transfer 2018 (10.0.0) and newer.
Use the Upgrade Path table to find out how you can move earlier or legacy versions to MOVEit Transfer 2020.1.
Your Older MOVEit Transfer Version |
Upgrade Path |
MOVEit Transfer 2018 (10.0.0) or newer |
Use Upgrade mode in MOVEit installer:
|
MOVEit Transfer 2017 PLUS SP1 (9.6) and older |
If you are running a version that is out of date or close to being out of date, you can:
|
Get the Installer
To get a MOVEit installer package:
- Sign-in to the Progress Customer and Community portal.
Download the product package. (When you get your MOVEit product package from your Progress Community page, the activation code is already embedded).
- Before you run the upgrade installer:
- Review Upgrade Guidelines. They identify useful tips and guidelines for existing MOVEit Transfer or MOVEit DMZ users.
- It is a good idea to copy and save your current product serial number. This Progress knowledge base article explains how to find it.
Get an Activation Code
For upgrades, activation codes are applied automatically when you run the MOVEit Transfer installer.
- Your upgrade activation code is embedded in the MOVEit installer file.
- The activation code is also stored in your Progress Community product page for reference.
- The activation code differs from your serial number. The code begins with your serial number and contains an additional eight characters.
Upgrade Considerations
Install-Time Decision for Azure Blob Encryption (Important Note if You Leveraged Blob Storage in MOVEit Transfer 2019)
This install-time item is relevant if you intend to use Azure Blobs for your filestore or if you are upgrading a MOVEit Transfer system (2019.0, for example) that uses Azure Blobs. When not enabled (cleared), the Encrypt all files at-rest with MOVEit checkbox (introduced with the 2019.1 installer), can provide performance advantages. In this mode, you will deploy your filestore to use only the native Azure Storage at-rest encryption.
When you run the MOVEit Install utility, only newer installation scenarios (MOVEit Transfer 2019.1, and newer, for example) provide an option for using just native Azure encryption (opting out of the second layer of MOVEit encryption) for your MOVEit Transfer 'at rest' filestore. This is not available to 2019.0 or upgrades from 2019.0.
MOVEit Installer Option for Filestore Encryption Modes
Checkbox |
Mode |
Result |
Cleared |
Azure Encryption Only (2019.x Default) |
Realize the full and intended performance gain of Azure block Blob (NoSQL) storage for your MOVEit Transfer filestore while using encryption at the Azure Storage Service level which uses the latest ciphers. |
Selected |
Azure Encryption and MOVEit Encryption. |
Apply MOVEit Transfer encryption throughout (filestore, non-root files, and more). |
Do not choose the Azure-only encryption mode if you plan to point to an existing Azure Blob store used from a 2019.0 MOVEit Transfer Server. This can result in an operating environment where two different encryption schemes are in use for your file store. Mixed encryption schemes are not currently supported by MOVEit Transfer. See the MOVEit Install Guide for details.
MySQL Database Deployments
When you run the MOVEit Transfer installer in an upgrade scenario on a MOVEit Transfer deployment using MySQL, the installer upgrades existing MySQL 5.7 servers to MySQL 8.x.
Any custom schema, tables, and fields (if applicable) must be backed up
It is best practice to backup any customizations before you run the MOVEit Transfer installer. MOVEit Transfer database schema customizations are not supported. If you change the name or add schema, indexes, or tables, the MOVEit Installer will not expect these manual changes and attempt to revert them.
Reset tamper check for logs
If you have logs that include data from before and after a software upgrade, tamper check verification shows false positive tamper errors when verifying the logs
To prevent this situation, do the following when upgrading MOVEit DMZ software to MOVEit Transfer 2017 (and later).
- Before you upgrade, manually start the MOVEit DMZ Log Tamper Check program from the Start menu.
- Immediately after you upgrade:
- Sign-on as System Administrator. Click SETTINGS.
- In the System section, Tamper Detection row, click Reset All Orgs.
- Click Reset Tamper Detection Data.
Upgrading to a release with Secure Folder Sharing (a post upgrade task is necessary)
If you upgrade your MOVEit Transfer installation with a version that enables Secure Folder Sharing, this feature set will be initially set to off. After the upgrade, as sysadmin user, you can apply the Secure Folder Sharing feature set selectively in Org Profile Settings. As sysadmin, you can apply these settings on an org-by-org basis.
Enable org UI Security Settings to Allow Secure Folder Sharing Feature Set (needed for upgrade installations)
Mobile Upgrade Considerations
MOVEit Mobile Server and legacy MOVEit Transfer Mobile were deprecated for the 2020 release. The latest mobile client that you install from app stores (MOVEit Mobile) only needs MOVEit Transfer 2019.2 or later. MOVEit Mobile connects directly to the MOVEit Transfer Server host. No co-installed mobile server is necessary.
MOVEit Mobile Upgrade Paths
This table outlines the current mobile usage scenarios.
Your Existing Mobile Solution |
Target Upgrade Approach |
None. |
MOVEit Mobile 2.0 Encourage users to get MOVEit Mobile Apps from the iOS (Apple App) and Android (Google Play) app stores.
|
MOVEit Mobile Server 1.4 or older (legacy). (separately installed Mobile Server) |
Move users from MOVEit Transfer Mobile legacy to MOVEit Mobile 2.0 Encourage users to get MOVEit Mobile Apps from the iOS (Apple App) and Android (Google Play) app stores.
|
System Requirements
MOVEit Transfer expects certain software and hardware for proper operation.
- MOVEit Transfer Server software requirements. Platform (Virtual), OS, Database, and runtime.
- MOVEit Transfer Server hardware requirements. Storage, CPU, and memory.
- Target SMTP email server requirement. Email server to relay package notifications through.
- Server-side content engine (AV/DLP) compatibility. Anti-virus (AV) and Data Loss Prevention (DLP) engines.
- Additional client compatibility. Browser, mobile, and batch clients.
Deployed MOVEit Transfer (Remote SQL Server and Network Attached Storage Shown)
MOVEit Transfer can also leverage MySQL and Azure SQL for its database (MS SQL Server is shown here) and Azure as its S/W and H/W platform. for more information, see Database Platform and find MOVEit Transfer in Azure Marketplace.
MOVEit Transfer can also leverage Azure Blob Storage for its encrypted file/package store.
Note for Azure Users
You can use the MOVEit Transfer Installer if you want to leverage a new MOVEit Transfer site to leverage Azure Blobs or Azure SQL. Otherwise, for site upgrades, you can use the migration instructions for Azure Blob Storage or Azure SQL for its database in the Administrator Guide.
Additional requirements, guidelines, and best practices for leveraging Azure Blob Storage can be found in the Administrator Guide.
Hardware Requirements
These requirements apply to the hardware platform where you install MOVEit Transfer.
Server Hardware Minimum Requirements
- Quad-core processor.
- 8GB RAM.
- 250GB or larger storage.
Typical Server Hardware Guidelines
Production systems benefit from additional resources, including:
- Fast multicore processors (quad-core or dual-quad-core server grade processors are common).
- At least 8GB RAM.
- Hard drive capacity of 1TB (SAS) is common.
Note: MOVEit Transfer requires a dedicated server or hosted virtual machine. Do not install MOVEit Transfer on a machine that has other applications installed.
These requirements apply to the supporting environment and operating system where you install MOVEit Transfer.
Before you attempt to install MOVEit Transfer server, ensure your Windows Server OS has the latest service packs and required updates installed.
Server Software Requirements
Before you attempt to install MOVEit Transfer server, ensure your Windows server has the latest service packs and required updates installed.
Supported Operating Systems for MOVEit Transfer and Modules
- Windows Server 2019 (English, French, Spanish, German, Japanese, Chinese Traditional, and Chinese Simplified)
- Windows Server 2016 (English, French, Spanish, German, Japanese, Chinese Traditional, and Chinese Simplified)
- Windows Server 2012 R2 (English, French, Spanish, German, Japanese, Chinese Traditional, and Chinese Simplified)
Note: MOVEit Transfer no longer supports Windows Server 2012 (although R2 is supported), 2008R2 and 2008. MOVEit Transfer expects one of the OS versions listed above.
Supported Virtualization Environments
MOVEit Transfer can be installed and run on virtual servers running:
- VMware ESX (64-bit guest servers)
- Microsoft Hyper-V (64-bit guest servers)
Email Server (for notifications)
MOVEit Transfer needs an SMTP server to relay package notifications, account notifications, and other user messages. You will be asked for an SMTP server and credentials during the install process.
If you do not have email server information at the time of install, you can use the MOVEit Transfer Configuration Utility to add this information. For more information, see the MOVEit Transfer Admin Guide.
TLS Certificate
For use in production environments, you should install a certificate from a trusted certificate authority. Apply the trusted certificate during installation or through the MOVEit Transfer Configuration Utility.
Tested Third-Party AV/DLP Engines
The following major anti-virus (AV) and data loss prevention (DLP) engines were tested with MOVEit Transfer.
AV Engines (some with AV/DLP)
Anti-Virus Scanner |
Latest Version Tested |
McAfee VirusScan Enterprise for Storage (VSES) |
Last tested with version 1.3.0.145 |
McAfee VirusScan Enterprise |
Last tested with version 8.8.0.2190 |
McAfee Web Gateway |
Last tested with version 7.8.2.8.0 |
Sophos Anti-Virus Dynamic Interface (SAVDI) scanner |
|
Sophos for Network Storage |
Last tested with version 10.8.2 VE3.77.1 |
Symantec Protection Engine |
Last tested with version 7.8.0.141 |
Trend Micro InterScan Web Security Virtual Appliance (IWSVA) * |
Last tested with version 6.5-SP2_Build_Linux_1852 |
DLP Engines
Data Loss Prevention Scanner |
Latest Version Tested |
McAfee Web Gateway* |
Last tested with version 7.8.2.8.0 |
Symantec DLP Suite |
Last tested with version 15.x* |
*DLP Blocked responses require additional configuration for some scanning engines such as McAfee and Symantec.
Supported Databases
MOVEit Transfer requires one of the following database platforms:.
- MySQL (8.0.21) (included in the MOVEit Automation installation)
- Azure SQL Server
- Microsoft SQL Server 2019 Enterprise/Standard
- Microsoft SQL Server 2017 Enterprise/Standard
- Microsoft SQL Server 2016 Enterprise/Standard
- Microsoft SQL Server 2014 Enterprise/Standard (After MOVEit Transfer 2020.1, the MOVEit Transfer Server will not support MS SQL Server 2014)
- Earlier versions (not supported)
It is best to run the MOVEit Transfer Server and the database it connects to in the same time zone. Otherwise, security features like multi-factor authentication for sign-on as well as secure connection protocols used between the services will not function.
You can create an Azure SQL database using the Azure Management Portal. See the upgrade and migration section for instructions on how to migrate your current database to Azure SQL.
Additional Clients
MOVEit Mobile App
MOVEit Mobile App 2.0 is available for the following devices:
- iOS (Apple devices). Available for download in the Apple App Store.
- Android (Android OS devices). Available for download from Google Play.
MOVEit Desktop Client
All current versions of the MOVEit Desktop client are supported. Older versions will work with limited feature capabilities. Download the latest versions from the MOVEit Products page.
Outlook Plug-in (Ad Hoc)
- Outlook Client:
Outlook 2016 (English, German, French, Japanese, Simplified Chinese, Spanish and Traditional Chinese)
Outlook 2013 (English, German, French, Japanese, Simplified Chinese, Spanish and Traditional Chinese)
Outlook 2010 (32-bit and 64-bit English, German, French, Japanese, Simplified Chinese, Spanish and Traditional Chinese)
- Mail or Exchange Server:
Ad Hoc Transfer Plug-in for Outlook is compatible with a variety of mail servers, such as Exchange Server 2013, Exchange Server 2010 (32-bit and 64-bit English and German), or Progress IMail 11 (using SMTP). When Outlook & Exchange are used together, Cached Exchange Mode is supported but is not required.
- Operating System:
Microsoft Windows 10, Microsoft Windows 8, Windows 7 (32-bit and 64-bit English, German, French, Chinese Simplified, Chinese Traditional, Japanese)
SFTP, SSH, and HTTPS
Because MOVEit conforms to HTTP, FTP, SSL and SSH standards, most clients that conform to IETF's RFCs for these protocol standards will work.
MOVEit Transfer Server is compatible with clients that adhere to FTP, HTTPS, SFTP, and SSH protocol industry standards
Supported AS2/AS3 Clients
MOVEit supports any AS2 client that has been "Drummond" or "eBusinessReady" certified; the software MOVEit uses to handle incoming AS2 files and MDNs has itself been certified "eBusinessReady" under a program now managed by Drummond.
AS3 clients are just FTP/SSL clients as far as MOVEit is concerned. MOVEit Automation handles the encryption/decryption, signing and verification of AS files in either case.
Batch File Transfers Involving MOVEit
Many administrators like to use ".bat" scripts for FTP transfers.
Batch files (*bat
) are limited by ftp.exe. ftp.exe cannot perform passive FTP transfers, which are often necessary if transferring through firewalls or secure FTP transfers for sensitive transmissions over the Internet or other untrusted networks, which is recommended.
MOVEit normally accepts only secure connections, so ftp.exe itself cannot be used to FTP files to and from MOVEit. As an alternative, use MOVEit Freely a free and secure alternative for ftp.exe (In other words, "ftps.exe"). If you would prefer to use FTP over SSH transmissions, free scriptable clients are available for almost every version of UNIX as well as most Windows operating systems from OpenSSH.
To avoid several common firewall issues with the FTP/SSL protocol, MOVEit also offers a free HTTPS-based command-line utility called MOVEit Xfer that accepts the same syntax and commands as MOVEit Freely and Microsoft ftp.exe client. Available in both Windows and Java 1.4.2+ versions, this scriptable utility provides single-port secure file transfer on a wide variety of platforms including UNIX, Linux, Windows, Macintosh and some mainframes.
Copies of MOVEit Xfer and MOVEit Freely are available from the MOVEit support site or from the MOVEit Freely information site.
Scheduled and Audited File Transfers Involving MOVEit with MOVEit Automation
MOVEit Automation is an enterprise file transfer manager capable of simultaneous file transfers to and from hundreds of Windows file systems, FTP/FTPS/SFTP servers, mail servers, web servers, MOVEit servers, and AS1/AS2/AS3 partners.
Included are a full-featured task scheduler, guaranteed delivery, instant (event-driven) transfers, multiple sources/destinations in a single task, the ability to run custom VBScripts against processed files in a fault-tolerant sandbox, and custom event log or email notification support (or both). Security features include secure channels for remote control/configuration and AES encryption of configuration information, including remote host credentials.
For more information, see the MOVEit Automation documentation.
Note to Cloud Subscribers
To learn about the latest feature refresh for the MOVEit Transfer cloud service managed by Progress Software Corporation, see the MOVEit Cloud Release Notes.
Some Differences Between On Prem MOVEit Transfer versus a MOVEit Cloud Subscription
For MOVEit Transfer customers interested in a MOVEit Cloud Subscription, the following table compares the two mechanisms for leveraging MOVEit.
Comparison of MOVEit Cloud and MOVEit Transfer On-Premises
MOVEit Cloud Service |
MOVEit Transfer On-Premises |
Provides the MOVEit Transfer feature set as enabled by your subscription. |
Provides the MOVEit Transfer feature set as enabled by your license. |
Progress Software provides hardware, server operating system, and database platform needed to run one or more MOVEit Transfer organizations ("orgs"), where you manage folders and file transfers. |
Hardware and appropriate Windows Server operating system version are required for installation. See System Requirements for details. |
Progress Software provides SystemAdmin level management and maintenance. Subscribers have:
|
System-wide access (SystemAdmin) and management required. System administrators can create orgs as needed as licensing permits. |
Software as a service (SaaS) with a Service Level Agreement (SLA) |
Maintained by you. |
Regular patches and service refresh applied by MOVEit Cloud Site Engineering as needed. |
Regular point releases made available as necessary. |
Known Issues
This section outlines known issues and typical workarounds for MOVEit Transfer 2020.1.1
ID |
Category |
Known Issue in MOVEit Transfer |
365955 |
Installer |
After you upgrade a MOVEit Transfer server to 2020 that leverages the legacy mobile server, if you subsequently uninstall only MOVEit Transfer, the next time you run the installer the Modify option displays but no real modify-install scenario exists. You will not be able to complete the MOVEit Transfer install process. Workaround: To run the installer successfully, you will need to uninstall the deprecated MOVEit Mobile Server manually. Then you can re-run the MOVEit Transfer Installer. |
UREP-5247 |
Central Agent, DMZ Agent |
The Analytics Agent cannot connect to the MOVEit Transfer or MOVEit Automation 2019.1 with MySQL 8.
To resolve this issue, contact Technical Support to receive a hotfix. |
30988 |
MOVEit Desktop Client |
In a multi-org, multi-URL environment, not all fields and controls associated with a newly selected MOVEit Transfer org display at sign-on (such as the IdP dropdown list, when applicable). (When the user selects a different connection URL at sign-on, the client browser's application cache does not automatically refresh.) Workaround: Click Refresh before sign-on. |
31190 |
REST API |
Some virtual folder operations do not extend to the REST API. Workaround: For full parity, use the WebUI or MOVEit Automation. |
Licensees and Evaluators
For more information, please check our:
- Progress Software End-user License Agreement (EULA).
- Knowledge base article about MOVEit licensing.
Copyright Notice
© 2020 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.
These materials and all Progress© software products are copyrighted and all rights are reserved by Progress Software Corporation. The information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear therein. The references in these materials to specific platforms supported are subject to change.
Corticon, DataDirect (and design), DataDirect Cloud, DataDirect Connect, DataDirect Connect64, DataDirect XML Converters, DataDirect XQuery, DataRPM, Defrag This, Deliver More Than Expected, Icenium, Ipswitch, iMacros, Kendo UI, Kinvey, MessageWay, MOVEit, NativeChat, NativeScript, OpenEdge, Powered by Progress, Progress, Progress Software Developers Network, SequeLink, Sitefinity (and Design), Sitefinity, SpeedScript, Stylus Studio, TeamPulse, Telerik, Telerik (and Design), Test Studio, WebSpeed, WhatsConfigured, WhatsConnected, WhatsUp, and WS_FTP are registered trademarks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and/or other countries. Analytics360, AppServer, BusinessEdge, DataDirect Autonomous REST Connector, DataDirect Spy, SupportLink, DevCraft, Fiddler, iMail, JustAssembly, JustDecompile, JustMock, NativeScript Sidekick, OpenAccess, ProDataSet, Progress Results, Progress Software, ProVision, PSE Pro, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, and WebClient are trademarks or service marks of Progress Software Corporation and/or its subsidiaries or affiliates in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates. Any other marks contained herein may be trademarks of their respective owners.
This document was published on Friday, January 8, 2021 at 12:53
NOV
11
2020