What OnBase Modules use DMCoreX?

[Nathan_Kossover]

If you are detecting DMCoreX API usage via either the security log or via database logging, one of the drawbacks of those approaches is that those logging methods 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. To assist with that, we have compiled a list of OnBase modules that still used DMCoreX in OnBase 10, 11, 12 & 13. If you do not own one of these modules and see a DMCoreX login when you analyze the security or database log, then you can be sure that it came from a custom application or script that uses DMCoreX. If you do own one of these modules, when you look at the logs you have to take that into account the possibility that you are seeing evidence of those modules in operation.

For OnBase 14, Hyland Software is working to ensure that no modules require DMCoreX. However, a few modules may still support DMCoreX as a backup option.

Please note that some of these modules have been scheduled for end-of-life at the same time as DMCoreX and will not be converted. Please see the complete end-of-life list on Community for details.

EDIT: Modules that used DMCoreX in OnBase 14
See newer post.

Modules that used DMCoreX in OnBase 13
Autostore Route to OnBase Integration
Cardiff TELEform Integration
Certified Records Management - in addition to being built on DMCoreX, this module allows the configuration of custom scripts using DMCoreX.
DJDE  - when used to view DJDE documents via the Application Server; DJDE via the Thick Client does not use DMCoreX.
Integration for eCopy 3/4 - The Integration for eCopy 5 does not use DMCoreX.
Exceptions Management
Integration for Web Dav
IRD Check Rendering - when used to view IRD Checks via the Application Server; IRD via the Thick Client does not use DMCoreX.
Lockbox
PCL - when used to view PCL documents via the Application Server; PCL via the Thick Client does not use DMCoreX.
PDS-1783 - used only by customers of Hyland Software's partner ITI/Fiserv.
R4 Acert V4 Software - This module is built on the Web Services Toolkit, which uses DMCoreX on the Application Server.
ReadSoft Eyes & Hands Integration
Statement Composition
Subscription Server
WorkView Configuration - WorkView itself does not use DMCoreX, but its configuration module is built on DMCoreX.

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.

Modules that used DMCoreX in OnBase 12 [Includes all Modules that Use DMCorex in OnBase 13]
AFP  - when used to view AFP documents via the Application Server; AFP via the Thick Client does not use DMCoreX.
Amicas - Instant View for Amicas
Directory Import Processor
Integration for Mitek Validify
Verity Full Text Indexing

Modules that used DMCoreX in OnBase 11 [Includes all Modules that Use DMCoreX in OnBase 12 or 13]
Integration for Accela

Modules that used DMCoreX in OnBase 10 [Includes all Modules that Use DMCoreX in OnBase 11, 12 or 13]
Integration for Fujitsu fi-6000NS
Integration for Microsoft BizTalk
OnBase Desktop
IMS Lockbox
WorkView - Specifically, the WorkView Client