Introduction to Custom Tasks

Process Director supports the ability to package unique business logic in Custom Tasks that can be mapped to Form events (e.g., buttons) and can be used in Process Timelines as Activities. This enables custom logic to be developed once with the scripting interfaces and re-used across many Form and Process Timeline definitions without any additional scripting.

Download the latest Custom Tasks here.

Documentation Example #

Adding a Custom Task to a Form Definition

Adding a Custom Task to a Process Timeline Definition

Using T-SQL with Custom Tasks

Several Custom Task types, such as the Database Connector Custom Tasks, allow you to use T-SQL to pass SQL statements directly to the Process Director database. Process Director implements some custom methods for using system variables in SQL statements, such as

• Encode types for Strings ($), numbers (#), and string handling for use in LIKE clauses (~).
• Pre, Post, and Null text operators for System Variables
• Pattern, Replace, and Trim for use with Regular Expressions

All of these items are documented in the System Variables Guide at the topics linked above in the list.

Custom Task Types #

All Custom Tasks should be located in the [Custom Tasks] folder, which is located at the root level of the partition(s) for your Process Director installation. In side the folder are a series of subfolders, each of which stores a specific category of Custom Tasks. You can navigate to each category of Custom Task by using the Table of Contents displayed in the upper right corner of the page, or clicking one of the links below.

Active Directory: Used for accessing data from Microsoft Active Directory.

Case: Used to manipulate Case definitions/instances.

Content Actions: Used to manipulate Content List objects.

Database Connectors: Used to access and manipulate data in external data stores.

Documents: Used to manipulate document attachments.

Form: Used to access and manipulate Form instances.

Form Data Mapping: Used to get or set data contained in Form instances.

IoT: Used to access data from remote "Internet of Things" (IoT) devices. Primarily intended for use with Machine Learning/AI operations.

Meta Data: Used to get or set Meta Data categories and attributes for object instances.

MS Dynamics: Used to access data from Microsoft Dynamics.

PDF: Used to perform PDF transform and conversion operations.

Process: Used to manipulate process instances.

User: Used to import or provision Process Director users without manually performing tasks via the IT Admin area.

Web Services: Used to access or post data via Web Services.

SharePoint: Used to access data from Microsoft SharePoint.

MS Dynamics: Used to access data from Microsoft Dynamics.