5.1 Configuring the Application Level Parameters

Use the Application Level Parameter Configuration tab to configure the parameters for the Transaction Filtering application, such as enabling or disabling the four-eyes workflow, define the parameters that must be matched during the good guy workflow, enabling and disabling bulk action and select all option, define the cut-off time required to complete the entire transaction workflow, and assign messages manually or automatically.

To configure the parameters, follow these steps:

1. Navigate to the Financial Services Analytical Applications Transactions Filtering landing page.
2. Click Transaction Filtering Admin. The Application Level Parameter Configuration is displayed.

   Figure 5-1 Application Level Parameter Configuration Tab

   
   

   

   
   
3. In the Audit section, select Yes to view the Debug details or select No to view the Info details.
   If you select Yes, then all the steps are logged in the system irrespective of the value in the Sta- tus column. If you select No, then only those steps for which the value is Y in the Status column are logged in the system.

   Note:

   For more information on the values in the Status column, see System Audit Logging Information.
4. In the 4 Eyes section, select Yes to enable the four-eyes workflow and select No to disable the four-eyes workflow.

   Note:

   If the 4 Eyes workflow is enabled, then the new alert data should be posted to the UI to view the new options which are Message Statuses, Blocked Recommended and Released Recommended.
5. In the Select All option for the Events Table section select Yes to enable Select All option and select No to disable Select All option in Alert list details Event tab. For more information on alert details and event table, see Oracle Financial Services Transaction Filtering User Guide.
6. In the Bulk Action section select Yes to enable Bulk Action option and select No to disable the Bulk Action option in the Alert list page.
7. In the EDQ section, provide the following values:
   • EDQ URL in the following format:

     <http>: <Hostname of the server in which EDQ is installed>: Port Num- ber

   • EDQ user name: The default username is displayed. You can update the username if required.
   • EDQ password: The default password is displayed. You can update the password if required.
   • EDQ webservice status username
   • EDQ webservice status password
8. In the ECM L2 Analysis section, select Yes to enable and then provide the following values:
   • ECM L2 Case Creation URL in the following format:

     <http>: <Hostname of the server in which ECM is installed>: <Port Num- ber>/<Context>

   • ECM Case Creation user name: Enter the ECM username.
   • ECM Case Creation password: Enter the ECM password.
9. In the FEEDBACK section, enter the URL where we need to post messages for HOLD, RELEASE, CLEAN, BLOCK in the feedback queue in the FEEDBACK URL field.
10. Custom feedback configuration can be done in the tables for HOLD, CLEAN and AUTORELEASE status.

    We introduced the new table and created the new Post processing actions similar as from IPE screen from admin UI to the table. (FCC_TF_PP_ACTIONS).

    The table contains the post processing action code, code attributes, Query and text message. These configurations are editable like how we can in admin UI screen.

    After installing this patch the post processing actions from the new table will be considered for message posting.

    Once the message is processed, whether the Feedback is sent or not will be recorded in the table. (FCC_TF_RAW_FEEDBACK).

    This table contains group message id, feedback sent or not along with post processing action code.

    This table is useful in re-triggering the messages to send the feedback successfully for those feedback which are not sent.

11. Table contains the post processing action code, code attributes , Query and text message.
12. In the UI section, provide the time period after which the system refreshes the notification (false positive) count in the Transaction Filtering window.

    Note:

    • The time period is in milliseconds.
    • The notification count is reset to zero every day at midnight.
13. Click Save. The following confirmation message is displayed: Records Updated Successfully.