RiskMinder Java Developer's Guide › Before You Begin › Preparing Additional Inputs

Preparing Additional Inputs

In addition to the mandatory inputs, the Risk Evaluation API also accepts additional inputs in form of name-value pairs. These additional inputs are especially useful if you want to create custom rules and Evaluation Callouts. This is because any parameter can be added to this class and can be passed to the custom rules and Evaluation Callouts. These inputs can then be used for evaluating risk.

The input to this class can include information, such as locale, calling application details, or other transaction-related details that can be used for risk evaluation. These additional name-value custom parameters can help you capture the real-time inputs from each transaction, and are processed by deployed custom rules for successful risk evaluation.

RiskMinder’s com.arcot.riskfortAPI.AdditionalInputs package provides you the AdditionalInputs class, which enables you to set the additional information that you plan to use. Some of the pre-defined additional input parameters supported by the Risk Evaluation AdditionalInputs class include:

• AR_RF_LOCALE_ID

  Specifies the locale that RiskMinder will use while returning the messages back to your calling application.

• AR_RF_CALLER_ID

  Specifies the transaction identifier in your calling application. This is useful for end-to-end tracking of transactions.

To implement custom risk evaluation parameters:

1. Use the AdditionalInputs() method to obtain an object that implements the AdditionalInputs class.
2. Set the necessary inputs for the returned object by using the put() method. The syntax of the method is:

   public void put(java.lang.String name, java.lang.String value)

   If the additional input is not present with the given name (name of the input parameter), then one is created. Otherwise, it is overwritten with the new value (value of the input parameter). It is recommended that you do not use large strings either for name or for value.

   Note: The name and value parameters must not contain = and the newline character (\n). The API behavior is undefined if name and value contain any of these characters.