Performing Pre-Processing and Post-Processing Tasks
This section discusses how to:
Set general pre-processing and post-processing options.
Code pre-processing and post-processing tasks.
Setting General Pre-Processing and Post-Processing Options
To perform pre-processing and post-processing tasks, you must select the appropriate Message Header or Message Trailer option on the Full Table Publish Rules page or on the Batch Publish Rules page.
To set general pre-processing and post-processing options:
Access the Full Table Publish Rules page or the Batch Publish Rules page.
To access the Full Table Publish Rules pages, select
.To access the Batch Publish Rules pages, select
.
In the Message Options section, select the appropriate options:
Message Header Select this option to perform pre-processing tasks on a service operation message.
Message Trailer Select this option to perform post-processing tasks on a service operation message.
Click the Save button.
Coding Pre-Processing and Post-Processing Tasks
The type of processing that you are performing determines the location in the message where you insert the pre-processing and post-processing logic.
Using PeopleSoft-Delivered Functions for Pre-Processing and Post-Processing
Consider using the following PeopleSoft-delivered functions in pre-processing logic:
Coding Pre-Processing and Post-Processing Tasks
The type of processing that you are performing, sequential or parallel, determines the location in the message where you insert pre-processing and post-processing logic.
The following code example shows sample pre-processing and post-processing code. Section numbers have been entered as remarks to show the location to insert code based on the processing that you are performing.
Processing |
Task |
Section |
---|---|---|
Parallel |
Pre-processing |
Section 1 |
Sequential |
Pre-processing |
Section 2 |
Sequential |
Post-processing |
Section 3 |
Parallel |
Post-processing |
Section 4 |
Important! If you change processing modes from sequential processing to parallel processing or vice versa, you must move any pre-processing and post-processing code to the appropriate section in the message, as described in the table.
If &ParallelFS Then ... If &Pre_Process_Flg = "Y" Then rem ****** Begin Pre-Processing Logic for parallel-enabled FullSync *****; Delete_Existing_Data(&MSG); /************************************************************************/ /* */ /* Section 1 */ /* */ /************************************************************************/ rem ****** End Pre-Processing Logic for parallel-enabled FullSync ******; End-If; End-If; &MSG_ROWSET = &MSG.GetRowset(); &MSG_LANG_CD = &MSG_ROWSET(1).PSCAMA.LANGUAGE_CD.Value; &MSG_BASE_LANG_CD = &MSG_ROWSET(1).PSCAMA.BASE_LANGUAGE_CD.Value; &FULL_INCR = "FULL"; Evaluate &MSG_ROWSET(1).PSCAMA.MSG_SEQ_FLG.Value When "H" If Not &ParallelFS Then rem ****** Begin Pre-Processing Logic for nonparallel-enabled FullSync ******; Delete_Existing_Data(&MSG); /*************************************************************************/ /* */ /* Section 2 */ /* */ /*************************************************************************/ rem ****** End Pre-Processing Logic for nonparallel-enabled FullSync ******; End-If; Break; When "T" If Not &ParallelFS Then /*************************************************************************/ /* */ /* Section 3 */ /* */ /*************************************************************************/ rem ** Insert Post-Processing Logic Here for nonparallel-enabled FullSync **; End-If; Break; When-Other Proc_Sub_Rowset(&MSG_ROWSET); rem ****** put additional process like editing here ********; If &ParallelFS Then ... If &Post_Process_Flg = "Y" Then /*************************************************************************/ /* */ /* Section 4 */ /* */ /*************************************************************************/ rem *** Insert Post-Processing Logic Here for parallel-enabled FullSync ***; End-If; ... Break; End-Evaluate;