What's New in Grooper 2025 - Revision history

Dgreenwood: /* VLM Analyze */

2026-06-10T19:00:25Z

VLM Analyze

← Older revision		Revision as of 14:00, 10 June 2026
Line 559:		Line 559:
	* '''Relative Of''' — A more flexible option that defines related Content Types whose Data Elements are exposed in the expression environment, regardless of whether they are parent documents or Secondary Types. Use when the related Content Type could be either a parent or a sibling.		* '''Relative Of''' — A more flexible option that defines related Content Types whose Data Elements are exposed in the expression environment, regardless of whether they are parent documents or Secondary Types. Use when the related Content Type could be either a parent or a sibling.

	== VLM Analyze ==		== VLM Analyze Activity ==

	=== New Activity: VLM Analyze ===		=== New Activity: VLM Analyze ===

Dgreenwood: /* Route */

2026-06-10T19:00:13Z

Route

← Older revision		Revision as of 14:00, 10 June 2026
Line 519:		Line 519:
	{{attn-box\|Spatial Grounding consumes significantly more tokens than AI Extract. Consider using a less expensive model to control costs.}}		{{attn-box\|Spatial Grounding consumes significantly more tokens than AI Extract. Consider using a less expensive model to control costs.}}

	== Route ==		== Route Activity ==

	=== New Activity: Route ===		=== New Activity: Route ===
Line 549:		Line 549:
	{{attn-box\|Nested Batches are still in the experimental stages. More work is needed to ensure operational rules are in place to prevent unsafe Batch deletion and improper task processing.}}		{{attn-box\|Nested Batches are still in the experimental stages. More work is needed to ensure operational rules are in place to prevent unsafe Batch deletion and improper task processing.}}

			== Content Type Relationships ==

			Content Type Relationships expose related Data Models to code expressions and other features. They are defined by three properties on a Content Model, Content Category, or Document Type:

			* '''Child Of''' — Specifies a parent Content Type that will always be assigned to a parent Batch Folder in the Batch. Makes all Data Elements from the parent document available in the child document's expression environment. Use for multi-level Batch structures where parent-child Batch Folder relationships are required.
			** ''Example:'' A Benefits Change Form document configured as "Child Of" a Personnel File will have access to all Personnel File Data Model fields in its expressions — including using <code>Employee_Name</code> in its Export Mappings.
			* '''Sibling Of''' — Specifies one or more Content Types that are assigned alongside the same Batch Folder as Secondary Types. Makes the Data Elements of those sibling Content Types directly accessible in the expression environment using the syntax <code>TypeName.FieldName</code>.
			** Note: "Sibling" here refers to sibling Content Types assigned to the same Batch Folder — not sibling Batch Folders within a Batch. There is no automatic event linkage between fields on different types; if a user edits sibling data, fields depending on it will not automatically recalculate.
			* '''Relative Of''' — A more flexible option that defines related Content Types whose Data Elements are exposed in the expression environment, regardless of whether they are parent documents or Secondary Types. Use when the related Content Type could be either a parent or a sibling.

	== VLM Analyze ==		== VLM Analyze ==

Dgreenwood: /* Content Type Relationships */

2026-06-10T18:59:49Z

Content Type Relationships

@@ Line 678: / Line 678: @@
 * '''/nodes''' — Endpoints to manage nodes in the Grooper node tree. ''Provides low-level access to the Grooper Repository's tree structure. Use with caution.''
 * '''/commands''' — Endpoints to execute commands on Grooper nodes, including Batches, documents (Batch Folders), or other node types.
 == Improved Security ==

Dgreenwood: /* Miscellaneous */

2026-06-10T18:59:30Z

Miscellaneous

Show changes

Dgreenwood: /* VLM Analyze */

2026-06-10T18:50:24Z

VLM Analyze

