Deprecated API

Contents

• Terminally Deprecated
• Interfaces
• Classes
• Methods

Terminally Deprecated Elements

Element	Description
com.aquima.interactions.ds.export.r12.ExportUtilR12	use com.aquima.interactions.ds.export.r17.ExportUtilR12
com.aquima.interactions.ds.xml.r12.XmlExportMetadataR12	use com.aquima.interactions.ds.xml.r17.XmlMetaData
com.aquima.interactions.ds.xml.r12.XmlExportR12	use com.aquima.interactions.ds.xml.r17.XmlExportR12
com.aquima.interactions.ds.xml.r12.XmlProjectMetaData
com.aquima.interactions.foundation.security.cert.ExportR12CertificateProvider	com.aquima.interactions.foundation.security.cert.ExportR17CertificateProvider
com.aquima.interactions.foundation.security.cert.ExportR12DecryptCertificateProvider	com.aquima.interactions.foundation.security.cert.ExportR17DecryptCertificateProvider
com.aquima.interactions.process.IProcessCase.createTask(IUserData, String, DateTimeValue, String[])	With this method you can create tasks that are not defined anywhere. We rely on the task definition in many places, so this is bound to cause problems. Instead of using this method, properly model your application with the tasks you need.

Deprecated Interfaces

Interface

Description

com.aquima.interactions.portal.IProcessScope

The process scope is intended to store the 'active' case or task in the session. Process related services, such as AQ_GetCaseInfo or AQ_GetTaskStatus can use this when the optional case or task id is not provided. This usage is discouraged: be explicit about the tasks and cases that you want to manipulate. In DCM 2.0, this concept is no longer used. The case or task to which something should happen always needs to be explicitly specified.

Deprecated Classes

Class	Description
com.aquima.interactions.ds.export.r12.ExportUtilR12	use com.aquima.interactions.ds.export.r17.ExportUtilR12
com.aquima.interactions.ds.xml.r12.XmlExportMetadataR12	use com.aquima.interactions.ds.xml.r17.XmlMetaData
com.aquima.interactions.ds.xml.r12.XmlExportR12	use com.aquima.interactions.ds.xml.r17.XmlExportR12
com.aquima.interactions.ds.xml.r12.XmlProjectMetaData
com.aquima.interactions.foundation.security.cert.ExportR12CertificateProvider	com.aquima.interactions.foundation.security.cert.ExportR17CertificateProvider
com.aquima.interactions.foundation.security.cert.ExportR12DecryptCertificateProvider	com.aquima.interactions.foundation.security.cert.ExportR17DecryptCertificateProvider

Deprecated Methods

Method	Description
com.aquima.interactions.config.legacy.ILegacyToggles.isExecuteDatamappingOnCancelTask()	Legacy toggle expected to be removed in DCM2
com.aquima.interactions.config.legacy.ILegacyToggles.isLegacyRestResponseValidation()	Expected to be removed in R18
com.aquima.interactions.foundation.types.DateValue.getLeanDateFormat()
com.aquima.interactions.process.dao.IProcessCaseDao.updateCase(long, CaseStatusType, String)	this method was used for locking/unlocking a case, use IProcessCaseDao.acquireLock(long, String) and IProcessCaseDao.unlockCase(long) instead
com.aquima.interactions.process.IProcessCase.createTask(IUserData, String, DateTimeValue, String[])	With this method you can create tasks that are not defined anywhere. We rely on the task definition in many places, so this is bound to cause problems. Instead of using this method, properly model your application with the tasks you need.