2021:Export (Activity) - Revision history

Dgreenwood at 16:15, 5 August 2025

2025-08-05T16:15:44Z

← Older revision		Revision as of 11:15, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}

Randallkinard at 18:38, 19 April 2024

2024-04-19T18:38:56Z

← Older revision		Revision as of 13:38, 19 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	<blockquote ~~style="font-size~~:~~125%">~~
	~~The '''~~Export~~''' activity exports processed document content to an external storage platform.~~		<blockquote>{{#lst:Glossary\|Export}}</blockquote>
	</blockquote>

	'''Export''' is an '''Unattended Activity''', typically added as of 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 Folders''' as PDF files to a Windows folder, exporting extracted '''Data Model''' fields to a 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 '''Unattended Activity''', typically added as of 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 Folders''' as PDF files to a Windows folder, exporting extracted '''Data Model''' fields to a 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.

Dgreenwood: Dgreenwood moved page Export (Activity) - 2021 to 2021:Export (Activity) without leaving a redirect

2023-12-28T20:53:12Z

Dgreenwood moved page Export (Activity) - 2021 to 2021:Export (Activity) without leaving a redirect

← Older revision	Revision as of 15:53, 28 December 2023
(No difference)

Dgreenwood: Removed redirect to Export (Activity) - 2023

2023-12-28T20:52:52Z

Removed redirect to Export (Activity) - 2023

← Older revision		Revision as of 15:52, 28 December 2023
Line 1:		Line 1:
	~~#REDIRECT [[Export (Activity) - 2023]]~~		{{AutoVersion}}
	<blockquote style="font-size:125%">		<blockquote style="font-size:125%">
	The '''Export''' activity exports processed document content to an external storage platform.		The '''Export''' activity exports processed document content to an external storage platform.

Dsmith: Redirected page to Export (Activity) - 2023

2023-12-12T16:12:26Z

Redirected page to Export (Activity) - 2023

← Older revision		Revision as of 11:12, 12 December 2023
Line 1:		Line 1:
			#REDIRECT [[Export (Activity) - 2023]]
	<blockquote style="font-size:125%">		<blockquote style="font-size:125%">
	The '''Export''' activity exports processed document content to an external storage platform.		The '''Export''' activity exports processed document content to an external storage platform.

Dgreenwood at 20:44, 9 December 2022

2022-12-09T20:44:34Z

← Older revision		Revision as of 15:44, 9 December 2022
Line 891:		Line 891:
	</tab>		</tab>
	</tabs>		</tabs>

			[[Category:Articles]]
			[[Category:Version 2021]]

Dgreenwood: /* About */

2021-10-06T15:26:23Z

About

← Older revision		Revision as of 10:26, 6 October 2021
Line 8:		Line 8:

	== About ==		== About ==

			{\|cellpadding="10" cellspacing="5"
			\|-
			\|style="font-size:14pt; color:#f89420; border: 2px solid #f89420; width:40px"\|[[File:Asset 22@4x.png]]
			\|style="border: 2px solid #f89420"\|
			You may download and import the file below into your own Grooper environment (version 2021). This contains a '''Batch''' with the example document(s), a '''Content Model''', and a '''Batch Process''' discussed in this article
			* [[Media:Export Activity (v2021).zip]]
			\|}

	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?		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?

Dgreenwood: /* Thread Pool Guidance */

2021-10-06T14:21:58Z

Thread Pool Guidance

@@ Line 746: / Line 746: @@
 Next, we will show you how to create a single threaded '''Thread Pool''' for an '''Export''' activity, and set up an '''Activity Processing''' service that utilizes it.  This will effectively throttle your export, so '''Batch Folders''' are indeed only exported one at a time, avoiding any issues with external platforms that cannot handle multi-threaded exports.
 <tabs style="margin:20px">
@@ Line 802: / Line 804: @@
 On to Grooper Config!  Grooper services are installed and edited using Grooper Config.  Open Grooper Config to install a new '''Activity Processing''' service.
 </tab>
 </tabs>

Dgreenwood: /* Shared Behavior Modes */

2021-10-05T21:19:43Z

Shared Behavior Modes

← Older revision		Revision as of 16:19, 5 October 2021
Line 658:		Line 658:
	With the '''''Shared Behavior Mode''''' set to ''LocalOrShared'', local behaviors will execute first. Shared behaviors will only execute if no local behavior is present.		With the '''''Shared Behavior Mode''''' set to ''LocalOrShared'', local behaviors will execute first. Shared behaviors will only execute if no local behavior is present.

	In our case, no local '''''Export Behavior''''' is present for "Red" documents, but there is a shared ''''''Export Behavior''''' configured on the "Red" '''Document Type'''.		In our case, no local '''''Export Behavior''''' is present for "Red" documents, but there is a shared '''''Export Behavior''''' configured on the "Red" '''Document Type'''.

	* So, the "Orange" documents export an XML file to "Folder B", using the local behavior.		* So, the "Orange" documents export an XML file to "Folder B", using the local behavior.

Dgreenwood: /* Shared Behavior Modes */

2021-10-05T21:15:22Z

Shared Behavior Modes

← Older revision		Revision as of 16:15, 5 October 2021
Line 643:		Line 643:
	\|-		\|-
	\|valign=top\|		\|valign=top\|
	With the '''''Shared Behavior Mode''''' set to ''SharedOrLocal'', shared behaviors ~~take priority~~. ~~They~~ will ~~supersede local behaviors~~.		With the '''''Shared Behavior Mode''''' set to ''SharedOrLocal'', shared behaviors will execute first. Local behaviors will only execute if no shared behavior is present.

	In our ~~case,~~ the local '''''Export Behavior''''' for the "Orange" '''Document ~~Type~~''' ~~is overridden by the~~ shared '''''Export ~~Behavior~~'''''~~. A PDF file is generated and placed in "Folder A" and~~ ''~~not~~'' ~~an XML file in "Folder B"~~.		Only our shared '''''Export Behaviors''''' execute in this instance. Grooper doesn't even bother to look at the local '''''Export Behavior''''' for the "Orange" and "Red" '''Document Types''' because shared '''''Export Behaviors''''' are present for these '''Document Types'''.

	~~Only our shared~~ ''''~~'Export Behaviors''''' execute~~ in ~~this instance~~.		* The "Orange" documents would export as a PDF file and be placed in "Folder A" (and ''not'' an XML file in "Folder B".
			* The "Red" documents would export as a PDF file and be placed in "Folder A".
	\|valign=top style="width:33%; text-align:center"\|		\|valign=top style="width:33%; text-align:center"\|
	[[File:Export-shared-behaviors-10.png]]		[[File:Export-shared-behaviors-10.png]]
Line 655:		Line 656:
	\|-		\|-
	\|valign=top\|		\|valign=top\|
	With the '''''Shared Behavior Mode''''' set to ''LocalOrShared'', local behaviors ~~take priority~~. ~~They~~ will ~~supersede shared behaviors~~.		With the '''''Shared Behavior Mode''''' set to ''LocalOrShared'', local behaviors will execute first. Shared behaviors will only execute if no local behavior is present.

	~~However~~, ~~for both~~ ''Or'' ~~modes (~~''~~LocalOrShared~~'' or ''~~SharedOrLocal'') if no matching behavior~~ is ~~found~~ for ~~the primary~~ '''''Export Behavior''''', the ~~secondary one will still execute~~.		In our case, no local '''''Export Behavior''''' is present for "Red" documents, but there is a shared ''''''Export Behavior''''' configured on the "Red" '''Document Type'''.

	* So, the "Orange" documents export an XML file to "Folder B", using the local behavior.		* So, the "Orange" documents export an XML file to "Folder B", using the local behavior.
	* However, the "Red" documents export a PDF file to "Folder A", using the shared behavior since no local behavior was found.		* However, the "Red" documents export a PDF file to "Folder A", using the shared behavior since no local behavior was found.

	\|valign=top style="width:33%; text-align:center"\|		\|valign=top style="width:33%; text-align:center"\|
	[[File:Export-shared-behaviors-11.png]]		[[File:Export-shared-behaviors-11.png]]