User exit samples configuration and deployment

The user exit samples provide reference code for implementing user-defined exits in the actions. Three types of overrides are created in this sample for reference.

Setup and configuration

The user exit samples use the following broker artifact.
  • FTM HVP User Exit Samples LIB
The user-defined properties (UDP) for this user exit sample are shown in the following table.
Table 1. User-defined properties
Property name Default value Description
UDP_IsfUpdatedInCache FALSE Indicates whether the user exit samples update the ISF.
UDP_Sender HVPBEF20XXX Specifies the value with which the user exit samples update the ISF, if UDP_IsfUpdatedInCache is TRUE.
UDP_RaiseTransactionInvalidEvent FALSE Indicates whether the user exit samples make the transaction invalid and raise an invalid transaction event.
UDP_SchemeOverride FALSE Indicates whether the user exit samples override the scheme.
UDP_Scheme Euro1 Specifies the scheme value to be updated if UDP_SchemeOverride is TRUE.
DB_SCHEMA FTM The name of the database schema.
LabelName UX_SEND_PAYMENT_TO_CSM Specifies the user exit name.

Deployment

The user exits have the following scenarios and steps to update the ISF, override the scheme, and raise a transaction invalid event.

To update the ISF, complete the following steps.
  1. Add the GenericUserExitSample.subflow from FTM HVP User Exit Samples LIB to EventProcessingWrapper.msgflow.
  2. Add the configuration for user exits. The key and value can be derived from the action for which the user exit is being configured. For more information, see User exits.
  3. Set the user-defined UDP_IsfUpdatedInCache property to TRUE, and set the UDP_Sender BIC value in the ISFMessage.Header.Sender field.
  4. Send an outgoing payment to a CSM message (for example pacs.008 or pacs.009) on the FXT.REQUEST.FROM.CHANNEL1 queue.
Completing the steps causes the sender BIC value to be updated while high value payment instructions are sent to CSM.
To override the scheme, complete the following steps.
  1. Add the GenericUserExitSample.subflow from FTM HVP User Exit Samples LIB to EventProcessingWrapper.msgflow.
  2. Add the configuration for user exits. The key and value can be derived from the action for which the user exit is being configured. For more information, see User exits.
  3. Set the user-defined UDP_SchemeOverride property to TRUE, and set UDP_Scheme to the values you want.
  4. Deploy the EventProcessingWrapper.msgflow.
  5. Send an outgoing payment to a CSM message (for example pacs.008 or pacs.009) on the FXT.REQUEST.FROM.CHANNEL1 queue.
Completing the steps causes the scheme value to be updated with the user exit overridden value.
To raise a transaction invalid event, complete the following steps.
  1. Add the GenericUserExitSample.subflow from FTM HVP User Exit Samples LIB to EventProcessingWrapper.msgflow.
  2. Add the configuration for user exits. The key and value can be derived from the action for which the user exit is being configured. For more information, see User exits.
  3. Set the user-defined UDP_RaiseTransactionInvalidEvent property to TRUE.
  4. Deploy the EventProcessingWrapper.msgflow.
  5. Send an outgoing payment to a CSM message (for example pacs.008 or pacs.009) on the FXT.REQUEST.FROM.CHANNEL1 queue.
Completing the steps causes the transaction to fail, and a negative acknowledgment is sent to the channel.