Expressions Cookbook - Revision history

Dgreenwood: /* Misc Expression Snippets */

2026-04-10T14:39:14Z

Misc Expression Snippets

← Older revision		Revision as of 09:39, 10 April 2026
Line 212:		Line 212:
	* <code>ParentFolder.ChildrenAtLevel(1).Count</code>		* <code>ParentFolder.ChildrenAtLevel(1).Count</code>
	**<li class="fyi-bullet"> Works for Default Value expressions but '''not''' Calculated Value expressions. Calculated Value expressions do not have access to <code>ChildrenAtLevel()</code> or <code>ParentFolder</code>		**<li class="fyi-bullet"> Works for Default Value expressions but '''not''' Calculated Value expressions. Calculated Value expressions do not have access to <code>ChildrenAtLevel()</code> or <code>ParentFolder</code>

			String expression to calculate a file name based on the current attachment's name.
			* Scenario: Merge/Export is generating a PDF from an HTML file. User wants the PDF to be named after the source file with ".html" replaced with ".pdf"
			* <code>$"{CurrentDocument.AttachmentFileName.Replace(CurrentDocument.AttachmentFileExtension, "")}.pdf"</code>

	== General ==		== General ==

2026-02-27T14:05:44Z

Misc Expression Snippets

← Older revision		Revision as of 09:05, 27 February 2026
Line 207:		Line 207:
	Count the number of children at a certain level. This would count the number of Batch Folders that are direct children of a Batch Folder being processed.		Count the number of children at a certain level. This would count the number of Batch Folders that are direct children of a Batch Folder being processed.
	* <code>ChildrenAtLevel(1).Count</code>		* <code>ChildrenAtLevel(1).Count</code>
			**<li class="fyi-bullet"> Works for Default Value expressions but '''not''' Calculated Value expressions. Calculated Value expressions do not have access to <code>ChildrenAtLevel()</code>

	Count the number of children at a certain level of a ''parent folder''. This would count the number of Batch Folders that are direct children of the ''parent'' Batch Folder relative to the Batch Folder being processed.		Count the number of children at a certain level of a ''parent folder''. This would count the number of Batch Folders that are direct children of the ''parent'' Batch Folder relative to the Batch Folder being processed.
	* <code>ParentFolder.ChildrenAtLevel(1).Count</code>		* <code>ParentFolder.ChildrenAtLevel(1).Count</code>
			**<li class="fyi-bullet"> Works for Default Value expressions but '''not''' Calculated Value expressions. Calculated Value expressions do not have access to <code>ChildrenAtLevel()</code> or <code>ParentFolder</code>

	== General ==		== General ==

2026-02-24T15:26:57Z

Accessing field values in Next Step Expressions

← Older revision		Revision as of 10:26, 24 February 2026
Line 118:		Line 118:

	==== Accessing field values in Next Step Expressions ====		==== Accessing field values in Next Step Expressions ====
	If the Batch Process has its Content Type property set, the data for this Content Type is exposed in a property named ~~“Data”~~.		If the Batch Process has its Content Type property set, the data for this Content Type is exposed in a property named <code>Data</code>.
	* Example expression: <code>If(Data.InvoiceAmount > 5000, ReviewL2, ReviewL1)</code>		* Example expression: <code>If(Data.InvoiceAmount > 5000, ReviewL2, ReviewL1)</code>
	* If this were set on an Extract step, ~~each document whose~~ InvoiceAmount value is greater than 5000 would be sent to a Review step named "ReviewL2". Otherwise, it would be sent to a Review step named "ReviewL1"		* If this were set on an Extract step, and the Batch had an "InvoiceAmount" value is greater than 5000 would be sent to a Review step named "ReviewL2". Otherwise, it would be sent to a Review step named "ReviewL1"
			**<li class="attn-bullet"> Be aware the <code>Data</code> property can only access '''Batch''' fields. It cannot access child Batch Folder data.

	== IP Profile Expressions ==		== IP Profile Expressions ==

