2023:Export (Activity) - Revision history

Dgreenwood at 15:25, 13 May 2025

2025-05-13T15:25:59Z

← Older revision		Revision as of 10:25, 13 May 2025
Line 245:		Line 245:
	The '''''File Export''''' definition is a carry over from older methods of exporting to a Windows file system in previous versions of Grooper. ''File Export'' exists mostly for backwards compatibility, but it can still be utilized for simple file system exports.		The '''''File Export''''' definition is a carry over from older methods of exporting to a Windows file system in previous versions of Grooper. ''File Export'' exists mostly for backwards compatibility, but it can still be utilized for simple file system exports.

	In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[~~NTFS (CMIS Connection Type)\|~~NTFS]]''''' connection is a preferable method to export document content to a Windows file system.		In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[NTFS]]''''' connection is a preferable method to export document content to a Windows file system.
	\|}		\|}

Line 264:		Line 264:
	The '''''IMAP Export''''' definition is a carry over from older methods of exporting across the IMAP protocol in previous versions of Grooper. '''''IMAP Export''''' exists mostly for backwards compatibility, but it can still be utilized for simple exports to email boxes.		The '''''IMAP Export''''' definition is a carry over from older methods of exporting across the IMAP protocol in previous versions of Grooper. '''''IMAP Export''''' exists mostly for backwards compatibility, but it can still be utilized for simple exports to email boxes.

	In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[~~IMAP (CMIS Connection Type)\|~~IMAP]]''''' connection is a preferable method to export document content to an IMAP server.		In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[IMAP]]''''' connection is a preferable method to export document content to an IMAP server.

	Furthermore, when connecting to a Microsoft Outlook inbox, the '''''[[~~Exchange (CMIS Connection Type)\|~~Exchange]]''''' binding is preferable to the '''''IMAP''''' binding. The '''''Exchange''''' binding has increased functionality specifically designed for the Outlook messaging system.		Furthermore, when connecting to a Microsoft Outlook inbox, the '''''[[Exchange]]''''' binding is preferable to the '''''IMAP''''' binding. The '''''Exchange''''' binding has increased functionality specifically designed for the Outlook messaging system.
	\|}		\|}

Line 283:		Line 283:
	The '''''FTP Export''''' definition is a carry over from older methods of exporting to FTP sites in pervious versions of Grooper. '''''FTP Export''''' exists mostly for backwards compatibility, but it can still be utilized for simple exports to FTP folders.		The '''''FTP Export''''' definition is a carry over from older methods of exporting to FTP sites in pervious versions of Grooper. '''''FTP Export''''' exists mostly for backwards compatibility, but it can still be utilized for simple exports to FTP folders.

	In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[~~FTP (CMIS Connection Type)\|~~FTP]]''''' connection is a preferable method to export document content to an FTP site.		In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[FTP]]''''' connection is a preferable method to export document content to an FTP site.
	\|}		\|}

