Updates and Enhancements in Version 22.1.0.5 (Banker Edition)
This section discusses the new features being introduced in this Encompass release.
Update to the Encompass Client Machines
The Encompass 22.1 Critical Patch 4 release includes the following update, which will be applied to users' Encompass client machines (22.1.0.5). This client update can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply new releases to users’ computers automatically, users will receive this update upon their initial log in of Encompass following the release.
(Updated on 9/15/2022)
If you are utilizing the Encompass SDK to open or update loan files, upgrading to the new SDK package for 22.1.0.5 is required to receive this update.
The current security certificate for Encompass expires on September 16, 2022. Recently, an Encompass 22.1 critical patch was deployed to update the Encompass security certificate used to sign the Encompass DLL files. (view the 22.1.0.4 release notes). This critical patch release provided a new Encompass security certificate that is valid until 2025.
However, after this release, it was determined that some DLLs were not updated with the new security certificate as expected. To address this issue, Encompass 22.1 Critical Patch 4 is now being provided. Please upgrade to Encompass 22.1.0.5 and then follow the steps below to ensure that all DLLs used by Encompass are using the new security certificate.
To Update DLLs for the New Security Certificate:
-
Accept the new 22.1 Critical Patch release. This client update can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply new releases to users’ computers automatically, users will receive this update upon their initial log in of Encompass following the release.
-
Once the upgrade process is complete, launch Encompass.*
-
When users launch Encompass, all of the associated files are replaced with the newest versions with the new security certificate.
-
*'... launch Encompass' refers to utilizing the AppLauncher.exe or an equivalent shortcut to AppLauncher.exe
-
The following pop-up message is displayed:
-
At this prompt, click Yes or No.
-
If you click Yes: Encompass closes, and the update will proceed. When the update is complete, you are prompted with the following message:
You can then click OK, relaunch Encompass, and then log in as usual.
-
If you click No:The update will be performed when you close Encompass. Once the update complete, you will receive the following message:
-
Additional Information:
-
Again, this client-side update can be controlled manually via the Encompass Version Manager tool. If the Version Manager has not been configured to always apply new releases to users' computers automatically, you must manually apply this update before September 16, 2022 to avoid any potential security warnings or issues that may occur due to the expired security certificate.
-
If an Encompass user does not update to Encompass 22.1.0.5 until after the existing security certificate expires on September 16, and the expired certificate is flagged by their company’s security policy, these users may encounter issues logging into or using Encompass.
-
Encompass SDK users: If you utilize the Encompass SDK, you must upgrade to the new SDK package (22.1.0.5) provided with this release to apply the new security certificate to your SDK. Solely applying the client-side update will not make the new security certificate available for your Encompass SDK.
-
Once you have upgraded to the latest Encompass SDK package, it is important to contact your third-party integration providers and inform them about the new SDK with the new security certificate. This helps ensure the providers can test the integration with the new SDK package.
-
For additional information, please review knowledge article 000114539.
NICE-42150
Next Section: Change Log | ||
Previous Section: Introduction |