2026-02-24T14:41:08Z

Batch Processing Expressions

← Older revision		Revision as of 09:41, 24 February 2026
Line 116:		Line 116:
	* <code>If(DatePart(DateInterval.Month, Batch.Created) = 6, TrueStepName, FalseStepName)</code>		* <code>If(DatePart(DateInterval.Month, Batch.Created) = 6, TrueStepName, FalseStepName)</code>
	* <code>If(DatePart(DateInterval.Day, Batch.Created) > 15, TrueStepName, FalseStepName)</code>		* <code>If(DatePart(DateInterval.Day, Batch.Created) > 15, TrueStepName, FalseStepName)</code>

			==== Accessing field values in Next Step Expressions ====
			If the Batch Process has its Content Type property set, the data for this Content Type is exposed in a property named “Data”.
			* Example expression: <code>If(Data.InvoiceAmount > 5000, ReviewL2, ReviewL1)</code>
			* If this were set on an Extract step, each document whose InvoiceAmount value is greater than 5000 would be sent to a Review step named "ReviewL2". Otherwise, it would be sent to a Review step named "ReviewL1"

	== IP Profile Expressions ==		== IP Profile Expressions ==

2026-01-27T17:32:03Z

Dgreenwood moved page Expressions Cookbook (Concept) to Expressions Cookbook without leaving a redirect

← Older revision	Revision as of 12:32, 27 January 2026
(No difference)

2026-01-27T17:28:38Z

@@ Line 3: / Line 3: @@
 Expressions are snippets of .NET code, allowing Grooper to do various things outside its "normal" parameters.  This includes calculating or validating extracted '''Data Field''' values in a '''Data Model''', applying conditional execution of a '''Batch Process''' or '''IP Profile''', and more!  This article collects examples of common (and maybe not so common) uses of expressions in Grooper.
 {|class="important-box"
+|

2025-10-15T13:57:23Z

Should Submit Expression

← Older revision		Revision as of 08:57, 15 October 2025
Line 70:		Line 70:
	** <code>Item.Flagged</code>		** <code>Item.Flagged</code>
	** <code>Not Item.Flagged</code>		** <code>Not Item.Flagged</code>
			**<li class="attn-bullet"> BE AWARE: You cannot use these expressions or others that inspect flag status if the Batch Process Step's "Error Dispossition" (found in the Activity's properties) has the "Flag" disposition enabled. Doing so will clear the flag from the previous step before the Should Submit Expression evaluates (rendering the expression useless).
	* This example would submit the task when the object (folder) contains one or more flagged pages		* This example would submit the task when the object (folder) contains one or more flagged pages
	** <code>DirectCast(Item, BatchFolder).FlaggedPages.Any()</code>		** <code>DirectCast(Item, BatchFolder).FlaggedPages.Any()</code>

2025-10-10T18:38:26Z

Calculated Value Expressions

← Older revision		Revision as of 13:38, 10 October 2025
Line 59:		Line 59:
	=== Calculated Value Expressions ===		=== Calculated Value Expressions ===
	{{#lst:Data Model Expressions\|calculated value cookbook}}		{{#lst:Data Model Expressions\|calculated value cookbook}}
			=== Is Valid Expressions ===
			{{#lst:Data Model Expressions\|is valid cookbook}}

	== Batch Processing Expressions ==		== Batch Processing Expressions ==

2025-10-09T16:45:13Z

Data Model Expressions

@@ Line 55: / Line 55: @@
 == Data Model Expressions ==
 {{#lst:Data Model Expressions|default value cookbook}}
 === Calculated Value Expressions ===
+{{#lst:Data Model Expressions|calculated value cookbook}}
 == Batch Processing Expressions ==

2025-10-08T21:35:01Z

Data Model Expressions

@@ Line 55: / Line 55: @@
 == Data Model Expressions ==
+{{#lst:Data Model Expressions|default value cookbook}}
 === Calculated Value Expressions ===