Line 300:		Line 300:
	The '''''SFTP Export''''' definition is a carry over from older methods of exporting to SFTP sites in previous versions of Grooper. '''''SFTP Export''''' exists mostly for backwards compatibility, but it can still be utilized for simple exports to SFTP folders.		The '''''SFTP Export''''' definition is a carry over from older methods of exporting to SFTP sites in previous versions of Grooper. '''''SFTP Export''''' exists mostly for backwards compatibility, but it can still be utilized for simple exports to SFTP folders.

	In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[~~SFTP (CMIS Connection Type)\|~~SFTP]]''''' connection is a preferable method to export document content to an SFTP site.		In current versions, using the '''''[[CMIS Export]]''''' definition with an '''''[[SFTP]]''''' connection is a preferable method to export document content to an SFTP site.
	\|}		\|}

Dgreenwood at 22:27, 28 February 2025

2025-02-28T22:27:46Z

← Older revision		Revision as of 17:27, 28 February 2025
Line 824:		Line 824:
	[[File:2023_Export_Activity_03_Thread_Pool_Guidance_03_1_Configure_An_Activity_Processing_Service_02.png]]		[[File:2023_Export_Activity_03_Thread_Pool_Guidance_03_1_Configure_An_Activity_Processing_Service_02.png]]
	<section end="single_threaded_export" />		<section end="single_threaded_export" />

	~~== Glossary ==~~
	~~<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}~~

	~~<u><big>'''Activity Processing (Concept)'''</big></u>: {{#lst:Glossary\|Activity Processing Concept}}~~

	~~<u><big>'''Activity Processing (Service)'''</big></u>: {{#lst:Glossary\|Activity Processing Service}}~~

	~~<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}~~

	~~<u><big>'''Batch Folder'''</big></u>: {{#lst:Glossary\|Batch Folder}}~~

	~~<u><big>'''Batch Page'''</big></u>: {{#lst:Glossary\|Batch Page}}~~

	~~<u><big>'''Batch Process Step'''</big></u>: {{#lst:Glossary\|Batch Process Step}}~~

	~~<u><big>'''Batch Process'''</big></u>: {{#lst:Glossary\|Batch Process}}~~

	~~<u><big>'''Batch'''</big></u>: {{#lst:Glossary\|Batch}}~~

	~~<u><big>'''Behavior'''</big></u>: {{#lst:Glossary\|Behavior}}~~

	~~<u><big>'''Box'''</big></u>: {{#lst:Glossary\|Box}}~~

	~~<u><big>'''Classify'''</big></u>: {{#lst:Glossary\|Classify}}~~

	~~<u><big>'''CMIS Connection'''</big></u>: {{#lst:Glossary\|CMIS Connection}}~~

	~~<u><big>'''CMIS Export'''</big></u>: {{#lst:Glossary\|CMIS Export}}~~

	~~<u><big>'''CMIS Repository'''</big></u>: {{#lst:Glossary\|CMIS Repository}}~~

	~~<u><big>'''CMIS'''</big></u>: {{#lst:Glossary\|CMIS}}~~

	~~<u><big>'''Content Category'''</big></u>: {{#lst:Glossary\|Content Category}}~~

	~~<u><big>'''Content Model'''</big></u>: {{#lst:Glossary\|Content Model}}~~

	~~<u><big>'''Content Type'''</big></u>: {{#lst:Glossary\|Content Type}}~~

	~~<u><big>'''Data Connection'''</big></u>: {{#lst:Glossary\|Data Connection}}~~

	~~<u><big>'''Data Element'''</big></u>: {{#lst:Glossary\|Data Element}}~~

	~~<u><big>'''Data Export'''</big></u>: {{#lst:Glossary\|Data Export}}~~

	~~<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}~~

	~~<u><big>'''Data Model'''</big></u>: {{#lst:Glossary\|Data Model}}~~

	~~<u><big>'''Document Type'''</big></u>: {{#lst:Glossary\|Document Type}}~~

	~~<u><big>'''Exchange'''</big></u>: {{#lst:Glossary\|Exchange}}~~

	~~<u><big>'''Execute'''</big></u>: {{#lst:Glossary\|Execute}}~~

	~~<u><big>'''Export Behavior'''</big></u>: {{#lst:Glossary\|Export Behavior}}~~

	~~<u><big>'''Export Definition'''</big></u>: {{#lst:Glossary\|Export Definition}}~~

	~~<u><big>'''Export'''</big></u>: {{#lst:Glossary\|Export}}~~

	~~<u><big>'''Extract'''</big></u>: {{#lst:Glossary\|Extract}}~~

	~~<u><big>'''FTP'''</big></u>: {{#lst:Glossary\|FTP}}~~

	~~<u><big>'''Grooper Repository'''</big></u>: {{#lst:Glossary\|Grooper Repository}}~~

	~~<u><big>'''Image Processing'''</big></u>: {{#lst:Glossary\|Image Processing}}~~

	~~<u><big>'''Image Processing'''</big></u>: {{#lst:Glossary\|Image Processing}}~~

	~~<u><big>'''IMAP'''</big></u>: {{#lst:Glossary\|IMAP}}~~

	~~<u><big>'''Node Tree'''</big></u>: {{#lst:Glossary\|Node Tree}}~~

	~~<u><big>'''NTFS'''</big></u>: {{#lst:Glossary\|NTFS}}~~

	~~<u><big>'''OCR'''</big></u>: {{#lst:Glossary\|OCR}}~~

	~~<u><big>'''PDF Data Mapping'''</big></u>: {{#lst:Glossary\|PDF Data Mapping}}~~

	~~<u><big>'''Processing Queue'''</big></u>: {{#lst:Glossary\|Processing Queue}}~~

	~~<u><big>'''Project'''</big></u>: {{#lst:Glossary\|Project}}~~

	~~<u><big>'''Recognize'''</big></u>: {{#lst:Glossary\|Recognize}}~~

	~~<u><big>'''Repository'''</big></u>: {{#lst:Glossary\|Repository}}~~

	~~<u><big>'''Service'''</big></u>: {{#lst:Glossary\|Service}}~~

	~~<u><big>'''SFTP'''</big></u>: {{#lst:Glossary\|SFTP}}~~

	~~<u><big>'''SharePoint'''</big></u>: {{#lst:Glossary\|SharePoint}}~~

	~~<u><big>'''Split Pages'''</big></u>: {{#lst:Glossary\|Split Pages}}~~

	~~<u><big>'''Split'''</big></u>: {{#lst:Glossary\|Split}}~~

	~~<u><big>'''Thread'''</big></u>: {{#lst:Glossary\|Thread}}~~

	~~<u><big>'''XML Transform'''</big></u>: {{#lst:Glossary\|XML Transform}}~~

Dgreenwood at 14:52, 19 September 2024

2024-09-19T14:52:57Z

← Older revision		Revision as of 09:52, 19 September 2024
Line 3:		Line 3:
	<blockquote>{{#lst:Glossary\|Export}}</blockquote>		<blockquote>{{#lst:Glossary\|Export}}</blockquote>

	'''Export''' is an "Code Activity" set on a '''[[Batch Process Step]]''', typically added as one of the last steps (if not the last step) of a '''Batch Process'''. It allows '''Grooper''' users to deliver processed '''Batch''' content to an external system. Whether exporting '''[[Batch Folder\|Batch Folders]]''' as PDF files to a Windows directory, exporting extracted '''Data Model''' fields to a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL database], exporting to a content management system, or some combination of multiple exports to multiple systems, the '''Export''' activity handles how document '''Batch Folders''' in a '''Batch''' ultimately leave '''Grooper''' after they have been classified and had their data extracted.		'''Export''' is a "Code Activity" set on a '''[[Batch Process Step]]''', typically added as one of the last steps (if not the last step) of a '''Batch Process'''. It allows '''Grooper''' users to deliver processed '''Batch''' content to an external system. Whether exporting '''[[Batch Folder\|Batch Folders]]''' as PDF files to a Windows directory, exporting extracted '''Data Model''' fields to a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL database], exporting to a content management system, or some combination of multiple exports to multiple systems, the '''Export''' activity handles how document '''Batch Folders''' in a '''Batch''' ultimately leave '''Grooper''' after they have been classified and had their data extracted.

	How documents are exported (what gets exported, where they go, and what format the exported content takes) is all controlled by '''''[[Behaviors#Export\|Export Behaviors]]'''''. This is a set of properties configured to control how '''Batch Folder''' content is exported based on its '''Document Type''' classification. '''''Export Behaviors''''' can be configured locally, configured as part of the '''Export''' activity's property configuration, or can be configured for a particular '''Content Type''', by configuring the '''''Behaviors''''' property of a '''Content Model''' and/or its descendant '''Content Categories''' or '''Document Types'''.		How documents are exported (what gets exported, where they go, and what format the exported content takes) is all controlled by '''''[[Behaviors#Export\|Export Behaviors]]'''''. This is a set of properties configured to control how '''Batch Folder''' content is exported based on its '''Document Type''' classification. '''''Export Behaviors''''' can be configured locally, configured as part of the '''Export''' activity's property configuration, or can be configured for a particular '''Content Type''', by configuring the '''''Behaviors''''' property of a '''Content Model''' and/or its descendant '''Content Categories''' or '''Document Types'''.

Dgreenwood at 14:52, 19 September 2024

2024-09-19T14:52:42Z

← Older revision		Revision as of 09:52, 19 September 2024
Line 3:		Line 3:
	<blockquote>{{#lst:Glossary\|Export}}</blockquote>		<blockquote>{{#lst:Glossary\|Export}}</blockquote>

	'''Export''' is an "~~Unattended~~ Activity" set on a '''[[Batch Process Step]]''', typically added as one of the last steps (if not the last step) of a '''Batch Process'''. It allows '''Grooper''' users to deliver processed '''Batch''' content to an external system. Whether exporting '''[[Batch Folder\|Batch Folders]]''' as PDF files to a Windows directory, exporting extracted '''Data Model''' fields to a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL database], exporting to a content management system, or some combination of multiple exports to multiple systems, the '''Export''' activity handles how document '''Batch Folders''' in a '''Batch''' ultimately leave '''Grooper''' after they have been classified and had their data extracted.		'''Export''' is an "Code Activity" set on a '''[[Batch Process Step]]''', typically added as one of the last steps (if not the last step) of a '''Batch Process'''. It allows '''Grooper''' users to deliver processed '''Batch''' content to an external system. Whether exporting '''[[Batch Folder\|Batch Folders]]''' as PDF files to a Windows directory, exporting extracted '''Data Model''' fields to a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL database], exporting to a content management system, or some combination of multiple exports to multiple systems, the '''Export''' activity handles how document '''Batch Folders''' in a '''Batch''' ultimately leave '''Grooper''' after they have been classified and had their data extracted.

	How documents are exported (what gets exported, where they go, and what format the exported content takes) is all controlled by '''''[[Behaviors#Export\|Export Behaviors]]'''''. This is a set of properties configured to control how '''Batch Folder''' content is exported based on its '''Document Type''' classification. '''''Export Behaviors''''' can be configured locally, configured as part of the '''Export''' activity's property configuration, or can be configured for a particular '''Content Type''', by configuring the '''''Behaviors''''' property of a '''Content Model''' and/or its descendant '''Content Categories''' or '''Document Types'''.		How documents are exported (what gets exported, where they go, and what format the exported content takes) is all controlled by '''''[[Behaviors#Export\|Export Behaviors]]'''''. This is a set of properties configured to control how '''Batch Folder''' content is exported based on its '''Document Type''' classification. '''''Export Behaviors''''' can be configured locally, configured as part of the '''Export''' activity's property configuration, or can be configured for a particular '''Content Type''', by configuring the '''''Behaviors''''' property of a '''Content Model''' and/or its descendant '''Content Categories''' or '''Document Types'''.
Line 675:		Line 675:

	== Processing Queue Guidance ==		== Processing Queue Guidance ==
	~~'''Unattended~~ Activities~~'''~~ in a '''Batch Process''' can be automated using an '''Activity Processing''' Grooper service. The '''Activity Processing''' service will act like a Windows service and automatically start tasks in a '''Batch''', as processing threads in your system's resources become available. This is one of the ways Grooper leverages your system resources for parallel processing.		"Code Activities" in a '''Batch Process''' can be automated using an '''Activity Processing''' Grooper service. The '''Activity Processing''' service will act like a Windows service and automatically start tasks in a '''Batch''', as processing threads in your system's resources become available. This is one of the ways Grooper leverages your system resources for parallel processing.

	Imagine you're running Grooper on a machine with eight (8) processing threads. If you have a '''Batch''' with five (5) '''Batch Folders''', and each one is on the '''Recognize''' step of the '''Batch Process''', there's no need for your system to process each '''Batch Folder''' sequentially (with each '''Batch Folder''' waiting to be processed until the one before it is finished).		Imagine you're running Grooper on a machine with eight (8) processing threads. If you have a '''Batch''' with five (5) '''Batch Folders''', and each one is on the '''Recognize''' step of the '''Batch Process''', there's no need for your system to process each '''Batch Folder''' sequentially (with each '''Batch Folder''' waiting to be processed until the one before it is finished).
Line 819:		Line 819:
	You can have multiple '''Activity Processing''' services running, each with their own '''Processing Queue'''.		You can have multiple '''Activity Processing''' services running, each with their own '''Processing Queue'''.

	You can automate the rest of the ~~'''Unattended~~ Activities~~'''~~ in a '''Batch Process''' by added a second '''Activity Processing''' service, assigning it the "Default" '''Processing Queue''', and assign the number of threads you want to utilize with the '''''Number of Threads''''' property.		You can automate the rest of the "Code Activities" in a '''Batch Process''' by added a second '''Activity Processing''' service, assigning it the "Default" '''Processing Queue''', and assign the number of threads you want to utilize with the '''''Number of Threads''''' property.
	\|}		\|}

Dgreenwood: /* Export Definitions */

2024-09-18T21:56:29Z

Export Definitions

Show changes

Dgreenwood: /* Export Behaviors */

2024-09-18T15:06:20Z

Export Behaviors

← Older revision		Revision as of 10:06, 18 September 2024
Line 78:		Line 78:

	== Export Behaviors ==		== Export Behaviors ==
			<blockquote>
			{{#lst:Glossary\|Export Behavior}}
			</blockquote>

	The '''Export''' activity exports documents according to an '''''Export Behavior'''''. This is a set of export property configurations based on the '''''Content Type''''' (i.e. '''Document Type''' of a '''Content Model''') assigned to a document '''Batch Folder''' during document classification. Once a '''Batch Folder''' is assigned a '''Document Type''', you have something you can point to that controls the flow of traffic out of Grooper.		The '''Export''' activity exports documents according to an '''''Export Behavior'''''. This is a set of export property configurations based on the '''''Content Type''''' (i.e. '''Document Type''' of a '''Content Model''') assigned to a document '''Batch Folder''' during document classification. Once a '''Batch Folder''' is assigned a '''Document Type''', you have something you can point to that controls the flow of traffic out of Grooper.

Randallkinard at 16:09, 26 August 2024

2024-08-26T16:09:47Z

Show changes

Randallkinard: /* Glossary */

2024-05-08T18:28:42Z

Glossary

← Older revision		Revision as of 13:28, 8 May 2024
Line 17:		Line 17:

	== Glossary ==		== Glossary ==
	<u><big>'''Activity ~~Processing~~'''</big></u>: {{#lst:Glossary\|Activity ~~Processing (Service)~~}}		<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}

	<u><big>'''Activity Processing'''</big></u>: {{#lst:Glossary\|Activity Processing (Concept)}}		<u><big>'''Activity Processing (Concept)'''</big></u>: {{#lst:Glossary\|Activity Processing Concept}}

	<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}		<u><big>'''Activity Processing (Service)'''</big></u>: {{#lst:Glossary\|Activity Processing Service}}

	<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}		<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}

Randallkinard: /* Glossary */

2024-05-08T18:26:59Z

Glossary

← Older revision		Revision as of 13:26, 8 May 2024
Line 17:		Line 17:

	== Glossary ==		== Glossary ==
	<u><big>'''Activity Processing'''</big></u>: {{#lst:Glossary\|Activity Processing}}		<u><big>'''Activity Processing'''</big></u>: {{#lst:Glossary\|Activity Processing (Service)}}

	<u><big>'''Activity Processing'''</big></u>: {{#lst:Glossary\|Activity Processing}}		<u><big>'''Activity Processing'''</big></u>: {{#lst:Glossary\|Activity Processing (Concept)}}

	<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}		<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}

Randallkinard at 18:25, 8 May 2024

2024-05-08T18:25:09Z

@@ Line 15: / Line 15: @@
 * [[Media:2023 Wiki Export-(Activity) Project.zip]]
 |}
 == About ==
 So you've ingested some documents into a '''Batch'''. You've obtained their full text data with the '''Recognize''' activity, either through OCR or extracting their native embedded text. You've classified these documents, assigning the '''Batch Folders''' a '''Document Type''' from a '''Content Model''' during the '''Classify''' activity. You've collected the data you want from these documents during the '''Extract''' activity. Now what?

← Older revision		Revision as of 17:27, 28 February 2025
Line 824:		Line 824:
	[[File:2023_Export_Activity_03_Thread_Pool_Guidance_03_1_Configure_An_Activity_Processing_Service_02.png]]		[[File:2023_Export_Activity_03_Thread_Pool_Guidance_03_1_Configure_An_Activity_Processing_Service_02.png]]
	<section end="single_threaded_export" />		<section end="single_threaded_export" />

	~~== Glossary ==~~
	~~<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}~~

	~~<u><big>'''Activity Processing (Concept)'''</big></u>: {{#lst:Glossary\|Activity Processing Concept}}~~

	~~<u><big>'''Activity Processing (Service)'''</big></u>: {{#lst:Glossary\|Activity Processing Service}}~~

	~~<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}~~

	~~<u><big>'''Batch Folder'''</big></u>: {{#lst:Glossary\|Batch Folder}}~~

	~~<u><big>'''Batch Page'''</big></u>: {{#lst:Glossary\|Batch Page}}~~

	~~<u><big>'''Batch Process Step'''</big></u>: {{#lst:Glossary\|Batch Process Step}}~~

	~~<u><big>'''Batch Process'''</big></u>: {{#lst:Glossary\|Batch Process}}~~

	~~<u><big>'''Batch'''</big></u>: {{#lst:Glossary\|Batch}}~~

	~~<u><big>'''Behavior'''</big></u>: {{#lst:Glossary\|Behavior}}~~

	~~<u><big>'''Box'''</big></u>: {{#lst:Glossary\|Box}}~~

	~~<u><big>'''Classify'''</big></u>: {{#lst:Glossary\|Classify}}~~

	~~<u><big>'''CMIS Connection'''</big></u>: {{#lst:Glossary\|CMIS Connection}}~~

	~~<u><big>'''CMIS Export'''</big></u>: {{#lst:Glossary\|CMIS Export}}~~

	~~<u><big>'''CMIS Repository'''</big></u>: {{#lst:Glossary\|CMIS Repository}}~~

	~~<u><big>'''CMIS'''</big></u>: {{#lst:Glossary\|CMIS}}~~

	~~<u><big>'''Content Category'''</big></u>: {{#lst:Glossary\|Content Category}}~~

	~~<u><big>'''Content Model'''</big></u>: {{#lst:Glossary\|Content Model}}~~

	~~<u><big>'''Content Type'''</big></u>: {{#lst:Glossary\|Content Type}}~~

	~~<u><big>'''Data Connection'''</big></u>: {{#lst:Glossary\|Data Connection}}~~

	~~<u><big>'''Data Element'''</big></u>: {{#lst:Glossary\|Data Element}}~~

	~~<u><big>'''Data Export'''</big></u>: {{#lst:Glossary\|Data Export}}~~

	~~<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}~~

	~~<u><big>'''Data Model'''</big></u>: {{#lst:Glossary\|Data Model}}~~

	~~<u><big>'''Document Type'''</big></u>: {{#lst:Glossary\|Document Type}}~~

	~~<u><big>'''Exchange'''</big></u>: {{#lst:Glossary\|Exchange}}~~

	~~<u><big>'''Execute'''</big></u>: {{#lst:Glossary\|Execute}}~~

	~~<u><big>'''Export Behavior'''</big></u>: {{#lst:Glossary\|Export Behavior}}~~

	~~<u><big>'''Export Definition'''</big></u>: {{#lst:Glossary\|Export Definition}}~~

	~~<u><big>'''Export'''</big></u>: {{#lst:Glossary\|Export}}~~

	~~<u><big>'''Extract'''</big></u>: {{#lst:Glossary\|Extract}}~~

	~~<u><big>'''FTP'''</big></u>: {{#lst:Glossary\|FTP}}~~

	~~<u><big>'''Grooper Repository'''</big></u>: {{#lst:Glossary\|Grooper Repository}}~~

	~~<u><big>'''Image Processing'''</big></u>: {{#lst:Glossary\|Image Processing}}~~

	~~<u><big>'''Image Processing'''</big></u>: {{#lst:Glossary\|Image Processing}}~~

	~~<u><big>'''IMAP'''</big></u>: {{#lst:Glossary\|IMAP}}~~

	~~<u><big>'''Node Tree'''</big></u>: {{#lst:Glossary\|Node Tree}}~~

	~~<u><big>'''NTFS'''</big></u>: {{#lst:Glossary\|NTFS}}~~

	~~<u><big>'''OCR'''</big></u>: {{#lst:Glossary\|OCR}}~~

	~~<u><big>'''PDF Data Mapping'''</big></u>: {{#lst:Glossary\|PDF Data Mapping}}~~

	~~<u><big>'''Processing Queue'''</big></u>: {{#lst:Glossary\|Processing Queue}}~~

	~~<u><big>'''Project'''</big></u>: {{#lst:Glossary\|Project}}~~

	~~<u><big>'''Recognize'''</big></u>: {{#lst:Glossary\|Recognize}}~~

	~~<u><big>'''Repository'''</big></u>: {{#lst:Glossary\|Repository}}~~

	~~<u><big>'''Service'''</big></u>: {{#lst:Glossary\|Service}}~~

	~~<u><big>'''SFTP'''</big></u>: {{#lst:Glossary\|SFTP}}~~

	~~<u><big>'''SharePoint'''</big></u>: {{#lst:Glossary\|SharePoint}}~~

	~~<u><big>'''Split Pages'''</big></u>: {{#lst:Glossary\|Split Pages}}~~

	~~<u><big>'''Split'''</big></u>: {{#lst:Glossary\|Split}}~~

	~~<u><big>'''Thread'''</big></u>: {{#lst:Glossary\|Thread}}~~

	~~<u><big>'''XML Transform'''</big></u>: {{#lst:Glossary\|XML Transform}}~~

← Older revision		Revision as of 09:52, 19 September 2024
Line 3:		Line 3:
	<blockquote>{{#lst:Glossary\|Export}}</blockquote>		<blockquote>{{#lst:Glossary\|Export}}</blockquote>

	'''Export''' is an "Code Activity" set on a '''[[Batch Process Step]]''', typically added as one of the last steps (if not the last step) of a '''Batch Process'''. It allows '''Grooper''' users to deliver processed '''Batch''' content to an external system. Whether exporting '''[[Batch Folder\|Batch Folders]]''' as PDF files to a Windows directory, exporting extracted '''Data Model''' fields to a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL database], exporting to a content management system, or some combination of multiple exports to multiple systems, the '''Export''' activity handles how document '''Batch Folders''' in a '''Batch''' ultimately leave '''Grooper''' after they have been classified and had their data extracted.		'''Export''' is a "Code Activity" set on a '''[[Batch Process Step]]''', typically added as one of the last steps (if not the last step) of a '''Batch Process'''. It allows '''Grooper''' users to deliver processed '''Batch''' content to an external system. Whether exporting '''[[Batch Folder\|Batch Folders]]''' as PDF files to a Windows directory, exporting extracted '''Data Model''' fields to a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL database], exporting to a content management system, or some combination of multiple exports to multiple systems, the '''Export''' activity handles how document '''Batch Folders''' in a '''Batch''' ultimately leave '''Grooper''' after they have been classified and had their data extracted.

	How documents are exported (what gets exported, where they go, and what format the exported content takes) is all controlled by '''''[[Behaviors#Export\|Export Behaviors]]'''''. This is a set of properties configured to control how '''Batch Folder''' content is exported based on its '''Document Type''' classification. '''''Export Behaviors''''' can be configured locally, configured as part of the '''Export''' activity's property configuration, or can be configured for a particular '''Content Type''', by configuring the '''''Behaviors''''' property of a '''Content Model''' and/or its descendant '''Content Categories''' or '''Document Types'''.		How documents are exported (what gets exported, where they go, and what format the exported content takes) is all controlled by '''''[[Behaviors#Export\|Export Behaviors]]'''''. This is a set of properties configured to control how '''Batch Folder''' content is exported based on its '''Document Type''' classification. '''''Export Behaviors''''' can be configured locally, configured as part of the '''Export''' activity's property configuration, or can be configured for a particular '''Content Type''', by configuring the '''''Behaviors''''' property of a '''Content Model''' and/or its descendant '''Content Categories''' or '''Document Types'''.

← Older revision		Revision as of 13:28, 8 May 2024
Line 17:		Line 17:

	== Glossary ==		== Glossary ==
	<u><big>'''Activity ~~Processing~~'''</big></u>: {{#lst:Glossary\|Activity ~~Processing (Service)~~}}		<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}

	<u><big>'''Activity Processing'''</big></u>: {{#lst:Glossary\|Activity Processing (Concept)}}		<u><big>'''Activity Processing (Concept)'''</big></u>: {{#lst:Glossary\|Activity Processing Concept}}

	<u><big>'''Activity'''</big></u>: {{#lst:Glossary\|Activity}}		<u><big>'''Activity Processing (Service)'''</big></u>: {{#lst:Glossary\|Activity Processing Service}}

	<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}		<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}