← Older revision		Revision as of 13:50, 10 June 2026
Line 518:		Line 518:

	{{attn-box\|Spatial Grounding consumes significantly more tokens than AI Extract. Consider using a less expensive model to control costs.}}		{{attn-box\|Spatial Grounding consumes significantly more tokens than AI Extract. Consider using a less expensive model to control costs.}}

			== Route ==

			=== New Activity: Route ===

			The Route activity routes Batch Folders (or Batches) to new Batches based on their Content Type, enabling branching workflows based on initial classification.

			Routing rules are defined by '''Route Definitions''', each specifying:
			* A Content Type to match.
			* A destination Batch Process.
			* An optional Boolean trigger expression for conditional routing.

			Additional options:
			* Items can be moved or cloned into the target Batch. If no route matches, the item remains in its current Batch.
			* Routed Batches can be started in a paused state for review.
			* The '''Include Sibling Types''' option adds all sibling Content Types not already present in the Secondary Type list.
			* Data Actions can copy or transform Data Fields during routing to support scenarios where source and target Content Types have different Data Models.

			Batches have a new '''Pending To Step''' property that supports running Route at the Batch level. Since a new Batch Process cannot be applied while a step is running on the existing one, this property defers the process change: the next time the Batch is completed or resumed, the new process and current step are applied and the Pending To Step value is cleared.

			=== New Concept: Nested Batches (Experimental) ===

			Batches can now have other Batches as their children in specific circumstances. These child Batches are called '''nested Batches'''.

			* Currently, the only way to create a nested Batch is with the Route activity using a Route Definition with its Method set to '''Convert'''. This converts the document (Batch Folder) to a Batch and routes it to the target Batch Process. Currently, this only works at Folder Level 1 in the parent Batch.
			* The Batches Filter has a new '''Include Nested Batches''' option to show nested Batches in the Batch List.

			'''Use case:''' A ZIP file containing 1,000 documents is imported as a Batch. The unzipped documents are classified as Check, EOB, or Mail — each needing to route to a different Batch Process. Without nested Batches, routing separates documents from their parent, making it impossible to monitor the overall import progress or roll back to a previous step. With the Convert method, documents are converted to nested Batches and remain in place.

			{{attn-box\|Nested Batches are still in the experimental stages. More work is needed to ensure operational rules are in place to prevent unsafe Batch deletion and improper task processing.}}


	== VLM Analyze ==		== VLM Analyze ==

Dgreenwood: /* Route */

2026-06-10T18:50:08Z

Route

@@ Line 657: / Line 657: @@
 ** Note: "Sibling" here refers to sibling Content Types assigned to the same Batch Folder — not sibling Batch Folders within a Batch. There is no automatic event linkage between fields on different types; if a user edits sibling data, fields depending on it will not automatically recalculate.
 * '''Relative Of''' — A more flexible option that defines related Content Types whose Data Elements are exposed in the expression environment, regardless of whether they are parent documents or Secondary Types. Use when the related Content Type could be either a parent or a sibling.
 == Miscellaneous ==

Dgreenwood: /* = Large Document Search Indexing */

2026-06-10T18:44:12Z

= Large Document Search Indexing

← Older revision		Revision as of 13:44, 10 June 2026
Line 312:		Line 312:
	This enables more efficient use of Azure resources by allowing multiple environments or departments to share a single AI Search service.		This enables more efficient use of Azure resources by allowing multiple environments or departments to share a single AI Search service.

	==== Large Document Search Indexing ===		==== Large Document Search Indexing ====

	Large documents would occasionally fail during search indexing due to how embeddings values were collected. Several improvements have been made:		Large documents would occasionally fail during search indexing due to how embeddings values were collected. Several improvements have been made:

Dgreenwood: /* Search Indexing Improvements */

2026-06-10T18:44:01Z

Search Indexing Improvements

