2024:Render (Activity) - Revision history

Dgreenwood: /* Set up Render Printer for multiple users and service accounts */

2025-05-01T15:48:10Z

Set up Render Printer for multiple users and service accounts

Dgreenwood: /* Set up Render Printer for multiple users and service accounts */

2025-05-01T15:16:42Z

Set up Render Printer for multiple users and service accounts

← Older revision		Revision as of 10:16, 1 May 2025
Line 180:		Line 180:
	#* Open the "Printers & Scanners" settings in Windows. Select the Grooper Render Printer. If it is not already listed as "Default", select "Manage". Then, select "Set as default".		#* Open the "Printers & Scanners" settings in Windows. Select the Grooper Render Printer. If it is not already listed as "Default", select "Manage". Then, select "Set as default".
	# Go to the local user/account's "Documents" folder in Windows File Explorer.		# Go to the local user/account's "Documents" folder in Windows File Explorer.
	#* <code>C:\Users\<loggedInUser>\~~Documents~~\</code>		#* <code>C:\Users\<loggedInUser>\AppData\Local\</code>
	# Create a folder named <code>GrooperRender</code>		# Create a folder named <code>GrooperRender</code>
	# Next, you will need to edit the environment variables for the logged in user ('''''not''''' the system variables).		# Next, you will need to edit the environment variables for the logged in user ('''''not''''' the system variables).

Dgreenwood: /* How To */

2025-04-30T21:15:33Z

How To

← Older revision		Revision as of 16:15, 30 April 2025
Line 53:		Line 53:

	== How To ==		== How To ==
	In order to run the Render activity, ~~there are~~ two ~~prerequisite~~ components:		In order to run the Render activity, two perquisite components must be in place:
	# The Grooper Render Printer must be installed		# The Grooper Render Printer must be installed
	# A special '''Processing Queue''' must be created for the Render activity and a dedicated '''Activity Processing''' service must run it.		# A special '''Processing Queue''' must be created for the Render activity and a dedicated '''Activity Processing''' service must run it.

Dgreenwood: /* About */

2025-04-30T21:11:48Z

About

← Older revision		Revision as of 16:11, 30 April 2025
Line 24:		Line 24:
	# The Grooper Render Printer must be set as the default printer under for the user account running the Render activity.		# The Grooper Render Printer must be set as the default printer under for the user account running the Render activity.
	# The native application for the file type must be installed on the machine running the Render activity. For example, Word must be installed in order for Render to render .docx files as PDFs.		# The native application for the file type must be installed on the machine running the Render activity. For example, Word must be installed in order for Render to render .docx files as PDFs.
	# The native application must provide a shell print verb~~. In other words, when you right click the file in Windows File Explorer, a "Print" option is present~~.		# The native application must provide a [https://learn.microsoft.com/en-us/windows/win32/shell/fa-verbs shell print verb].

	Once the document is processed with the '''Render''' activity, you will be able to manipulate the document as if it is a PDF document in Grooper. You will be able to use other PDF related activities, such as '''[[Split Pages]]''' to split out individual pages of multi-page PDFs and the native PDF text extraction functionality of the '''[[Recognize]]''' activity.		Once the document is processed with the '''Render''' activity, you will be able to manipulate the document as if it is a PDF document in Grooper. You will be able to use other PDF related activities, such as '''[[Split Pages]]''' to split out individual pages of multi-page PDFs and the native PDF text extraction functionality of the '''[[Recognize]]''' activity.

Dgreenwood: /* How To */

2025-04-30T20:55:09Z

How To

← Older revision		Revision as of 15:55, 30 April 2025
Line 53:		Line 53:

	== How To ==		== How To ==
	~~There~~ are ~~several~~ components ~~to consider~~ for ~~configuration of~~ the '''~~Render~~''' ~~activity~~.		In order to run the Render activity, there are two prerequisite components:
			# The Grooper Render Printer must be installed
			# A special '''Processing Queue''' must be created for the Render activity and a dedicated '''Activity Processing''' service must run it.

	=== Install the Grooper Render Printer ===		=== Install the Grooper Render Printer ===

			The Grooper Render Printer is the application that digitally "prints" the file to a PDF format Grooper can use. It must be:
			* Installed on the Grooper web server or a processing server (wherever the '''Activity Processing''' service processing Render tasks will be installed).
			* Set as the default printer.

	==== 1. Download the Grooper Render Printer installer ====		==== 1. Download the Grooper Render Printer installer ====

