What's New in Grooper 2023.1 - Revision history

Dgreenwood: /* "FIFO" Batch Priority */

2026-04-07T16:00:54Z

"FIFO" Batch Priority

← Older revision		Revision as of 11:00, 7 April 2026
Line 301:		Line 301:
	* Batch priority values will not increment by exactly "1".		* Batch priority values will not increment by exactly "1".
	** Row IDs are also generated for Batch Folders created by Import Jobs. This means there may be gaps between the numbers assigned to each Batch's priority.		** Row IDs are also generated for Batch Folders created by Import Jobs. This means there may be gaps between the numbers assigned to each Batch's priority.
	** Example: Batch #1 is imported with 10 documents. Its Row ID is 100, so its priority will be 100. Batch #2 is imported next. Its Row ID will be 111, accounting for ~~the~~ 10 ~~imported~~ documents and ~~the~~ Batch node itself. Therefore its priority will be 111.		** Example: Batch #1 is imported with 10 documents. Its Row ID is 100, so its priority will be 100. Batch #2 is imported next. Its Row ID will be 111, accounting for Batch #1's previously imported 10 documents and Batch #2's node itself. Therefore its priority will be 111.

	=== Dynamic Value Lists ===		=== Dynamic Value Lists ===

Dgreenwood: /* "FIFO" Batch Priority */

2026-04-07T15:47:59Z

"FIFO" Batch Priority

← Older revision		Revision as of 10:47, 7 April 2026
Line 291:		Line 291:
	=== "FIFO" Batch Priority ===		=== "FIFO" Batch Priority ===

	Traditionally in Grooper, '''Batches''' are created with a set priority (between "1" and "5"). When all ~~'''~~Batches~~'''~~ have the same priority, processing can bottleneck around processor intensive activities. This can cause situations where the first ~~'''~~Batch~~'''~~ that was imported isn't necessarily the first ~~'''~~Batch~~'''~~ to finish processing or get to a ~~'''~~Review~~'''~~ step first.		Traditionally in Grooper, '''Batches''' are created with a set priority (between "1" and "5"). When all Batches have the same priority, processing can bottleneck around processor intensive activities. This can cause situations where the first Batch that was imported isn't necessarily the first Batch to finish processing or get to a Review step first.

	~~'''~~Batches~~'''~~ can now be processed with a "First In, First Out" priority in Grooper. ~~'''''~~Import Providers~~'''''~~ have a ~~new ''~~'''Batch Creation''''' option called '''''Increment Priority'''''. Turning this property on increments each '''Batch's''' priority by "1" each time a new '''Batch''' is created. This causes each '''Batch''' to fully run through a '''Batch Process''' before the next is started.		Batches can now be processed with a "First In, First Out" priority in Grooper. Import Providers have a '''Batch Creation''' option called '''Increment Priority'''.

	'''''Please note!''''' ~~This functionality~~ is ~~intended~~ for ~~large user-directed imports,~~ ''~~not~~'' '''Batch''' ~~imports directed~~ by ~~an '''''~~Import ~~Watcher~~'~~'''' service~~.		Turning this property on sets each '''Batch's''' priority to the Batch's Row ID value from the Grooper database. Row IDs are assigned to Grooper nodes sequentially as items are created in the Grooper database. Since lower priority values are processed first, Batches created earlier (with lower Row IDs) will be processed before those created later, achieving FIFO behavior.

			Please note the following:
			* Enabling '''Increment Priority''' will override whatever value is set for the '''Priority''' setting in the '''Batch Creation''' settings.
			* Batch priority values will not increment by exactly "1".
			** Row IDs are also generated for Batch Folders created by Import Jobs. This means there may be gaps between the numbers assigned to each Batch's priority.
			** Example: Batch #1 is imported with 10 documents. Its Row ID is 100, so its priority will be 100. Batch #2 is imported next. Its Row ID will be 111, accounting for the 10 imported documents and the Batch node itself. Therefore its priority will be 111.

	=== Dynamic Value Lists ===		=== Dynamic Value Lists ===

Dgreenwood: /* Misc other changes */

2024-02-12T18:32:45Z

Misc other changes

