Registering extensions

For the workflow to make the extension available with the extension node, it must first be registered in the IM_HOME/data/workflowextensions.xml file.

Each method requires an activity entry in the XML file. The activity entry includes these aspects:

Activity ID: An activity ID is required and must be unique in the workflow. This name is in the extension window activity type menu.
Implementation type: The implementation type contains the class name and the method name that is started by this extension.
Parameters sections: The parameters sections list the input and out parameters and their data types. These parameters are in the extension window Input/Out Parameters.
Transition restriction: The transition restriction defines the join type. Split type can also be defined. For more information, see the information in the extensions directory.

<ACTIVITY ACTIVITYID="SendMailByProperty" LIMIT="600000">
   <IMPLEMENTATION_TYPE>
<APPLICATION
      CLASS_NAME="com.ibm.itim.CustomWorkflowExtensions.CustomEmail"
      METHOD_NAME="sendMailByProperty"/>
   </IMPLEMENTATION_TYPE>
   <PARAMETERS>
<IN_PARAMETERS PARAM_ID="inperson" TYPE="Person"/>
<IN_PARAMETERS PARAM_ID="mailtag" TYPE="String"/>
<IN_PARAMETERS PARAM_ID="propertyfilename" TYPE="String"/>
<IN_PARAMETERS PARAM_ID="attributelist" TYPE="String"/>
   </PARAMETERS>
   <TRANSITION_RESTRICTION JOIN="XOR"/>
</ACTIVITY>

The Application Extension class file must be in a JAR file, which must be in the IBM Verify Identity Governance class path. After these changes are completed, you must restart the server before the extensions are available in the workflow.