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

User Exit Operations

User exits have defined operations and entry points.

For each subject area, you can implement user exits to add custom functionality for the following operations:

Save

Send for Approval

Task Operations

Merge

Mark Not A Match

Custom Operations

HM Save Relationship

HM Custom Operations

Open

The following table describes the user exit entry points available for each operation. Save, Send for Approval, and Task Operations are variations on the process of saving changes to the subject area data view and provide the same set of entry points.

Operation	Entry Point	Description
Save, Send for Approval, Task Operations	beforeValidation	This entry point is no longer supported. Use the beforeEverything entry point instead.
	afterValidation	This entry point is no longer supported. Use the beforeEverything entry point instead.
	beforeEverything	Called before any processing is done. Use this to perform custom validation or augmentation of the data in the subject area. Informatica Data Director saves changes that the user exit makes to the data in the subject area. Can report Errors, Warnings, and Confirmations. Can set start and end dates for a period. Runs outside the save transaction.
	beforeSave	Called after the search for duplicates, just before performing the composite save. Use this to run custom business logic that augments the data in the subject area. Informatica Data Director saves changes that the user exit makes to data in the subject area. Can report Errors. Runs as part of the composite save transaction. SIF requests to the Operational Reference Store are part of this transaction.
	afterSave	Called after the subject area changes are saved. Use this to perform maintenance of data that is not part of the subject area. Can report Errors that roll back the transaction. Runs as part of the composite save transaction. SIF requests to the Operational Reference Store are part of this transaction.
	afterEverything	Called after the save transaction is committed. Use this to provide user notifications or perform maintenance of data that is not part of the subject area when the changes cannot be executed as part of the transaction. Can report Warnings. Runs outside the save transaction.
Merge	beforeEverything	Called before any processing is done. Use this to perform custom validation or augmentation of the data in the subject area. Can report Errors, Warnings, and Confirmations. Can set start and end dates for a period. Runs outside the save transaction.
	beforeMerge	Called just before the merge is performed. Use this to run custom business logic to provide error or confirmation messages. Can report Errors. Runs as part of the merge transaction. SIF requests to the Operational Reference Store are part of this transaction.
	afterMerge	Called after the merge operation has completed. Use this to perform maintenance for data that is not part of the subject area. Can report Errors that roll back the merge. Runs as part of the merge transaction. SIF requests to the Operational Reference Store are part of this transaction.
	afterEverything	Called after the merge transaction is committed. Use this to provide user notifications or perform maintenance of data that is not part of the subject area when the changes cannot be executed as part of the transaction. Can report Warnings. Runs outside the transaction.
Mark Not A Match	beforeEverything	Called before any processing is done. Use this to perform custom validation or augmentation of the data in the subject area. Can report Errors, Warnings, and Confirmations. Can set start and end dates for a period. Runs outside the save transaction.
	beforeMarkNotAMatch	Called just before the not a match is performed. Use this to run custom business logic to provide error or confirmation messages. Can report Errors. Runs as part of the not a match transaction. SIF requests to the Operational Reference Store are part of this transaction.
	afterMarkNotAMatch	Called after the not a match operation is completed. Use this to perform maintenance for data that is not part of the subject area. Can report Errors that will roll back the merge. Runs as part of the not a match transaction. SIF requests to the Operational Reference Store will be part of this transaction.
	afterEverything	Called after the not a match transaction has been committed. Use this to provide user notifications or perform maintenance of data that is not part of the subject area when the changes cannot be executed as part of the transaction. Can report Warnings. Runs outside the transaction.
User Operation	processOperation	Called when the Informatica Data Director user invokes the custom operation user exit from the More Actions menu in the data view. Use this to run custom business logic. The user exit can return Error or Warning messages. The data view is refreshed if this completes without error so that any changes to the subject area made by the user exit are reflected in Informatica Data Director.
HM Save Relationship	beforeEverything	Called before any processing is done. Use this to perform custom validation or augmentation of the relationship. Can report Errors, Warnings, and Confirmations. Can set start and end dates for a period. Runs outside the save transaction.
	afterValidation	Called after validation and cleanse function execution are performed. Use this to perform custom validation or augmentation of the relationship. Can report Errors, Warnings, and Confirmations. Runs outside the save transaction.
	beforeSave	Called just prior to performing the save. Use this to run custom business logic that augments the data associated with the relationship. Can report Errors. Runs as part of the save transaction. SIF requests to the Operational Reference Store are part of this transaction.
	afterSave	Called after the relationship changes are saved. Use this to perform maintenance of data associated with the relationship. Can report Errors which roll back the save. Runs as part of the save transaction. SIF requests to the Operational Reference Store are part of this transaction.
	afterEverything	Called after the save transaction is committed. Use this to provide user notifications or perform maintenance of data associated with the relationship when the changes cannot be executed as part of the transaction. Can report Warnings. Runs outside the save transaction.
HM User Operation	processOperation	Called when the Informatica Data Director user invokes the custom operation user exit from the More Actions menu in the data view. Use this to run custom business logic. The user exit can return Error or Warning messages. The user exit indicates which parts of the graph need to be refreshed as a result of the user exit operation.
Open	beforeOpen	Called before an open operation is performed. Use this to mark columns as read-only in edit mode and to overwrite column values. Can report errors, warnings, confirmations, and custom messages. Runs outside the open transaction
Open	afterOpen	Called after the open operation is completed. Use this to send various notifications to the data in the subject area. Also, you can use this for custom checking of the data that is loaded to the database. Can report errors, warnings, confirmations, and custom messages. Runs as part of the open transaction. SIF requests to the Operational Reference Store are part of this transaction.

Each user exit is supplied with the following data, which is described in detail in the Javadoc:

the subject area data that is being operated on

a SiperianClient object that can be used to perform SIF operations against the Operational Reference Store database, plus the Operational Reference Store ID and user credentials to use in SIF requests

Rename Saved Search

Table of Contents

Data Director Implementation Guide

Data Director Implementation Guide

User Exit Operations

User Exit Operations