2023:Behaviors - Revision history

Dgreenwood at 16:21, 2 September 2025

2025-09-02T16:21:06Z

Dgreenwood: Dgreenwood moved page 2023:Behaviors (Property) to 2023:Behaviors

2025-05-29T19:47:19Z

Dgreenwood moved page 2023:Behaviors (Property) to 2023:Behaviors

← Older revision	Revision as of 14:47, 29 May 2025
(No difference)

Dgreenwood: /* Glossary */

2025-02-28T22:25:18Z

Glossary

← Older revision		Revision as of 17:25, 28 February 2025
Line 389:		Line 389:
	<!--#endregion-->		<!--#endregion-->
	<!--#endregion-->		<!--#endregion-->

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

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

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

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

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

	~~<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>'''Classification Method'''</big></u>: {{#lst:Glossary\|Classification Method}}~~

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

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

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

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

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

	~~<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 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>'''Data Section'''</big></u>: {{#lst:Glossary\|Data Section}}~~

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

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

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

	~~<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>'''Extractor Type'''</big></u>: {{#lst:Glossary\|Extractor Type}}~~

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

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

	~~<u><big>'''Import Query Results'''</big></u>: {{#lst:Glossary\|Import Query Results}}~~

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

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

	~~<u><big>'''Labelset-Based'''</big></u>: {{#lst:Glossary\|Labelset-Based}}~~

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

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

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

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

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

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

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

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

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

Randallkinard at 14:02, 26 August 2024

2024-08-26T14:02:38Z

Show changes

Randallkinard: /* PDF Generate */

2024-05-03T15:24:19Z

PDF Generate

← Older revision		Revision as of 10:24, 3 May 2024
Line 159:		Line 159:
	[[Image:2023_Behaviors_01_About_04.png]]		[[Image:2023_Behaviors_01_About_04.png]]

	====PDF ~~Generate~~====		==== PDF Data Mapping ====
	The ''PDF Generate Behavior'' is a '''Content Type''' '''''Behavior''''' designed to create an exportable PDF file with additional native PDF elements, using the classification and extraction content of a '''Batch Folder'''. This includes capabilities to export extracted data as PDF metadata, inserting bookmarks, and creating PDF annotations, such as highlighting, checkbox and signature widgets.		The ''PDF Generate Behavior'' is a '''Content Type''' '''''Behavior''''' designed to create an exportable PDF file with additional native PDF elements, using the classification and extraction content of a '''Batch Folder'''. This includes capabilities to export extracted data as PDF metadata, inserting bookmarks, and creating PDF annotations, such as highlighting, checkbox and signature widgets.

	Understanding the full functionality of the ''PDF ~~Generate~~ Behavior'' is worthy of it’s own article, which can be found [[PDF ~~Generate~~ Behavior\|~~here~~]].		Understanding the full functionality of the '''''[[PDF Data Mapping (Behavior)\|PDF Data Mapping]]''''' is worthy of it’s own article, which can be found <u>[[PDF Data Mapping (Behavior)\|by clicking this link]]</u>.

	[[Image:behaviours_03.png]]		[[Image:behaviours_03.png]]

Randallkinard: /* Labeling */

2024-05-03T15:21:33Z

Labeling

← Older revision		Revision as of 10:21, 3 May 2024
Line 155:		Line 155:
	* Sectional data extraction - Using a '''Data Section''' object's ''Transaction Detection'' '''''Extract Method'''''		* Sectional data extraction - Using a '''Data Section''' object's ''Transaction Detection'' '''''Extract Method'''''

	Understanding the full functionality of the ''Labeling Behavior'' is worthy of it’s own article, which can be found [[Labeling Behavior ~~- 2021~~\|~~here~~]].		Understanding the full functionality of the '''''[[Labeling Behavior (Behavior)\|Labeling Behavior]]''''' is worthy of it’s own article, which can be found <u>[[Labeling Behavior (Behavior)\|by clicking this link]]</u>.

	[[Image:2023_Behaviors_01_About_04.png]]		[[Image:2023_Behaviors_01_About_04.png]]

Randallkinard at 15:16, 3 May 2024

2024-05-03T15:16:01Z

@@ Line 15: / Line 15: @@
 * [[Media:2023_Wiki_Behaviors_Project.zip]]
 |}
 <!--#region About-->

Randallkinard at 20:41, 19 April 2024

2024-04-19T20:41:55Z

← Older revision		Revision as of 15:41, 19 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	[[Image:behaviours_00.png\|right\|thumb\|250px\|Behaviors are like telling the mind what to let in and out.]]		[[Image:behaviours_00.png\|right\|thumb\|250px\|Behaviors are like telling the mind what to let in and out.]]
	~~<section begin="glossary" />~~
	~~<blockquote>~~
	~~'''''Behaviors''''' are properties set on '''Content Types''' and '''Export''' activities that control the flow of documents into and out of '''Grooper''' .~~
	~~</blockquote>~~
	~~<section end="glossary" />~~

	<~~!--~~#~~region About--~~>		<blockquote>{{#lst:Glossary\|Behavior}}</blockquote>
	~~==About==~~
	{\|class="download-box"		{\|class="download-box"
	\|		\|
Line 21:		Line 16:
	\|}		\|}

			<!--#region About-->
			==About==
	'''''Behaviors''''' are born of the idea that consolidating the control of the flow of data to the objects most relevant to its collection and delivery ('''Content Types'''{'''Content Model''', '''Content Category''', '''Document Type'''} and the '''Export''' activity) creates a more streamlined and effective '''Grooper''' experience. If the '''Content Type''' controls all the relevant information about how documents are organized and what is to be collected from them, it is logical that controlling how those documents come into '''Grooper''', and how they get out, should also be defined by the same object. It is also a much cleaner experience to not have multiple steps in a '''Batch Process''' to cover the types of '''Export''' activities ('''Legacy Export''', '''Mapped Export''', '''Database Export'''), but instead a single '''Export''' activity that leverages the '''Behaviors''' of the '''Content Type''', '''Behaviors''' defined on the '''Export''' activity, or both.		'''''Behaviors''''' are born of the idea that consolidating the control of the flow of data to the objects most relevant to its collection and delivery ('''Content Types'''{'''Content Model''', '''Content Category''', '''Document Type'''} and the '''Export''' activity) creates a more streamlined and effective '''Grooper''' experience. If the '''Content Type''' controls all the relevant information about how documents are organized and what is to be collected from them, it is logical that controlling how those documents come into '''Grooper''', and how they get out, should also be defined by the same object. It is also a much cleaner experience to not have multiple steps in a '''Batch Process''' to cover the types of '''Export''' activities ('''Legacy Export''', '''Mapped Export''', '''Database Export'''), but instead a single '''Export''' activity that leverages the '''Behaviors''' of the '''Content Type''', '''Behaviors''' defined on the '''Export''' activity, or both.

Randallkinard: Randallkinard moved page 2023:Behaviors to 2023:Behaviors (Property) without leaving a redirect: new naming convention

2024-04-18T19:35:53Z

Randallkinard moved page 2023:Behaviors to 2023:Behaviors (Property) without leaving a redirect: new naming convention

← Older revision	Revision as of 14:35, 18 April 2024
(No difference)

Randallkinard: moved file download box to "About" section // via Wikitext Extension for VSCode

2024-03-13T14:21:42Z

moved file download box to "About" section // via Wikitext Extension for VSCode

← Older revision		Revision as of 09:21, 13 March 2024
Line 6:		Line 6:
	</blockquote>		</blockquote>
	<section end="glossary" />		<section end="glossary" />

			<!--#region About-->
			==About==
	{\|class="download-box"		{\|class="download-box"
	\|		\|
Line 17:		Line 20:
	* [[Media:2023_Wiki_Behaviors_Project.zip]]		* [[Media:2023_Wiki_Behaviors_Project.zip]]
	\|}		\|}
	~~<!--#region About-->~~
	~~==About==~~

	'''''Behaviors''''' are born of the idea that consolidating the control of the flow of data to the objects most relevant to its collection and delivery ('''Content Types'''{'''Content Model''', '''Content Category''', '''Document Type'''} and the '''Export''' activity) creates a more streamlined and effective '''Grooper''' experience. If the '''Content Type''' controls all the relevant information about how documents are organized and what is to be collected from them, it is logical that controlling how those documents come into '''Grooper''', and how they get out, should also be defined by the same object. It is also a much cleaner experience to not have multiple steps in a '''Batch Process''' to cover the types of '''Export''' activities ('''Legacy Export''', '''Mapped Export''', '''Database Export'''), but instead a single '''Export''' activity that leverages the '''Behaviors''' of the '''Content Type''', '''Behaviors''' defined on the '''Export''' activity, or both.		'''''Behaviors''''' are born of the idea that consolidating the control of the flow of data to the objects most relevant to its collection and delivery ('''Content Types'''{'''Content Model''', '''Content Category''', '''Document Type'''} and the '''Export''' activity) creates a more streamlined and effective '''Grooper''' experience. If the '''Content Type''' controls all the relevant information about how documents are organized and what is to be collected from them, it is logical that controlling how those documents come into '''Grooper''', and how they get out, should also be defined by the same object. It is also a much cleaner experience to not have multiple steps in a '''Batch Process''' to cover the types of '''Export''' activities ('''Legacy Export''', '''Mapped Export''', '''Database Export'''), but instead a single '''Export''' activity that leverages the '''Behaviors''' of the '''Content Type''', '''Behaviors''' defined on the '''Export''' activity, or both.

← Older revision		Revision as of 17:25, 28 February 2025
Line 389:		Line 389:
	<!--#endregion-->		<!--#endregion-->
	<!--#endregion-->		<!--#endregion-->

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

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

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

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

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

	~~<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>'''Classification Method'''</big></u>: {{#lst:Glossary\|Classification Method}}~~

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

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

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

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

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

	~~<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 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>'''Data Section'''</big></u>: {{#lst:Glossary\|Data Section}}~~

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

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

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

	~~<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>'''Extractor Type'''</big></u>: {{#lst:Glossary\|Extractor Type}}~~

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

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

	~~<u><big>'''Import Query Results'''</big></u>: {{#lst:Glossary\|Import Query Results}}~~

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

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

	~~<u><big>'''Labelset-Based'''</big></u>: {{#lst:Glossary\|Labelset-Based}}~~

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

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

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

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

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

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

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

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

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

← Older revision		Revision as of 11:21, 2 September 2025
Line 52:		Line 52:

	* Document classification - Using the ''Labelset-Based'' '''''Classification Method'''''		* Document classification - Using the ''Labelset-Based'' '''''Classification Method'''''
	* Field based data extraction - Using the ''Labeled Value'' ~~'''''~~Extractor ~~Type'''''~~		* Field based data extraction - Using the ''Labeled Value'' Value Extractor
	* Tabular data extraction - Using a '''Data Table''' object's ''Tabular Layout'' '''''Extract Method'''''		* Tabular data extraction - Using a '''Data Table''' object's ''Tabular Layout'' '''''Extract Method'''''
	* Sectional data extraction - Using a '''Data Section''' object's ''Transaction Detection'' '''''Extract Method'''''		* Sectional data extraction - Using a '''Data Section''' object's ''Transaction Detection'' '''''Extract Method'''''

	Understanding the full functionality of the '''''[[Labeling Behavior (Behavior)\|Labeling Behavior]]''''' is worthy of ~~it’s~~ own article, which can be found <u>[[Labeling Behavior (Behavior)\|by clicking this link]]</u>.		Understanding the full functionality of the '''''[[Labeling Behavior (Behavior)\|Labeling Behavior]]''''' is worthy of its own article, which can be found <u>[[Labeling Behavior (Behavior)\|by clicking this link]]</u>.

	[[Image:2023_Behaviors_01_About_04.png]]		[[Image:2023_Behaviors_01_About_04.png]]
Line 315:		Line 315:
	<!--#endregion-->		<!--#endregion-->
	<!--#region Text Rendering Setup-->		<!--#region Text Rendering Setup-->
	===Text Rendering Setup===		== How To: Text Rendering Setup==
	In this section we well look at the steps required to establish a '''Text Rendering''' behavior.		In this section we well look at the steps required to establish a '''Text Rendering''' behavior.
	<!--#region Default Text Document View-->		<!--#region Default Text Document View-->
	====Default Text Document View====		===Default Text Document View===
	By default, when text based documents are viewed in '''Grooper''' you will see them as if you would in any other text editing application, which can be obvious when there is no word wrapping. No steps are required to view the text based document in this way.		By default, when text based documents are viewed in '''Grooper''' you will see them as if you would in any other text editing application, which can be obvious when there is no word wrapping. No steps are required to view the text based document in this way.

Line 324:		Line 324:
	<!--#endregion-->		<!--#endregion-->
	<!--#region Non Word-Wrapped Text Document-->		<!--#region Non Word-Wrapped Text Document-->
	====Non Word-Wrapped Text Document====		===Non Word-Wrapped Text Document===
	In previous versions of '''Grooper''' native text files were rendered as paginated documents without word wrapping (the rendered document would be as wide as the longest line of text.) To mimic this style, use the following steps.		In previous versions of '''Grooper''' native text files were rendered as paginated documents without word wrapping (the rendered document would be as wide as the longest line of text.) To mimic this style, use the following steps.

Line 363:		Line 363:
	<!--#endregion-->		<!--#endregion-->
	<!--#region Word-Wrapped Document-->		<!--#region Word-Wrapped Document-->
	====Word-Wrapped Document====		===Word-Wrapped Document===
	With a ''Text Rendering'' behavior you can not only view a native text document as a non-standard, paginated image, but you can force a document dimension and cause lines of text to wrap accordingly.		With a ''Text Rendering'' behavior you can not only view a native text document as a non-standard, paginated image, but you can force a document dimension and cause lines of text to wrap accordingly.