Transactions are triggered using PeopleCode within PeopleSoft and are written to transaction tables. If you want to allow processing by multiple drivers, you can categorize the processing of transactions by using a different driver subtype value.
The PeopleSoft administrator or consultant has the ability to trigger transactions under any circumstance associated with a pre-defined PeopleSoft process, or he or she can create transactions via a batch mechanism.
You can use the following information to create your own transaction triggers, also known as PeopleCode function calls:
A PeopleCode function call would be as follows:
DirXML_Trans(Transaction Table, Transaction Sub Type, Transaction Schema, Transaction Event, Transaction Association ID, Transaction Date Time, Transaction Value, Row Delete Field Name, Row Delete Field Key);
Using the above format and sample data, a real function call would look like this:
The name of the table where transactions are written to. This table is built within PeopleTools and the field elements should be consistent with the delivered DIRXML_TRANS01 table.
DIRXML_TRANS01
Transaction Sub Type
The name used to identify the type of transaction. The driver uses this parameter to process the types of transactions you specify.
NPSDriver1
Transaction Schema
The name of the Schema CI object that the transaction type is connected to. The driver uses the name of this object to query for the data connected to the transaction type.
DIRXML_SCHEMA01
Transaction Event
The type of XML event that is written to the transaction table. This can be 1 of 4 values as listed.
A=ADD
M=MODIFY
D=DELETE
R=ROW DELETE
Transaction Association ID
The identifier that is used to associate a particular record within PeopleSoft to an eDirectory object. It could be the EMPLID value for employees, STUDENTID value for students, DEPTID for departments, ACCTID for account codes, and so forth. Key elements must be identified for the Transaction Schema.
DIRXML_ASSOC_ID
Transaction Date Time
The date/time element used to determine when the transaction is processed.
%Datetime
Transaction Value
The parameter contains 1...n values that the developer wants to pass to the driver during processing. This value might not be available via the Schema object when a transaction is processed by the driver.
