Email Processing - Revision history

Rpatton: // via Wikitext Extension for VSCode

2026-02-19T22:49:05Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 17:49, 19 February 2026
Line 258:		Line 258:
	# Save your changes to the Data Field.		# Save your changes to the Data Field.
	# Repeat the process for all Data Fields.		# Repeat the process for all Data Fields.

			{\|class="fyi-box"
			\|-
			\|
			'''FYI'''
			\|
			Read Metadata has fewer metadata source fields to select than extracting metadata with an Import Behavior. Keep this in mind when deciding which method to use.
			\|}

	''' Configuring Extraction at Level 2 '''		''' Configuring Extraction at Level 2 '''
Line 278:		Line 286:
	# Enter in the following Calculated Value Expression:		# Enter in the following Calculated Value Expression:

	<code><Level 1 Document Type>.<Data Field ~~Name~~></code>		<code><Level 1 Document Type>.<Level 1 Data Field></code>

	So in our example, the expression would be:		So in our example, the expression would be:
Line 286:		Line 294:
	#<li value=7> Set the Calculate Mode property to AlwaysSet.		#<li value=7> Set the Calculate Mode property to AlwaysSet.
	# Test your extraction for both Data Models to make sure the correct information is extracted.		# Test your extraction for both Data Models to make sure the correct information is extracted.
	#* Note, that the Data Fields configured with the ~~abovementioned~~ Calculated Value will not appear during a test because nothing has actually been extracted from Level 1 yet for Grooper to copy to Level 2.		#* Note, that the Data Fields configured with the above mentioned Calculated Value will not appear during a test because nothing has actually been extracted from Level 1 yet for Grooper to copy to Level 2.

	<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmltkl0n002yuxg0if2zloxx9?embed_v=2&utm_source=embed" loading="lazy" title="12 Configuring Read Metadata for Email" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmltkl0n002yuxg0if2zloxx9?embed_v=2&utm_source=embed" loading="lazy" title="12 Configuring Read Metadata for Email" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>


	Once you have set up your model, you then need to set up your Batch Process to properly extract all the information.		Once you have set up your model, you then need to set up your Batch Process to properly extract all the information. The two different folders need to be classified differently, so we will need two Classify Batch Process Steps. Also, since we are extracting information from two different levels, we need two different Extract Batch Process Steps.

			A typical Batch Process for extracting emails might look something like:
			* Execute - Expand Attachments
			* Split Pages
			* Recognize
			* Classify
			* Extract
			* Export

			A Batch Process for obtaining metadata from the Level 1 Document Type and text data from the Level 2 Document Type might look like this instead:
			* Execute - Expand Attachments
			* Split Pages
			* Recognize
			* Classify Level 1
			* Classify Level 2
			* Extract Level 1
			* Extract Level 2
			* Export

			You might also have some Review steps in there to make sure your Batch Process is working as you expect it to.

			You also want to make sure your Export Batch Process Step is set to run at Folder Level 2 where your Export Behavior has been set.

	<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmltwabfd01yz5q0iriejzjd2?embed_v=2&utm_source=embed" loading="lazy" title="13 The Batch Process with Read Metadata" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmltwabfd01yz5q0iriejzjd2?embed_v=2&utm_source=embed" loading="lazy" title="13 The Batch Process with Read Metadata" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

Rpatton: // via Wikitext Extension for VSCode

2026-02-19T22:17:24Z

// via Wikitext Extension for VSCode

@@ Line 238: / Line 238: @@
 ==== Extracting metadata with the Read Metadata extractor ====
-(Work In Progress)
+We have discussed how to extract metadata from emails on import. You can also extract metadata from emails during the Extract Step in your Batch Process. It does take a little more time to set up and requires some understanding of folder levels and Content Model hierarchy, but it can at times be more reliable than the Import Behavior when extracting information from documents.
 === Changes to the Batch Process ===

Rpatton: // via Wikitext Extension for VSCode

