Data Director Implementation Guide

10.4 HotFix 1
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Configuring a User Exit

User exits are configured by subject area.

A subject area can have user exits defined for each of the user exit operations described earlier in this section.

<subjectArea name="Organization" displayName="Organization">
      <primaryObject hmEntityTypeUid="Organization">
         <subTypeQualifier columnUid="C_PARTY|PARTY_TYPE" filterValue="Organization"/>
         <layout columnsNum="3">
            <column columnUid="C_PARTY|ORGANIZATION_NAME" editStyle="FIELD" required="true"/>
            …
         </layout>
      </primaryObject>
      …
      <userExits className="com.siperian.bdd.userexits.sample.SaveHandler"/>
      <userExits className="com.siperian.bdd.userexits.sample.SendForApprovalHandler"/>
      <userExits className="com.siperian.bdd.userexits.sample.CustomActionProvider"     
         actionName="Custom User Exit"/>
   </subjectArea>

The following code snippet is an example of configuring ClassName for the HM Save Relationship User Exits in the IDDConfig.xml file.

<hmRelationshipTypes>
<hmRelationshipType hmRelationshipUid="HM_RELATIONSHIP_TYPE.contains member">
<layout columnsNum="2">
<column columnUid="C_RL_PARTY_GROUP|HUB_STATE_IND" editStyle="FIELD" horizontalStyle="MEDIUM"/>
</layout>
<userExit className="com.siperian.bdd.userexits.sample.HMRelationshipSaveHandler"/>
<userExit className="com.siperian.bdd.userexits.sample.HMRelationshipHandler"/>
</hmRelationshipType>
</hmRelationshipTypes>

Rename Saved Search

Table of Contents

Data Director Implementation Guide

Data Director Implementation Guide

Configuring a User Exit

Configuring a User Exit