Siebel Clinical Trial Management System Guide > Setting Up and Configuring Clinical Payments Integration > Process of Setting Up Clinical Payments Integration >

Configuring Siebel Tools for Clinical Payments Integration


This task describes how to create and configure Siebel Tools objects that are required for Siebel Clinical payments integration. The status value that triggers the workflow to send the payment request to the third-party application can be configured in Siebel Tools.

This task is a step in Process of Setting Up Clinical Payments Integration.

To configure Siebel Tools for clinical payments integration

  1. In Siebel Tools, lock the LS Clinical Payments project.
  2. Select Business Component Object type in the object explorer.
  3. Query for Clinical Payments.
  4. Select Business Component User property under Business Component in the object explorer.
  5. Create the user properties in the following table.
    Business Component User Property Name
    Value
    Description

    Named Method n

    "SendPayment", "INVOKESVC", "Clinical Payments", "Workflow Process Manager", "RunProcess", ' "ProcessName" ', ' "LS Clinical Payments Outbound" ', " 'Object Id' ", " [Id] "

    This property is used to configure the LS Clinical Payments Outbound workflow.

    On Field Update Invoke n

    "", "Clinical Payments", "SendPayment", "[Status] = LookupValue('FUNDRQ_STATUS','To Be Submitted') AND [Status] IS NOT NULL"

    This property sets the status trigger for the LS Clinical Payments Outbound workflow. By default, a status of To Be Submitted for a payment request triggers the LS Clinical Payments Outbound workflow to send the payment request to the third-party application.

    This property can be configured to use a different Status value to trigger the LS Clinical Payments Outbound workflow.

    Status Confirmation Popup 1

    "Status", "Waiting for Acknowledgement", "In Progress", "FUNDRQ_STATUS", "<optional custom status message>"

    This property adds In Progress to the values of the Status field for manual configuration.

    The <optional custom message> field can be customized to override the following default warning message:

    A payment request is in the process of being sent to the target system. Changing the status may lead to a duplicate payment request being sent in the future. Do you want to continue?

    Status Confirmation Popup 2

    "Status", "Waiting for Acknowledgement", "Withdraw", "FUNDRQ_STATUS", "<optional custom message>"

    This property adds Withdraw to the values of the Status field for manual configuration.

  6. Compile the locked and updated project.

    For information about compiling projects, see Developing and Deploying Siebel Business Applications.

Siebel Clinical Trial Management System Guide Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.