2023:Object Library (Node Type): Difference between revisions

From Grooper Wiki
No edit summary
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{stubs}}
{{stubs}}
<section begin="glossary" />
<blockquote>
An '''Object Library''' is a .NET framework library containing custom objects used to customize the way Grooper works. 
</blockquote>
<section end="glossary" />
'''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 ==
{{AutoVersion}}
 
<blockquote>{{#lst:Glossary|Object Library}}</blockquote>


=== Import and Compile an Object Library ===
'''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.
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.
{|class="attn-box"
{|class="attn-box"
Line 19: Line 16:
|}
|}


==== Import the Grooper ZIP ====
=== Import the Grooper ZIP ===
{|class="how-to-table"
{|class="how-to-table"
|-
|-
Line 49: Line 46:
|}
|}


==== Compile the Object Library ====
=== Compile the Object Library ===


{|class="how-to-table"
{|class="how-to-table"
Line 62: Line 59:
# Close and re-open Grooper Design Studio.
# 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.
#* 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.
{|class="attn-box"
|
&#9888;
|
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.
|}
|
|
[[File:2023 ObjectLibrary 02 02 Compile 01.png]]
[[File:2023 ObjectLibrary 02 02 Compile 01.png]]
|}
|}
[[Category:Articles]]
 
== 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.
 
# Download "MSBuild.zip" from https://grooper.bisok.com/Downloads/MSBuild/MSBuild.zip
# Extract the ZIP contents.
# Copy the "MSBuild" folder to the "Script Templates" folder in your Grooper install directory.
#* By default this location will be <code>C:\Program Files\BIS\Grooper\Script Templates</code>
# If Design Studio is open, close it and re-open it.  You should now be able to compile scripts.

Revision as of 09:02, 22 November 2024

STUB

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


This article is about an older version of Grooper.

Information may be out of date and UI elements may have changed.

20252023

extension Object Library nodes are .NET libraries that contain code files for customizing the Grooper's functionality. 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 code expressions on Data Field and Batch Process Step objects.
  • Creating custom Connection Types for CMIS Connections for import/export operations from/to CMS systems.
  • 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.

  1. 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.
  2. Select Share > Import ZIP Archive...

The "Import ZIP Archive" dialog will pop up.


  1. Using the Filename property, select the Grooper ZIP you wish to import.
  2. Press the "Execute" button when finished.


  1. If successful you will see a dialog noting the file was imported. Press "OK" to continue.
  2. 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.

  1. Select the Object Library you wish to compile.
  2. Navigate to the "Scripting" tab.
  3. Press the "Compile" button.
  4. Wait for the script to complete compiling. You will see a message in the "Output" window noting it compiled successfully (or failed).
  5. 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.