2026-02-13T15:28:03Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 10:28, 13 February 2026
Line 210:		Line 210:
	Metadata is any information attached to a file or an email that does not necessarily include the text or image you see when you open the file/email. For a file on your computer, this might include the name of the file or the date the file was created. For an email it might include details such as the name and email address of the sender, the date received, or the subject line.		Metadata is any information attached to a file or an email that does not necessarily include the text or image you see when you open the file/email. For a file on your computer, this might include the name of the file or the date the file was created. For an email it might include details such as the name and email address of the sender, the date received, or the subject line.

	We can actually extract metadata from emails. There are two ways to do this. We can extract metadata upon import or we can ~~add~~ a Read Metadata ~~Batch Process Step to our Batch Process to process during extraction~~.		We can actually extract metadata from emails. There are two ways to do this. We can extract metadata upon import or we can configure the Data Field with a Read Metadata extractor that will populate the Field with metadata on extract.

	==== Extracting metadata on import ====		==== Extracting metadata on import ====
Line 236:		Line 236:
	<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljo9jpj006qzk0iwatxgim4?embed_v=2&utm_source=embed" loading="lazy" title="11 Extracting Metadata on Import" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljo9jpj006qzk0iwatxgim4?embed_v=2&utm_source=embed" loading="lazy" title="11 Extracting Metadata on Import" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	==== Extracting metadata with the Read Metadata ~~Batch Process Step~~ ====		==== Extracting metadata with the Read Metadata extractor ====

	(Work In Progress)		(Work In Progress)

Rpatton: // via Wikitext Extension for VSCode

2026-02-13T15:03:08Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 10:03, 13 February 2026
Line 216:		Line 216:
	To extract metadata on import, you first need to configure an [[Import Behavior]] on your [[Content Type]] and then configure the Read Mappings property on your Import Behavior. The Read Mappings property specifically allows you to read metadata from the import and assign it to populate a [[Data Field]] or other items such as the name of the document that's imported.		To extract metadata on import, you first need to configure an [[Import Behavior]] on your [[Content Type]] and then configure the Read Mappings property on your Import Behavior. The Read Mappings property specifically allows you to read metadata from the import and assign it to populate a [[Data Field]] or other items such as the name of the document that's imported.

			'''Configuring your Import Behavior'''
	# On your Content Type, typically the [[Content Model]], locate the Behaviors property and open the editor by clicking the "..." icon.		# On your Content Type, typically the [[Content Model]], locate the Behaviors property and open the editor by clicking the "..." icon.
	# In the editor, click the "+" icon and select "Import Behavior" from the drop down.		# In the editor, click the "+" icon and select "Import Behavior" from the drop down.
	# Click the "..." to the right of the [[Import Definition]] property.		# Click the "..." to the right of the Import Definition property.
	# Click the "+" icon to add a new Import Definition. Select "CMIS Import".		# Click the "+" icon to add a new Import Definition. Select "CMIS Import".
	# Click the "☰" to the right of the CMIS Repository property. Navigate to and select the email repository you want to import from.		# Click the "☰" to the right of the CMIS Repository property. Navigate to and select the email repository you want to import from.

Rpatton: // via Wikitext Extension for VSCode

2026-02-13T15:00:55Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 10:00, 13 February 2026
Line 235:		Line 235:
	<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljo9jpj006qzk0iwatxgim4?embed_v=2&utm_source=embed" loading="lazy" title="11 Extracting Metadata on Import" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljo9jpj006qzk0iwatxgim4?embed_v=2&utm_source=embed" loading="lazy" title="11 Extracting Metadata on Import" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	=== Extracting metadata with the Read Metadata Batch Process Step ===		==== Extracting metadata with the Read Metadata Batch Process Step ====

	(Work In Progress)		(Work In Progress)

Rpatton: // via Wikitext Extension for VSCode

2026-02-13T14:59:29Z

// via Wikitext Extension for VSCode

@@ Line 106: / Line 106: @@
 <div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljl2vk40001070i66qal5wd?embed_v=2&utm_source=embed" loading="lazy" title="13 User Directed Email Import (Part 1)(Copy)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
 <div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljl3j2m0003zw0ils1glmb1?embed_v=2&utm_source=embed" loading="lazy" title="14 User Directed Email Import (Part 2)(Copy)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
