Below are the major issues that were resolved since the release of EKM18.1, including issues that were addressed in the EKM 18.1.1 Service Pack.
Compatibility issues between the current version of EKM and older versions of Workbench have been resolved.
When uploading a folder to EKM using the File Transfer Client, files that you have excluded from the upload are no longer erroneously uploaded.
When using the File Transfer Client to upload files/folders to EKM, uploading a Workbench project file without its associated _files folder no longer causes the upload to fail.
Workbench project files are now properly cached when Workbench projects are uploaded to EKM via a cache server. This applies when using the action in Workbench, and when uploading a Workbench (.wbpj) file and its _files folder using the File Transfer Client in EKM. It also applies when Workbench projects are uploaded to the Master workspace from a Slave workspace in a Master-Slave configuration.
When downloading files via a cache server using the File Transfer Client, the dialog box now reports the Percentage cached value correctly.
When saving to a repository that contains a large number of sub-directories, you can now navigate these sub-directories with reasonable speed, and sort them alphabetically.
When using the EKM Client API to interact with an EKM repository, users are now successfully authenticated with the server file transfer service.
When running jobs in a multi-node Linux cluster, attempting to cancel a job that is running on a non-primary node no longer results in an exception.
When submitting distributed CFX jobs to an HPC cluster via EKM, and the solver version is 18.0 or higher, using certain .def files no longer causes jobs to fail.
When updating a Workbench project that has a space in its name, the project is now properly updated in EKM once the job is complete.