CMS_API_DELETE

1min

Functionality
Description
FileNet notes
Documentum Notes
Box Notes
M365/SharePoint Notes
IV_CMSPROFILE 
Required: Determines which configured CMS Profile in Link Enterprise SAP to utilize. Combination of CMS Profile and CMS Tag determine the API destination and thus load across an RFC destination. 
﻿
﻿
﻿
﻿
IV_CMSTAG 
Required: Determine which configured CMS Profile in Enterprise  SAP to utilize. Combination of CMS Profile and CMS Tag determine the API destination and thus load across an RFC destination. 
﻿
﻿
﻿
﻿
IV_REPOSITORY 
Required: Determines which configured repository in Link Enterprise SAP to utilize 
﻿
Object Store 



Docbase 




Default is the only Store/Repository supported since Box currently doesn’t support the notion of different repositories. 
Site, site collection 




IV_TYPE 
﻿
Optional: what CMS type to delete. 
DOCUMENT CLASS 
OBJECT TYPE 
METADATA TEMPLATE 
CONTENT TYPE 
﻿
IV_USE_MAPPING 




Optional: use mapping of IV_TYPE to CMS type in Enterprise Connector if CMS. Used if ArchiveLink doctype name to CMS type mapping is required. 
﻿
﻿
﻿
﻿
IV_LOCATION 


Optional: (Mandatory for M365/SharePoint only and not used in any other CMS system) Specifies where to delete the document from. 


Not utilized. 


Not utilized. 


Not utilized. 


This is required and is the Document Library. For documents originally created by Link Enterprise, this is stored at the time of create in a Link Enterprise table in the scenario that the config changes and thus can be used for subsequent deletes. 
ET_RETURN 




Table that indicates a success of an error. The TYPE field will contain an ‘S’ or ‘E’ respectively and the MESSAGE field will contain information in the case of an error. 
﻿
﻿
﻿
﻿
CT_CUSTOM 
Future use 
﻿
﻿
﻿
﻿
﻿

Functionality	Description	FileNet notes	Documentum Notes	Box Notes	M365/SharePoint Notes
IV_CMSPROFILE	Required: Determines which configured CMS Profile in Link Enterprise SAP to utilize. Combination of CMS Profile and CMS Tag determine the API destination and thus load across an RFC destination.
IV_CMSTAG	Required: Determine which configured CMS Profile in Enterprise SAP to utilize. Combination of CMS Profile and CMS Tag determine the API destination and thus load across an RFC destination.
IV_REPOSITORY	Required: Determines which configured repository in Link Enterprise SAP to utilize	Object Store	Docbase	Default is the only Store/Repository supported since Box currently doesn’t support the notion of different repositories.	Site, site collection
IV_TYPE	Optional: what CMS type to delete.	DOCUMENT CLASS	OBJECT TYPE	METADATA TEMPLATE	CONTENT TYPE
IV_USE_MAPPING	Optional: use mapping of IV_TYPE to CMS type in Enterprise Connector if CMS. Used if ArchiveLink doctype name to CMS type mapping is required.
IV_LOCATION	Optional: (Mandatory for M365/SharePoint only and not used in any other CMS system) Specifies where to delete the document from.	Not utilized.	Not utilized.	Not utilized.	This is required and is the Document Library. For documents originally created by Link Enterprise, this is stored at the time of create in a Link Enterprise table in the scenario that the config changes and thus can be used for subsequent deletes.
ET_RETURN	Table that indicates a success of an error. The TYPE field will contain an ‘S’ or ‘E’ respectively and the MESSAGE field will contain information in the case of an error.
CT_CUSTOM	Future use

CMS_API_UPDATE

Ping and Load API's