Code fragment UPoCs

These code fragment UPoCs work within the Code Fragment Interface.

This table shows the code fragment UPoCs:
UPoC Description
Xlate Action Pre-Processor This UPoC processes the source values before the translation action completes.

You can use this UPoC to choose a subset of source values based on a source value.

  • $xlateInVals and $xlateInTypes are the data fetched from the input list.
  • $xlateOutVals and $xlateOutTypes are initialized to $xlateInVals and $xlateInTypes respectively.
  • $xlateOutVals and $xlateOutTypes can be modified to determine what values are included in the main translation phase.

An error happens if $xlateOutVals does not exist at the end of the callout.

Xlate Action Body UPoC This UPoC is available only with the CALL translation action within a translation.
  • $xlateInVals and $xlateInTypes are the values entering this phase.
  • Modifying $xlateOutVals and $xlateOutTypes has no effect.
  • Because XPM does not perform implicit data store, use xpmstore.
  • $xlateOutList is for reference only.

This UPoC gives ultimate control over the translation, and defines special actions that are not intrinsically available in the translator.

Xlate Action Post-Processor This UPoC processes the destination values immediately after the translation action completes.
  • $xlateInVals and $xlateInTypes are the values of the actions’ destination objects after the main body.
  • There is no automatic storing of message elements. Therefore, modifying $xlateOutVals and $xlateOutTypes has no effect.