Dgreenwood: Dgreenwood moved page Render (Activity) to 2024:Render (Activity)

2025-02-28T22:47:09Z

Dgreenwood moved page Render (Activity) to 2024:Render (Activity)

← Older revision	Revision as of 17:47, 28 February 2025
(No difference)

Randallkinard at 15:14, 22 November 2024

2024-11-22T15:14:23Z

← Older revision		Revision as of 10:14, 22 November 2024
Line 185:		Line 185:
	# Click "OK" in the "New User Variables" window.		# Click "OK" in the "New User Variables" window.
	# You should see the new variable added to the "User variables for <loggedInUser>" list. Click "OK" to finish.		# You should see the new variable added to the "User variables for <loggedInUser>" list. Click "OK" to finish.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Randallkinard at 23:10, 19 November 2024

2024-11-19T23:10:16Z

← Older revision		Revision as of 18:10, 19 November 2024
Line 12:		Line 12:
	[[File:Asset 22@4x.png]]		[[File:Asset 22@4x.png]]
	\|		\|
	You may download and import the file(s) below into your own Grooper environment (version ~~2023~~). There is a '''Batch''' with the example document(s) discussed in this tutorial.		You may download and import the file(s) below into your own Grooper environment (version 2024). There is a '''Batch''' with the example document(s) discussed in this tutorial.
	<br>		<br>
	Please upload the '''Project''' to your '''Grooper''' environment before uploading the '''Batch'''. This will allow the documents within the '''Batch''' to maintain their classification status.		Please upload the '''Project''' to your '''Grooper''' environment before uploading the '''Batch'''. This will allow the documents within the '''Batch''' to maintain their classification status.

Randallkinard: 2024 updates // via Wikitext Extension for VSCode

2024-11-15T19:57:31Z

2024 updates // via Wikitext Extension for VSCode

Show changes

Randallkinard at 16:53, 28 August 2024

2024-08-28T16:53:22Z

← Older revision		Revision as of 11:53, 28 August 2024
Line 1:		Line 1:
	{{~~Migrated2023~~}}		{{Migrated}}
	{{2023:{{PAGENAME}}}}		{{2023:{{PAGENAME}}}}

← Older revision		Revision as of 10:14, 22 November 2024
Line 185:		Line 185:
	# Click "OK" in the "New User Variables" window.		# Click "OK" in the "New User Variables" window.
	# You should see the new variable added to the "User variables for <loggedInUser>" list. Click "OK" to finish.		# You should see the new variable added to the "User variables for <loggedInUser>" list. Click "OK" to finish.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

← Older revision		Revision as of 10:48, 1 May 2025
Line 179:		Line 179:
	# Ensure the Grooper Render Printer is the default printer.		# Ensure the Grooper Render Printer is the default printer.
	#* Open the "Printers & Scanners" settings in Windows. Select the Grooper Render Printer. If it is not already listed as "Default", select "Manage". Then, select "Set as default".		#* Open the "Printers & Scanners" settings in Windows. Select the Grooper Render Printer. If it is not already listed as "Default", select "Manage". Then, select "Set as default".
	# Go to the local user/account's "~~Documents~~" folder in Windows File Explorer.		# Go to the local user/account's "AppData\Local" folder in Windows File Explorer.
	#* <code>C:\Users\<loggedInUser>\AppData\Local\</code>		#* <code>C:\Users\<loggedInUser>\AppData\Local\</code>
			#* Note: This folder is hidden by default.
	# Create a folder named <code>GrooperRender</code>		# Create a folder named <code>GrooperRender</code>
	# Next, you will need to edit the environment variables for the logged in user ('''''not''''' the system variables).		# Next, you will need to edit the environment variables for the logged in user ('''''not''''' the system variables).
Line 188:		Line 189:
	# For the "Variable Name:" enter <code>GROOPER_RENDERPATH</code>		# For the "Variable Name:" enter <code>GROOPER_RENDERPATH</code>
	# For the "Variable Value:" enter the path for the folder created in Step 3.		# For the "Variable Value:" enter the path for the folder created in Step 3.
	#* <code>C:\Users\<loggedInUser>\~~Documents~~\GrooperRender</code>		#* <code>C:\Users\<loggedInUser>\AppData\Local\GrooperRender</code>
	# Click "OK" in the "New User Variables" window.		# Click "OK" in the "New User Variables" window.
	# You should see the new variable added to the "User variables for <loggedInUser>" list. Click "OK" to finish.		# You should see the new variable added to the "User variables for <loggedInUser>" list. Click "OK" to finish.