2.90:Export Provider - Revision history

Dgreenwood at 16:03, 5 August 2025

2025-08-05T16:03:47Z

← Older revision		Revision as of 11:03, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{\|cellpadding=10 cellspacing=5 style="margin:12px"		{\|cellpadding=10 cellspacing=5 style="margin:12px"
	\|-		\|-

Dgreenwood at 22:04, 18 September 2024

2024-09-18T22:04:16Z

← Older revision		Revision as of 17:04, 18 September 2024
Line 5:		Line 5:
	'''LEGACY CONTENT DETECTED!!		'''LEGACY CONTENT DETECTED!!

	This guidance is ~~mostly~~ obsolete in version 2021. Export operations have changed with the incorporation of '''''Export Behaviors'''''. However, '''''Export Providers''''' are somewhat analogous to adding an '''''Export Definition''''' to an '''''Export Behavior''''' configuration.		This guidance is obsolete as of version 2021 and beyond. Export operations have changed with the incorporation of '''''Export Behaviors'''''. However, '''''Export Providers''''' are somewhat analogous to adding an '''''Export Definition''''' to an '''''Export Behavior''''' configuration.

	Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.		Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.

Dgreenwood at 22:03, 18 September 2024

2024-09-18T22:03:18Z

← Older revision		Revision as of 17:03, 18 September 2024
Line 5:		Line 5:
	'''LEGACY CONTENT DETECTED!!		'''LEGACY CONTENT DETECTED!!

	This guidance is mostly obsolete in version 2021. Export operations have changed with the incorporation of '''''Export Behaviors'''''. However, '''''Export Providers''''' are somewhat analogous to adding an '''''Export ~~Type~~''''' to an '''''Export Behavior''''' configuration.		This guidance is mostly obsolete in version 2021. Export operations have changed with the incorporation of '''''Export Behaviors'''''. However, '''''Export Providers''''' are somewhat analogous to adding an '''''Export Definition''''' to an '''''Export Behavior''''' configuration.

	Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.		Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.

Dgreenwood: Dgreenwood moved page Export Provider to 2.90:Export Provider without leaving a redirect

2023-12-28T22:14:46Z

Dgreenwood moved page Export Provider to 2.90:Export Provider without leaving a redirect

← Older revision	Revision as of 17:14, 28 December 2023
(No difference)

Dgreenwood at 15:36, 25 September 2023

2023-09-25T15:36:40Z

← Older revision		Revision as of 10:36, 25 September 2023
Line 1:		Line 1:
	{\|cellpadding="10" cellspacing="5"		{\|cellpadding=10 cellspacing=5 style="margin:12px"
	\|-style="background-color:#~~f89420~~; color:white"		\|-
	~~\|style="font~~-~~size~~:~~22pt~~"\|'''&#~~9888~~;'''\|\|This guidance is ~~somewhat~~ obsolete in version 2021. Export operations have changed with the incorporation of '''''Export Behaviors'''''. However, '''''Export Providers''''' are somewhat analogous to adding an '''''Export Type''''' to an '''''Export Behavior''''' configuration.		\|style="font-size:200%; background-color:#662d91; color:white; width:28px; text-align:center"\|'''‼'''
			\|style="border: 4px solid #662d91"\|
			'''LEGACY CONTENT DETECTED!!

			This guidance is mostly obsolete in version 2021. Export operations have changed with the incorporation of '''''Export Behaviors'''''. However, '''''Export Providers''''' are somewhat analogous to adding an '''''Export Type''''' to an '''''Export Behavior''''' configuration.

	Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.		Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.

Dgreenwood at 20:45, 9 December 2022

2022-12-09T20:45:27Z

← Older revision		Revision as of 15:45, 9 December 2022
Line 64:		Line 64:

	However, going forward, output operations should be implemented using the new ''CMIS Bindings'' and ''CMIS Export''. There are two main differences. Connection settings found in ''''Export Settings''''' in the legacy providers will be entered in the connection settings of whichever Connection Type is selected. What file path or server you're connecting to and any login credentials necessary will be entered there. Two, you will need to "import [[CMIS Repository\|repositories]]" in order to export to them. Refer to the '''CMIS Connection''' article for information about setting up a '''CMIS Connection''' and importing repositories.		However, going forward, output operations should be implemented using the new ''CMIS Bindings'' and ''CMIS Export''. There are two main differences. Connection settings found in ''''Export Settings''''' in the legacy providers will be entered in the connection settings of whichever Connection Type is selected. What file path or server you're connecting to and any login credentials necessary will be entered there. Two, you will need to "import [[CMIS Repository\|repositories]]" in order to export to them. Refer to the '''CMIS Connection''' article for information about setting up a '''CMIS Connection''' and importing repositories.

			[[Category:Articles]]
			[[Category:Version 2.90]]

Dgreenwood at 18:48, 24 September 2021

2021-09-24T18:48:20Z

← Older revision		Revision as of 13:48, 24 September 2021
Line 5:		Line 5:
	Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.		Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.

	Visit the [[Export (Activity)]] article for more information.		Visit the [[Export (Activity)]] article for more current information.
	\|}		\|}

Dgreenwood at 18:48, 24 September 2021

2021-09-24T18:48:04Z

← Older revision		Revision as of 13:48, 24 September 2021
Line 1:		Line 1:
			{\|cellpadding="10" cellspacing="5"
			\|-style="background-color:#f89420; color:white"
			\|style="font-size:22pt"\|'''⚠'''\|\|This guidance is somewhat obsolete in version 2021. Export operations have changed with the incorporation of '''''Export Behaviors'''''. However, '''''Export Providers''''' are somewhat analogous to adding an '''''Export Type''''' to an '''''Export Behavior''''' configuration.

			Furthermore, the '''Document Export''' activity no longer exists in version 2021. It is replaced with the '''Export''' activity.

			Visit the [[Export (Activity)]] article for more information.
			\|}

	{\|style="float:right" cellspacing="10"		{\|style="float:right" cellspacing="10"
	\|-		\|-

Dgreenwood at 20:43, 23 November 2020

2020-11-23T20:43:17Z

← Older revision		Revision as of 15:43, 23 November 2020
Line 14:		Line 14:
	There are two categories of '''''Export Providers''''': ''[[CMIS Export]]'' and ''[[Legacy Export]]''		There are two categories of '''''Export Providers''''': ''[[CMIS Export]]'' and ''[[Legacy Export]]''

	''CMIS Export'' uses Grooper's [[CMIS+]] architecture to export documents to various storage platforms, using '''[[CMIS Connection]]s''' connecting to specific platforms using''[[CMIS Binding]]s''. The ''Legacy Export'' providers only exist to provide backwards compatibility. Their storage platform endpoints have ''CMIS Binding'' analogues suitable for ''CMIS Export''. For example, the legacy ''Mail Export'' provider has a corresponding ''IMAP'' binding, allowing ''CMIS Export'' to export to IMAP mail servers. ''CMIS Export'' should be prioritized over ''Legacy Export'' going forward.		''CMIS Export'' uses Grooper's [[CMIS+]] architecture to export documents to various storage platforms, using '''[[CMIS Connection]]s''' connecting to specific platforms using ''[[CMIS Binding]]s''.

			The ''Legacy Export'' providers only exist to provide backwards compatibility. Their storage platform endpoints have ''CMIS Binding'' analogues suitable for ''CMIS Export''. For example, the legacy ''Mail Export'' provider has a corresponding ''IMAP'' binding, allowing ''CMIS Export'' to export to IMAP mail servers. ''CMIS Export'' should be prioritized over ''Legacy Export'' going forward.
	</onlyinclude>		</onlyinclude>

Dgreenwood at 20:42, 23 November 2020

2020-11-23T20:42:07Z

← Older revision		Revision as of 15:42, 23 November 2020
Line 5:		Line 5:
	\|[[file:1557844395737-263.png\|center]]		\|[[file:1557844395737-263.png\|center]]
	\|}		\|}
			<onlyinclude>
			<blockquote style="font-size:14pt">
			'''''Export Providers''''' are used by the '''Document Export''' activity to define where and how Grooper content is exported.
			</blockquote>

	~~<blockquote style="font-size:14pt">~~'''Export ~~Providers~~''' are ~~used by~~ the ~~Document Export activity to define where and how~~ Grooper content ~~is exported~~.~~</blockquote>~~		Which '''''Export Provider''''' you choose will determine where your processed content in Grooper (including documents and their metadata) are exported. They allow you to define the connection type when exporting outside of Grooper, such as file systems, content management repositories, or mail servers.

	~~What~~ Export ~~Provider you choose will determine where your processed content in Grooper (including documents~~ and ~~their metedata) are exported. They allow you to define the connection type when exporting outside of Grooper, such as file systems, content management repositories, or mail servers.~~		There are two categories of '''''Export Providers''''': ''[[CMIS Export]]'' and ''[[Legacy Export]]''

	~~There are two categories of~~ Export ~~Providers:~~ CMIS Export ~~and~~ Legacy Export		''CMIS Export'' uses Grooper's [[CMIS+]] architecture to export documents to various storage platforms, using '''[[CMIS Connection]]s''' connecting to specific platforms using''[[CMIS Binding]]s''. The ''Legacy Export'' providers only exist to provide backwards compatibility. Their storage platform endpoints have ''CMIS Binding'' analogues suitable for ''CMIS Export''. For example, the legacy ''Mail Export'' provider has a corresponding ''IMAP'' binding, allowing ''CMIS Export'' to export to IMAP mail servers. ''CMIS Export'' should be prioritized over ''Legacy Export'' going forward.
			</onlyinclude>

	== CMIS Export ==		== CMIS Export ==

	[[CMIS Export]] has two different provider types:		''[[CMIS Export]]'' has two different provider types:

	* [[CMIS Export#MappedExport\|Mapped Export]]		* ''[[CMIS Export#MappedExport\|Mapped Export]]''
	* [[CMIS Export#Unmapped Export\|Unmapped Export]]		* ''[[CMIS Export#Unmapped Export\|Unmapped Export]]''

	These export providers use connections to storage platforms using Grooper's CMIS+ architecture. Connections are created as "bindings" modeled after the CMIS standard. CMIS Connections can be created to the following storage platforms for Mapped and/or Unmapped Export.		These export providers use connections to storage platforms using Grooper's CMIS+ architecture. Connections are created as "bindings" modeled after the CMIS standard. '''CMIS Connections''' can be created to the following storage platforms for Mapped and/or Unmapped Export.

	* The ApplicationXtender document management platform.		* The ApplicationXtender document management platform.
Line 28:		Line 33:
	** The Microsoft OneDrive cloud storage platform.		** The Microsoft OneDrive cloud storage platform.
	** Microsft SharePoint sites.		** Microsft SharePoint sites.
			* The Box.com cloud document storage platform.
	* FTP (File Transfer Protocal) and SFTP (SSH File Transfer Protocal) servers.		* FTP (File Transfer Protocal) and SFTP (SSH File Transfer Protocal) servers.
	* IMAP (Internet Message Access Protocol)mail servers		* IMAP (Internet Message Access Protocol)mail servers
	* The Microsoft Windows NTFS file system.		* The Microsoft Windows NTFS file system.

	Mapped Export differs from Unmapped Export in that information from a Content Model, such as a document's ~~classification type~~ and extracted data, can be exported as well (The metadata is "mapped" from Grooper to the storage platform). Unmapped Export is a simpler export. Processed files are simply exported according to the format you choose in Grooper (such as PDF or TIFF). Metadata is not mapped to any location in the storage platform. However, a metadata buddy file can be created alongside the document (such as a CSV or XML file).		''Mapped Export'' differs from ''Unmapped Export'' in that information from a '''Content Model''', such as a document's classified '''Document Type''' and extracted data in a '''Data Model''', can be exported as well. The metadata is "mapped" from Grooper to the storage platform. ''Unmapped Export'' is a simpler export. Processed files are simply exported according to the format you choose in Grooper (such as PDF or TIFF). Metadata is not mapped to any location in the storage platform. However, a metadata "buddy file" can be created alongside the document (such as a CSV or XML file).

	For more information on [[CMIS Export]] visit the full article.		For more information on ''[[CMIS Export]]'' visit the full article.

	== Legacy Export ==		== Legacy Export ==

	The '''Legacy Export''' providers are the export providers used for document export operations prior to the switch to Grooper's [[CMIS+]] infrastructure in version 2.72. These are depreciated Grooper components. Depreciated means they are still available for use, just not recommended. No further improvements or updates will be made to these provider types. The old components have been replaced by new [[CMIS Binding]]s with increased functionality and better performance. By and large, these legacy providers operate the same as they did in previous versions.		The ''Legacy Export'' providers are the export providers used for document export operations prior to the switch to Grooper's CMIS+ infrastructure in version 2.72. These are depreciated Grooper components. Depreciated means they are still available for use, just not recommended. No further improvements or updates will be made to these provider types. The old components have been replaced by new ''[[CMIS Binding]]s'' with increased functionality and better performance. By and large, these legacy providers operate the same as they did in previous versions.

	* There are four Legacy Export providers:		* There are four ''Legacy Export'' providers:
	** [[File System Export]] - This provider exports content over a local network to the Windows file system.		** ''[[File System Export]]'' - This provider exports content over a local network to the Windows file system.
	** [[FTP Export]] - This provider exports content using the FTP and FTPS protocols.		** ''[[FTP Export]]'' - This provider exports content using the FTP and FTPS protocols.
	** [[Mail Export]] - This provider exports content to mail servers using the IMAP protocol.		** ''[[Mail Export]]'' - This provider exports content to mail servers using the IMAP protocol.
	** [[SFTP Export]] - This provider exports content using the SFTP protocol.		** ''[[SFTP Export]]'' - This provider exports content using the SFTP protocol.

	However, going forward, output operations should be implemented using the new [[CMIS ~~Binding]]s~~ and [[CMIS Export]]. There are two main differences. Connection settings found in "Export Settings" in the legacy providers will be entered in the connection settings of whichever Connection Type is selected. What file path or server you're connecting to and any login credentials necessary will be entered there. Two, you will need to "import [[CMIS Repository\|repositories]]" in order to export to them. Refer to the [[CMIS Connection]] article for information about setting up a CMIS Connection and importing repositories.		However, going forward, output operations should be implemented using the new ''CMIS Bindings'' and ''CMIS Export''. There are two main differences. Connection settings found in ''''Export Settings''''' in the legacy providers will be entered in the connection settings of whichever Connection Type is selected. What file path or server you're connecting to and any login credentials necessary will be entered there. Two, you will need to "import [[CMIS Repository\|repositories]]" in order to export to them. Refer to the '''CMIS Connection''' article for information about setting up a '''CMIS Connection''' and importing repositories.