Extending Request Workflows

This chapter describes how to extend request workflows with custom routines.

Prerequisites

We assume that you are familiar with Java and with building Java projects and that Ant and a Java compiler are installed and in your path.

Documentation

To understand this issue, we recommend reading these chapters:

DirX Identity Application Development Guide

Understanding the Default Application Workflow Technology > Understanding Request Workflows

Read the entire chapter, especially these sections:

Request Workflow Architecture - provides all information for understanding request workflow features and architecture.

Customizing Request Workflows - explains in detail how to customize request workflows. Here you can find these sections:

Using Variable Substitution - explains how to set variable text sections in mail texts that are replaced during runtime.

Implementing an Activity - describes how to implement and deploy a job for a custom activity. It especially expands on how to read configuration data and workflow objects.

Implementing a Java Class for Finding Participants - describes how to implement your custom algorithm for finding participants.

Implementing Participant Filters and Constraints - shows how you can filter participants and how to implement rules and constraints on participants.

Interfaces

This chapter provides information about the interfaces you can use.

For the API documentation, consult the following folder on your DVD:

Documentation\DirXIdentity\RequestWorkflows\index.html

Training

View the webinar that explain this topic:

Request Workflows

Note: you can download webinars from our support portal. If you do not have access to the support portal, contact your responsible support organization.

Examples

For sample sources, see the following folder on your DVD:

Additions\RequestWorkflows\samples.

Hints, Tips and Tricks

If you need to read or write in the DirX Identity domain, you can obtain an LDAP connection from the Java server.

For participants finder, constraint and filter, see the *Extended interfaces. They provide a context, which provides a getter for the connection.

If you implement an activity, your job class should extend a provided Abstract Job. This also provides the LDAP connection through a getter method. See the corresponding chapter in the DirX Identity Application Development Guide and the sample.

There is no environment outside of IdS-J for running and testing jobs of a request workflow, participant finders and constraints. For information on how to debug with IdS-J, see the chapter "Using the Programming Environment" in this guide.