← Older revision		Revision as of 13:32, 12 February 2024
Line 392:		Line 392:

	'''''Custom Statements''''' allow users to configure a custom SQL statement using an expression. This will allow for more nuanced SQL database exports. For example, a user could modify existing records in a database with an UPDATE command using '''''Custom Statements'''''.		'''''Custom Statements''''' allow users to configure a custom SQL statement using an expression. This will allow for more nuanced SQL database exports. For example, a user could modify existing records in a database with an UPDATE command using '''''Custom Statements'''''.

			Users define two properties to configure each '''''Custom Statement''''':
			# '''''Source Scope''''': Specifies the '''Data Elements''' to be used for the statement.
			#* Can be set to a '''Data Model''', '''Data Section''' or '''Data Table'''
			# '''''Statement'''': A code expression used to generate the SQL statement.
			#* Example: <code>$"UPDATE invoices SET status=2 WHERE id={Invoice Id}"</code>
	\|}		\|}

Dgreenwood: /* Misc other changes */

2024-02-12T18:26:22Z

Misc other changes

← Older revision		Revision as of 13:26, 12 February 2024
Line 387:		Line 387:

	''Note: This functionality was added late in the development cycle. Currently, nodes may only be published one at a time. Future development will include the capability to publish multiple nodes by multi-selecting them.''		''Note: This functionality was added late in the development cycle. Currently, nodes may only be published one at a time. Future development will include the capability to publish multiple nodes by multi-selecting them.''
	\|}		\|-
			\|
			New '''''Data Export''''' functionality: '''''Custom Statements'''''

			'''''Custom Statements''''' allow users to configure a custom SQL statement using an expression. This will allow for more nuanced SQL database exports. For example, a user could modify existing records in a database with an UPDATE command using '''''Custom Statements'''''.
			\|}

	=== Expressions and Scripting Related Changes ===		=== Expressions and Scripting Related Changes ===

Dgreenwood: /* Misc other changes */

2024-02-05T14:55:24Z

Misc other changes

← Older revision		Revision as of 09:55, 5 February 2024
Line 385:		Line 385:
	** Example 1: If you attempt to publish an '''OCR Profile''' to a repository that does not contain the parent '''Project''', the Publish will fail.		** Example 1: If you attempt to publish an '''OCR Profile''' to a repository that does not contain the parent '''Project''', the Publish will fail.
	** Example 2: If you attempt to publish a '''Document Type''' to a repository and its parent '''Content Model''' does not exist, the Publish will fail (even if the parent '''Project''' does).		** Example 2: If you attempt to publish a '''Document Type''' to a repository and its parent '''Content Model''' does not exist, the Publish will fail (even if the parent '''Project''' does).

			''Note: This functionality was added late in the development cycle. Currently, nodes may only be published one at a time. Future development will include the capability to publish multiple nodes by multi-selecting them.''
	\|}		\|}

Dgreenwood: /* Misc other changes */

2024-02-05T14:43:22Z

Misc other changes

← Older revision		Revision as of 09:43, 5 February 2024
Line 385:		Line 385:
	** Example 1: If you attempt to publish an '''OCR Profile''' to a repository that does not contain the parent '''Project''', the Publish will fail.		** Example 1: If you attempt to publish an '''OCR Profile''' to a repository that does not contain the parent '''Project''', the Publish will fail.
	** Example 2: If you attempt to publish a '''Document Type''' to a repository and its parent '''Content Model''' does not exist, the Publish will fail (even if the parent '''Project''' does).		** Example 2: If you attempt to publish a '''Document Type''' to a repository and its parent '''Content Model''' does not exist, the Publish will fail (even if the parent '''Project''' does).
	\|
	~~The "Import/Upload ZIP" "Export/Download ZIP" and "Publish To Repository" commands now support multi-selection in the web client.~~
	\|}		\|}

Dgreenwood: /* Misc other changes */

2024-02-05T14:41:28Z

Misc other changes

← Older revision		Revision as of 09:41, 5 February 2024
Line 385:		Line 385:
	** Example 1: If you attempt to publish an '''OCR Profile''' to a repository that does not contain the parent '''Project''', the Publish will fail.		** Example 1: If you attempt to publish an '''OCR Profile''' to a repository that does not contain the parent '''Project''', the Publish will fail.
	** Example 2: If you attempt to publish a '''Document Type''' to a repository and its parent '''Content Model''' does not exist, the Publish will fail (even if the parent '''Project''' does).		** Example 2: If you attempt to publish a '''Document Type''' to a repository and its parent '''Content Model''' does not exist, the Publish will fail (even if the parent '''Project''' does).
			\|
			The "Import/Upload ZIP" "Export/Download ZIP" and "Publish To Repository" commands now support multi-selection in the web client.
	\|}		\|}