@@ Line 121: / Line 120: @@
 <div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljljj770033zz0ixpyuoheb?embed_v=2&utm_source=embed" loading="lazy" title="13 Scheduled Import for Emails (Part 1)(Copy)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
 <div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljlk3m90002zk0ixefm68xy?embed_v=2&utm_source=embed" loading="lazy" title="05 Scheduled Import for Emails (Part 2)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
@@ Line 207: / Line 205: @@
 <div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmad0nc6q006xxb0jdgiv4m38?embed_v=2&utm_source=embed" loading="lazy" title="09 Adding Render to the Batch Process" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
 === Changes to the Batch Process ===

Rpatton: // via Wikitext Extension for VSCode

2026-02-12T15:24:47Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 10:24, 12 February 2026
Line 91:		Line 91:
	#* The CMIS Repository is needed to configure the import provider used to import emails into Grooper.		#* The CMIS Repository is needed to configure the import provider used to import emails into Grooper.

	[https://app.supademo.com/~~demo~~/~~cm9u1jv00069myt0i8w0c9f5i Click here for an interactive walkthrough]~~		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljkzgxm001axy0ipdubtkck?embed_v=2&utm_source=embed" loading="lazy" title="12 The Exchange CMIS Connection(Copy)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	==== User-directed (ad-hoc) email imports ====		==== User-directed (ad-hoc) email imports ====
Line 105:		Line 105:
	For an interactive walkthrough of a user-directed email import, click the links below.		For an interactive walkthrough of a user-directed email import, click the links below.

	[https://app.supademo.com/~~demo~~/~~cm9vg5la305mfyt0ie1u938f2~~ User-Directed Email ~~Imports~~ (Part 1)]		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljl2vk40001070i66qal5wd?embed_v=2&utm_source=embed" loading="lazy" title="13 User Directed Email Import (Part 1)(Copy)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
	<br>[https://app.supademo.com/~~demo~~/~~cm9vk4sfy01bpy60iyj4u7ell~~ User-Directed Email ~~Imports~~ (Part 2)]

			<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljl3j2m0003zw0ils1glmb1?embed_v=2&utm_source=embed" loading="lazy" title="14 User Directed Email Import (Part 2)(Copy)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	==== Automated (scheduled) email imports ====		==== Automated (scheduled) email imports ====
Line 118:		Line 120:
	For an interactive walkthrough of an automated Specific Times email import, click the links below.		For an interactive walkthrough of an automated Specific Times email import, click the links below.

	[https://app.supademo.com/~~demo~~/~~cm972zs2e002z0d0irrv21k3q~~ Scheduled ~~Email Imports~~ (Part 1)]		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljljj770033zz0ixpyuoheb?embed_v=2&utm_source=embed" loading="lazy" title="13 Scheduled Import for Emails (Part 1)(Copy)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
	<br>[https://app.supademo.com/~~demo~~/~~cm977xnwd01tqv20imvqygxcl~~ Scheduled ~~Email Imports~~ (Part 2)]

			<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljlk3m90002zk0ixefm68xy?embed_v=2&utm_source=embed" loading="lazy" title="05 Scheduled Import for Emails (Part 2)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	=== Attachment considerations ===		=== Attachment considerations ===
Line 136:		Line 140:
	#* The Execute Step should come before any processing is performed on documents such as Split Pages or Recognize.		#* The Execute Step should come before any processing is performed on documents such as Split Pages or Recognize.

	[https://app.supademo.com/~~demo~~/~~cm9vtuqqo032ny60ivn6t7uew Click here for an interactive walkthrough]~~		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmljlpjr6003azw0i3ug7gdac?embed_v=2&utm_source=embed" loading="lazy" title="06 Expanding Email Attachments" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	=== Body considerations ===		=== Body considerations ===
Line 163:		Line 167:
	\|}		\|}

	[https://app.supademo.com/~~demo~~/cma48po4801yt130iqooplqo3 ~~Click here for an interactive walkthrough]~~		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cma48po4801yt130iqooplqo3?embed_v=2&utm_source=embed" loading="lazy" title="07 Expanding Out the Email Body" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	==== Rendering the Email Body ====		==== Rendering the Email Body ====
Line 185:		Line 189:
	# To see the rendered PDF, click on the "Renditions" icon in the top right corner of the Document Viewer and select "PDF".		# To see the rendered PDF, click on the "Renditions" icon in the top right corner of the Document Viewer and select "PDF".

	[https://app.supademo.com/~~demo~~/cmacy8zyt00v6wk0i70e8jmh7 ~~Click here for an interactive walkthrough]~~		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmacy8zyt00v6wk0i70e8jmh7?embed_v=2&utm_source=embed" loading="lazy" title="08 Rendering the Email Body" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	==== Adding a Render Batch Process Step ====		==== Adding a Render Batch Process Step ====
Line 202:		Line 206:
	# Finally, move your Render Batch Process Step to the top of your Batch Process right under the Execute Step configured to expand the body of the email.		# Finally, move your Render Batch Process Step to the top of your Batch Process right under the Execute Step configured to expand the body of the email.

	[https://app.supademo.com/~~demo~~/cmad0nc6q006xxb0jdgiv4m38 ~~Click here for an interactive walkthrough]~~		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmad0nc6q006xxb0jdgiv4m38?embed_v=2&utm_source=embed" loading="lazy" title="09 Adding Render to the Batch Process" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	=== Changes to the Batch Process ===		=== Changes to the Batch Process ===
Line 210:		Line 214:
	For example, the Split Pages Batch Process Step by default is set to a Folder Level of 1. However, after expanding out attachments, are documents will be located at Folder Level 2. We would need to adjust our Batch Process Step Scope to split the pages at the appropriate folder level.		For example, the Split Pages Batch Process Step by default is set to a Folder Level of 1. However, after expanding out attachments, are documents will be located at Folder Level 2. We would need to adjust our Batch Process Step Scope to split the pages at the appropriate folder level.

	[https://app.supademo.com/~~demo~~/cmae00v8n03hu2l0jjfru20fx ~~Click here for an interactive walkthrough]~~		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.78; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cmae00v8n03hu2l0jjfru20fx?embed_v=2&utm_source=embed" loading="lazy" title="10 Changes to the Batch Process" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

Rpatton: /* Expanding the Body of the Email */

2025-05-23T12:59:17Z

Expanding the Body of the Email

← Older revision		Revision as of 07:59, 23 May 2025
Line 148:		Line 148:
	# In the Command sub properties, set the Body Expansion property to one of the following three options:		# In the Command sub properties, set the Body Expansion property to one of the following three options:
	#* ''Prefer_Text'' - The body will be expanded as plain text if available. If not, it will expand as an HTML.		#* ''Prefer_Text'' - The body will be expanded as plain text if available. If not, it will expand as an HTML.
	#* ''Prefer_HTML'' - The body will be expanded as HTML if available. If not, it will expand as ~~an HTML~~.		#* ''Prefer_HTML'' - The body will be expanded as HTML if available. If not, it will expand as plain text.
	#* ''Text_HTML'' - The body will be expanded as plain text if available. If not, the HTML of the body will be written out as text.		#* ''Text_HTML'' - The body will be expanded as plain text if available. If not, the HTML of the body will be written out as text.
	# Assign the correct Scope to the Batch Process Step.		# Assign the correct Scope to the Batch Process Step.

Rpatton: // via Wikitext Extension for VSCode

2025-05-07T16:00:22Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 11:00, 7 May 2025
Line 106:		Line 106:

	[https://app.supademo.com/demo/cm9vg5la305mfyt0ie1u938f2 User-Directed Email Imports (Part 1)]		[https://app.supademo.com/demo/cm9vg5la305mfyt0ie1u938f2 User-Directed Email Imports (Part 1)]
	[https://app.supademo.com/demo/cm9vk4sfy01bpy60iyj4u7ell User-Directed Email Imports (Part 2)]		<br>[https://app.supademo.com/demo/cm9vk4sfy01bpy60iyj4u7ell User-Directed Email Imports (Part 2)]

	==== Automated (scheduled) email imports ====		==== Automated (scheduled) email imports ====
Line 119:		Line 119:

	[https://app.supademo.com/demo/cm972zs2e002z0d0irrv21k3q Scheduled Email Imports (Part 1)]		[https://app.supademo.com/demo/cm972zs2e002z0d0irrv21k3q Scheduled Email Imports (Part 1)]
	[https://app.supademo.com/demo/cm977xnwd01tqv20imvqygxcl Scheduled Email Imports (Part 2)]		<br>[https://app.supademo.com/demo/cm977xnwd01tqv20imvqygxcl Scheduled Email Imports (Part 2)]

	=== Attachment considerations ===		=== Attachment considerations ===

Rpatton: // via Wikitext Extension for VSCode

2025-05-07T15:58:50Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 10:58, 7 May 2025
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}

	~~{{WIP}}~~		<blockquote>Grooper is capable of processing documents imported from email. Both email attachments and the email body itself can be processed just like any other imported document in Grooper, but there are a few differences in processing.</blockquote>

	~~<blockquote>~~Grooper ~~is capable~~ of ~~processing~~ documents ~~imported from email~~. ~~Both email attachments and the email body itself can be processed just like any other imported document~~ in ~~Grooper, but there are a few differences in processing~~.~~</blockquote>~~		{\|class="download-box"
			\|
			[[File:Asset 22@4x.png]]
			\|
			You may download the ZIP(s) below and upload it into your own Grooper environment (version 2025). The first contains one or more '''Batches''' of sample documents. The second contains one or more '''Projects''' with resources used in examples throughout this article.
			* [[Media:2025 Wiki Email-Processing Batch.zip]]
			* [[Media:2025 Wiki Email-Processing Project.zip]]
			\|}

	==About==		==About==
Line 13:		Line 20:
	# '''Attachment considerations''' - Does the email have attachments that need to be processed?		# '''Attachment considerations''' - Does the email have attachments that need to be processed?
	# '''Body considerations''' - Do you want to process the email body? If so, do you need to just process the body's text? Do you need to process the rendered HTML seen in an email client? Does the email have any images you need to process?		# '''Body considerations''' - Do you want to process the email body? If so, do you need to just process the body's text? Do you need to process the rendered HTML seen in an email client? Does the email have any images you need to process?
	# '''~~Conditioning considerations~~''' - Based on your answers to questions 2 and 3, the Batch Process will need to be adjusted to accommodate the scenario.		# '''Changes to the Batch Process''' - Based on your answers to questions 2 and 3, the Batch Process will need to be adjusted to accommodate the scenario.

	==How To==		==How To==

	In the following sections you will learn the differences ~~between~~ importing and processing emails rather than importing documents ~~directly from an outside repository~~ such as ~~through~~ an NTFS ~~connection~~.		In the following sections you will learn the differences in importing and processing emails rather than importing documents through a different connection such as an NTFS.

	=== Import considerations ===		=== Import considerations ===
Line 197:		Line 204:
	[https://app.supademo.com/demo/cmad0nc6q006xxb0jdgiv4m38 Click here for an interactive walkthrough]		[https://app.supademo.com/demo/cmad0nc6q006xxb0jdgiv4m38 Click here for an interactive walkthrough]

	=== ~~Conditioning considerations~~ ===		=== Changes to the Batch Process ===

			Now that we have our attachments or body of our emails expanded, we can go ahead and process them through Grooper. However, the act of expanding out the attachments or email body has changed what folder level contains the document we want to process. We need to make sure all Batch Process Steps following the email expansion steps are configured at the correct Folder Level.

			For example, the Split Pages Batch Process Step by default is set to a Folder Level of 1. However, after expanding out attachments, are documents will be located at Folder Level 2. We would need to adjust our Batch Process Step Scope to split the pages at the appropriate folder level.

			[https://app.supademo.com/demo/cmae00v8n03hu2l0jjfru20fx Click here for an interactive walkthrough]