Understanding TREE_CHANGE Service Operations

Every time you perform an action in PeopleSoft Tree Manager to change a tree definition (such as delete, any kind of save, copy, branch, or unbranch), a TREE_CHANGE service operation is published based on the Tree Key information using the PSTREEPUBSUB record.

Note:

From PeopleTools 8.48, sending a TREE_CHANGE service operation every time tree changes are made is optional. To improve performance, you can select not to send a TREE_CHANGE service operation whenever you change a tree definition. The default setting is sending a TREE_CHANGE service operation. This service operation is not saved to the database.

If applications want to use TREE_CHANGE service operation, they must create a service operation handler. The service operation handler runs every time this service operation is published.

This example shows the TREE_CHANGE service operation.

Note:

The field EVENT_ID is defined in the Financials database as a Char,20 field, and is used by a number of applications. In PeopleTools PSTREEPUBSUB, the field was defined as a Number,6. To avoid conflicts, EVENT_ID has been removed from PSTREEPUBSUB and replaced with TREE_EVENT_ID.

This change may affect applications who subscribe to the TREE_CHANGE event, and check for EVENT_ID in PeopleCode using field name.