Randallkinard: added links to mentioned articles // Edit via Wikitext Extension for VSCode

2024-02-01T21:00:15Z

added links to mentioned articles // Edit via Wikitext Extension for VSCode

← Older revision		Revision as of 16:00, 1 February 2024
Line 44:		Line 44:
	* GrooperSDK		* GrooperSDK

	For more information, be sure to check out the [[~~Remote Scripting Setup - 2023.1\|~~Remote Scripting Setup]] article.		For more information, be sure to check out the [[Remote Scripting Setup]] article.

	== New and improved processing features ==		== New and improved processing features ==
Line 64:		Line 64:


	For more information, be sure to check out the "Secondary Types" article ~~'''''COMING SOON!!'''''~~		For more information, be sure to check out the [[Secondary Types]] article.
	\|		\|
	[[File:2023-1 WhatsNewInGrooper 03.png]]		[[File:2023-1 WhatsNewInGrooper 03.png]]
Line 84:		Line 84:

	''FYI: X12 refers to the organization developing and maintaining the EDI standards. X12 is the common EDI standard in the US and North America.''		''FYI: X12 refers to the organization developing and maintaining the EDI standards. X12 is the common EDI standard in the US and North America.''

			For more information, be sure to check out the [[XML Schema Integration]] article.

	=== XML Data Interchange ===		=== XML Data Interchange ===
Line 92:		Line 94:
	* Validate an XML document against an XML schema using the '''Execute''' activity, configured with an '''''XML File - Validate Schema''''' command.		* Validate an XML document against an XML schema using the '''Execute''' activity, configured with an '''''XML File - Validate Schema''''' command.
	* Generate an XML document according to an XML schema using a new '''''Merge/Export Format''''' (called '''''XML Format''''').		* Generate an XML document according to an XML schema using a new '''''Merge/Export Format''''' (called '''''XML Format''''').

			For more information, be sure to check out the [[XML Schema Integration]] article.

	=== New node type: Resource Files ===		=== New node type: Resource Files ===

Dgreenwood: /* Misc other changes */

2024-02-01T15:49:12Z

Misc other changes

← Older revision		Revision as of 10:49, 1 February 2024
Line 374:		Line 374:
	* New “self” CSS construct		* New “self” CSS construct
	** Useful when editing container-level CSS and you want to edit the container’s own CSS, rather than its children’s CSS.		** Useful when editing container-level CSS and you want to edit the container’s own CSS, rather than its children’s CSS.
			\|-
			\|
			The "Publish To Repository" command now works with any descendant of the '''Projects''' folder.
			* This means you can publish individual nodes in a '''Project''' to another Grooper Repository (not just the whole '''Project''').
			* The ancestor nodes ''must'' exist in the destination repository for the Publish operation to work.
			** Example 1: If you attempt to publish an '''OCR Profile''' to a repository that does not contain the parent '''Project''', the Publish will fail.
			** Example 2: If you attempt to publish a '''Document Type''' to a repository and its parent '''Content Model''' does not exist, the Publish will fail (even if the parent '''Project''' does).
	\|}		\|}

Dgreenwood: /* Header-Value is out. Tabular Layout is in */

2024-01-12T18:38:10Z

Header-Value is out. Tabular Layout is in

← Older revision		Revision as of 13:38, 12 January 2024
Line 186:		Line 186:

	'''''Tabular Layout''''' will greatly improve your table extraction results, particularly if you familiarize yourself with all [[Tabular Layout]] can do for you.		'''''Tabular Layout''''' will greatly improve your table extraction results, particularly if you familiarize yourself with all [[Tabular Layout]] can do for you.

			{\|class="attn-box"
			\|
			⚠
			\|
			'''PLEASE NOTE:''' If you are currently using '''''Header-Value''''' in production, you should take '''''extra''''' care when testing your upgrade to ensure your results are consistent. You may need to adjust aspects of your table extraction setup to get the best results possible after upgrading.

			'''''ALWAYS BACKUP YOUR GROOPER DATABASE BEFORE UPGRADING TO ENSURE YOU CAN REVERT BACK IF NECESSARY'''''
			\|}

	==== Known conversion issues ====		==== Known conversion issues ====