← Older revision		Revision as of 13:44, 10 June 2026
Line 288:		Line 288:
	* '''Remembered column widths''' — The Search page now remembers adjusted column widths in the results list, persisted in the user's browser cache across searches and page visits.		* '''Remembered column widths''' — The Search page now remembers adjusted column widths in the results list, persisted in the user's browser cache across searches and page visits.

	== Search Indexing Improvements ==		=== Search Indexing Improvements ===

	=== Indexes Tab ===		The following improvements were made to how documents are added to a search index and how search indexes are managed throughout version 2025's development.

			==== Indexes Tab ====

	A new '''Indexes''' tab has been added to the Grooper Root node in the Design page. It is visible when the Grooper Repository has an AI Search option enabled.		A new '''Indexes''' tab has been added to the Grooper Root node in the Design page. It is visible when the Grooper Repository has an AI Search option enabled.
Line 301:		Line 303:
	* If an Index Name Prefix is in use, toggle the view to see all indexes displayed with full names.		* If an Index Name Prefix is in use, toggle the view to see all indexes displayed with full names.

	=== Index Name Prefix ===		==== Index Name Prefix ====

	AI Search has a new '''Index Name Prefix''' property. This prevents name collisions when multiple Grooper repositories share a single AI Search service.		AI Search has a new '''Index Name Prefix''' property. This prevents name collisions when multiple Grooper repositories share a single AI Search service.
Line 310:		Line 312:
	This enables more efficient use of Azure resources by allowing multiple environments or departments to share a single AI Search service.		This enables more efficient use of Azure resources by allowing multiple environments or departments to share a single AI Search service.

	=== Large Document Search Indexing ===		==== Large Document Search Indexing ===

	Large documents would occasionally fail during search indexing due to how embeddings values were collected. Several improvements have been made:		Large documents would occasionally fail during search indexing due to how embeddings values were collected. Several improvements have been made:
Line 318:		Line 320:
	* Fixed additional internal issues.		* Fixed additional internal issues.

	=== Chunking Method ===		==== Chunking Method ====

	A new '''Chunking Method''' configuration is available under '''Vector Search Options''' in an Indexing Behavior. This controls how chunks are created when collecting vector embeddings from large documents.		A new '''Chunking Method''' configuration is available under '''Vector Search Options''' in an Indexing Behavior. This controls how chunks are created when collecting vector embeddings from large documents.

Dgreenwood: /* Search Page Improvements */

2026-06-10T18:42:46Z

Search Page Improvements

← Older revision		Revision as of 13:42, 10 June 2026
Line 235:		Line 235:
	* The previous '''Exchange OAuth''' method (a user login method requiring a Microsoft account) is still available and is fine for testing, but OAuth Service Login is preferred for production scenarios.		* The previous '''Exchange OAuth''' method (a user login method requiring a Microsoft account) is still available and is fine for testing, but OAuth Service Login is preferred for production scenarios.

	== ~~Search Page Improvements~~ ==		== Document indexing and search improvements ==

	=== Saved Queries ===		=== Search Page Improvements ===

			The following improvements were made to the [[Search Page]] user interface throughout version 2025's development.

			==== Saved Queries ====

	Search queries are now stored in a Grooper database table ("Query") instead of the user's browser cache. Saved searches persist across browsers and machines.		Search queries are now stored in a Grooper database table ("Query") instead of the user's browser cache. Saved searches persist across browsers and machines.
Line 247:		Line 251:
	* The panel can be collapsed to save screen space.		* The panel can be collapsed to save screen space.

	=== Search Parameter Editors ===		==== Search Parameter Editors ====

	Editors have been added for the '''Filter''', '''Select''', and '''Order By''' parameters, making it easier for users unfamiliar with the search syntax to configure these parameters. Look for the "more" icon at the end of each property.		Editors have been added for the '''Filter''', '''Select''', and '''Order By''' parameters, making it easier for users unfamiliar with the search syntax to configure these parameters. Look for the "more" icon at the end of each property.
Line 262:		Line 266:
	A '''Show All''' toggle in the Filter Editor reveals all fields in the search index, giving users a simple way to browse available fields and construct basic queries.		A '''Show All''' toggle in the Filter Editor reveals all fields in the search index, giving users a simple way to browse available fields and construct basic queries.

	=== AI Helper: Generate Filter ===		==== AI Helper: Generate Filter ====

	The Search page has a new '''AI Helper''' button for the Filter parameter. This replaces the previous AI Query Helper button and works significantly better — it focuses solely on generating a filter rather than building the whole query, and it injects more information including values for drop-down list fields.		The Search page has a new '''AI Helper''' button for the Filter parameter. This replaces the previous AI Query Helper button and works significantly better — it focuses solely on generating a filter rather than building the whole query, and it injects more information including values for drop-down list fields.

	=== Sort by Column Header ===		==== Sort by Column Header ====

	Users can now click a column header in the search results list to quickly sort results by that field.		Users can now click a column header in the search results list to quickly sort results by that field.

	=== Result Set Command Permissions ===		==== Result Set Command Permissions ====

	Result Set commands can now be secured using Permission Sets configurations, allowing administrators to control which users have access to specific commands on the Search page:		Result Set commands can now be secured using Permission Sets configurations, allowing administrators to control which users have access to specific commands on the Search page:
Line 279:		Line 283:
	* '''Download''' — Currently enabled for all users.		* '''Download''' — Currently enabled for all users.

	=== Miscellaneous Search Page Improvements ===		==== Miscellaneous Search Page Improvements ====

	* '''Case-insensitive string comparisons''' — String comparisons in Filters are now case-insensitive by default (the previous case-sensitive mode was difficult to use in practice). This is implemented by adding a lowercase normalizer for string fields. Requires API version 2025-09-01 or higher.		* '''Case-insensitive string comparisons''' — String comparisons in Filters are now case-insensitive by default (the previous case-sensitive mode was difficult to use in practice). This is implemented by adding a lowercase normalizer for string fields. Requires API version 2025-09-01 or higher.

Dgreenwood: /* Search Page Improvements */

2026-06-10T18:41:07Z

Search Page Improvements

@@ Line 202: / Line 202: @@
 ** '''List editors''' — Generate list entries.
 ** '''Instruction editors''' — Generate instructions for AI Extract.
 == Search Page Improvements ==