Some months ago I put up a list of the OnBase modules that still use DMCoreX. This is useful because if you are detecting DMCoreX usage via either the security log or database logging, the log cannot tell you if the DMCoreX login you see is because of an official OnBase module you own that still uses DMCoreX in your OnBase version or because of custom scripting.
As promised, in OnBase 14 we have worked very hard to convert the official OnBase modules off of DMCoreX. However, there are still a few modules that use DMCoreX in the 14 release. This is usually because some modules will be removed from the OnBase product suite in OnBase 15. Whether they have a successor product or the successor product already exists, they can still be used with DMCoreX in OnBase 14.
Without any further ado, here are the modules that use DMCoreX in OnBase 14.
Autostore Route to OnBase Integration - Support for this product is being ended in OnBase 15.
Cardiff TELEform Integration - Support for this product is being ended in OnBase 15.
Certified Records Management - Support for this product is being ended in OnBase 15. In addition to being built on DMCoreX, this module allows the configuration of custom scripts using DMCoreX.
Integration for eCopy Sharescan 3/4 - Support for eCopy Sharescan 3/4 will be removed in OnBase 15. The Integration for eCopy ShareScan 5.X has been available since OnBase 11 and does not use DMCoreX in any way.
Integration for Web Dav - Support for this product is being ended in OnBase 15.
Exceptions Management - Support for this product is being ended in OnBase 15.
Lockbox - Support for this product is being ended in OnBase 15.
When upgrading WorkView installations to OnBase 14, DMCoreX is used solely for the database upgrade and is not otherwise used. This requirement will be fully removed for OnBase 15.
Web Services Toolkit uses DMCoreX on the Application Server. The security log will not reflect Web Services Toolkit usage because its authentication is not handled by DMCoreX, but the database log will.
In addition, WorkView, Workflow and Certified Records Management allow the configuration of custom scripts using DMCoreX. These are optional portions of the module; they may not be configured, or in the case of WorkView and Workflow, they may be using scripts with the Unity API instead of DMCoreX.
Because of the scripting options above, some of our installers continue to install the DMCoreX DLL, but it is not explicitly used by any modules except in the cases outlined above.
To learn what OnBase modules used DMCoreX in earlier versions, please refer to the original post.
