Object Library (Object)

⚠	This article was migrated from an older version and has not been updated for the current version of Grooper. This tag will be removed upon article review and update.

STUB	This article is a stub. It contains minimal information on the topic and should be expanded.

This article is about the current version of Grooper. Note that some content may still need to be updated.
2025	2023

extension Object Library node objects are .NET libraries that contain code files for customizing the functionality of Grooper. These libraries are used for a range of customization and integration tasks, allowing users to extend Grooper's capabilities.

Examples include:

• Adding custom Activities that execute within Batch Processes
• Creating custom commands available during the Review Activity and in the Design page.
• Defining custom methods that can be called from expressions on Data Field and Batch Process Step objects
• Establish custom Grooper Services that perform automated background tasks at regular intervals

Object Libraries are used to customize Grooper with scripting. They can be used to create a variety of new tools, including custom Activities, custom object commands, custom CMIS Connection types and more.

How To: Import and compile an Object Library

This tutorial is for users who are attempting to import an Object Library developed by BIS or another Grooper user into their own environment. This will explain how to upload an Object Library to a Project in your environment and compile it.

⚠	PLEASE NOTE: In version 2023, Object Libraries must be compiled in the Grooper Windows client (thick client), even if they are functional in the web client.

Import the Grooper ZIP

Copy the Grooper ZIP containing the Object Library to your Grooper server and Open Grooper Design Studio. Right click the Project where you want to import the Object Library. Note: If the Grooper ZIP is itself a Project that contains the Object Library, you will need to import from the Projects folder node. Select Share > Import ZIP Archive... The "Import ZIP Archive" dialog will pop up.
Using the Filename property, select the Grooper ZIP you wish to import. Press the "Execute" button when finished.
If successful you will see a dialog noting the file was imported. Press "OK" to continue. The Object Library will be imported to the selected Project.

Compile the Object Library

In order for the Object Library to work, its code must first be compiled. Select the Object Library you wish to compile. Navigate to the "Scripting" tab. Press the "Compile" button. Wait for the script to complete compiling. You will see a message in the "Output" window noting it compiled successfully (or failed). Close and re-open Grooper Design Studio. This is an important but sometimes overlooked step. You must close and re-open Grooper Design Studio in order to register the newly compiled DLLs. ⚠ If your Object Library is a custom Activity or a resource used by an Activity (such as a custom CMIS Connection type), you must also stop and start any running Activity Processing services. This will ensure the services register the newly compiled DLLs.

How To: Manually install the compile tool

In some cases the Grooper compile tool (MSBuild) does not install correctly, preventing users from compiling scripts (The "Compile" button will be greyed out). In this case, you can manually install the compile tool.

1. Download "MSBuild.zip" from https://grooper.bisok.com/Downloads/MSBuild/MSBuild.zip
2. Extract the ZIP contents.
3. Copy the "MSBuild" folder to the "Script Templates" folder in your Grooper install directory.
   • By default this location will be C:\Program Files\BIS\Grooper\Script Templates
4. If Design Studio is open, close it and re-open it. You should now be able to compile scripts.